Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1191572
| From | Willy Tarreau <w@1wt.eu> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH v3 2/3] x86/ldt: Make modify_ldt optional |
| Date | 2015-07-24 09:30 +0200 |
| Message-ID | <pPFAC-7kn-7@gated-at.bofh.it> (permalink) |
| References | (2 earlier) <pPlVf-3Ua-11@gated-at.bofh.it> <pPyfM-527-11@gated-at.bofh.it> <pPypr-5dm-3@gated-at.bofh.it> <pPyz7-5oO-5@gated-at.bofh.it> <pPyIN-5Po-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Thu, Jul 23, 2015 at 05:09:21PM -0700, Kees Cook wrote: > > All this to say that probably only a handful of tricky syscalls would > > need an on/off switch but clearly not all of them at all, so I'd rather > > add a few entries just for the relevant ones, mainly to fix compatibility > > issues and nothing more. Eg: what's the point of disabling exit(), wait(), > > kill(), fork() or getpid()... It would only increase the difficulty to > > sort out bug reports. > > > > Just my opinion, > > Well, I would really like to have something like this around so that I > can trivially globally disable syscalls when they have security risks. I understand, but while maybe it could make sense to have the option on any linux-specific syscall, having it on the standard, portable ones will be useless as disabling them will break most applications. > My hack[1] to disable kexec_load, for example, was terrible while I > waited for a kernel that supported the disable_kexec_load sysctl. This typically is one linux-specific syscall which no regular application would rely on and which can come with side effects. I think there are not *that* many, none of them is performance-critical, and they'd rather be dealt with one at a time. > [1] https://outflux.net/blog/archives/2013/12/10/live-patching-the-kernel/ Thanks, that (and the linked articles) was an interesting read. Willy -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: [PATCH v3 2/3] x86/ldt: Make modify_ldt optional Kees Cook <keescook@chromium.org> - 2015-07-24 01:40 +0200
Re: [PATCH v3 2/3] x86/ldt: Make modify_ldt optional Andy Lutomirski <luto@amacapital.net> - 2015-07-24 01:50 +0200
Re: [PATCH v3 2/3] x86/ldt: Make modify_ldt optional Willy Tarreau <w@1wt.eu> - 2015-07-24 02:00 +0200
Re: [PATCH v3 2/3] x86/ldt: Make modify_ldt optional Kees Cook <keescook@chromium.org> - 2015-07-24 02:10 +0200
Re: [PATCH v3 2/3] x86/ldt: Make modify_ldt optional Willy Tarreau <w@1wt.eu> - 2015-07-24 09:30 +0200
Re: [PATCH v3 2/3] x86/ldt: Make modify_ldt optional Willy Tarreau <w@1wt.eu> - 2015-07-24 09:50 +0200
csiph-web