Re: [Full-disclosure] Facebook Attach EXE Vulnerability

The main thing is that the security division at facebook probably runs the bug hunting page (as with everywhere else, which does make a decent bit of sense). And, if you spot bugs before they do, then that looks bad on them (internally at the company and externally to the world). So, it is no

Re: [Full-disclosure] Filezilla's silent caching of user's credentials

The issue is that someone gained access to that file. You sharing your drives over the internet with read privileges? You have other vulnerable software being leveraged to read that file? Would you prefer they MD5'd it? It sounds like your issue is that your password is stored. I mean, they mo

Re: [Full-disclosure] Real Player 0day for WinXP

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 It's not a new vulnerability. It's just a new exploit. Quit bitching. webDEViL wrote: > I will leave that upto you to understand. > > > Sent from my iPhone > > On Jul 8, 2010, at 11:00 PM, Shreyas Zare wrote: > >> Hi, >> >> And how is this real pla

Re: [Full-disclosure] go public to avoid jail

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Way to over stretch what he was talking about. Stop trying to ban shit, you're not solving any problems. Didn't we already do the blacklist thing a hundred thousand times? Ed Carp wrote: > Oh, stop it. If you give your buddy a knife, knowing they'

Re: [Full-disclosure] Windows Vista/7 : SMB2.0 NEGOTIATE PROTOCOLREQUEST Remote B.S.O.D.

Nearly a year before release, of the new version (of the same thing). *sigh* - Original Message - From: James Matthews To: full-disclosure@lists.grok.org.uk Sent: Thursday, September 10, 2009 12:56 AM Subject: Re: [Full-disclosure] Windows Vista/7 : SMB2.0 NEGOTIATE PROTOCOLR

Re: [Full-disclosure] [funsec] Internet attacks against Georgian web s ites

Anybody making n3td3v stickers that read: "Somebody lied to him and Iraq happened."? I am buying, so long as n3td3v doesn't make them, or receive proceeds (of course). - mutiny n3td3v wrote: > On Mon, Sep 8, 2008 at 2:41 AM, Ureleet <[EMAIL PROTECTED]> wrote: >> d

Re: [Full-disclosure] New round of SSH scan IP's

Banned, along with you for not noticing that nobody gives fuck. James Lay wrote: > Fresh IP’s from when they started, about 2 hours ago. If you see one > that’s yours, something is amiss on your network. > > 117.21.127.181 > 12.107.136.162 > 12.206.87.124 > 12.26.44.155 > 12.47.156.114 > 121.119

Re: [Full-disclosure] Critical flaw rocks the internet

Details or shut the fuck up. Ivan . wrote: > http://www.smh.com.au/news/security/critical-flaw-rocks-the-internet/2008/07/09/1215282882891.html > > ___ > Full-Disclosure - We believe in it. > Charter: http://lists.grok.org.uk/full-disclosure-charter.html

Re: [Full-disclosure] [NANOG] IOS rootkits

Dumb and outlandish statements like these are why you are not responsible for any networks, outside your own (if even). n3td3v wrote: > On Wed, May 21, 2008 at 5:05 PM, mutiny <[EMAIL PROTECTED]> wrote: > >> A rootkit for Cisco will not damage anything, Cisco has even shown

Re: [Full-disclosure] [NANOG] IOS rootkits

Miss Wallace: Why does "n3td3v" hate network security enthusiasts? Why is "n3td3v" being so disruptive? A rootkit for Cisco will not damage anything, Cisco has even shown interest in the development. A rootkit for Cisco will cause Cisco to look into the issue more closely, which in turn will ma

Re: [Full-disclosure] Hey ISS/X-Force Dudez!!!!

Getting the fuck out of town for the weekend, enjoy. It's IBM ISS now. :-( Much lameness followed suit, a pay raise and a lot of lame. Thanks for "fully disclosing" your Friday night plans. --- Professor Micheal Chatner wrote: > I might be at the Masquerade in Atlanta tomorrow! I'l