{"issue":{"created_at":"2011-08-19T01:59:59Z","state":"closed","updated_at":"2011-12-12T09:36:02Z","user":{"gravatar_id":"f1acc6318028fdba9874c77bc622a2fb","id":6088,"url":"https://api.github.com/users/bitprophet","avatar_url":"https://secure.gravatar.com/avatar/f1acc6318028fdba9874c77bc622a2fb?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","login":"bitprophet"},"comments":12,"body":"### Description\n\nMachine Fabric runs on: Windows 7  \r\nMachine I try to connect to: Ubuntu 10.04.1\r\n\r\nI'm trying to use public key authentication with a freshly generated keypair.\r\n\r\nThis is my fabfile:\r\n\r\n    from fabric.api import *\r\n    from fabric.operations import *\r\n\r\n    env.host = ['user@host']\r\n    env.key_filename = r'S:\\server.priv.ppk'\r\n\r\n    def ver():\r\n        run('uname -a')\r\n\r\nAnd this is what I see when I run it:\r\n\r\n    S:\\Fabric>fab --show=debug ver\r\n    Using fabfile 'S:\\Fabric\\fabfile.py'\r\n    Commands to run: ver\r\n    [user@host] Executing task 'ver'\r\n    [user@host] run: /bin/bash -l -c \"uname -a\"\r\n    Please enter passphrase for private key:\r\n    Password for user@host [Enter for previous]:\r\n    Stopped.\r\n    \r\nI aborted when I was asked for the password.\r\n\r\nWhen I point PuTTY to this private key and connect, typing my passphrase once incorrectly and once correctly, it looks like this:\r\n    Using username \"user\".\r\n    Authenticating with public key \"rsa-key-20101205\"\r\n    Passphrase for key \"rsa-key-20101205\":\r\n    Wrong passphrase\r\n    Authenticating with public key \"rsa-key-20101205\"\r\n    Passphrase for key \"rsa-key-20101205\":\r\n    Linux MyHostName 2.6.32-25-server #45-Ubuntu SMP Sat Oct 16 20:06:58 UTC 2010 x86_64 GNU/Linux\r\n    Ubuntu 10.04.1 LTS\r\n\r\n    Welcome to the Ubuntu Server!\r\n    * Documentation:  http://www.ubuntu.com/server/doc\r\n\r\nNote that:\r\n\r\n* I cannot tell if it has picked up the right private key, because the path to the key is not displayed (PuTTY doesn't either), not even on debug. Can I turn this on?\r\n* I cannot tell if it has picked up the right private key, because the name of the key is not displayed (PuTTY does), not even on debug. Can I turn this on?\r\n* It doesn't say that my passphrase is invalid when I enter the wrong one intentionally (PuTTY does).\r\n* What it does is complain if the private key file is not accessible.\r\n\r\nI tried to pass the path to the private key...\r\n\r\n* ... as a command line argument (-i)\r\n* ... in my code (`env.key_filename = r'S:\\server.priv.ppk'`)\r\n* ... in an rcfile (`key_filename = S:\\server.priv.ppk`)\r\n\r\nAll have exactly the same effect, as described above.\r\n\r\nI'm not really sure where to go from here. Is there anyway to tell Fabric to display what it is trying to do and why it fails?\n\n----\n\nOriginally submitted by **Henrik Heimbuerger** ([hheimbuerger](https://github.com/hheimbuerger)) on **2010-12-05** at **02:33pm EST**\n\n### Relations\n\n* Related to #269: Improve display/debugging of key authentication mechanisms\n\n\n----\n\nClosed as *Worksforme* on **2010-12-30** at **02:25pm EST**","assignee":{"gravatar_id":"f1acc6318028fdba9874c77bc622a2fb","id":6088,"url":"https://api.github.com/users/bitprophet","avatar_url":"https://secure.gravatar.com/avatar/f1acc6318028fdba9874c77bc622a2fb?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","login":"bitprophet"},"id":1437961,"labels":[{"name":"Bug","color":"a04040","url":"https://api.github.com/repos/fabric/fabric/labels/Bug"},{"name":"Core","color":"ededed","url":"https://api.github.com/repos/fabric/fabric/labels/Core"}],"number":265,"pull_request":{"patch_url":null,"html_url":null,"diff_url":null},"title":"Cannot use public key authentication","closed_at":"2011-08-19T02:11:58Z","html_url":"https://github.com/fabric/fabric/issues/265","url":"https://api.github.com/repos/fabric/fabric/issues/265","milestone":{"created_at":"2011-08-19T01:59:59Z","state":"closed","closed_issues":2,"due_on":null,"creator":{"gravatar_id":"f1acc6318028fdba9874c77bc622a2fb","id":6088,"url":"https://api.github.com/users/bitprophet","avatar_url":"https://secure.gravatar.com/avatar/f1acc6318028fdba9874c77bc622a2fb?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","login":"bitprophet"},"number":10,"title":"0.9.4","description":null,"url":"https://api.github.com/repos/fabric/fabric/milestones/10","open_issues":0}},"action":"created","comment":{"created_at":"2011-12-12T09:36:02Z","updated_at":"2011-12-12T09:36:02Z","user":{"gravatar_id":"5790f885fb416018f1fa6e2db4c1c469","id":359568,"url":"https://api.github.com/users/fzx","avatar_url":"https://secure.gravatar.com/avatar/5790f885fb416018f1fa6e2db4c1c469?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","login":"fzx"},"body":"@bitprophet,thank you for your help. I can SSH to the IP, after disabled the its IPv6 Protocol\u0013, the problem still existed. I want to use fabric, but this problem is very annoying.","id":3103826,"url":"https://api.github.com/repos/fabric/fabric/issues/comments/3103826"}}