search for: sshd1

Displaying 4 results from an estimated 4 matches for "sshd1".

Did you mean: sshd
2006 Oct 31
2
Running two sshd's
Hi all, I'm wondering whether it is feasible or not to run two distinct sshd daemons with different config options! I have a CentOS 4.4 gateway with 2 Ethernet interfaces. One is connected to the Internet and the other to the LAN. Basically, what I would like to do is having a sshd that listens to the LAN interface with password enabled auth. and a sshd bound to the Internet interface with
2005 Jan 12
1
OpenSSH-39 not sending syslog msges to proper files
...ls properly to specified files. This happens when I set the syslogfacility as local7 and Log Level as INFO for sshd. However OpenSSH -38 works correctly for the same setting. I denied a host in /etc/hosts.deny and sshd should send a message "refused connect from" to the /var/adm/syslog/sshd1.log as per my setting whenever a new ssh connection happens from the denied host to this sshd server. But this is not happening in OpenSSH-39. My testing also points that the problem is produced with Log Level INFO if sshd re-executes itself for new connection. When sshd runs with re-exec featur...
2008 Jun 12
3
[Bug 1476] New: .ssh/known_hosts does not save port number
...Priority: P2 Component: ssh AssignedTo: unassigned-bugs at mindrot.org ReportedBy: parasietje at gmail.com Problem: .ssh/known_hosts does not save the port number, only the IP/hostname. Thus, multiple ssh-servers on the same IP will cause key collisions. Recreate: Run sshd1 with certificate1 on port 2221 Run sshd2 with certificate2 on port 2222 Connect to localhost, port 2221. The server certificate is added to .ssh/known_hosts Connect to localhost, port 2222 Ssh reports REMOTE HOST KEY CHANGED Expected behavior: Ssh makes a difference between the ssh-server...
2000 Dec 28
2
ssh-agent, protocol 2, openssh-2.3.0p1
Hi -- I saw an email on December 26th in the openssh-unix-dev mailing list archived on MARC, indicating that agent forwarding is indeed not working for 2.2, but that it is working for 2.3. That email referred to a user with 2.3 clients and 2.2 server. I am running the 2.3 client AND server and am having a similar problem. The only unusual aspect of my installation is that I'm using port 24