Archives
Archives
| From: | "Javier Juan Martínez Cabezón" <tazok.id0@×××××.com> | ||
|---|---|---|---|
| To: | gentoo-hardened@l.g.o | ||
| Subject: | Re: [gentoo-hardened] Tool for eliminating non used code or symbols? | ||
| Date: | Mon, 25 Mar 2013 15:17:30 | ||
| Message-Id: | 51506ABF.1050106@gmail.com | ||
| In Reply to: | Re: [gentoo-hardened] Tool for eliminating non used code or symbols? by PaX Team |
||
| 1 | On 25/03/13 13:52, PaX Team wrote: |
| 2 | > On 25 Mar 2013 at 9:01, Kfir Lavi wrote: |
| 3 | > |
| 4 | >> Hi, |
| 5 | >> I'm looking for a way to reduce glibc code size. |
| 6 | >> It can be a way to make system smaller and minimize the impact |
| 7 | >> of attack vectors in glibc, as in return-to-libc attack. |
| 8 | > |
| 9 | > study this and draw your conclusions whether the whole exercise is |
| 10 | > worth it or not: |
| 11 | > |
| 12 | > https://www.usenix.org/conference/usenix-security-11/q-exploit-hardening-made-easy |
| 13 | > |
| 14 | > |
| 15 | |
| 16 | This paper seems interesting against Return oriented programming: |
| 17 | |
| 18 | http://www.cs.jhu.edu/~s/teaching/cs460/2012-fall/ROPdefender.pdf |