Re: Viruses and hackers make Windows more secure - Gates

From: Dazz (cashdj_at_hotmail.com)
Date: 01/31/04


Date: Sat, 31 Jan 2004 23:02:46 +1000

On Sat, 31 Jan 2004 09:24:36 GMT, Iceman <1c3m4n@chi-mafia.org> wrote:

<snipped>

>> I'd like you to cite some references. It is not in a virus'/worm's best
>> interests to kill its host computer.
>>
>Its pretty well known, and you may specifically want to bring down a server
>or crash multiple systems.

Are you trying to say that computer worms are meant specifically to
bring down their host?

lol, you just don't have a clue, do you.

Worms generally don't kill their host, however, in recent times, they
have been used to help launch DoS's against various targets, such as
M$ or SCO. But this is still not their host, it's merely a target of
their payload.

Viruses on the other hand, may be specifically written to kill their
host (sometimes they kill their hosts because of bad programming), but
not all viruses are intended to kill their host.

Ever heard of macro viruses? How many of them kill their host?

Once again, you post a complete load of bollocks.

<snipped>

>> http://www.sophos.com/pressoffice/pressrel/au/20031204yeartopten.html
>>
>
>Your point? If you read what I wrote then you wouldn't have to have written
>this crap. Sure it was a focus, for years it could not be breached, little
>knowledge. If you had any freaking idea of what went on they you would know
>that one of the first that worked was done by hacking Unix servers so they
>could have they had a large platform from which to work in order to get
>into NT. Get it? Unix was broken into to get to NT. None of the viruses you

lol. "Unix was broken into to get to NT." What a load of bullshit.

Did you pull that out of your ass? Are you talking about a specific
case?

Unix was around and getting hacked/cracked before NT was even thought
of.

Unix was not broken to get into NT, Unix was broken into because it
was a target, and because it could be done.

The same can be said for NT based systems (or any system for that
matter).

But please, if you have information to the contrary, please post it.
I'm sure we can all do with a good laugh (apart from reading your
insane, inept and incompetent posts).

You and Tracker would make a good team - perhaps you should write a
book together?

>mentioned ever hit my systems. Plus without a little investigation I will
>not take your word that all of those messed with NT. I do recognize many of
>them from infected 9x computers that I have cleaned up for others, as well
>as cleaning them out of email messages on servers.

It's funny, but I just had to look at the nick of the person I'm
replying to, because I was sure this was tracker (well, it makes about
as much sense as one of her posts).

So, you don't believe that the aforementioned viruses/worms affected
NT?

Hmmm, it's obvious that you just don't have a clue about what you
speak. But, just for you, I'm going to break it down.

1. W32/Sobig-F - systems affected: Windows 2000, Windows 95, Windows
98, Windows Me, Windows NT, Windows XP

2. W32/Blaster-A - systems affected: Windows 2000, Windows NT,
Windows Server 2003, Windows XP

3. W32/Nachi-A - systems affected: Microsoft IIS, Windows 2000,
Windows XP

4. W32/Gibe-F - systems affected: Windows 2000, Windows 95, Windows
98, Windows Me, Windows NT, Windows Server 2003, Windows XP

5. W32/Dumaru-A - systems affected: Windows 2000, Windows 95, Windows
98, Windows Me, Windows NT, Windows XP

6. W32/Sober-A - systems affected: Windows 2000, Windows 95, Windows
98, Windows Me, Windows NT, Windows Server 2003, Windows XP

7. W32/Mimail-A - systems affected: Windows 95, Windows 98, Windows
NT, Windows 2000, Windows XP, Windows Me

8. W32/Bugbear-B - systems affected: Windows 95, Windows 98, Windows
NT, Windows 2000, Windows XP, Windows Me

9. W32/Sobig-E - systems affected: Windows 95, Windows 98, Windows
NT, Windows 2000, Windows XP, Windows Me

10.W32/Klez-H - systems affected: Windows 95, Windows 98, Windows NT,
Windows 2000, Windows XP, Windows Me

Quite simply, all of these viruses/worms have infected NT and NT based
systems.

If you don't believe me, take a look at any anti-virus site.

For you not to know this shows how little you keep up to date with
what's happening.

<snipped>

>The bulk of peeps on the Usenet are not admin's. They are a bunch of low
>lifes who go about touting shit they do no understand. In one breath they

lol, that's the most apt self description I've ever heard from anyone.

The simple fact that you didn't recognise that the above listed
viruses/worms do infect NT based systems, doesn't speak much for your
knowledge of systems and their security.

>speak of the "unstoppable" power of their OS, in a few messages later they
>cry because their systems lock up, crash or whatever and cannot figure out
>why. The ridiculous nature of their behaviors is laughable. The rabid anti
>MS attitudes blinds them to anything honest. Other ignorant peeps follow
>them into thinking how secure their Linux system is, "inherently so" yet I
>can walk right in using well known slpoits if I chose to do so.
>
>Therefore I laugh and mock them for they are every bit as culpable as the
>Windows lAAmers. PKB? One cannot be complacent with *any* OS.

So very true.

<snipped>

>Yeah right, minutes? LOL! I s'pose 50,224 minutes could constitute minutes.
>LMAO. It's crap statements like that which blow your credibility and other
>users of your ilk.

Interesting. Another opinon that you're trying to pass of as a
statement.

But please enlighten us, where did you pull the 50,224 minutes from?

Your arse?

<snipped>

>I can tell you with certainty that most of the peeps in linux ng's are not
>admins, nor intelligent. They talk the talk without knowledge and spread a

The same can be said for any newsgroup. Didn't you know? Everyone on
usenet is an expert.

<snipped>

>Same thing with Linux or any OS for that matter. With SP2 for XP, if they
>stay the course, XP when updated will be locked down, "breaking" many
>things peeps do, "forcing" them to learn, though many will strictly learn
>how to re-enable the soft spots without regards to what they are doing.

This is the best thing M$ have done in years, however, until SP2 does
get released, I'm not going to congratulate M$.

I'll believe it when I see it - but I hope they do.

Dazz



Relevant Pages

  • Re: someone knows if time.windows.com permanent down?
    ... I can't synchronize since 4 days with this server and I have no idea ... when windows synchronize the time with this server successfully last ... from using their overtaxed NTP server so I didn't go there. ... necessarily mean their host is down or unreachable. ...
    (microsoft.public.windows.vista.general)
  • Re: Web Server on XP Pro
    ... the Windows XP into the domain. ... features of the server versions. ... I wonder why you would host the web site on a Windows XP Pro ...
    (microsoft.public.windows.server.sbs)
  • Re: Syncing Server Time
    ... > We have multiple HP-UX 10.20 servers running on an Windows NT domain. ... > date/time on each server. ... Sounds like poor design, what happens if this host gets the wrong time, ... I assume NTP software for NT is also available. ...
    (comp.sys.hp.hpux)
  • Re: Help: Host files for different user profiles?
    ... am using Windows 2003 Server and not XP. ... The problem is that the paired machine has is serving up web pages with image ... single windows server installation to accomplish this. ... We are trying to set up a Windows XP server and host through a screen ...
    (microsoft.public.windowsxp.network_web)
  • Re: SBS 2008 VPN and Windows 7
    ... Windows Server Networking User Assistance ... Windows Small Business Server 2008 Unleashed ... Today he mentioned that he cannot resolve host names over the VPN. ... The VPN connection on the Windows 7 machine seems to be getting its DNS ...
    (microsoft.public.windows.server.sbs)