creating ssh key with no passphrase

Hi,

I'm trying to create an ssh key automatically with no passphrase but
ssh-keygen -q -f ~/.ssh/id_rsa -t rsa -N="" would tell me:
passphrase too short: have 1 bytes, need > 4
How am I able to create a key for automatic file exchange with no human
interaction?

Thank you!
Ron

Ron Eggler wrote:

> Hi,
>
> I'm trying to create an ssh key automatically with no passphrase but
> ssh-keygen -q -f ~/.ssh/id_rsa -t rsa -N="" would tell me:
> passphrase too short: have 1 bytes, need > 4
> How am I able to create a key for automatic file exchange with no human
> interaction?
>
> Thank you!
> Ron
Ah, I'm not sure if I got it, I tried:
ssh-keygen -N '' -C backup1 -t rsa -f ~/.ssh/id_rsa
and copied the ~/.ssh/id_rsa.pub porrtion into the server's
~/.ssh/known_hosts but for some reason it wouldn't let me in... :( Any
ideas what i could have done wrong? Or is my keygen command "corrupt"?
Thank you!
--
chEErs roN

Ron Eggler wrote:
> Ron Eggler wrote:
>
>> Hi,
>>
>> I'm trying to create an ssh key automatically with no passphrase but
>> ssh-keygen -q -f ~/.ssh/id_rsa -t rsa -N="" would tell me:
>> passphrase too short: have 1 bytes, need > 4
>> How am I able to create a key for automatic file exchange with no human
>> interaction?
>>
>> Thank you!
>> Ron
> Ah, I'm not sure if I got it, I tried:
> ssh-keygen -N '' -C backup1 -t rsa -f ~/.ssh/id_rsa
> and copied the ~/.ssh/id_rsa.pub porrtion into the server's
> ~/.ssh/known_hosts but for some reason it wouldn't let me in... :( Any
> ideas what i could have done wrong? Or is my keygen command "corrupt"?
> Thank you!

Leave out the -N option. This will prompt you for a password, and let
you hit enter for a blank password.

Joe Beasley wrote:

> Ron Eggler wrote:
>> Ron Eggler wrote:
>>
>>> Hi,
>>>
>>> I'm trying to create an ssh key automatically with no passphrase but
>>> ssh-keygen -q -f ~/.ssh/id_rsa -t rsa -N="" would tell me:
>>> passphrase too short: have 1 bytes, need > 4
>>> How am I able to create a key for automatic file exchange with no human
>>> interaction?
>>>
>>> Thank you!
>>> Ron
>> Ah, I'm not sure if I got it, I tried:
>> ssh-keygen -N '' -C backup1 -t rsa -f ~/.ssh/id_rsa
>> and copied the ~/.ssh/id_rsa.pub porrtion into the server's
>> ~/.ssh/known_hosts but for some reason it wouldn't let me in... :( Any
>> ideas what i could have done wrong? Or is my keygen command "corrupt"?
>> Thank you!
>
> Leave out the -N option. This will prompt you for a password, and let
> you hit enter for a blank password.
Joe, I want to be able to generate the key without any user interaction.
So the -N option is needed. The problem i have now is, that the public key I
pasted into ~/.ssh/authorized_keys wouldn't work. It doesn't let me in...
(
Aany ideas what could be the problem?
Both, server & client are using ssh2.

--
chEErs roN

On Mon, 17 Mar 2008 22:24:31 +0000, Ron Eggler wrote:

> Ah, I'm not sure if I got it, I tried: ssh-keygen -N '' -C backup1 -t
> rsa -f ~/.ssh/id_rsa and copied the ~/.ssh/id_rsa.pub porrtion into the
> server's ~/.ssh/known_hosts but for some reason it wouldn't let me in...
> Any ideas what i could have done wrong? Or is my keygen command
> "corrupt"?

It looks like you found your previous problem (-N=""). As to why the key
is not working, you need to put the public part in the destination
login's authorized_keys2 file.

known_hosts doesn't solve the client authentication problem (let me
login!) but the server authentication problem (is the server into which
I'm logging in really what I think it is?).

BTW, I'd not generally name the key id_rsa. That has a special meaning.
I'd call it something else, and then explicitly use it either via "ssh -i
keyname" or by placing an entry for the server in the client login's
~/.ssh/config file.

- Andrew