Hello,
I want to use a shell-script to transfer data over sftp.
I donīt find a way to login in automatically.
I tried to send the password in a script like possible with
ftp
sftp user@server << cmd
password
cd /distant/directory
lcd /local/directoryget ssh_install
get ( or put) your... (2 Replies)
hello
I want to connect from server1 to server2 (Aix 5.3) with ssh, without password prompt.
So i define a ssh-key
On server1:
ssh-keygen -b 1024 -f identity -P '' -t dsa
scp identity.pub toto@server2:/tmp/identity-.pub
On server 2:
cat identity-.pub >> .ssh/authorized_keys
chmod 400... (2 Replies)
Hi,
When logging in using SSH access (to a remotely
hosted account), I received a prompt to accept
a server's key fingerprint. Wrote that string
of code down for comparision.
Already emailed my host for their listing of the
string of code for the server's key fingerprint
(for comparison,... (1 Reply)
Hi all,
I have a sshkey which I use to connect from my unix box to a linux box without any issue......
however I downloaded this same key to my laptop and tried to connect to the same linux box but it failed.....
As my laptop is running MS Vista I guessing I going have to convert it ...... (1 Reply)
Hi,
I want to use ssh to add a register key on remote ssh server. Since there are space characters in my register key string, it always failed. If there is no space characters in the string, it worked fine. The following is what I have tried. It seems that "ssh" command doesn't care about double... (9 Replies)
Hello,
Using AIX 6.1 boxes.
User user1 connects from box A to box B using ssh.
When password authentication is used everything is fine. When I configure user1 to use public key authentication sftp client works fine(no password asked), but ssh client fails. This is sshd log:
Accepted publickey... (3 Replies)
Hi, I've used the following way to set ssh public key authentication and it is working fine on Solaris 10, RedHat Linux and SuSE Linux servers without any problem. But I got error 'Server refused our key' on Solaris 8 system. Solaris 8 uses SSH2 too. Why? Please help. Thanks.
... (1 Reply)
why I can login by telnet using root account
but when i use login by ssh using root account
it is not successful ,is it different password
i am sure ssh service is started (2 Replies)
I'm stumped on an issue I'm having with RSA key based SSH logons.
I have 30 servers in a database cluster. They are all Red Hat Enterprise Linux Server release 6.4.
I want to be able to run a command on all of them from any one of them using SSH.
I generated private and public keys on... (1 Reply)
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 OPENDARWIN
dsa
DSA(1) OpenSSL DSA(1)NAME
dsa - DSA key processing
SYNOPSIS
openssl dsa [-inform PEM|DER] [-outform PEM|DER] [-in filename] [-passin arg] [-out filename] [-passout arg] [-des] [-des3] [-idea] [-text]
[-noout] [-modulus] [-pubin] [-pubout] [-engine id]
DESCRIPTION
The dsa command processes DSA keys. They can be converted between various forms and their components printed out. Note This command uses
the traditional SSLeay compatible format for private key encryption: newer applications should use the more secure PKCS#8 format using the
pkcs8
COMMAND OPTIONS -inform DER|PEM
This specifies the input format. The DER option with a private key uses an ASN1 DER encoded form of an ASN.1 SEQUENCE consisting of the
values of version (currently zero), p, q, g, the public and private key components respectively as ASN.1 INTEGERs. When used with a
public key it uses a SubjectPublicKeyInfo structure: it is an error if the key is not DSA.
The PEM form is the default format: it consists of the DER format base64 encoded with additional header and footer lines. In the case
of a private key PKCS#8 format is also accepted.
-outform DER|PEM
This specifies the output format, the options have the same meaning as the -inform option.
-in filename
This specifies the input filename to read a key from or standard input if this option is not specified. If the key is encrypted a pass
phrase will be prompted for.
-passin arg
the input file password source. For more information about the format of arg see the PASS PHRASE ARGUMENTS section in openssl(1).
-out filename
This specifies the output filename to write a key to or standard output by is not specified. If any encryption options are set then a
pass phrase will be prompted for. The output filename should not be the same as the input filename.
-passout arg
the output file password source. For more information about the format of arg see the PASS PHRASE ARGUMENTS section in openssl(1).
-des|-des3|-idea
These options encrypt the private key with the DES, triple DES, or the IDEA ciphers respectively before outputting it. A pass phrase is
prompted for. If none of these options is specified the key is written in plain text. This means that using the dsa utility to read in
an encrypted key with no encryption option can be used to remove the pass phrase from a key, or by setting the encryption options it
can be use to add or change the pass phrase. These options can only be used with PEM format output files.
-text
prints out the public, private key components and parameters.
-noout
this option prevents output of the encoded version of the key.
-modulus
this option prints out the value of the public key component of the key.
-pubin
by default a private key is read from the input file: with this option a public key is read instead.
-pubout
by default a private key is output. With this option a public key will be output instead. This option is automatically set if the input
is a public key.
-engine id
specifying an engine (by it's unique id string) will cause req to attempt to obtain a functional reference to the specified engine,
thus initialising it if needed. The engine will then be set as the default for all available algorithms.
NOTES
The PEM private key format uses the header and footer lines:
-----BEGIN DSA PRIVATE KEY-----
-----END DSA PRIVATE KEY-----
The PEM public key format uses the header and footer lines:
-----BEGIN PUBLIC KEY-----
-----END PUBLIC KEY-----
EXAMPLES
To remove the pass phrase on a DSA private key:
openssl dsa -in key.pem -out keyout.pem
To encrypt a private key using triple DES:
openssl dsa -in key.pem -des3 -out keyout.pem
To convert a private key from PEM to DER format:
openssl dsa -in key.pem -outform DER -out keyout.der
To print out the components of a private key to standard output:
openssl dsa -in key.pem -text -noout
To just output the public part of a private key:
openssl dsa -in key.pem -pubout -out pubkey.pem
SEE ALSO dsaparam(1), gendsa(1), rsa(1), genrsa(1)0.9.7d 2003-11-20 DSA(1)