Public bug reported:

Whenever I press Enter instead of putting in passphrase in ssh-keygen,
login password is stored and requested anyway.

I found "PermitEmptyPasswords no" in /etc/ssh/sshd_config and changed
"no" to "yes".

Then I restarted ssh daemon, but problem persisted. But this IMHO isn't
problem of ssh daemon, but keygen itself.

I didn't find parameter in /etc/ssh/ssh_config which would allow me to
generate key without password.

I tried to google for some help about empty password, but all I found
was generic stuff for other distributions (skipping password as usual).

I consider this usability bug, because it affects automation (like
backup via ssh) as redundant and repetitive input is required, and
introduces confusion.

Also approach "User is moron, who is not psychically adept in deciding
what he wants", which could lead to this bug as well is _not_ good
practise.

Please, fix this. Let ssh-keygen create keys without passwords by
default.

If not, at least modify ssh-keygen, so it doesn't confuse user by
sentence "Enter passphrase (empty for no passphrase):" which clearly
lies.

Sorry for tone of report, if you feel it's sharp. I'm very upset about
this issue as I spent some time searching for help to no avail.

U use Ubuntu Lucid, fully up to date, openssh 1:5.2p1-2ubuntu1.

** Affects: openssh (Ubuntu)
     Importance: Undecided
         Status: New

-- 
SSH uses login password even when empty password was specified in ssh-keygen
https://bugs.launchpad.net/bugs/511668
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to