| 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
| ||
|
Message-ID: <402BD80A.2080400@umn.edu> From: eckman at umn.edu (Brian Eckman) Subject: Re: Re: <to various comments>EEYE: Microsoft ASN.1 ... Drew Copley wrote: <mass snippage> > But, it turns out, that the guys > who can write exploit code also can reverse engineer patches... </mass snippage> You said it all in that sentence. No other commentary was necesary to make your point. Besides reading exploit code (if such code were released, which it was not), I'd imagine (as you mention) reverse engineering the patch and/or sniffing the network traffic of your (or another) scanner in action would be much more productive methods of determining how to write an exploit than your advisory was. Brian -- Brian Eckman Security Analyst OIT Security and Assurance University of Minnesota "There are 10 types of people in this world. Those who understand binary and those who don't."
Powered by blists - more mailing lists