10-05-2015
ssh-keygen's manpage says "DSA keys must be exactly 1024 bits as specified by FIPS 186-2" and the tool refuses to create keys larger than 1024 bits. So it seems conceivable, that the ssh daemon refuses to accept such keys.
Can you verify, that a different type of key (1024 bit DSA or some RSA key) would work?
8 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi All,
I have putty on my system (Vista). I need some server details to login via internet for my personnel practice. Can any body help me out.
In case this not feasible, just let me know any other way to work with UNIX terminal on Windows Vista itself.
Please help me since i am desparately... (3 Replies)
Discussion started by: vikas_kesarwani
3 Replies
2. Solaris
We have two servers A and B (both running Solaris 10) out of which one is application server and the other is database server. The two servers faced certain network issues and the two servers were temporarily disconnected.this happened around 5AM GMT monday.Can anyone suggest some log files or... (2 Replies)
Discussion started by: asalman.qazi
2 Replies
3. Shell Programming and Scripting
Hi All,
How can we access oracle database which is in another server using shell scripts?
Please share your ideas.
Regards,
Raja (1 Reply)
Discussion started by: Rajakct84
1 Replies
4. Shell Programming and Scripting
Hi,
I have situation where i need to automate transferring 10000+ files using sftp.
while read line
do
if ; then
echo "-mput /home/student/Desktop/folder/$line/* /cygdrive/e/folder/$line/">>sftpCommand.txt
fi
done< files.txt
sftp -b sftpCommand.txt stu@192.168.2.1
The above... (1 Reply)
Discussion started by: noobrobot
1 Replies
5. IP Networking
Hi
Can any one please help identify the issue in scenario 2:
Connectivity Diagram:
1) Distribution Switch----Int_Switch----LabSwitch(Fa1/0)----Terminal Ser
2) Distribution Swtich----Int_Swtich----LabSwitch(Fa2/0)----3640 Router
---all links are access links
Distribution Switch... (0 Replies)
Discussion started by: sureshcisco
0 Replies
6. Red Hat
Hello,
I have a weird issue, I have RHEL 5.7 running with openssh5.2 where sftpgroup OS group is chroot. I see the difference difference in timestamp on files, when I login via ssh and SFTP, I see four hour difference, is something missing in my configuration.
#pwd... (8 Replies)
Discussion started by: bobby320
8 Replies
7. Shell Programming and Scripting
I had the below sftp script working perfectly but the problem is I am not able to send the echo statements .
#!/bin/sh
echo "Starting to sftp..."
sftp admin@myip << END_SCRIPT
cd /remotepath/
lcd /localpath/
mget myfiles*.csv
bye
END_SCRIPT
echo "Sftp successfully."
echo
echo... (11 Replies)
Discussion started by: scriptscript
11 Replies
8. Shell Programming and Scripting
I am trying to setup a password less connection from a Linux server to Window server and will be using a script to scp a file without using password.
Linux Server (source)
servername : testlinux
id : testbatch
Windows Server (Target)
servername : testwin
id : testwinlogin
I copied... (5 Replies)
Discussion started by: dr46014
5 Replies
LEARN ABOUT DEBIAN
openpgp2ssh
OPENPGP2SSH(1) BSD General Commands Manual OPENPGP2SSH(1)
NAME
openpgp2ssh -- translate OpenPGP keys to SSH keys
SYNOPSIS
openpgp2ssh < mykey.gpg
gpg --export $KEYID | openpgp2ssh $KEYID
gpg --export-secret-key $KEYID | openpgp2ssh $KEYID
DESCRIPTION
openpgp2ssh takes an OpenPGP-formatted primary key and associated subkeys on standard input, and spits out the requested equivalent SSH-style
key on standard output.
If the data on standard input contains no subkeys, you can invoke openpgp2ssh without arguments. If the data on standard input contains mul-
tiple keys (e.g. a primary key and associated subkeys), you must specify a specific OpenPGP key identifier as the first argument to indicate
which key to export. The key ID is normally the 40 hex digit OpenPGP fingerprint of the key or subkey desired, but openpgp2ssh will accept
as few as the last 8 digits of the fingerprint as a key ID.
If the input contains an OpenPGP RSA public key, it will be converted to the OpenSSH-style single-line keystring, prefixed with the key type
(`ssh-rsa'). This format is suitable (with minor alterations) for insertion into known_hosts files and authorized_keys files.
If the input contains an OpenPGP RSA secret key, it will be converted to the equivalent PEM-encoded private key.
openpgp2ssh is part of the monkeysphere(7) framework for providing a PKI for SSH.
CAVEATS
The keys produced by this process are stripped of all identifying information, including certifications, self-signatures, etc. This is
intentional, since ssh attaches no inherent significance to these features.
openpgp2ssh will produce output for any requested RSA key. This means, among other things, that it will happily export revoked keys, unveri-
fiable keys, expired keys, etc. Make sure you do your own key validation before using this tool!
EXAMPLES
gpg --export-secret-key $KEYID | openpgp2ssh $KEYID | ssh-add -c /dev/stdin
This pushes the secret key into the active ssh-agent(1). Tools such as ssh(1) which know how to talk to the ssh-agent(1) can now rely on the
key.
AUTHOR
openpgp2ssh and this man page were written by Daniel Kahn Gillmor <dkg@fifthhorseman.net>.
BUGS
openpgp2ssh only works with RSA keys. DSA keys are the only other key type available in both OpenPGP and SSH, but they are currently unsup-
ported by this utility.
openpgp2ssh only accepts raw OpenPGP packets on standard input. It does not accept ASCII-armored input. openpgp2ssh Currently only exports
into formats used by the OpenSSH. It should support other key output formats, such as those used by lsh(1) and putty(1).
Secret key output is currently not passphrase-protected.
openpgp2ssh currently cannot handle passphrase-protected secret keys on input.
SEE ALSO
pem2openpgp(1), monkeysphere(1), monkeysphere(7), ssh(1), monkeysphere-authentication(8), monkeysphere-host(8)
BSD
March 1,, 2009 BSD