02-25-2005
trouble auto connecting ssh 3.6.1 (Solaris 8) to ssh 3.0.1 (Solaris 6)
I am currently setting up rdiff-backup to use ssh to connect and remotely backup and retrieve data. I am doing so by creating rsa keys for each server and copying the relevant key to the /.ssh folder on the relevant server.
All seems to work well when severs running solaris 8 with ssh 3.6.1 are talking to each other, but I have one server running solaris 6 with ssh 3.0.1 and it will not except the key being sent to it from the connecting server.
The connecting server is running solaris 8 with ssh 3.6.1.
On the Solaris 6 server in the / directory instead of a .ssh folder there is a .ssh2 folder. I have tried placing the public rsa key for the connecting server in the file "authorized_keys" and then "authorized_keys2" with no success.
Any suggestions??
Regards Tim
ssh -C -v 250
OpenSSH_3.6.1p1, SSH protocols 1.5/2.0, OpenSSL 0x0090702f
debug1: Reading configuration data //.ssh/config
debug1: Applying options for 250
debug1: Reading configuration data /usr/local/etc/ssh_config
debug1: Rhosts Authentication disabled, originating port will not be trusted.
debug1: Connecting to 195.248.193.250 [195.248.193.250] port 22.
debug1: Connection established.
debug1: identity file /.ssh/id_rsa_250 type 1
debug1: Remote protocol version 2.0, remote software version 3.0.1 SSH Secure Shell
debug1: match: 3.0.1 SSH Secure Shell pat 3.0.*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_3.6.1p1
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-cbc hmac-md5 zlib
debug1: kex: client->server aes128-cbc hmac-md5 zlib
debug1: sending SSH2_MSG_KEXDH_INIT
debug1: expecting SSH2_MSG_KEXDH_REPLY
debug1: Host '195.248.193.250' is known and matches the DSA host key.
debug1: Found key in /.ssh/known_hosts:5
debug1: ssh_dss_verify: signature correct
debug1: Enabling compression at level 6.
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,password
debug1: Next authentication method: publickey
debug1: Offering public key: /.ssh/id_rsa_250
debug1: Authentications that can continue: publickey,password
debug1: Next authentication method: password
root@195.248.193.250's password:
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi all...
When i send a command via ssh, from a hp10.20 to a sol9 server, i get the following:
# ssh mouton uname -a
mouton root's password:
Of course, after giving the passwd, it works. I'd like to be able to send commands without giving this password.
When i set the sshd in debug mode... (1 Reply)
Discussion started by: penguin-friend
1 Replies
2. Solaris
howdy,
I have a couple of headless Solaris 8 servers i can access via ssh for basic periodic patching.
I would like to use the X server to access some of the apps that reside there also, but when i start X it errors out, complaining it can't find /dev/fb.
Is there a way to bypass the... (3 Replies)
Discussion started by: [MA]Flying_Meat
3 Replies
3. Solaris
Hi all,
i need to run ssh for solaris 8
my server version is
SunOS myserver 5.8 Generic_117350-25 sun4u sparc SUNW,Sun-Fire-880
wher i can get this?
pls help
Thanx n Regards/Ajay (3 Replies)
Discussion started by: ajays
3 Replies
4. Solaris
hye guys..i'm new here..just want to ask how to configure SSH service in solaris 10??
hope you all will help me..tq (2 Replies)
Discussion started by: FaiRiZuL
2 Replies
5. Solaris
Hi,
I m new to Sun Solaris.
I've only changed the PermitRootLogin from no to yes, so that I can login as root from Window vista by using Putty.exe. Then I can create new users and change password.
Except the above configuration, i have do nothing to my SSH server.
Am I need to generate... (5 Replies)
Discussion started by: stacychiam
5 Replies
6. Solaris
Hi,
I am unable to login into my terminal hosting Solaris 10 and get the below error message
"Server refused to allocate pty
ld.so.1: sh: fatal: libc.so.1: open failed: No such file or directory "
Is there anyways i can get into my machine and what kind of changes are required to be... (7 Replies)
Discussion started by: sankasu
7 Replies
7. Solaris
Hi, It's a Solaris 10 zone. I can ssh to other systems without problems, but can not ssh to it (output attached). I don't think there is a firewall here. /etc/ipf/ipf.conf contains nothing.
What could be the problem cause? Please help. Thank you in advance!
sshclient$ ssh -v thiserver... (1 Reply)
Discussion started by: aixlover
1 Replies
8. Solaris
Got a strange problem.
I have 4 Solaris servers all configured the same, Solaris 10 x86 update 10.
When I try to ssh from one Solaris 10 server to another server ssh hangs.
I have an identical server and when I try this everything works fine.
The weird thing is if I am root on the server... (1 Reply)
Discussion started by: ccj4467
1 Replies
9. IP Networking
Hi all.
Im working in a telco Environment and recently setup a new server. The other servers are a combination of Solaris + Linux machines.
Using my new server , I can ping all other servers ( solaris + redhat linux )
but the issue lies where I try to ssh.
I can only successfully ssh linux... (3 Replies)
Discussion started by: Junaid Subhani
3 Replies
10. Solaris
I'm having an issue with SSH on a server that hasn't had any configuration changes made on it in a long time. I SSH to the server and it hangs at "debug1: SSH2_MSG_KEXINIT sent" for exactly 40 seconds then connects fine after that pause. Everything I have found points to DNS, but I use host files... (19 Replies)
Discussion started by: kingdbag
19 Replies
LEARN ABOUT REDHAT
ssh-keysign
SSH-KEYSIGN(8) BSD System Manager's Manual SSH-KEYSIGN(8)
NAME
ssh-keysign -- ssh helper program for hostbased authentication
SYNOPSIS
ssh-keysign
DESCRIPTION
ssh-keysign is used by ssh(1) to access the local host keys and generate the digital signature required during hostbased authentication with
SSH protocol version 2.
ssh-keysign is disabled by default and can only be enabled in the the global client configuration file /etc/ssh/ssh_config by setting
HostbasedAuthentication to ``yes''.
ssh-keysign is not intended to be invoked by the user, but from ssh(1). See ssh(1) and sshd(8) for more information about hostbased authen-
tication.
FILES
/etc/ssh/ssh_config
Controls whether ssh-keysign is enabled.
/etc/ssh/ssh_host_dsa_key, /etc/ssh/ssh_host_rsa_key
These files contain the private parts of the host keys used to generate the digital signature. They should be owned by root, read-
able only by root, and not accessible to others. Since they are readable only by root, ssh-keysign must be set-uid root if hostbased
authentication is used.
SEE ALSO
ssh(1), ssh-keygen(1), ssh_config(5), sshd(8)
AUTHORS
Markus Friedl <markus@openbsd.org>
HISTORY
ssh-keysign first appeared in OpenBSD 3.2.
BSD
May 24, 2002 BSD