Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1512898
| From | Daniel Micay <danielmicay@gmail.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [kernel-hardening] Re: [PATCH] fork: make whole stack_canary random |
| Date | 2016-10-31 22:10 +0100 |
| Message-ID | <sys09-7Ib-1@gated-at.bofh.it> (permalink) |
| References | <sylrH-3r1-9@gated-at.bofh.it> <synjQ-4H2-31@gated-at.bofh.it> <synDb-4Pf-9@gated-at.bofh.it> <syrGN-7md-15@gated-at.bofh.it> <syrQt-7pC-19@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
> It makes a lot of sense on x86_64 where it means the canary is still > 56 > bits. Also, you want -fstack-check for protecting again stack > overflows > rather than stack *buffer* overflow. SSP won't really help you in that > regard. Sadly, while -fstack-check now works well in GCC 6 with little > performance cost, it's not really a complete feature (and Clang impls > it > as a no-op!). Note: talking about userspace after the entropy bit. The kernel doesn't really -fstack-check, at least in even slightly sane code...
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH] fork: make whole stack_canary random Jann Horn <jann@thejh.net> - 2016-10-31 15:10 +0100
Re: [PATCH] fork: make whole stack_canary random Kees Cook <keescook@chromium.org> - 2016-10-31 17:10 +0100
Re: [kernel-hardening] Re: [PATCH] fork: make whole stack_canary random Jann Horn <jann@thejh.net> - 2016-10-31 17:30 +0100
Re: [kernel-hardening] Re: [PATCH] fork: make whole stack_canary random Florian Weimer <fw@deneb.enyo.de> - 2016-10-31 21:50 +0100
Re: [kernel-hardening] Re: [PATCH] fork: make whole stack_canary random Jann Horn <jann@thejh.net> - 2016-10-31 22:00 +0100
Re: [kernel-hardening] Re: [PATCH] fork: make whole stack_canary random Daniel Micay <danielmicay@gmail.com> - 2016-10-31 22:00 +0100
Re: [kernel-hardening] Re: [PATCH] fork: make whole stack_canary random Daniel Micay <danielmicay@gmail.com> - 2016-10-31 22:10 +0100
Re: [kernel-hardening] Re: [PATCH] fork: make whole stack_canary random Florian Weimer <fw@deneb.enyo.de> - 2016-10-31 22:20 +0100
Re: [kernel-hardening] Re: [PATCH] fork: make whole stack_canary random Jann Horn <jann@thejh.net> - 2016-10-31 22:30 +0100
Re: [kernel-hardening] Re: [PATCH] fork: make whole stack_canary random Florian Weimer <fw@deneb.enyo.de> - 2016-10-31 22:30 +0100
Re: [kernel-hardening] Re: [PATCH] fork: make whole stack_canary random Daniel Micay <danielmicay@gmail.com> - 2016-10-31 22:30 +0100
Re: [kernel-hardening] Re: [PATCH] fork: make whole stack_canary random Daniel Micay <danielmicay@gmail.com> - 2016-10-31 22:30 +0100
Re: [kernel-hardening] Re: [PATCH] fork: make whole stack_canary random Florian Weimer <fw@deneb.enyo.de> - 2016-10-31 22:40 +0100
Re: [kernel-hardening] Re: [PATCH] fork: make whole stack_canary random Daniel Micay <danielmicay@gmail.com> - 2016-10-31 23:10 +0100
Re: [kernel-hardening] Re: [PATCH] fork: make whole stack_canary random Florian Weimer <fw@deneb.enyo.de> - 2016-10-31 23:20 +0100
csiph-web