La inserción de SSH en github falla, pero puede autenticarse

Por alguna razón parece que no puedo push a Github usando Powershell , pero parece que CygWin funciona sin problemas.

Estoy trabajando en la configuration de envíos automáticos a un repository usando el Progtwigdor de tareas, y simplemente parece ser más eficiente usando Powershell para eso.

Lo que me molesta es que soy perfectamente capaz de ingresar a mi count usando ssh -T github@github.com y el file de configuration parece estar configurado correctamente también. Ver debajo de la image:

enter image description here

Desde mi comprensión básica de Git, el post de error que me dan al presionar simplemente dice que podría no estar autenticado correctamente. Pero mirando mi ssh ¿parece que estoy autenticado?

Esta es mi configuration:

 [core] repositoryformatversion = 0 filemode = false bare = false logallrefupdates = true symlinks = false ignorecase = true [remote "origin"] url = git@github.com:Somename/SomeRepo.git fetch = +refs/heads/*:refs/remotes/origin/* 

El script progtwigdo:

 echo "cool" git add . git commit -m "some stuff" git push origin master 

Salida ssh -vT git@github.com :

 MVC master $ ssh -v git@github.com OpenSSH_5.4p1, OpenSSL 1.0.0 29 Mar 2010 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Connecting to github.com [192.30.253.112] port 22. debug1: Connection established. debug1: identity file /.ssh/id_rsa type -1 debug1: identity file /.ssh/id_rsa-cert type -1 debug1: identity file /.ssh/id_dsa type -1 debug1: identity file /.ssh/id_dsa-cert type -1 debug1: Remote protocol version 2.0, remote software version libssh-0.7.0 debug1: no match: libssh-0.7.0 debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.4 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client aes128-ctr hmac-sha1 none debug1: kex: client->server aes128-ctr hmac-sha1 none debug1: sending SSH2_MSG_KEXDH_INIT debug1: expecting SSH2_MSG_KEXDH_REPLY debug1: Host 'github.com' is known and matches the RSA host key. debug1: Found key in /.ssh/known_hosts:1 debug1: ssh_rsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: Roaming not allowed by server debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey debug1: Next authentication method: publickey debug1: Offering public key: C:\\Users\\Todai\\.ssh\\ps_id_rsa debug1: Server accepts key: pkalg ssh-rsa blen 279 debug1: Authentication succeeded (publickey). debug1: channel 0: new [client-session] debug1: Entering interactive session. PTY allocation request failed on channel 0 debug1: client_input_channel_req: channel 0 rtype exit-status reply 0 Hi SomeName! You've successfully authenticated, but GitHub does not provide shell access. debug1: channel 0: free: client-session, nchannels 1 Connection to github.com closed. Transfernetworking: sent 2640, received 1992 bytes, in 0.2 seconds Bytes per second: sent 13538.5, received 10215.4 debug1: Exit status 1 

git config --list :

 MVC master $ git config --list core.symlinks=false core.autocrlf=true core.fscache=true color.diff=auto color.status=auto color.branch=auto color.interactive=true help.format=html http.sslcainfo=C:/Program Files/Git/mingw64/ssl/certs/ca-bundle.crt diff.astextplain.textconv=astextplain rebase.autosquash=true cnetworkingential.helper=manager filter.lfs.clean=git-lfs clean -- %f filter.lfs.smudge=git-lfs smudge -- %f filter.lfs.requinetworking=true user.name=todai88 user.email=joabaj88@gmail.com cnetworkingential.helper=manager core.repositoryformatversion=0 core.filemode=false core.bare=false core.logallrefupdates=true core.symlinks=false core.ignorecase=true remote.origin.url=git@github.com:SomeName/PluralSight_MVC.git remote.origin.fetch=+refs/heads/*:refs/remotes/origin/* user.name=SomeName user.email=SomeEmail@email.com