I'm not finding much about passphrase-protected keys with cap here on my end. I have a feeling that most deploy servers don't use a passphrase on their key. I mean, there's not much need for one really, if your server is compromised, the attacker has access to your code already. Any word from the cap list? They may have a better clue as to how cap handles passphrases than I do.
--tek On Mon, Sep 22, 2008 at 2:37 PM, Fritzek <[EMAIL PROTECTED]>wrote: > > in addition to former reply: the cap 2.0 was the standard coming with > osx leopard. my fault was to never check the version :( > > On Sep 22, 9:09 pm, Tekkub <[EMAIL PROTECTED]> wrote: > > Fritzek, > > Ah, sorry for the confusion. What version of Cap did you upgrade from, > 2.4? > > > > --tek > > > > On Mon, Sep 22, 2008 at 12:52 PM, Fritzek > > <[EMAIL PROTECTED]>wrote: > > > > > > > > > Hi Tekkub > > > > > thanks for your answer. nice way to report success, but I can > > > understand the meaning behind ;-) > > > for the deploy issue: no, it was ask in the past for a passphrase and > > > not now. I just have one key. its registered in my profile and it was > > > the same as it was working yesterday. > > > I don't understand: if the ssh test reports a success (btw it was > > > asking for a passphrase too) and the deploy proccess will not, what is > > > different. At capistrano group I've got no answer to exclude cap from > > > issue list. > > > > > thanks in advance > > > > > Fritzek > > > > > On Sep 22, 8:39 pm, Tekkub <[EMAIL PROTECTED]> wrote: > > > > Fritzek, > > > > "I can't do that" is actually a success. It means you connected, but > we > > > > don't give you a shell. As for your deploy issues, it's asking for a > > > > passphrase now and it didn't in the past? Sounds like your server > > > started > > > > using a different key... one that was created with a passphrase. > Make > > > sure > > > > you only have one key, or that cap is using the correct one if you > have > > > many > > > > you cannot remove. > > > > > > --tek > > > > > > On Mon, Sep 22, 2008 at 7:41 AM, Fritzek < > > > [EMAIL PROTECTED]>wrote: > > > > > > > Hi, > > > > > since today when checking ssh access to github via "ssh -vi ~/.ssh/ > > > > > id_rsa [EMAIL PROTECTED]" github answer with "I can't do that, > fritzek." > > > > > here full log: > > > > > *** > > > > > OpenSSH_4.3p2 Debian-9etch2, OpenSSL 0.9.8c 05 Sep 2006 > > > > > debug1: Reading configuration data /etc/ssh/ssh_config > > > > > debug1: Applying options for * > > > > > debug1: Connecting to github.com [65.74.177.129] port 22. > > > > > debug1: Connection established. > > > > > debug1: permanently_set_uid: 0/0 > > > > > debug1: identity file /root/.ssh/id_rsa type 1 > > > > > debug1: Remote protocol version 2.0, remote software version > > > > > OpenSSH_4.7 > > > > > debug1: match: OpenSSH_4.7 pat OpenSSH* > > > > > debug1: Enabling compatibility mode for protocol 2.0 > > > > > debug1: Local version string SSH-2.0-OpenSSH_4.3p2 Debian-9etch2 > > > > > debug1: Miscellaneous failure > > > > > No credentials cache found > > > > > > > debug1: Miscellaneous failure > > > > > No credentials cache found > > > > > > > debug1: SSH2_MSG_KEXINIT sent > > > > > debug1: SSH2_MSG_KEXINIT received > > > > > debug1: kex: server->client aes128-cbc hmac-md5 none > > > > > debug1: kex: client->server aes128-cbc hmac-md5 none > > > > > debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent > > > > > debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP > > > > > debug1: SSH2_MSG_KEX_DH_GEX_INIT sent > > > > > debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY > > > > > debug1: Host 'github.com' is known and matches the RSA host key. > > > > > debug1: Found key in /root/.ssh/known_hosts:3 > > > > > debug1: ssh_rsa_verify: signature correct > > > > > debug1: SSH2_MSG_NEWKEYS sent > > > > > debug1: expecting SSH2_MSG_NEWKEYS > > > > > debug1: SSH2_MSG_NEWKEYS received > > > > > 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: /root/.ssh/id_rsa > > > > > debug1: Remote: Forced command: gerve fritzek > > > > > 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> > > > > > Enter passphrase for key '/root/.ssh/id_rsa': > > > > > debug1: read PEM private key done: type RSA > > > > > debug1: Remote: Forced command: gerve fritzek > > > > > debug1: Remote: Port forwarding disabled. > > > > > debug1: Remote: X11 forwarding disabled. > > > > > debug1: Remote: Agent forwarding disabled. > > > > > debug1: Remote: Pty allocation disabled. > > > > > debug1: Authentication succeeded (publickey). > > > > > debug1: channel 0: new [client-session] > > > > > debug1: Entering interactive session. > > > > > debug1: Sending environment. > > > > > debug1: Sending env LANG = en_US.UTF-8 > > > > > debug1: client_input_channel_req: channel 0 rtype exit-status reply > 0 > > > > > I can't do that, fritzek. > > > > > debug1: channel 0: free: client-session, > > > > > nchannels 1 > > > > > Connection to github.com closed. > > > > > debug1: Transferred: stdin 0, stdout 0, stderr 34 bytes in 0.5 > seconds > > > > > debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 63.0 > > > > > debug1: Exit status 1 > > > > > *** > > > > > > > deployment vi capistrano also stucks with permissions error which > > > > > might be the same like here. > > > > > last deployment was yesterday and I was asked for id_rsa > passphrase. > > > > > only change was the upgrade of capistrano to version 2.5 > > > > > > > thanks in advance > > > > > > > Fritzek > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "GitHub" 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/github?hl=en -~----------~----~----~----~------~----~------~--~---
