search for: identityfile2

...SA keys are used by the SSH 2 protocol implementation. You can generate RSA keys for use with SSH 2 protocol with: $ ssh-keygen -t rsa -f /etc/ssh_host_rsa_key To use RSA or DSA keys in SSH 2 protocol, simply add the public keys to the .ssh/authorised_keys2 file. IdentityFile2, HostDsaKey and DSAAuthentication are obsolete: You can use multiple IdentityFile and HostKey options instead, e.g HostKey /etc/ssh_host_key HostKey /etc/ssh_host_dsa_key HostKey /etc/ssh_host_rsa_key in /etc/sshd_config The option DSAAuthentication has been re...

...SA keys are used by the SSH 2 protocol implementation. You can generate RSA keys for use with SSH 2 protocol with: $ ssh-keygen -t rsa -f /etc/ssh_host_rsa_key To use RSA or DSA keys in SSH 2 protocol, simply add the public keys to the .ssh/authorised_keys2 file. IdentityFile2, HostDsaKey and DSAAuthentication are obsolete: You can use multiple IdentityFile and HostKey options instead, e.g HostKey /etc/ssh_host_key HostKey /etc/ssh_host_dsa_key HostKey /etc/ssh_host_rsa_key in /etc/sshd_config The option DSAAuthentication has been re...

...are no sshd_config directives that affect agent forwarding. The Mandrake installation (on A) uses ssh-agent to set up KDE, so I see an ssh-agent running and have a corresponding SSH_AGENT_PID and SSH_AUTH_SOCKET in the shell environment. I ssh-add .ssh/gary_shea.dsa (my identity file, set up with IdentityFile2 in .ssh/ssh_config). ssh-add -l shows the identity. If I then 'ssh -A' to machine B, I do not need to type the passphrase, indicating that the ssh-agent works to that extent. BUT, my environment on B does not contain the SSH_AGENT_PID and SSH_AUTH_SOCK entries. I am forwarding X11 also,...

The code that handles identity files listed on the command line only adds the files to the options.identity_files array, which is for RSA keys. If you use the SSH2 protocol and have a DSA identity, you cannot specific it with -i on the command line.

...sb/.ssh/id_dsa <remotehost> ::snip:: debug: key does not exist: /root/.ssh/id_dsa Note that it is _still_ trying to use root's id_dsa key (root does not actually have one) despite my -i argument on the command line. 2) Next I tried specifying jamesb's dsa key in ~root/.ssh/config: IdentityFile2 ~jamesb/.ssh/id_dsa Then I got the following output: debug: try pubkey: /home/jamesb/.ssh/id_dsa @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: UNPROTECTED PRIVATE KEY FILE! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ Bad ownership or mod...

...r, oRhostsRSAAuthentication, + oOpenCommand, oCloseCommand, oProxyCommand, oGlobalKnownHostsFile, oUserKnownHostsFile, oConnectionAttempts, oBatchMode, oCheckHostIP, oStrictHostKeyChecking, oCompression, oCompressionLevel, oTCPKeepAlive, oNumberOfPasswordPrompts, @@ -149,6 +150,8 @@ { "identityfile2", oIdentityFile }, /* alias */ { "hostname", oHostName }, { "hostkeyalias", oHostKeyAlias }, + { "opencommand", oOpenCommand }, + { "closecommand", oCloseCommand }, { "proxycommand", oProxyCommand }, { "port", oPort }, { &...

...The 'DSAAuthentication' option is deprecated in favour of the general 'PubkeyAuthentication' option. The host key section of my sshd_config looks like this: HostKey /etc/ssh/ssh_host_key HostKey /etc/ssh/ssh_host_rsa_key HostKey /etc/ssh/ssh_host_dsa_key For the client, the 'IdentityFile2' option is deprecated in favor of an autodetecting 'IdentityFile' option. You can specity rsa1, dsa and rsa keys using this option. RSA pubkey auth seems a little quicker than DSA and it is not vulnerable to the problems described in the WARNING.RNG file. Full changelog: 20001113 -...

...icateFile, oUser, oEscapeChar, oRhostsRSAAuthentication, oProxyCommand, oGlobalKnownHostsFile, oUserKnownHostsFile, oConnectionAttempts, oBatchMode, oCheckHostIP, oStrictHostKeyChecking, oCompression, @@ -202,6 +203,7 @@ static struct { { "identityfile", oIdentityFile }, { "identityfile2", oIdentityFile }, /* obsolete */ { "identitiesonly", oIdentitiesOnly }, + { "certificatefile", oCertificateFile }, { "hostname", oHostName }, { "hostkeyalias", oHostKeyAlias }, { "proxycommand", oProxyCommand }, @@ -366,6 +368,37 @@...