Boost logo

Boost :

Subject: Re: [boost] Trying modular Boost
From: Lars Viklund (zao_at_[hidden])
Date: 2014-01-04 16:59:58


On Sat, Jan 04, 2014 at 09:35:04PM +0000, Richard wrote:
> >The way Github (and bitbucket, and others) identify people is via the
> >public key you have registered on your account.
>
> Then wouldn't it be "legalize_at_[hidden]" and not "git_at_[hidden]"?

No, it would be git_at_.

> When I copy/pasted the command given at
> <https://svn.boost.org/trac/boost/wiki/TryModBoost>
>
> I always get this error:
>
> > git clone --recursive git_at_[hidden]:boostorg/boost.git modular-boost
> Cloning into 'modular-boost'...
> Permission denied (publickey).
> fatal: Could not read from remote repository.
>
> Please make sure you have the correct access rights
> and the repository exists.
>
> I don't know how else to interpret this except that I am not able to
> authenticate as user 'git' -- and why would I? I don't have the
> private/public key for user git.

When Github gets a login attempt for SSH user git, it uses the signature
from your private key to look up the corresponding public key registered
with some logical Github account and uses that logical Github account
for rights and permissions.

If you want a primary source for the clone URL, log into Github and on
the right-hand-panel for the repository you have a 'clone URL' which
looks just like the one cited in our wiki.

If you want to test whether your key is properly registered and/or if
your agent is working, you can use a SSH client (or putty, or plink) to
make a (failing) connect akin to:

∫ ssh -i ~/.ssh/id_github git_at_[hidden]
PTY allocation request failed on channel 0
Hi zao! You've successfully authenticated, but GitHub does not provide
shell access.
Connection to github.com closed.

-- 
Lars Viklund | zao_at_[hidden]

Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk