full-disclosure - Re: A modest proposal

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <CAG5KPzzVYUHGZYe9PV_SfqN=-WdCWE3PQSTjbJH-70igNUH3tA@mail.gmail.com>
Date: Fri, 20 Jul 2012 09:20:17 +0100
From: Ben Laurie <ben@...ks.org>
To: Glenn and Mary Everhart <everhart@....com>
Cc: full-disclosure@...ts.grok.org.uk
Subject: Re: A modest proposal

On Fri, Jul 20, 2012 at 2:08 AM, Glenn and Mary Everhart
<everhart@....com> wrote:
> Hello, FD...
> A thought occurred to me:
> Why not use the same kind of polymorphism and software metamorphism that
> is used by malware writers as a protective measure?
>
> If you have a piece of code that you don't want malware to be able to
> inspect, that might perhaps
> have some "secrets" in it or that you want not to be trivial to have
> some other code patch,
> why not arrange for that code to be different in form (but the same in
> function) with every copy?

http://www.ics.uci.edu/~franz/ has DARPA money to do just that. Not
convinced its a great idea myself.

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