full-disclosure - Re: Hikaru

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <4ef5fec60712211817x33f3694bse4ae2c5a7e0ac4c3@mail.gmail.com>
Date: Fri, 21 Dec 2007 18:17:34 -0800
From: coderman <coderman@...il.com>
To: Ben <comsatcat@...thlink.net>
Cc: full-disclosure@...ts.grok.org.uk
Subject: Re: Hikaru

On Dec 21, 2007 5:36 PM, Ben <comsatcat@...thlink.net> wrote:
> All,
>
> I read a paper last night titled "The Geometry of Innocent Flesh on the Bone" (http://www.cse.ucsd.edu/~hovav/).  It described a technique similar to return-into-libc.

yes, this is fun stuff :)

'''
Our thesis: In any suﬃciently large body of x86 executable code there
will exist suﬃciently
many useful code sequences that an attacker who controls the stack
will be able, by means
of the return-into-libc techniques we introduce, to cause the
exploited program to undertake
arbitrary computation.
'''

10 pts to the first person using this approach to dlopen for full
arbitrary execution :)

so which is more useful in practice, NX or ASLR?
_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/