-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
let's go there anyway, and if hd moore doesn't comply, we can just
slap some sort of law on the license to make it against the law
not to
require that downloaders have the license.
While we are at it, why don't we just impose government
restrictions
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
There's been some buzz about a new bug within the TCP/IP-protocol.
According to the people who discovered it, it affects some if not
all
OSes. They explain it a little bit in an interview (URL below)
without
telling any details.
Fyodor released some
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, 20 Sep 2008 09:38:20 -0400 n3td3v [EMAIL PROTECTED]
wrote:
This service allows a legitimate user to observe the last 5
sessions
of which users logged in to the account, this is known as the
'Last
account activity' feature.
Uh, so what?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 15 Sep 2008 03:09:12 -0400 n3td3v [EMAIL PROTECTED]
wrote:
n3td3v is outspoken but hes not a troll. he is a serious security
researcher with his own mailing list.
There is a difference between being outspoken and making dumb
comments no one
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 03 Sep 2008 14:47:22 -0400 n3td3v [EMAIL PROTECTED]
wrote:
On Wed, Sep 3, 2008 at 5:06 PM, [EMAIL PROTECTED] wrote:
I'd place bets that whoever it is, they're on the RBN payroll...
I thought a high ranking security professional like
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Even though I had the vulnerability 4 hrs well before the real
publication of the bug and had the exploit along with the some
crash details like int 3 Kernel Exception/Trap @ 0x01002FF3,
different attack cases, exceptions of http/ftp and further
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
My judgment is telling me to just ignore this, but I'll entertain
it with one response.
On Wed, 03 Sep 2008 20:04:34 -0400 Shyaam [EMAIL PROTECTED] wrote:
This is a healthy discussion. This topic leads to a very good
question. When
do we call a bug
