Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 1193

Summary: Error in /etc/init.d/sshd - wrong parameters to ssh-keygen?
Product: Gentoo Linux Reporter: Rickard Andersson <arpen>
Component: Current packagesAssignee: Martin Schlemmer (RETIRED) <azarah>
Status: RESOLVED FIXED    
Severity: normal    
Priority: High    
Version: 1.0 RC6 r14   
Hardware: x86   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---

Description Rickard Andersson 2002-03-16 19:30:06 UTC
When I try to start sshd I get an error when the script tries to generate the 
Hostkey. The RSA-Hostkey and DSA-Hostkey get generated though.

The results in that SSH1 is disabled as the daemon starts. Not that anyone 
misses SSH1, but it's kinda ugly.

root@kennel root # /etc/init.d/sshd start
 * Generating Hostkey...
You must specify a key type (-t).
Usage: ssh-keygen [options]
Options:
  -b bits     Number of bits in the key to create.
  -c          Change comment in private and public key files.
  -e          Convert OpenSSH to IETF SECSH key file.
  -f filename Filename of the key file.
  -i          Convert IETF SECSH to OpenSSH key file.
  -l          Show fingerprint of key file.
  -p          Change passphrase of private key file.
  -q          Quiet.
  -y          Read private key file and print public key.
  -t type     Specify type of key to create.
  -B          Show bubblebabble digest of key file.
  -C comment  Provide new comment.
  -N phrase   Provide new passphrase.
  -P phrase   Provide old passphrase.
 * Starting sshd...
Could not load host key: /etc/ssh/ssh_host_key
Disabling protocol version 1. Could not load host key                                        
 [ ok ]
root@kennel root #
Comment 1 Martin Schlemmer (RETIRED) gentoo-dev 2002-03-16 23:40:33 UTC
I think this is fixed in the latest openssh, just remerge it and update
/etc/init.d/sshd
Comment 2 Rickard Andersson 2002-03-17 19:58:33 UTC
Yup, it is. I noticed right after I entered the bug. Should I make the bug as closed now or what?