Hi,

I'm interested to know if anyone has a better solution (or has a
solution to my existing question) for the following situation.

I have a remote login box that also functions as a local login box.
Users connect to the machine over the local network to run X apps, they
can also connect to it remotely (from other sites) using SSH to do the
same sort of thing.

Many users never access it from remote, but do use it locally alot.
Others use it both locally and remotely.  Locally, it is more effort
than it's worth to enforce use of public keys (a proportion are windows
users), however I want to mandate public keys for remote connections.

My current solution is to run a second sshd on another port and have
that be the externally accessible sshd (and configure it to only allow
public key connections).  However the way sshd logs, I can't work out
what was logged by which daemon.

Are there any other solutions people can think of ?  Is there an option
I don't know about ?

Cheers for your help,
Dave

Reply via email to