Educause Security Discussion mailing list archives
Re: Password Cracking & Consequences
From: Michael Mills <mmills () RKON COM>
Date: Fri, 27 Aug 2004 13:22:14 -0500
Justin, You make very valid points these options are available and they are also auditable. To not lose my main point, IT staff knowingly cracking passwords is not a good practice. It is also not part of any recommended "Best Practices". If there is a way to lock something up, then there is a way to unlock it. Its just how hard you make the unlocking process that counts. Michael Mills -----Original Message----- From: The EDUCAUSE Security Discussion Group Listserv [mailto:SECURITY () LISTSERV EDUCAUSE EDU] On Behalf Of Justin Azoff Sent: Friday, August 27, 2004 11:53 AM To: SECURITY () LISTSERV EDUCAUSE EDU Subject: Re: [SECURITY] Password Cracking & Consequences Michael Mills wrote:
Actually is does matter. If the IT staff "Cracks" users accounts then the IT staff can log on as that user and do as they wish (any department for that matter). However if that same IT person changes that users password and then logs on as that person, an audit trail is created. Even if that
IT
user would delete that audit trail, that deletion would show up in the
audit
trail. So again, I stress the point that under no circumstances should ANYONE know ANYONE else's password, weather it is by "cracking" or by
asking
someone their password.
Are you aware that there is a program called "su" in unix, and windows has "Run as..."? What about adding their ssh key to ~user/.ssh/authorized_keys and then logging in as them over the network, no password required? If someone on the IT staff wanted to do something on a users account they do not need to know the users password. Cracking a users password is not about knowing their password, it is about knowing that they have a weak password. -- -- Justin Azoff -- Network Performance Analyst ********** Participation and subscription information for this EDUCAUSE Discussion Group discussion list can be found at http://www.educause.edu/cg/. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. ********** Participation and subscription information for this EDUCAUSE Discussion Group discussion list can be found at http://www.educause.edu/cg/.
Current thread:
- Re: Password Cracking & Consequences, (continued)
- Re: Password Cracking & Consequences Gary Flynn (Aug 27)
- Re: Password Cracking & Consequences Eric Pancer (Aug 27)
- Re: Password Cracking & Consequences Christian Wilson (Aug 27)
- Re: Password Cracking & Consequences Justin Azoff (Aug 27)
- Re: Password Cracking & Consequences Scott Bradner (Aug 27)
- Re: Password Cracking & Consequences Scott Bradner (Aug 27)
- Re: Password Cracking & Consequences Gary Flynn (Aug 27)
- Re: Password Cracking & Consequences Gary Flynn (Aug 27)
- Re: Password Cracking & Consequences Michael Mills (Aug 27)
- Re: Password Cracking & Consequences Scott Bradner (Aug 27)
- Re: Password Cracking & Consequences Michael Mills (Aug 27)
- Re: Password Cracking & Consequences Michael Mills (Aug 27)
- Re: Password Cracking & Consequences Mike Austin (Aug 27)
- Re: Password Cracking & Consequences Davis, Thomas R. (Aug 27)
- Re: Password Cracking & Consequences Gary Flynn (Aug 27)
- Re: Password Cracking & Consequences Gary Flynn (Aug 27)
- Re: Password Cracking & Consequences Michael Mills (Aug 27)
- Re: Password Cracking & Consequences Cal Frye (Aug 28)
- Re: Password Cracking & Consequences Jere Retzer (Aug 28)
- Re: Password Cracking & Consequences Brian Eckman (Aug 29)
- Re: Password Cracking & Consequences Ron Parker (Aug 30)
(Thread continues...)