Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Secure-Shell
[Top] [All Lists]

Re: Enforce Passphrase on keys

Subject: Re: Enforce Passphrase on keys
Date: Thu, 03 Jul 2008 17:11:25 +0100
On Thu, 2008-07-03 at 09:31 -0500, Michael Wisniewski wrote:
Hi!

I've been trying to dig around and find a way to enforce passphrases
on private keys when you authenticate.  The closest post that I can
find would be...

http://marc.info/?l=openssh-unix-dev&m=106941429416956&w=2

---
if openssl rsa -noout -passin pass:none -in /path/to/key ; then
       echo user is a dork
fi
---

However, how does one go about implementing this if their private key
is on the local system?  If the private key is on your server, you
could probably put it in a login script.  But being that it is on the
local system, how would you go about verifying the passphrase?

The reason why I'm going down this road is because we have had
problems where a user's private key is compromised.  Some user's do
not use passphrases on their private keys.  Once a key is copied off
the system, the attacker then logs in without worrying about
passwords.  My idea is to have the server deny the connection if a
passphrase does not exist on a private key.


Thanks!

don't thing something like this is possible. the way to go is to enforce
the security policies on the local system (so it does not get
compromised) and user education. appropriate action against the user who
did not follow company security policies should be taken, let them be
aware of that.

other method would be to replace the keys authentication with something
more scalable, e.g. Kerberos.

Martin. 

<Prev in Thread] Current Thread [Next in Thread>