<br>
<div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">From: n3td3v <<a href="mailto:xploitable@gmail.com">xploitable@gmail.com</a>><br>
Subject: [Full-disclosure] TippingPoint don't "Get it"<br>To: <a href="mailto:full-disclosure@lists.grok.org.uk">full-disclosure@lists.grok.org.uk</a><br>Message-ID:<br> <<a href="mailto:4b6ee9310609011156k38e5aad8i47c8b0d83a008119@mail.gmail.com">
4b6ee9310609011156k38e5aad8i47c8b0d83a008119@mail.gmail.com</a>><br>Content-Type: text/plain; charset=ISO-8859-1; format=flowed<br><br>Hackers for years, including my hackers have been trying to do what TP<br>is doing. If folks from TP/3Com read Full-Disclosure list they'll know
<br>even with "Full Disclosure" you cannot change companies to "fast up<br>their security response". It is neat that the folks at TP/3Com are<br>trying half disclosure tactics, but if agressive folks like you and me
<br>can't change the bug priorty of high profile vendors, then its<br>unlikely a "reduced disclosure" policy on the TP/3Com sight is going<br>to turn heads. 3Com if they "really" want to get vendors to fix TP
<br>reported bugs is to mail those disclosure not only to the TP/3Com site<br>but to the wider security community via mailing lists.<br><br>Link 1: <a href="http://news.com.com/2061-10789_3-6111474.html">http://news.com.com/2061-10789_3-6111474.html
</a></blockquote><div><br>
Hey.. You killed Jeb!! Not nice :( <br>
</div><br>
</div><br>