full-disclosure - DCOM RPC exploit (dcom.c)

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: <3F25000B.28600.11D3CFC2@localhost>
From: nick at virus-l.demon.co.uk (Nick FitzGerald)
Subject: DCOM RPC exploit  (dcom.c)

tcpdumb <tcpdumb@...bytes.org> wrote:

> Well that's not entirely accurate. At least RaMeN had some nice features
> such as fixing the security hole it used to gain access to the vulnerable
> Host. ;) (Even if it's just a feature to prevent multiple attacks, it's
> basically a good idea)

Could you please explain in some detail how something that is both 
unethical, at least under all professional computing "codes of conduct" 
and/or "ethical codes" I know of and under the personal ethics of most 
"security professionals" (altering the contents of a computer one does 
not have suitable authority to alter in that way), and illegal in most 
countries ("computer [data] tampering" or similar) is a "good idea"?

Regards,

Nick FitzGerald