full-disclosure - Re: Obfuscated patches

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] [thread-next>] [day] [month] [year] [list]

Date: Tue, 21 Apr 2009 12:01:02 +0100
From: Pedro <fractalg@...hspeedweb.net>
To: <full-disclosure@...ts.grok.org.uk>
Subject: Re: Obfuscated patches

Hello,

If it's a patch why do you need to obfuscate ? Patch the binary and bindiff
it :)

If you are talking about starting to obfuscate the resulting binaries,
that's a dark way to go... Waste of cpu cycles, compatibility problems, etc
etc etc...

Pedro

On 4/21/09 11:08, "Dennis Yurichev" <dennis@...us.info> wrote:

> Hi.
> 
> Just curious: will we see one day obfuscated patches
> (in a manner of obfuscated code) to make reverse engineer's
> (who would like to create exploits after security patches out)
> work harder?
> 

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/