search for: testkey

...at the first connection test "make test" for openssh with openssl-0.9.6m returns no errors (i don't get errors for openssh with openssl-0.9.7g on Linux) i found the following problem: ssh-keygen creates a corrupt public key for rsa1 ("keygen -t rsa1" and "keygen -yf testkey") the public key starts with a sequence of 0 and has only a few digits at the end keygen -l returns key lengths between 80 and 128 for diffent keygen runs the corrupt key isn't accepted in authorized_keys (while the correct pub key from another system is) rsa and dsa have no problems fra...

Nigel Kersten and I had previously worked on a plist provider spec for Mac OS X. Attached is a PDF of the current state. I would appreciate any input and criticisms. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To

Hi, is there a particular reason why this feature is "user" based and not "user-pubkey" based? What I mean is that it works for installation with small number of pubkeys per user. But imagine i.e. a GitHub scale - all users logging in as user "git". On each auth request all the keys from database would be fetched and feeded to OpenSSH. Now I am only asking this out

...he encrypted string, and whoever is reading the file must recognise the key type (either here or in the prior sequence of public keys) and use it to know how many bits and pieces to expect. As evidence I attach a test key file that I just generated using the command "./ssh-keygen -t rsa -o -f testkey" and no passphrase. Hex-dumping the base64 content, the relevant section is here: 00000140 DE DF 00 00 03 C8 92 77 30 13 92 77 30 13 00 00 .......w0..w0... 00000150 00 07 73 73 68 2D 72 73 61 00 00 01 01 00 AC 84 ..ssh-rsa....... Offset 0x142 is just beyond the end of the public key compon...

https://bugzilla.mindrot.org/show_bug.cgi?id=3153 Bug ID: 3153 Summary: Prefer user specified keys to avoid the agent overloading MaxAuthTries before even trying the key that was specified Product: Portable OpenSSH Version: 8.2p1 Hardware: Other OS: Linux Status: NEW

Hey folks - I''m running into some weirdness getting ssh keys realized properly. The manifest I''m working with is here: http://www.pastie.org/1744771 . I''m using 2.6.3 epel repo on a Centos 5.5 box . The expected behaviour is to have the user created and their public key put in their authorized_keys as well as the studio_app user''s authorized_keys. What ends

http://bugzilla.mindrot.org/show_bug.cgi?id=884 dtucker at zip.com.au changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #663 is|0 |1 obsolete| | ------- Additional Comments From dtucker at zip.com.au 2004-10-29 22:03 -------

...pletely about this, this must be an SSH bug which is likely because I'm using Gentoo as the SSH server. When trying to forward X11 connections, I get X11 connection rejected because of wrong authentication. kwrite: cannot connect to X server XXXXXXXXX:10.0 Using command ssh -Y -p 1111 -4 -i testkey test at 127.0.0.1 I'm not using any X11 library build with ipv6 support. I tried building the relevant library (after seeing the dependency of the X11 application) with ipv6 support, but it was of no help. Of course first I did not use -4. In the server, I've tried disabling ipv6 support...