version 1.2, 2000/04/06 21:28:22 |
version 1.3, 2000/04/12 07:45:43 |
|
|
$Id$ |
$Id$ |
|
|
|
howto: |
|
1) generate server key: |
|
$ umask 077 |
|
$ openssl dsaparam 1024 -out dsa1024.pem |
|
$ openssl gendsa -out /etc/ssh_dsa_key dsa1024.pem -rand /dev/arandom |
|
2) enable ssh2: |
|
server: add 'Protocol 2,1' to /etc/sshd_config |
|
client: ssh -o 'Protocol 2,1', or add to .ssh/config |
|
|
works: |
works: |
secsh-transport: works w/o rekey |
secsh-transport: works w/o rekey |
proposal exchange, i.e. different enc/mac/comp per direction |
proposal exchange, i.e. different enc/mac/comp per direction |
|
|
tcp-forwarding: -L works |
tcp-forwarding: -L works |
dss: verification works, |
dss: verification works, |
key database in ~/.ssh/known_hosts with bits == 0 hack |
key database in ~/.ssh/known_hosts with bits == 0 hack |
dss: signature works, keygen w/ openssl: |
dss: signature works, keygen w/ openssl |
$ umask 077 |
|
$ openssl dsaparam 1024 -out dsa1024.pem |
|
$ openssl gendsa -out /etc/ssh_dsa_key dsa1024.pem -rand /dev/arandom |
|
start sshd with '-2' flag |
|
client interops w/ sshd2, lshd |
client interops w/ sshd2, lshd |
server interops w/ ssh2, lsh, ssh.com's Windows client, SecureCRT |
server interops w/ ssh2, lsh, ssh.com's Windows client, SecureCRT |
server supports multiple concurrent sessions (e.g. with SSH.com Windows client) |
server supports multiple concurrent sessions (e.g. with SSH.com Windows client) |