| 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
| ||
|
From: lscharf at aoe.vt.edu (Luke Scharf) Subject: Re: Microsoft Security, baby steps ?[Scanned] [Scanned] [Scanned] On Thu, 2004-03-18 at 14:40, James P. Saveker wrote: > That's the *real* challenge of trying to secure a network - the vast gap > between what could be done given the proper mandate and financing, and what > you can usually actually deploy with the mandate and financing you actually > got. :) Plus, in the case of VT, many of the machines on campus are owned, for instance, by the students who use them. It's a little harder to impose something like a domain and SUS on them -- when it's their own machine. The current policy, AFAIK, is "if your machine does something bad, we'll turn off the network port and sort it out later." -Luke -- Luke Scharf, Systems Administrator Virginia Tech Aerospace and Ocean Engineering
Powered by blists - more mailing lists