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]
From: mvp at joeware.net (joe)
Subject: RE: MS should re-write code with security in mind. lame bitching about xpsp2

I think you meant your first line to be

"All OS vendors should bite the bullet and re-write their code with security
in mind."

Not sure why you singled MS out for that statement. Especially considering
the rest of the post. 

  joe


-----Original Message-----
From: full-disclosure-admin@...ts.netsys.com
[mailto:full-disclosure-admin@...ts.netsys.com] On Behalf Of Clairmont, Jan
M
Sent: Wednesday, August 18, 2004 11:52 AM
To: full-disclosure@...ts.netsys.com
Subject: [Full-Disclosure] RE: [Full-Disclosure]MS should re-write code with
security in mind. lame bitching about xpsp2

M$ should just bite the bullet and re-write windows with security in mind,
give it a true process scheduler, multiuser
with windows as a client server processes.  Build in 256 bit encryption and
secure communications between processes and external communication with no
unencrypted traffic.  That would shut down a lot of these mindless bugs.
All mail should be encrypted and point-to-point, with the mail servers only
able to re-direct and broadcast mail with authentication.   Maybe we could
slow a lot of  the hacking down  and spam.  But again until the market place
demands it M$, Linux and everybody else it's business as usual.

Keeps us employed I guess.

Jan Clairmont
Firewall Administrator/Consultant



Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ