On Sunday, December 25, 2016 at 1:58:40 AM UTC, Maxie Schmidt wrote: > > What other ways do you suggest I try? ssh-copy-id fails with the > same Permission denied (publickey) error. Is there another way to upload > keys to the trac server? >
the only user-allowed way is via the web interface. Once a key gets entered there, it gets copied into a trac store. I can see your (updated) key in this store. The store itself is not used by the sshd to allow logins. There is a process that updates the file (authorized_keys file of the git user account) responsible for the latter. And this process does not want to copy your key from the store for the reason unknown (perhaps there is some blacklisting going on, I don't know). After learning how to use auditd, I found the process to be certain GCE-specific python script called manage_accounts. I have no idea whether any manual intervention is possible without breaking things. We are seriously out of luck here, as we have only very few people who know more details about this GCE-specific trac/git connection, and they are most probably either on vacation, or insanely busy (or both :-)). Perhaps a temporary way out for you would be to push your Sage branches to a github repo and let your trac tickets refer to these branches. Sorry for not being more helpful at this point. Dima -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
