From: Dave Harrison [mailto:[EMAIL PROTECTED]
> 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.
Dave Harrison wrote:
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.
Just give the external sshd a d
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 re
3 matches
Mail list logo
