🚀 go-pugleaf

Wes> == Wes Morgan <morgan@ms.uky.edu> 

 Wes> Seriously, let's look at the possibilities:

 Wes> 	- I can set a simple policy that says "this system is not to be used
 Wes> 	  for the development or use of password cracking software".  My users
 Wes> 	  are Engineering students; they have no curricular need to develop
 Wes> 	  such software on our systems.  

 Wes> 	  This approach benefits everyone (in theory).  The users don't have
 Wes> 	  to worry about admins (or Crack users) rooting through their files, 
 Wes> 	  and I don't have to worry about Crack fanciers.......

Or you could run shadow passwords, and run Crack yourself, and have a
proactive password checker.

This also benefits everyone, because it means that people are less
likely to have their accounts broken into, you don't get into problems
with people being duped into giving out your /etc/passwd for Joe Cracker
to run through Crack on his 486/50 (or on the SS2 he broke into last
week), and even if someone does get your shadow file, your passwords
will have some degree of strength.

I realize that this isn't always doable, but it's a big improvement.

--
Christopher Davis * ckd@eff.org * System Administrator, EFF * +1 617 864 0665
            ``Ed Gruberman, you fail to grasp Ti Kwan Leep.
            Approach me that you might see.'' -- The Master