Hi,
I installed opessh from wary 5.2.2 package manager.
I tried to start /usr/bin/sshd.
It gave error "host keys not available."
I generated keys for rsa1, rsa and dsa using ssh-keygen.
Changed /etc/ssh/sshd_config to allow "Protocol 2,1"
When I executed /usr/bin/sshd, it is running.
But when I try to connect to puppy machine from putty on windows, it says "server unexpectedly closed connection" and doesn't allow me to login.
Please help.
Srinivas Nayak
How to start sshd in Wary 5.2.2?
How to start sshd in Wary 5.2.2?
[Precise 571 on AMD Athlon XP 2000+ with 512MB RAM]
[Fatdog 720 on Intel Pentium B960 with 4GB RAM]
[url]http://srinivas-nayak.blogspot.com/[/url]
[Fatdog 720 on Intel Pentium B960 with 4GB RAM]
[url]http://srinivas-nayak.blogspot.com/[/url]
Can you post your sshd_config file? - this could give a clue.
You can also ssh from puppy to puppy (usefull for testing) - what happens if you do in puppy console:
You can also ssh from puppy to puppy (usefull for testing) - what happens if you do in puppy console:
Code: Select all
ssh root@localhost
Hi,
So works fine. asks for login password, accepts password "woofwoof". and comes to # prompt.
However from other machine's putty, I am not able to login.
my sshd_config is:
givesssh root@localhost
# ssh root@localhost
The authenticity of host 'localhost (127.0.0.1)' can't be established.
RSA key fingerprint is 75:9e:be:f5:dc:6d:e1:bd:76:04:e6:24:be:6f:dd:12.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'localhost' (RSA) to the list of known hosts.
root@localhost's password:
# pwd
/root
#
So works fine. asks for login password, accepts password "woofwoof". and comes to # prompt.
However from other machine's putty, I am not able to login.
my sshd_config is:
# cat /etc/ssh/sshd_config
# $OpenBSD: sshd_config,v 1.82 2010/09/06 17:10:19 naddy Exp $
# This is the sshd server system-wide configuration file. See
# sshd_config(5) for more information.
# This sshd was compiled with PATH=/usr/bin:/bin:/usr/sbin:/sbin
# The strategy used for options in the default sshd_config shipped with
# OpenSSH is to specify options with their default value where
# possible, but leave them commented. Uncommented options change a
# default value.
Port 22
#AddressFamily any
#ListenAddress 0.0.0.0
#ListenAddress ::
# The default requires explicit activation of protocol 1
Protocol 2,1
# HostKey for protocol version 1
#HostKey /etc/ssh/ssh_host_key
# HostKeys for protocol version 2
HostKey /etc/ssh/ssh_host_rsa_key
HostKey /etc/ssh/ssh_host_dsa_key
#HostKey /etc/ssh/ssh_host_ecdsa_key
# Lifetime and size of ephemeral version 1 server key
#KeyRegenerationInterval 1h
#ServerKeyBits 1024
# Logging
# obsoletes QuietMode and FascistLogging
#SyslogFacility AUTH
#LogLevel INFO
# Authentication:
LoginGraceTime 2m
PermitRootLogin yes
StrictModes yes
#MaxAuthTries 6
#MaxSessions 10
RSAAuthentication yes
PubkeyAuthentication yes
#AuthorizedKeysFile .ssh/authorized_keys
# For this to work you will also need host keys in /etc/ssh/ssh_known_hosts
#RhostsRSAAuthentication no
# similar for protocol version 2
#HostbasedAuthentication no
# Change to yes if you don't trust ~/.ssh/known_hosts for
# RhostsRSAAuthentication and HostbasedAuthentication
#IgnoreUserKnownHosts no
# Don't read the user's ~/.rhosts and ~/.shosts files
#IgnoreRhosts yes
# To disable tunneled clear text passwords, change to no here!
#PasswordAuthentication yes
#PermitEmptyPasswords no
# Change to no to disable s/key passwords
#ChallengeResponseAuthentication yes
# Kerberos options
#KerberosAuthentication no
#KerberosOrLocalPasswd yes
#KerberosTicketCleanup yes
#KerberosGetAFSToken no
# GSSAPI options
#GSSAPIAuthentication no
#GSSAPICleanupCredentials yes
# Set this to 'yes' to enable PAM authentication, account processing,
# and session processing. If this is enabled, PAM authentication will
# be allowed through the ChallengeResponseAuthentication and
# PasswordAuthentication. Depending on your PAM configuration,
# PAM authentication via ChallengeResponseAuthentication may bypass
# the setting of "PermitRootLogin without-password".
# If you just want the PAM account and session checks to run without
# PAM authentication, then enable this but set PasswordAuthentication
# and ChallengeResponseAuthentication to 'no'.
#UsePAM no
#AllowAgentForwarding yes
#AllowTcpForwarding yes
#GatewayPorts no
X11Forwarding yes
#X11DisplayOffset 10
#X11UseLocalhost yes
#PrintMotd yes
#PrintLastLog yes
#TCPKeepAlive yes
#UseLogin no
UsePrivilegeSeparation yes
#PermitUserEnvironment no
#Compression delayed
#ClientAliveInterval 0
#ClientAliveCountMax 3
#UseDNS yes
#PidFile /var/run/sshd.pid
#MaxStartups 10
#PermitTunnel no
#ChrootDirectory none
# no default banner path
#Banner none
# override default of no subsystems
Subsystem sftp /usr/libexec/sftp-server
# Example of overriding settings on a per-user basis
#Match User anoncvs
# X11Forwarding no
# AllowTcpForwarding no
# ForceCommand cvs server
#
[Precise 571 on AMD Athlon XP 2000+ with 512MB RAM]
[Fatdog 720 on Intel Pentium B960 with 4GB RAM]
[url]http://srinivas-nayak.blogspot.com/[/url]
[Fatdog 720 on Intel Pentium B960 with 4GB RAM]
[url]http://srinivas-nayak.blogspot.com/[/url]
Hm. nothing obvious. Maybe disable "Strict Mode"
and add
check also your /etc/host.deny file.
if there is ALL:ALL then remove it - that blocks all connections ...
anybody else?
and add
Code: Select all
PasswordAuthentication yes
if there is ALL:ALL then remove it - that blocks all connections ...
anybody else?
Dear emil,
Many thanks for help.
my sshd worked with adding "sshd : ALL : allow" in host.allow file.
Sincerely,
Srinivas Nayak
Many thanks for help.
check also your /etc/host.deny file.
if there is ALL:ALL then remove it - that blocks all connections ...
my sshd worked with adding "sshd : ALL : allow" in host.allow file.
Sincerely,
Srinivas Nayak
[Precise 571 on AMD Athlon XP 2000+ with 512MB RAM]
[Fatdog 720 on Intel Pentium B960 with 4GB RAM]
[url]http://srinivas-nayak.blogspot.com/[/url]
[Fatdog 720 on Intel Pentium B960 with 4GB RAM]
[url]http://srinivas-nayak.blogspot.com/[/url]