Yeah... all the keys are there. Only in user ssh-keys it shows not
ready.
On Jun 17, 9:57 am, Johan Sørensen <[email protected]> wrote:
> On Wed, Jun 17, 2009 at 2:55 PM, Wilton
>
>
>
> Ferreira<[email protected]> wrote:
> > Now I see a strange behavior in the ssh keys.
>
> > First the application work normally my user have one key with a
> > "ready" key.
> > Later I go there and insert a new ssh-key, and the ssh-key is not
> > ready. All the new keys for other users don't get ready.
>
> > Looking at the application:
> > 1. poller running with git user and on environment "production"
> > 2. activemq running by the user "activemq" (ubuntu-install)
> > 3. git/.ssh/authorized_keys have the 02 ssh-keys
> > 4. database ssh-keys have the keys too.
> > 5. in log/message_processing.log
> > SshKeyProcessor consuming message. Command: add_to_authorized_keys.
> > Arguments: ### START KEY 13 ### command="gitorious wilton",no-port-
> > forwarding,no-X11-forwarding,no-agent-forwarding,no-pty ssh-rsa
> > <the_key> SshKey:13-User:3
>
> > The difference with the ready and non ready keys is the "u...@host" in
> > the final.
> > Project and repositories are working normal.
>
> Are the keys actually getting added to $GIT_USER_HOME/.ssh/authorized_keys?
>
> JS
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Gitorious" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/gitorious?hl=en
-~----------~----~----~----~------~----~------~--~---
