Re: [Declude.Virus] Sobig- Phase II bombardment

2003-08-22 Thread Jim Matuska
ECTED] - Original Message - From: "John Tolmachoff (Lists)" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, August 22, 2003 1:58 PM Subject: RE: [Declude.Virus] Sobig- Phase II bombardment > Any one seeing hearing of any happenings on this? > > John Tolmac

RE: [Declude.Virus] Sobig- Phase II bombardment

2003-08-22 Thread R. Scott Perry
Any one seeing hearing of any happenings on this? F-Secure has reported that 1 of the 20 servers appears to be up, but it is so overwhelmed that viruses aren't getting anything from it. But that does mean that some could be getting through. All we've seen is what seems to be a precautionary me

RE: [Declude.Virus] Sobig- Phase II bombardment

2003-08-22 Thread John Tolmachoff \(Lists\)
Any one seeing hearing of any happenings on this? John Tolmachoff MCSE CSSA Engineer/Consultant eServices For You www.eservicesforyou.com --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.Virus mailing list. To unsubscribe

Re: [Declude.Virus] Sobig- Phase II bombardment

2003-08-22 Thread andyb
If it was easy, and if every computer user was computer literate and responsible, we wouldn't have jobs... Andy - Original Message - From: "Markus Gufler" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, August 22, 2003 3:17 PM Subject: RE: [Dec

RE: [Declude.Virus] Sobig- Phase II bombardment

2003-08-22 Thread Mark Smith
> What they (M$) really need to do, is make windows update > integrated into Windows, the problem is they tell you "Stay > current with updates" in a little box above the taskbar when There are huge debates about this. It's amazing that people are against this. Look at the newsgroups, etc...

Re: [Declude.Virus] Sobig- Phase II bombardment

2003-08-22 Thread paul
>It make's me really wonder how many stupid people is not able to patch > the own system (or at least outlook). Exactly! > they can't do more. (except write a worm that install automatically all available patches from MS) What they (M$) really need to do, is make windows update integrated into W

Re: [Declude.Virus] Sobig- Phase II bombardment

2003-08-22 Thread Bill Landry
> To: <[EMAIL PROTECTED]> Sent: Friday, August 22, 2003 10:33 AM Subject: RE: [Declude.Virus] Sobig- Phase II bombardment > > > > >It would seem to me that someone's decoded this encrypted list and if we > >knew what it was we could setup access lists to block

RE: [Declude.Virus] Sobig- Phase II bombardment

2003-08-22 Thread Markus Gufler
> Sobig.G will have a line "X-MailScanner: The Sobig.G virus is in the > attachment, you will be infected if you open it"... and > Sobig.G will spread just as fast as Sobig.F. It make's me really wonder how many stupid people is not able to patch the own system (or at least outlook). I swear

RE: [Declude.Virus] Sobig- Phase II bombardment

2003-08-22 Thread Avolve Support
3414 x20 (Business) >Fax:+1 201 934-9206 > >http://www.HM-Software.com/ > > >-Original Message- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] On Behalf Of Mark Smith >Sent: Friday, August 22, 2003 01:23 PM >To: [EMAIL PROTECTED] >Subject: RE: [Decl

RE: [Declude.Virus] Sobig- Phase II bombardment

2003-08-22 Thread Fritz Squib
See http://isc.sans.org/diary.html?date=2003-08-22 Sobig Update Cycle SoBig-F, the most recent incarnation in the family of Sobig mass mailing viruses, will be entering its update cycle today at 19:00 UTC. Between 19:00 and 22:00 UTC, the virus will attempt to contact a predefined set of hosts t

RE: [Declude.Virus] Sobig- Phase II bombardment

2003-08-22 Thread John Tolmachoff \(Lists\)
According to this NBC news report, it will occur every Friday and Sunday. http://www.nbc4.tv/technology/2426381/detail.html?treets=la&tml=la_natlbreak &ts=T&tmi=la_natlbreak_15913_01270008222003 John Tolmachoff MCSE CSSA Engineer/Consultant eServices For You www.eservicesforyou.com

RE: [Declude.Virus] Sobig- Phase II bombardment

2003-08-22 Thread R. Scott Perry
No only that - but what's this "web address" that will be updated. If it's an IP - then it should be easy to contact the upstream provider. If it's a FQDN - then it should be easy for the registrar to "lock" this particular domain against updates I don't see why this is supposedly so difficult t