I just update tm2 to the new version i can't do a pull/fetch/push using git because he don't take my privatekey ! But in the previous version this working ^^
I check the path of git, it's ok a commit for example work, if i push myself in the terminal it's working.
Maybe someone have a idea ?
same problem
On 18 Dec 2011, at 11:15, ExploZe wrote:
I just update tm2 to the new version i can't do a pull/fetch/push using git because he don't take my privatekey ! But in the previous version this working ^^
I check the path of git, it's ok a commit for example work, if i push myself in the terminal it's working.
Maybe someone have a idea ?
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
I'm encountering what may be the same issue trying to use GitHub and push a commit. Using TM1 and the terminal work fine, but TM2 fails and returns "Permission denied (publickey)." to see what's happening in TM2 I dia "ssh -vT git@github.com^R" and compared its output to the same command in TM1. Here's a snippet:
debug1: Authentications that can continue: publickey debug1: Next authentication method: publickey debug1: Offering RSA public key: /Users/alan/.ssh/id_rsa debug1: Remote: Forced command: gerve [USERNAME] debug1: Remote: Port forwarding disabled. debug1: Remote: X11 forwarding disabled. debug1: Remote: Agent forwarding disabled. debug1: Remote: Pty allocation disabled. debug1: Server accepts key: pkalg ssh-rsa blen 277 debug1: PEM_read_PrivateKey failed debug1: read PEM private key done: type <unknown> debug1: read_passphrase: can't open /dev/tty: Device not configured debug1: No more authentication methods to try. Permission denied (publickey).
Since this works in TM1 and terminal, I'm guessing there's something incomplete in my Avian configuration that's preventing it from correctly accessing the private key -- but I don't know what that is.
Thanks -Alan
On Dec 18, 2011, at 4:15 AM, ExploZe wrote:
I just update tm2 to the new version i can't do a pull/fetch/push using git because he don't take my privatekey ! But in the previous version this working ^^
I check the path of git, it's ok a commit for example work, if i push myself in the terminal it's working.
Maybe someone have a idea ?
_______________________________________________ textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
On 18 Dec 2011, at 14:37, Alan Schussman wrote:
I'm encountering what may be the same issue trying to use GitHub and push a commit. Using TM1 and the terminal work fine, but TM2 fails and returns "Permission denied (publickey)." to see what's happening in TM2 I dia "ssh -vT git@github.com^R" and compared its output to the same command in TM1. Here's a snippet:
debug1: Authentications that can continue: publickey debug1: Next authentication method: publickey debug1: Offering RSA public key: /Users/alan/.ssh/id_rsa
Is this the correct private key for the server in question?
Thinking perhaps it’s an issue of not reading .ssh/config or similar, that would otherwise have instructed it to use another key.
On Dec 18, 2011, at 6:53 AM, Allan Odgaard wrote:
On 18 Dec 2011, at 14:37, Alan Schussman wrote:
I'm encountering what may be the same issue trying to use GitHub and push a commit. Using TM1 and the terminal work fine, but TM2 fails and returns "Permission denied (publickey)." to see what's happening in TM2 I dia "ssh -vT git@github.com^R" and compared its output to the same command in TM1. Here's a snippet:
debug1: Authentications that can continue: publickey debug1: Next authentication method: publickey debug1: Offering RSA public key: /Users/alan/.ssh/id_rsa
Is this the correct private key for the server in question?
Thinking perhaps it’s an issue of not reading .ssh/config or similar, that would otherwise have instructed it to use another key.
Yes, it's the correct key. For comparison, here's the same snippet for the command run in TM1 (I'm happy to send the full output to you, Allan, if you think it will help).
debug1: Authentications that can continue: publickey debug1: Next authentication method: publickey debug1: Offering RSA public key: /Users/alan/.ssh/id_rsa debug1: Remote: Forced command: gerve [USERNAME] debug1: Remote: Port forwarding disabled. debug1: Remote: X11 forwarding disabled. debug1: Remote: Agent forwarding disabled. debug1: Remote: Pty allocation disabled. debug1: Server accepts key: pkalg ssh-rsa blen 277 debug1: Remote: Forced command: gerve ats debug1: Remote: Port forwarding disabled. debug1: Remote: X11 forwarding disabled. debug1: Remote: Agent forwarding disabled. debug1: Remote: Pty allocation disabled. debug1: Authentication succeeded (publickey). Authenticated to github.com ([207.97.227.239]:22).
I've tried the permission settings and ~/.ssh/config changes suggested at http://help.github.com/ssh-issues/ -- they don't seem to have any effect.
Thanks- -Alan
I'm encountering what may be the same issue trying to use GitHub and push a commit. Using TM1 and the terminal work fine, but TM2 fails and returns "Permission denied (publickey)."
I get the same when using bitbucket. Works fine from command line and TM1.
Thanks
Alex
-
Alan Schussman -
Alex Sullivan -
Allan Odgaard -
ExploZe -
Timothy Bates