Snort mailing list archives
Re: A case of beer on 63.204.135.168
From: "Ryan Lindsey" <rlindsey () austin rr com>
Date: Fri, 22 Feb 2002 18:23:13 -0600
I agree. Some of us aren't exactly the most knowledgable on computer security. That's why we are subscribed to this list. Yes, maybe this guy doesn't know what he is doing but who cares? What effect does it have on you? I have a WinXP box for video games and junk and it's probably wide open. If someone wants to hack my box and check out my counter-strike config, have at it. Like I have anything worth knowing about on my computer anyway. Maybe some good porn but that's about it. Anyway, sorry for the rant, but you shouldn't beat down on someone just because they don't know what they are doing, much less make it public. rbl ----- Original Message ----- From: "dr.kaos" <dr.kaos () kaos to> To: <jjennings () zoominternet net>; <snort-users () lists sourceforge net> Sent: Friday, February 22, 2002 5:14 PM Subject: Re: [Snort-users] A case of beer on 63.204.135.168
On Friday 22 February 2002 04:48 pm, Jeff Jennings wrote:This week's grand prize goes to 63.204.135.168 For allowing PUT rights on Port 80 (I wonder how many hackers are lurking here). Being vulnerable on Port 25 and many other ports... Anyone need an open relay?Ok, now, I don't mean to be a dick... but... Posting someone else's IP to the list, at least in my book, qualifies as
bad
practice. Granted, the guy's box may be insecure, but so are those of the majority of the Win box owners out there. Hell, for all we know, this list
is
subscribed to by countless lurking script-kiddies just _hoping_ someone
will
post info like this to the list. Let's all do the world a favor and help each other _improve_ the security
of
each other's networks. If you're really concerned, try to contact the owner of the box, or more easily, his ISP, and notify him/them of the problem. Posting his IP could be constitued as _part_ of the problem. In this case, I think I'll take a drink on your behalf as well... ;)No wonder the guy is spewing Code Reds... We just ran a port scan and tested the guy. Some guy running IIS over a DSL connection with a site that is listed as "Under Construction". Just another unsuspecting guy who installed IIS on his home computer and has no idea of how to protect it.Yeah, you're right, they represent the vast majority of the population,
but
let's educate them rather than humiliating them and making them more of a target than they likely already are. Again, I'm not trying to be mean, just wanna be helpful... ..[hiccup]... peace, ./dr.kaos _______________________________________________ Snort-users mailing list Snort-users () lists sourceforge net Go to this URL to change user options or unsubscribe: https://lists.sourceforge.net/lists/listinfo/snort-users Snort-users list archive: http://www.geocrawler.com/redir-sf.php3?list=snort-users
_______________________________________________ Snort-users mailing list Snort-users () lists sourceforge net Go to this URL to change user options or unsubscribe: https://lists.sourceforge.net/lists/listinfo/snort-users Snort-users list archive: http://www.geocrawler.com/redir-sf.php3?list=snort-users
Current thread:
- attack Scott Taylor (Feb 22)
- Re: attack Erek Adams (Feb 22)
- Re: attack Phil Wood (Feb 22)
- RE: attack Wayne Work (Feb 22)
- Re: attack Skip Carter (Feb 22)
- A case of beer on 63.204.135.168 Jeff Jennings (Feb 22)
- Re: A case of beer on 63.204.135.168 dr . kaos (Feb 22)
- Re: A case of beer on 63.204.135.168 John Sage (Feb 22)
- Re: A case of beer on 63.204.135.168 dr . kaos (Feb 22)
- Message not available
- Re: A case of beer on 63.204.135.168 John Sage (Feb 22)
- A case of beer on 63.204.135.168 Jeff Jennings (Feb 22)
- Re: A case of beer on 63.204.135.168 Ryan Lindsey (Feb 22)
- Re: A case of beer on 63.204.135.168 John Sage (Feb 22)
- Re: A case of beer on 63.204.135.168 spyguy703 (Feb 22)
- OT: A case of beer on 63.204.135.168 Chris Keladis (Feb 22)
- Re: attack Erek Adams (Feb 22)
- Re: A case of beer on 63.204.135.168 John Kiehnle (Feb 23)
- <Possible follow-ups>
- re: attack Glenn Forbes Fleming Larratt (Feb 22)
- RE: attack McCammon, Keith (Feb 22)
- Re: re: attack Scott Taylor (Feb 22)