News for hackers. Stuff that matters.
Re:/bin/false is not security by dsr_ on Saturday February 04, 2012 @09:22AM (#3551092)
If you have a server where only a few people should ever SSH in, use AllowUsers.

If you have a larger number, assign them to a group and AllowGroup.

Simple, fast, and effective.

If you can turn off password auth in favor of keys, do that, too.

Re:/bin/false is not security by sciurus on Saturday February 04, 2012 @06:10PM (#3552551)
If you're using keys for special-purpose accounts, be sure to limit what they can do. You can specify that only a certain command can be run, that port forwarding isn't permitted, etc.

http://www.openbsd.org/cgi-bin/man.cgi?query=sshd&sektio...

Re:/bin/false is not security by bluehavana on Saturday February 04, 2012 @12:41PM (#3551505)
Keys get pretty unmanageable at scale. The biggest part of key management is changing keys, which is a really important part of security.

Use Kerberos and a Directory Service if you can, unless you have a solution to SSH key changes.

Re:/bin/false is not security by nbm on Saturday February 04, 2012 @01:58PM (#3551723)
Keys probably don't have to become unmanageable at scale - you can try use SSH certificate authentication.

Sign your keys with a CA, and encode the "principals" that the user has (so, be able to log into some machines as themself, some machines as some other user), and a validity period. Revocation wasn't there yet when last I looked at it (mid-last-year), but might be there now.

One benefit is that individual connections don't need to be brokered by an external authentication/authorisation service. However, it is a relatively new feature and there may be rough edges (such as making sure all your clients have a recent enough version of the tools to work with certificates - Lion was the first MacOS X version to have it, for example).