News for hackers. Stuff that matters.
Re:OpenSSH Server Best Practices (security related) by sneak on Tuesday October 23, 2012 @12:49PM (#4688914)
Setting ClientAliveInterval and ClientAliveCountMax does not disconnect idle users. It's for detecting failed network connections. Your ssh client will still reply to protocol level alive checks even if you are sitting idle at a prompt.

What he's looking for instead is:

    echo "TMOUT=300 >> /etc/bashrc
You can argue that this doesn't really enhance security, though...
Re:OpenSSH Server Best Practices (security related) by Florin_Andrei on Tuesday October 23, 2012 @03:00PM (#4689740)
It's prudent to do this as many people just leave ssh sessions hanging open forever, and their desktops don't auto-lock the screensaver.

It's still easily thwarted if the user keeps "top" running in it, or something.

Re:OpenSSH Server Best Practices (security related) by sneak on Tuesday October 23, 2012 @03:31PM (#4689940)
> many people just leave ssh sessions hanging open forever, and their desktops don't auto-lock the screensaver

Not "many people" use ssh to begin with.

Re:OpenSSH Server Best Practices (security related) by Florin_Andrei on Wednesday October 24, 2012 @03:57PM (#4694740)
I'm talking about engineering staff, like me, my co-workers, and (very likely) you.
Re:OpenSSH Server Best Practices (security related) by sneak on Wednesday October 24, 2012 @08:04PM (#4695658)
Who would hire someone to use ssh who doesn't know enough to encrypt their disk and lock their screen on a timeout?
Re:OpenSSH Server Best Practices (security related) by graywh on Tuesday October 23, 2012 @02:08PM (#4689330)
I've used timeoutd to disconnect idle users.