11-12-2008
Public/Private Key SSH from UNIX to Windows (Cygwin)
Hello all,
I have a bit of trouble working a passwordless SSH from UNIX to Cygwin running windows 2k3. Here are some details. I AM able to SSH from the Windows box to the UNIX box using the keys. Also, I'm able to SSH from UNIX to Windows w/o the keys. However, when I try to do it with the keys the following output is produced
....
debug3: check_host_in_hostfile: match line 1
debug1: Host 'xx.xx.xx.xxis known and matches the RSA host key.
debug1: Found key in /cygdrive/c/cygwin/home/user/.ssh/known_hosts:1
debug2: bits set: 522/1024
debug1: ssh_rsa_verify: signature correct
debug2: kex_derive_keys
debug2: set_newkeys: mode 1
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug2: set_newkeys: mode 0
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug2: key: /cygdrive/c/cygwin/home/user/.ssh/identity (0x0)
debug2: key: /cygdrive/c/cygwin/home/user/.ssh/id_rsa (0x0)
debug2: key: /cygdrive/c/cygwin/home/user/.ssh/id_dsa (0x0)
debug1: Authentications that can continue: publickey,password,keyboard- interactive
debug3: start over, passed a different list publickey,password,keyboard- interactive
debug3: preferred publickey,keyboard-interactive,password
debug3: authmethod_lookup publickey
debug3: remaining preferred: keyboard-interactive,password
debug3: authmethod_is_enabled publickey
debug1: Next authentication method: publickey
debug1: Trying private key: /cygdrive/c/cygwin/home/user/.ssh/identity
debug3: no such identity: /cygdrive/c/cygwin/home/user/.ssh/identity
debug1: Trying private key: /cygdrive/c/cygwin/home/user/.ssh/id_rsa
debug1: read PEM private key done: type RSA
debug3: sign_and_send_pubkey
debug2: we sent a publickey packet, wait for reply
Connection closed by [remote host]
I'm not entirely sure that I'm using priveledged separation. Honestly it was so difficult to start the sshd service that I can't remember. When I check the windows service it does state that the CYGWIN sshd server is logged on as Local System.
I did uncomment out the following in sshd_config:
RSAAuthentication yes
PubkeyAuthentication yes
AuthorizedKeysFile .ssh/authorized_keys
If someone could work with me on this I'd very much appreciate it.
Thanks,
Kevin
Last edited by kclerks11; 11-19-2008 at 05:55 PM..
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi,
I am trying to scp a file from our Unix server to the local Windows machine.I have created the key pair in Unix server using ssh-keygen command in unix.
But I am not sure where can we put the public key(generated on Unix) in Windows machine so that scp from Unix machine to Windows is... (3 Replies)
Discussion started by: dennis.jacob
3 Replies
2. UNIX for Dummies Questions & Answers
Hi everyone,
I have a quick/newb question:
I know that a public key is used to encrypt data and a private key is used to decrypt data but who keeps the public/private keys??
Does the Web Server hold both?
Does the Web Server have the public key and does the client have the private key? ... (3 Replies)
Discussion started by: tical00
3 Replies
3. Shell Programming and Scripting
Hi everybody,
I need some help on writing a script that is able to remote copy file to one server. I already created this types of scripts, and works ok as long as this server I want to copy from is access through telnet. Here is how I do it:
ftp -n xxx.xxx.xxx.xxx << _EOF_
user user_name... (6 Replies)
Discussion started by: Alexis Duarte
6 Replies
4. Shell Programming and Scripting
hello,
iam able to ssh to a linux server from a linux server called "machine1" using the private/public key method, so I dont need to enter any password when I run my script but iam not able to ssh from machine1 to a UNIX server, access is denied.
note that I am using an application id which is... (6 Replies)
Discussion started by: wydadi
6 Replies
5. UNIX for Dummies Questions & Answers
Hi,
please guide me create a public/private key using ssh-keygen, lets say I have been access to server named pngpcdb1with a userid and password ...!!! and also please explain in detail the concept of these keys and ssh as I was planning to use them in ftp related scripts..! Thanks in... (1 Reply)
Discussion started by: rahul125
1 Replies
6. Solaris
Hi i am using solaris 10.I am trying to setup a public/private key but it is not working.Appreciate your repsonse on it
There are two servers DB1 server and DB2 server.
1)I have generated public/private key using below step on both servers.
ssh-keygen -t rsa
2)From DB1 server moved the... (6 Replies)
Discussion started by: muraliinfy04
6 Replies
7. UNIX for Dummies Questions & Answers
Hi,
What tool is used to generate public and private keys for SCP?
Do you have an example script that generates these keys, puts them in files and then another example script that references them from SCP?
Thanks, (9 Replies)
Discussion started by: Astrocloud
9 Replies
8. Shell Programming and Scripting
Hi All,
I have a requirement where i need to check if an rsa public key corresponds to a private key and hence return success or failure. Currently i am using the command
diff <( ssh-keygen -y -e -f "$PRIVKEY" ) <( ssh-keygen -y -e -f "$PUBLICKEY" )
and its solving my purpose. This is in... (1 Reply)
Discussion started by: mritusmoi
1 Replies
9. UNIX for Advanced & Expert Users
Hi,
we have private and public key, encrypt file using public and want to decrypt using private key. can you please advise below commands are correct or other remedy if unix have?
encrypt -a arcfour -k publickey.asc -i TESTFILE.csv -o TESTFILE00.csv
decrypt -a arcfour -k privatekey.asc... (2 Replies)
Discussion started by: rizwan.shaukat
2 Replies
10. UNIX for Advanced & Expert Users
I have a user account configuration with ssh public/private key that works on multiple servers centos and rhel. One server (Server F) that is not working in centos 6.8. When i ssh into server f I get prompted for a password. I have verified the config and it all is good. I put sshd into debug... (8 Replies)
Discussion started by: bash_in_my_head
8 Replies
LEARN ABOUT DEBIAN
ssh-vulnkey
SSH-VULNKEY(1) BSD General Commands Manual SSH-VULNKEY(1)
NAME
ssh-vulnkey -- check blacklist of compromised keys
SYNOPSIS
ssh-vulnkey [-q | -v] file ...
ssh-vulnkey -a
DESCRIPTION
ssh-vulnkey checks a key against a blacklist of compromised keys.
A substantial number of keys are known to have been generated using a broken version of OpenSSL distributed by Debian which failed to seed
its random number generator correctly. Keys generated using these OpenSSL versions should be assumed to be compromised. This tool may be
useful in checking for such keys.
Keys that are compromised cannot be repaired; replacements must be generated using ssh-keygen(1). Make sure to update authorized_keys files
on all systems where compromised keys were permitted to authenticate.
The argument list will be interpreted as a list of paths to public key files or authorized_keys files. If no suitable file is found at a
given path, ssh-vulnkey will append .pub and retry, in case it was given a private key file. If no files are given as arguments, ssh-vulnkey
will check ~/.ssh/id_rsa, ~/.ssh/id_dsa, ~/.ssh/identity, ~/.ssh/authorized_keys and ~/.ssh/authorized_keys2, as well as the system's host
keys if readable.
If ``-'' is given as an argument, ssh-vulnkey will read from standard input. This can be used to process output from ssh-keyscan(1), for
example:
$ ssh-keyscan -t rsa remote.example.org | ssh-vulnkey -
Unless the PermitBlacklistedKeys option is used, sshd(8) will reject attempts to authenticate with keys in the compromised list.
The output from ssh-vulnkey looks like this:
/etc/ssh/ssh_host_key:1: COMPROMISED: RSA1 2048 xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx root@host
/home/user/.ssh/id_dsa:1: Not blacklisted: DSA 1024 xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx /home/user/.ssh/id_dsa.pub
/home/user/.ssh/authorized_keys:3: Unknown (blacklist file not installed): RSA 1024 xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx user@host
Each line is of the following format (any lines beginning with ``#'' should be ignored by scripts):
filename:line: status: type size fingerprint comment
It is important to distinguish between the possible values of status:
COMPROMISED
These keys are listed in a blacklist file, normally because their corresponding private keys are well-known. Replacements must be
generated using ssh-keygen(1).
Not blacklisted
A blacklist file exists for this key type and size, but this key is not listed in it. Unless there is some particular reason to
believe otherwise, this key may be used safely. (Note that DSA keys used with the broken version of OpenSSL distributed by Debian
may be compromised in the event that anyone captured a network trace, even if they were generated with a secure version of OpenSSL.)
Unknown (blacklist file not installed)
No blacklist file exists for this key type and size. You should find a suitable published blacklist and install it before deciding
whether this key is safe to use.
The options are as follows:
-a Check keys of all users on the system. You will typically need to run ssh-vulnkey as root to use this option. For each user,
ssh-vulnkey will check ~/.ssh/id_rsa, ~/.ssh/id_dsa, ~/.ssh/identity, ~/.ssh/authorized_keys and ~/.ssh/authorized_keys2. It will
also check the system's host keys.
-q Quiet mode. Normally, ssh-vulnkey outputs the fingerprint of each key scanned, with a description of its status. This option sup-
presses that output.
-v Verbose mode. Normally, ssh-vulnkey does not output anything for keys that are not listed in their corresponding blacklist file
(although it still produces output for keys for which there is no blacklist file, since their status is unknown). This option causes
ssh-vulnkey to produce output for all keys.
EXIT STATUS
ssh-vulnkey will exit zero if any of the given keys were in the compromised list, otherwise non-zero.
BLACKLIST FILE FORMAT
The blacklist file may start with comments, on lines starting with ``#''. After these initial comments, it must follow a strict format:
o All the lines must be exactly the same length (20 characters followed by a newline) and must be in sorted order.
o Each line must consist of the lower-case hexadecimal MD5 key fingerprint, without colons, and with the first 12 characters removed
(that is, the least significant 80 bits of the fingerprint).
The key fingerprint may be generated using ssh-keygen(1):
$ ssh-keygen -l -f /path/to/key
This strict format is necessary to allow the blacklist file to be checked quickly, using a binary-search algorithm.
FILES
~/.ssh/id_rsa
If present, contains the protocol version 2 RSA authentication identity of the user.
~/.ssh/id_dsa
If present, contains the protocol version 2 DSA authentication identity of the user.
~/.ssh/identity
If present, contains the protocol version 1 RSA authentication identity of the user.
~/.ssh/authorized_keys
If present, lists the public keys (RSA/DSA) that can be used for logging in as this user.
~/.ssh/authorized_keys2
Obsolete name for ~/.ssh/authorized_keys. This file may still be present on some old systems, but should not be created if it is
missing.
/etc/ssh/ssh_host_rsa_key
If present, contains the protocol version 2 RSA identity of the system.
/etc/ssh/ssh_host_dsa_key
If present, contains the protocol version 2 DSA identity of the system.
/etc/ssh/ssh_host_key
If present, contains the protocol version 1 RSA identity of the system.
/usr/share/ssh/blacklist.TYPE-LENGTH
If present, lists the blacklisted keys of type TYPE (``RSA'' or ``DSA'') and bit length LENGTH. The format of this file is described
above. RSA1 keys are converted to RSA before being checked in the blacklist. Note that the fingerprints of RSA1 keys are computed
differently, so you will not be able to find them in the blacklist by hand.
/etc/ssh/blacklist.TYPE-LENGTH
Same as /usr/share/ssh/blacklist.TYPE-LENGTH, but may be edited by the system administrator to add new blacklist entries.
SEE ALSO
ssh-keygen(1), sshd(8)
AUTHORS
Colin Watson <cjwatson@ubuntu.com>
Florian Weimer suggested the option to check keys of all users, and the idea of processing ssh-keyscan(1) output.
BSD
May 12, 2008 BSD