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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
From: vosipov at (V.O.)
Subject: IDS (ISS) and reverse engineering

Recently I've got to listen to a marketing pitch by an ISS guy. He was going
along the lines of "our X-force reverse-engineered Microsoft RPC libraries
and created signatures..." and "we use protocol decoding, so we
reverse-engineered various closed-source protocols in order to create out

What struck me - isn't this kind of activity actually illegal in the US? To
which extent it is possible to disassemble Windows code? And if it is
illegal, then aren't their customers (plus many other IDSes, with the
exclusion of Snort, probably) in danger - what if Microsoft or whoever else
sues ISS for doing this? :)

I'm puzzled.

Powered by blists - more mailing lists