On Thu, Mar 4, 2010 at 06:16, Vinay Sajip wrote:
> Jesus Cea jcea.es> writes:
>
> > Do you have access to any other machine vía SSH?. I would try to
> > generate a new SSH key in Ubuntu. If that solves the issue connecting to
> > ther machines, I would ask python commint gatekeeper to change you
Jesus Cea jcea.es> writes:
> Do you have access to any other machine vía SSH?. I would try to
> generate a new SSH key in Ubuntu. If that solves the issue connecting to
> ther machines, I would ask python commint gatekeeper to change your SSH
> commit key. Do the test against a machine you can up
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/04/2010 10:06 AM, Vinay Sajip wrote:
> Thanks for the response. I checked the permissions and verified them to be 600
> on ~/.ssh/id_rsa. Your suggestion to ssh -v is a good one, and it lets me in
> despite there being debug messages about the k
M.-A. Lemburg egenix.com> writes:
>
> Try running ssh-agent in debug mode and see whether ssh has
> problems connecting to it.
>
Hi Marc,
Thanks for the suggestion. If I kill the existing agent and start a new one
with -d, it works! But if I try again after starting without -d, it stops
worki
Jack Diederich gmail.com> writes:
>
> Most of my problems with ssh are permissions related. Make sure the
> directory and the individual files under .ssh are "-rw--" (it will
> refuse to use them if the permissions are too permissive). If you are
> getting failures trying ssh'ing in manually
Vinay Sajip wrote:
> Jesus Cea jcea.es> writes:
>
>>
>> I would use "ssh-agent" directly, via "ssh-add". It is what I do.
>>
>
> Hi Jesus,
>
> Thanks for the response. I've tried that, with no luck. The key is added to
> ssh-agent, which I verified using "ssh-add -l" - but I still get prompted
R. David Murray bitdance.com> writes:
>
> Is it possible that the ssh being called by the svn command can't access
> your environment to find the agent? I'm not sure how that would happen,
> though, unless you have a 'tunnels' section in your svn config. Or you
> have something wrapping your s
Jesus Cea jcea.es> writes:
>
> I would use "ssh-agent" directly, via "ssh-add". It is what I do.
>
Hi Jesus,
Thanks for the response. I've tried that, with no luck. The key is added to
ssh-agent, which I verified using "ssh-add -l" - but I still get prompted for
the passphrase every time.
Re
Alexandre Vassalotti peadrop.com> writes:
>
> On Wed, Mar 3, 2010 at 5:32 PM, Vinay Sajip wrote:
> > I've installed Keychain and invoked it in my .bashrc, and whenever I open a
> > terminal session, it tells me that it found an existing ssh-agent and the
> > SSH_AUTH_SOCK and SSH_AGENT_PID seem
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/04/2010 03:28 AM, Alexandre Vassalotti wrote:
> On Wed, Mar 3, 2010 at 5:32 PM, Vinay Sajip wrote:
>> I've installed Keychain and invoked it in my .bashrc, and whenever I open a
>> terminal session, it tells me that it found an existing ssh-agen
On Wed, Mar 3, 2010 at 5:32 PM, Vinay Sajip wrote:
> I'm having some odd problems with my SSH key and Keychain which I hope someone
> on this list can help with.
[snip]
Most of my problems with ssh are permissions related. Make sure the
directory and the individual files under .ssh are "-rw--
On Wed, 03 Mar 2010 22:32:24 +, Vinay Sajip wrote:
> I've installed Keychain and invoked it in my .bashrc, and whenever I open a
> terminal session, it tells me that it found an existing ssh-agent and the
> SSH_AUTH_SOCK and SSH_AGENT_PID seem to be correct. Yet, I get prompted for
> the
> pa
On Wed, Mar 3, 2010 at 5:32 PM, Vinay Sajip wrote:
> I've installed Keychain and invoked it in my .bashrc, and whenever I open a
> terminal session, it tells me that it found an existing ssh-agent and the
> SSH_AUTH_SOCK and SSH_AGENT_PID seem to be correct.
Are you using Ubuntu? If so, Seahorse
I'm having some odd problems with my SSH key and Keychain which I hope someone
on this list can help with.
When I became a Python committer, I was using Windows, mostly, so I set up an
SSH key using PuTTY and Pageant which worked flawlessly.
More recently, I've being using Linux, mostly, as my pr
14 matches
Mail list logo
