generating a ssh key without ssh-keygen

I have a server that runs linux (REDHAT) and a client running Solaris.
I'd like to connect to the server sshd using a ssh client but the I
don't have ssh-keygen in the client.
Is there a way in which I can generate the required public and private
keys on my server and then put it on my client?

abi

Abi wrote:
> I have a server that runs linux (REDHAT) and a client running Solaris.
> I'd like to connect to the server sshd using a ssh client but the I
> don't have ssh-keygen in the client.
> Is there a way in which I can generate the required public and private
> keys on my server and then put it on my client?
>
> abi
>

? I don't quite follow. You know how to use ssh-keygen, and if you have
said program on your server you can use it to create a key-pair. Use a
floppy and take it to your client. Are you asking how to do this whole
process? are you asking how to initiate a ssh connection using a key?

clg

In article <(E-Mail Removed)>, Abi wrote:

>I have a server that runs linux (REDHAT) and a client running Solaris.
>I'd like to connect to the server sshd using a ssh client but the I
>don't have ssh-keygen in the client.
>Is there a way in which I can generate the required public and private
>keys on my server and then put it on my client?

I could send you one. What are the username and IP address where you
intend to install it ?

Or you could generate them on the server and save them to filenames not
already in use.

--
Elvis Notargiacomo http://www.sendacow.org.uk/homepage.html

In article <(E-Mail Removed)>,
all mail refused <(E-Mail Removed)> wrote:
>In article <(E-Mail Removed)>, Abi wrote:
>
>>I have a server that runs linux (REDHAT) and a client running Solaris.
>>I'd like to connect to the server sshd using a ssh client but the I
>>don't have ssh-keygen in the client.
>>Is there a way in which I can generate the required public and private
>>keys on my server and then put it on my client?
>
>I could send you one. What are the username and IP address where you
>intend to install it ?

Hopefully that's a joke. In case it's not obvious, doing this would
be the equivalent of giving out the password to the account in question.

>Or you could generate them on the server and save them to filenames not
>already in use.

There's a good chance ssh-keygen really is on the client (it's required
to generate the host keys if sshd is installed) but you can generate
keys on the server and copy them:

[Server]
$ ssh-keygen -t rsa -f $HOME/.ssh/tmp_rsa
(Enter pass phrase)
$ cat $HOME/.ssh/tmp_rsa.pub >>$HOME/.ssh/authorized_keys
(if you want to allow the new key to access the server)

[Client]
$ scp server:.ssh/tmp_rsa $HOME/.ssh/id_rsa
$ scp server:.ssh/tmp_rsa.pub $HOME/.ssh/id_rsa.pub

Once you've tested it, delete the tmp files from the server.

--
Darren Tucker (dtucker at zip.com.au)
GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4 37C9 C982 80C7 8FF4 FA69
Good judgement comes with experience. Unfortunately, the experience
usually comes from bad judgement.

Abi <(E-Mail Removed)> wrote in
news:(E-Mail Removed):

>
> I have a server that runs linux (REDHAT) and a client running Solaris.
> I'd like to connect to the server sshd using a ssh client but the I
> don't have ssh-keygen in the client.
> Is there a way in which I can generate the required public and private
> keys on my server and then put it on my client?
>

OpenSSH works well on Solaris as well. Why dont you upgrade the solaris
box?


P.Krumins

On Mon, 12 Jan 2004 23:10:39 +0530, Abi <(E-Mail Removed)> wrote:
>
> I have a server that runs linux (REDHAT) and a client running Solaris.
> I'd like to connect to the server sshd using a ssh client but the I
> don't have ssh-keygen in the client.
> Is there a way in which I can generate the required public and private
> keys on my server and then put it on my client?

I don't think it matters what Unix like system you generate ssh keys on,
any more than it matters (it doesn't) which systems you use your public
key (authorized_keys) on. I use the same authorized keys generated in
Linux for Linux, Solaris, FreeBSD and NetBSD servers.

However, if you generate private keys on a server, you probably want to
remove them promptly for safe keeping, especially if you use any without a
strong passphrase.

--
David Efflandt - All spam ignored http://www.de-srv.com/

Carl <moc.erawtfosdigir@treblig_tnomal> writes:

> ? I don't quite follow. You know how to use ssh-keygen, and if you
> have said program on your server you can use it to create a key-pair.

Thanks for all your replies.
the problem was that when I generate a private and public key pair on
the server, I get the server name added to the private key. So, when
I copied that file on to the client and ran

$ ssh server -l username

it still asked me for a password. this is what I ran on the server

$ ssh-keygen -t dsa -f ./private
$ cat ./private.pub >> ./ssh/authorized_keys
$ ftp client
mput ./private

and in the client

$ mv ./private .ssh/id_dsa

is there something wrong in what I do.
Hope I am clear

abi

Abi wrote:
> Carl <moc.erawtfosdigir@treblig_tnomal> writes:
>
>
>>? I don't quite follow. You know how to use ssh-keygen, and if you
>>have said program on your server you can use it to create a key-pair.
>
>
> Thanks for all your replies.
> the problem was that when I generate a private and public key pair on
> the server, I get the server name added to the private key. So, when
> I copied that file on to the client and ran
>

they name of the key is irrelevant. You can rename it at your leisure.


> $ ssh server -l username
>
> it still asked me for a password. this is what I ran on the server
>

did you enter an empty passphrase for your key you generated?

> $ ssh-keygen -t dsa -f ./private
> $ cat ./private.pub >> ./ssh/authorized_keys
> $ ftp client
> mput ./private
>
> and in the client
>
> $ mv ./private .ssh/id_dsa
>
> is there something wrong in what I do.
> Hope I am clear
>
> abi

try this

ssh -2v server -l username

that should force protocol 2 and give more detail about the failure.

oh and be sure to check the permissions on your key files on both the
server and the client.

my authorized_keys file is 700

I tested exactly what you did, sans the file transfers and it works
fine, with the -2.

Also note that dsa has issues and perhaps the server admin disabled dsa
keys, try it with rsa.


cl



im using a windows client so I cant help there...