full-disclosure - M$ - so what should they do?

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>] [day] [month] [year] [list]

Message-ID: <A54506325BF6C74ABFBB7434F71661CFACB6C1@dnzakex1.datacom.co.nz>
From: StuartF at datacom.co.nz (Stuart Fox (DSL AK))
Subject: M$ - so what should they do? 

> > 
> > 	[SNIP}
> > 
> > >
> > > The second one, I concur completely, get the App stuff out of the 
> > > Windows folders.
> > >
> > 
> > Which includes IE.
> 
> Actually, just doing that one *alone* (splitting it out so it 
> isn't entwined into the OS) would probably do more than 
> anything else.  But we're not likely to see that happen, not 
> since the Microsoft witnesses swore on a Bible that IE was an 
> integral part of the OS....

But then of course if you look at it, it's just a set of com components
in a few dll's and iexplore.exe is just the glue that binds them all
together.  It actually probably wouldn't be that hard to remove IE from
the Windows folders - just move those dll's.  Of course, since there are
now so many MS applications that use those components for presentation,
you could argue they are an integral part of the OS (that just means
they should go into C:\program files\common files or somewhere like
that).