04-15-2009
Ok, sorry for the delay, took awhile to get to the other guy.
here is the error he gets:
OpenSSH_3.7.1p2, SSH protocols 1.5/2.0, OpenSSL 0.9.6g 9 Aug 2002
Debug1: Reading configureation data /usr/local/etc/ssh_config
Debug2: ssh_connect: needpriv 0
Debug1: Connecting to xxx.xxx.xxx.xxx [xxx.xxx.xxx.xxx] port xx
Debug1: Connection Established.
Debug2: key_type_from_name: unknown key type '1024'
Debug1: identity file /export/home/sysadmin/.ssh/identity type -1
Debug2: key-type_from_name: unknown key type '----begin'
Debug1: identity file /export/home/sysadmin/.ssh/id_rsa type 1
Debug2: key_type_from_name: unknown key type '----begin'
Debug1: identity file /export/home/sysadmin/.ssh/id_dsa type 2
Ssh_exchange_identification: Conneciton closed by remote host
Debug1: Calling cleanup 0x3c0cc(0x0)
Ok, we already know that the cause of the unknown keytype '----begin' is because the prefixs we have in our keys, if we remove them, we don't get the error. (not sure y they are there in the first place??)
Also we know that the unknown 1024 is because we don't have an identity file for the user. (no problem for us, as the identity is only used for ssh protocol 1, which we cannot use)
We believe that we just need to get our rsa and dsa keys to match (copy mine into his, or vice versa) to get it to work.
anyone else have some imput on this??
thanks again.
Last edited by EWTGPAC; 04-15-2009 at 11:59 AM..
10 More Discussions You Might Find Interesting
1. Cybersecurity
I'm not sure if this is appropriate for the forum, but I figured it was security related, so here goes...
I'm writing an anlaysis for my group about moving some of the old internet protocols (rsh, rlogin, etc...) to the SSH suite of tools. An outside security group recommended a commercial... (7 Replies)
Discussion started by: jalburger
7 Replies
2. Solaris
Hi,
I would like to login from a Sun server running ssh:
Sun_SSH_1.1, SSH protocols 1.5/2.0, OpenSSL 0x0090704f
to
ssh: SSH Secure Shell 3.0.1 on sparc-sun-solaris2.6
How can I achieve this?
Thanks a million in advance (1 Reply)
Discussion started by: newbewie
1 Replies
3. Programming
I couldn't compile this code in gcc (SUSE Linux) 4.3.1 20080507.
got me these!
sniffer.c: In function ‘int CreateRawSocket(int)':
sniffer.c:16: error: ‘htons' was not declared in this scope
sniffer.c: In function ‘int BindRawSocketToInterface(char*, int, int)':
sniffer.c:31: error: ‘bzero'... (2 Replies)
Discussion started by: galaxy.ice
2 Replies
4. UNIX for Dummies Questions & Answers
I have a FreeBSD server on my home network. It is hooked to the router with an Ethernet cable. Both the server and the router are in the basement. The other computers in the house are upstairs, wireless. So the server's local IP address is set outside the wireless pool, and suppose it's... (1 Reply)
Discussion started by: gabi
1 Replies
5. Solaris
I set the RETRIES and DISABLETIME in /etc/default/login on 2 systems:
- 1 Solaris 9 system running Sun SSH
- 1 Solaris 9 system running Openssh 5.2 P1
I expected that after n failed logins, the login process will hang for n seconds.
It does when the attempted login is done at the console... (8 Replies)
Discussion started by: jabentay
8 Replies
6. Solaris
hi All,
We tried to establish a connection from OpenSSH3.8.1 running on Windows Box to SunSSH-1.1 running on Solaris 10. Please see the debug statements.
C:\Documents and Settings\sadmin\.ssh>ssh sadmin@10.4.3.8 -v -v -v
OpenSSH_3.8.1p1, OpenSSL 0.9.7d 17 Mar 2004
debug1: Reading... (2 Replies)
Discussion started by: venusunil
2 Replies
7. UNIX for Advanced & Expert Users
Hi all,
I have a Solaris 10 server with SUN_SSH_1.1 installed.
I want to restrict a user via SFTP to only be able to access one directory. I've written a little script in .profile which works perfectly for an ssh login but it appears sftp doesn't read the .profile file so it doesn't work.
... (2 Replies)
Discussion started by: Donkey25
2 Replies
8. Solaris
My one Sun machine is not able to ssh another machine of Sun. Although I have configured the ssh successfully
( SunOS sunbox2 5.9 Generic_118558-34 sun4u sparc SUNW,Sun-Blade-2500 )
ERROR
bash-2.05# ssh sunbox2
/etc/ssh/ssh_config: line 34: Bad configuration option: PermitRootLogin... (0 Replies)
Discussion started by: z_haseeb
0 Replies
9. Solaris
which should i prefer to install in my system openssh or ssh package provided by SUN by default. can i have two packages installed at the same time? (2 Replies)
Discussion started by: chidori
2 Replies
10. Red Hat
There was a security analysis run on one server which has RHEL 5.8 installed and it is showing security vulnerabilities with respect to ssh in OpenSSH with reference no CVE-2007-4752. The vulnerability solution in the security report is showing solution as below:
1) Download and apply the... (3 Replies)
Discussion started by: RHCE
3 Replies
LEARN ABOUT DEBIAN
ssh-add
SSH-ADD(1) BSD General Commands Manual SSH-ADD(1)
NAME
ssh-add -- adds private key identities to the authentication agent
SYNOPSIS
ssh-add [-cDdkLlXx] [-t life] [file ...]
ssh-add -s pkcs11
ssh-add -e pkcs11
DESCRIPTION
ssh-add adds private key identities to the authentication agent, ssh-agent(1). When run without arguments, it adds the files ~/.ssh/id_rsa,
~/.ssh/id_dsa, ~/.ssh/id_ecdsa and ~/.ssh/identity. After loading a private key, ssh-add will try to load corresponding certificate informa-
tion from the filename obtained by appending -cert.pub to the name of the private key file. Alternative file names can be given on the com-
mand line.
If any file requires a passphrase, ssh-add asks for the passphrase from the user. The passphrase is read from the user's tty. ssh-add
retries the last passphrase if multiple identity files are given.
The authentication agent must be running and the SSH_AUTH_SOCK environment variable must contain the name of its socket for ssh-add to work.
Any keys recorded in the blacklist of known-compromised keys (see ssh-vulnkey(1)) will be refused.
The options are as follows:
-c Indicates that added identities should be subject to confirmation before being used for authentication. Confirmation is performed by
the SSH_ASKPASS program mentioned below. Successful confirmation is signaled by a zero exit status from the SSH_ASKPASS program,
rather than text entered into the requester.
-D Deletes all identities from the agent.
-d Instead of adding identities, removes identities from the agent. If ssh-add has been run without arguments, the keys for the default
identities will be removed. Otherwise, the argument list will be interpreted as a list of paths to public key files and matching
keys will be removed from the agent. If no public key is found at a given path, ssh-add will append .pub and retry.
-e pkcs11
Remove keys provided by the PKCS#11 shared library pkcs11.
-k When loading keys into the agent, load plain private keys only and skip certificates.
-L Lists public key parameters of all identities currently represented by the agent.
-l Lists fingerprints of all identities currently represented by the agent.
-s pkcs11
Add keys provided by the PKCS#11 shared library pkcs11.
-t life
Set a maximum lifetime when adding identities to an agent. The lifetime may be specified in seconds or in a time format specified in
sshd_config(5).
-X Unlock the agent.
-x Lock the agent with a password.
ENVIRONMENT
DISPLAY and SSH_ASKPASS
If ssh-add needs a passphrase, it will read the passphrase from the current terminal if it was run from a terminal. If ssh-add does
not have a terminal associated with it but DISPLAY and SSH_ASKPASS are set, it will execute the program specified by SSH_ASKPASS and
open an X11 window to read the passphrase. This is particularly useful when calling ssh-add from a .xsession or related script.
(Note that on some machines it may be necessary to redirect the input from /dev/null to make this work.)
SSH_AUTH_SOCK
Identifies the path of a UNIX-domain socket used to communicate with the agent.
FILES
~/.ssh/identity
Contains the protocol version 1 RSA authentication identity of the user.
~/.ssh/id_dsa
Contains the protocol version 2 DSA authentication identity of the user.
~/.ssh/id_ecdsa
Contains the protocol version 2 ECDSA authentication identity of the user.
~/.ssh/id_rsa
Contains the protocol version 2 RSA authentication identity of the user.
Identity files should not be readable by anyone but the user. Note that ssh-add ignores identity files if they are accessible by others.
EXIT STATUS
Exit status is 0 on success, 1 if the specified command fails, and 2 if ssh-add is unable to contact the authentication agent.
SEE ALSO
ssh(1), ssh-agent(1), ssh-keygen(1), ssh-vulnkey(1), sshd(8)
AUTHORS
OpenSSH is a derivative of the original and free ssh 1.2.12 release by Tatu Ylonen. Aaron Campbell, Bob Beck, Markus Friedl, Niels Provos,
Theo de Raadt and Dug Song removed many bugs, re-added newer features and created OpenSSH. Markus Friedl contributed the support for SSH
protocol versions 1.5 and 2.0.
BSD
October 18, 2011 BSD