search for: ede3

...-128-ecb camellia-192-cbc camellia-192-ecb camellia-256-cbc camellia-256-ecb cast cast-cbc cast5-cbc cast5-cfb cast5-ecb cast5-ofb des des-cbc des-cfb des-ecb des-ede des-ede-cbc des-ede-cfb des-ede-ofb des-ede3 des-ede3-cbc des-ede3-cfb des-ede3-ofb des-ofb des3 desx rc2 rc2-40-cbc rc2-64-cbc rc2-cbc rc2-cfb rc2-ecb rc2-ofb rc4 rc4-40 seed seed-cbc seed-cfb seed-ecb...

...c > camellia-192-ecb  camellia-256-cbc  camellia-256-ecb  cast > cast-cbc          cast5-cbc         cast5-cfb         cast5-ecb > cast5-ofb         des               des-cbc           des-cfb > des-ecb           des-ede           des-ede-cbc       des-ede-cfb > des-ede-ofb       des-ede3          des-ede3-cbc      des-ede3-cfb > des-ede3-ofb      des-ofb           des3              desx > rc2               rc2-40-cbc        rc2-64-cbc        rc2-cbc > rc2-cfb           rc2-ecb           rc2-ofb           rc4 > rc4-40            seed              seed-cbc          seed-c...

...bit keypairs to 4096 bits, it really doesn't matter that much, because they're still only encrypted with 3DES, which provides an effective 112 bits of symmetric encryption strength: $ head -4 ~/.ssh/id_rsa -----BEGIN RSA PRIVATE KEY----- Proc-Type: 4,ENCRYPTED DEK-Info: DES-EDE3-CBC,XXXXXXXXXXXXXXXX $ According to NIST[1][2], a minimum of 112-bit symmetric / 2048-bit asymmetric keystrength is recommended for protection up until about 2030. For protection beyond 2030, or for the paranoid, larger keysizes are recommended. Other recommendations (e.g., those of ECRYPT...

...hangs and sits at: ... debug2: service_accept: ssh-userauth debug1: SSH2_MSG_SERVICE_ACCEPT received I don't know why the error 'Not a RSA1 key file' comes up, as my private key (id_rsa) remains unchanged and begins: -----BEGIN RSA PRIVATE KEY----- Proc-Type: 4,ENCRYPTED DEK-Info: DES-EDE3-CBC,... Other points of interest: 'ssh-keygen -B' correctly identifies my private key and returns what appears to be a valid bubble-babble digest, beginning with '1024 ...' 'ssh-keygen -l' correctly identifies my private key and returns what appears to be a valid finger...

http://bugzilla.mindrot.org/show_bug.cgi?id=887 Summary: Problem connecting OpenSSH Client to a F-Secure SSH Server Product: Portable OpenSSH Version: -current Platform: All OS/Version: other Status: NEW Severity: major Priority: P2 Component: sftp AssignedTo: openssh-bugs at

...(0x0) andreas at lukas:~$ ls -al .ssh/id_rsa* -rw------- 1 andreas andreas 951 Aug 2 2003 .ssh/id_rsa -rw-r--r-- 1 andreas andreas 223 Aug 2 2003 .ssh/id_rsa.pub andreas at lukas:~$ head -n3 .ssh/id_rsa -----BEGIN RSA PRIVATE KEY----- Proc-Type: 4,ENCRYPTED DEK-Info: DES-EDE3-CBC,483908A29B0FB1E5 first i believed in a subtily broken binary but i got the same error when deinstalling, purging and reinstalling a newly downloaded package. i have not found a similar error with google. please advice.

I've just compiled and installed openssh-2.9.9p2 (compiled against openssl-0.9.6b using gcc-3.0.0) on a Slackware 7-based Linux machine (kernel 2.4.6ac2). The previously installed version was 2.9p2, compiled against openssl-0.9.6a, also with gcc-3.0.0, but with a different build of gcc-3.0.0. Everything seems to work fine except for one problem: passphrase matching for ssh2 keys

http://bugzilla.mindrot.org/show_bug.cgi?id=1337 Summary: SCP performance twice as slow as RCP Product: Portable OpenSSH Version: 3.8.1p1 Platform: Other OS/Version: AIX Status: NEW Severity: enhancement Priority: P3 Component: scp AssignedTo: bitbucket at mindrot.org ReportedBy:

...bit keypairs to 4096 bits, it really doesn't matter that much, because they're still only encrypted with 3DES, which provides an effective 112 bits of symmetric encryption strength: $ head -4 ~/.ssh/id_rsa -----BEGIN RSA PRIVATE KEY----- Proc-Type: 4,ENCRYPTED DEK-Info: DES-EDE3-CBC,XXXXXXXXXXXXXXXX $ According to NIST[1][2], a minimum of 112-bit symmetric / 2048-bit asymmetric keystrength is recommended for protection up until about 2030. For protection beyond 2030, or for the paranoid, larger keysizes are recommended. Other recommendations (e.g., those of ECRYPT...