full-disclosure - [Secure Network Operations, Inc.] FullDisclosure != Exploit Release

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]

From: Ken at infosec101.org (Ken Pfeil)
Subject: [Secure Network Operations, Inc.] FullDisclosure != Exploit Release

<*sigh*>..(Help me Jeebus...)
Did you bother to think *at all* before spewing this out, or are you
trolling?
OK, I've got 2 minutes free, I'm game..

> -----Original Message-----
> From: full-disclosure-admin@...ts.netsys.com
> [mailto:full-disclosure-admin@...ts.netsys.com]On Behalf Of Giri,
> Sandeep
> Sent: Wednesday, January 29, 2003 3:00 PM
> To: 'full-disclosure@...ts.netsys.com'
> Subject: RE: RE : RE : [Full-Disclosure] [Secure Network Operations,
> Inc.] FullDisclosure != Exploit Release
>
>
> Hi!
> From a security professional's point of view, releasing an exploit is
> beneficial.

I guess you're the "professional", or are you expressing someone else's
viewpoint?

> If he releases exploit someone would certainly write a virus for the same.
> Which will make companies realise the benefit in hiring the security
> professionals.

I'd frame this little number if I were you. It'll make dandy literature for
a potential client, maybe circulate it with your resume?
>
> So, from my point of view, writing viruses which doesn't
> physically destroy
> any thing is also okay;)

Care to clarify this? So I guess a POC fer turning people inside-out ain't
gonna fly in your book, huh? It's good to have scruples.

>
> Sorry, if it hurts the ethics..and if it sends wrong singnals
> about my area
> of work.

Yeah, I can see this making into the CISSP ethics clause now <hehe>.

>
> Thanks.
> Regards,
> Sandeep Giri
>
>
<snip>