| 1 & 2. Use ssh -v, that'll tell you the encryption algorithm and | strength being used.
This is the output i am getting ssh -v localhost OpenSSH_3.4p1, SSH protocols 1.5/2.0, OpenSSL 0x0090602f debug1: Reading configuration data /etc/ssh/ssh_config debug1: Rhosts Authentication disabled, originating port will not be trusted. debug1: ssh_connect: needpriv 0 debug1: Connecting to localhost [127.0.0.1] port 22. debug1: Connection established. debug1: identity file /root/.ssh/identity type -1 debug1: identity file /root/.ssh/id_rsa type -1 debug1: identity file /root/.ssh/id_dsa type -1 debug1: Remote protocol version 1.99, remote software version OpenSSH_3.4p1 debug1: match: OpenSSH_3.4p1 pat OpenSSH* Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_3.4p1 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client aes128-cbc hmac-md5 none debug1: kex: client->server aes128-cbc hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: dh_gen_key: priv key bits set: 120/256 debug1: bits set: 1551/3191 debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Host 'localhost' is known and matches the RSA host key. debug1: Found key in /root/.ssh/known_hosts:1 debug1: bits set: 1595/3191 debug1: ssh_rsa_verify: signature correct debug1: kex_derive_keys debug1: newkeys: mode 1 debug1: SSH2_MSG_NEWKEYS sent debug1: waiting for SSH2_MSG_NEWKEYS debug1: newkeys: mode 0 debug1: SSH2_MSG_NEWKEYS received debug1: done: ssh_kex2. debug1: send SSH2_MSG_SERVICE_REQUEST debug1: service_accept: ssh-userauth debug1: got SSH2_MSG_SERVICE_ACCEPT debug1: authentications that can continue: publickey,password debug1: next auth method to try is publickey debug1: try privkey: /root/.ssh/identity debug1: try privkey: /root/.ssh/id_rsa debug1: try privkey: /root/.ssh/id_dsa debug1: next auth method to try is password can understand much from this geek debug data. The algorithms you're referring to are symmetric | algorithms, and won't use 1024-bit keys: more in the region of 128-256 | bits. I need to use 1024 bit ketys. What should I do? ANy nice lil manual for this ? | 3. Depends on whether you're referring to the server or the client. The | server keys are typically created when the server software is | installed. The client keys are created whenever you run ssh-keygen. I want to re-install the server keys after i change my encrytion to 3DES and 1024 bit keys. Then, obviously want to generate the client key too with the new 1024 bit keys/ | 4, Define `my own key combination'. You can specify the number of | bits in your client key when using ssh-keygen. You cannot create a | keypair with a specific fingerprint. To tell you actually, i am not very comfortable about this fingerprint business. Please do point to me to a nice link where i can read and learn on my own :-). | | There's lots of stuff on these available on the 'net. If you can't | locate it, let me know -- I give encryption tutorials for a nominal | fee (usual nominal fee being half your kingdom and your daughter's | hand in marriage ;-) | lots of stuff on the net would be nice cause, if i will pay u tution fees, then what i have to offer is 1. lots of linux problems bursting my head ( thats half my kingdom). 2. godwillingly, if i am blessed with a daughter, then after 30 years, she should be ready to marry an Old man who is a linux Geek :-)) | Arvind> this is my sshd process running root 16207 1 1 09:28 ? | Arvind> 00:00:01 /usr/sbin/sshd root 16212 16207 0 09:29 ? | Arvind> 00:00:00 /usr/sbin/sshd | | Arvind> how do i know if it is in the chroot jail ? hey what about the chroot jail ? Arvind ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Oh, it's good to be a geek. http://thinkgeek.com/sf _______________________________________________ linux-india-help mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/linux-india-help
