Re: [Full-disclosure] Slander of security researcher n3td3v

2009-08-11 Thread John C. A. Bambenek, GCIH, CISSP
Winner! On 8/11/09, Michael Simpson wrote: > 2009/8/11 someone lawyer : >> List, >> >> Comment lead to the belief list wants to mock my client. >> >> some...@lawyer.com >> > > i pursue your case long time > > ___ > Full-Disclosure - We believe in it. >

Re: [Full-disclosure] Oh Yeah, botnet communications

2009-02-23 Thread John C. A. Bambenek, GCIH, CISSP
Yes, its possible, I mapped out something on a high level that would use rss/xml and would evade most detection methods on the network... Problem comes in is that stuff gets detected at infection-time and gets reverse engineered. Stealthy botnets is easy, stealthy infection is trickier. On 2/19/09

Re: [Full-disclosure] Administrivia: Spring Cleaning

2009-02-01 Thread John C. A. Bambenek, GCIH, CISSP
Looks like someone else is volunteering to join Andrew is F-D purgatory On 1/31/09, don bailey wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > valdis.kletni...@vt.edu wrote: >> On Sat, 31 Jan 2009 03:38:06 MST, don bailey said: >> >>> of noise. If this is allowed, it only proves that

Re: [Full-disclosure] DIE IN A FIRE post

2008-08-27 Thread John C. A. Bambenek, GCIH, CISSP
Sending a "die in a fire" response to a test message... On Wed, Aug 27, 2008 at 11:06 AM, Shirk Dog <[EMAIL PROTECTED]>wrote: > What can be more stupid then sending a TEST message to a mailing list. > > And if you are coming over, bring beer :) > > Shirkdog > ' or 1=1-- > http://www.shirkdog.us

Re: [Full-disclosure] Linus summarizes state of the "security industry" with precision and accuracy.

2008-08-18 Thread John C. A. Bambenek, GCIH, CISSP
Who's Linus? On Mon, Aug 18, 2008 at 3:50 PM, Simon Valiquette <[EMAIL PROTECTED]> wrote: > coderman un jour écrivit: > > ... hypothesis that "security researchers" are all masturbating monkey > > whores is now proven definitively. [0] > > > > """ > > Too often, so-called "security" is split into

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

2008-08-11 Thread John C. A. Bambenek, GCIH, CISSP
I haven't looked terribly closely but the cyber attacks don't seem to match up with what I would consider military objectives... there are plenty of nationalists that come crawling out of the woodwork during events like this. If the attacks are targetted more at military objectives then I'd say yo

Re: [Full-disclosure] [funsec] facebook messages worm

2008-08-06 Thread John C. A. Bambenek, GCIH, CISSP
What's the infection vector? URL Link? Rouge Facebook app? On Wed, Aug 6, 2008 at 4:44 PM, Gadi Evron <[EMAIL PROTECTED]> wrote: > Hi all. > > There's a facebook (possibly worm) something malicious sending fake > messages from real users (friends). > > The sample also has a remote drop site (ve

Re: [Full-disclosure] Geeks

2008-05-19 Thread John C. A. Bambenek, GCIH, CISSP
For the record, I got it because I got tired of HR guys asking me about security certifications just before deciding not to give me an interview. It's like a college degree... it's a piece of paper that is your entrance ticket. On Mon, May 19, 2008 at 9:25 PM, Daniel Marsh <[EMAIL PROTECTED]> wrot

Re: [Full-disclosure] Geeks

2008-05-14 Thread John C. A. Bambenek, GCIH, CISSP
on Apetit! > > > Professor Micheal Chatner > > > > Well, I see you've dropped the CISSP. I suppose that's progress. > > > > Paul Schmehl ([EMAIL PROTECTED]) > > Senior Information Security Analyst > > The University of Texas at Dallas >

Re: [Full-disclosure] HD Moore

2008-05-02 Thread John C. A. Bambenek, GCIH, CISSP
You wouldn't know whether n3td3v was worst or not if you just filtered the bastard and stop feeding the poor kid the attention he craves instead of the ritalin he needs. Just sayin'... On Fri, May 2, 2008 at 11:26 AM, Blaine Fleming <[EMAIL PROTECTED]> wrote: > Rob Thompson wrote: > > n3td3v - i

Re: [Full-disclosure] sans handler gives out n3td3v e-mail to public

2008-04-02 Thread John C. A. Bambenek, GCIH, CISSP
http://www.allfordmustangs.com/photopost/data/3243/Lambo-Doors-So-Played-Out.jpg That's all I got. On Wed, Apr 2, 2008 at 5:02 AM, Micheal Turner <[EMAIL PROTECTED]> wrote: > Once upon a time in toy town, I offered to contract > the services of a professional hit-man to have n3td3v > executed -

Re: [Full-disclosure] OpenID. The future of authentication on the web?

2008-03-24 Thread John C. A. Bambenek, GCIH, CISSP
When it comes to IT... the user is the *last* person I want empowered. On Mon, Mar 24, 2008 at 10:21 AM, Petko D. Petkov < [EMAIL PROTECTED]> wrote: > on your last comment, > > OpenID is exactly design for that! To give the power back to the user! > > On Mon, Mar 24, 2008 at 3:10 PM, Paul Schmehl

Re: [Full-disclosure] OpenID. The future of authentication on the web?

2008-03-24 Thread John C. A. Bambenek, GCIH, CISSP
s hard as keeping track of passwords. Put them all > together and then you will experience the pain. > > On the other hand OpenID provides you with a unique ID. Only you can > use it on every system without the need to worry. > > On Mon, Mar 24, 2008 at 3:22 PM, John C. A. Bamb

Re: [Full-disclosure] OpenID. The future of authentication on the web?

2008-03-24 Thread John C. A. Bambenek, GCIH, CISSP
; wrote: > what about usernames? you still need to keep track of your usernames > since sometimes your preferred username is either taken or not > possible or you need to login via email or any other peculiarity the > site supports. > > On Mon, Mar 24, 2008 at 2:43 PM, John C.

Re: [Full-disclosure] OpenID. The future of authentication on the web?

2008-03-24 Thread John C. A. Bambenek, GCIH, CISSP
For the automated low-hanging fruit attacks, they won't crack. They're simply trawling for passwords and rarely do they even think to cross-check. For someone to spend the kind of thought and attention the victim has to be specifically targetted. Now, to be fair, I only advocate that strategy for

Re: [Full-disclosure] OpenID. The future of authentication on the web?

2008-03-24 Thread John C. A. Bambenek, GCIH, CISSP
I would disagree. One could simply create a template password and then salt it with some acronym for the site in question. For instance, S0m3p4ss!### where ### is a 3-letter acronym for the site they are accessing. Still need only one password to remember and you don't necessarily have a single