full-disclosure - XP vs 2K

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <005801c4cb0a$a39307d0$6500a8c0@p41700>
From: chows at ozemail.com.au (Gregh)
Subject: XP vs 2K

----- Original Message ----- 
From: "Geo" <georger@....net>
To: <full-disclosure@...ts.netsys.com>
Sent: Monday, November 15, 2004 9:58 PM
Subject: Re: [Full-Disclosure] XP vs 2K


>> Curt, as XP can have its bells & whistles shut
>> down to perform as 2K can, your preference must
>> be security related.  Would you be spcefic, or
>> should I just read every advisory again?  This
>> perplexes me as M$ at least eventually patch XP
>> while 2K is entering its next life.
> 
> You don't have to be security oriented to not want XP in the workplace.
> There are plenty of other reasons. Install XP to someplace other than C: and
> the default directory name, delete boot.ini then try and recover using the
> Cd if you want to experience but one of them.. (you'll have to try the same
> thing with W2K to understand the full meaning of what I'm describing)
> 

I'd like to know what it is you mean to be honest. Never had to do that with W2K before but wiped XP off C and reinstalled the same image of C as G before. Then had to run a repair install directly after that. Never a problem that wasn't fixed by altering card entries in registry or easier - updating to the next SP.

Greg.