full-disclosure - Re: 0day Vulnerability in VLC (this is my first release of the vuln anywhere)

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]

Date: Tue, 23 Apr 2013 12:13:13 -0400
From: Valdis.Kletnieks@...edu
To: Georgi Guninski <guninski@...inski.com>
Cc: full-disclosure@...ts.grok.org.uk, jay van <jay4sdata@...il.com>
Subject: Re: 0day Vulnerability in VLC (this is my first
	release of the vuln anywhere)

On Tue, 23 Apr 2013 17:51:55 +0300, Georgi Guninski said:
> Completely disagree.
>
> IMHO nobody should bother negotiating with terrorist vendors.
>
> Q: What responsibility vendors have?
> A: Zero. Check their disclaimers.

And disclaimer or no disclaimer, there's a lot of vendors who want to
Do The Right Thing and fix their stuff to protect their users (if for
no other reason than the possibility of lost customers if they ignore
security issues too often).

If you're a black hat, do whatever the heck you want.

If you're a white hat, be responsible and at least try to engage the
vendor.  If you're worried about being stiffed for the credit for the
find, write the advisory and post the MD5 hash somewhere before contacting
the vendor.  If they respond and work on the problem, the process works.
If they blow you off, go blackhat and do whatever the heck you want. :)

Now wasn't that easy? :)

Content of type "application/pgp-signature" skipped

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