bug-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: different CVS_SERVER for different hosts


From: Mark D. Baushke
Subject: Re: different CVS_SERVER for different hosts
Date: Sun, 02 Nov 2003 08:07:45 -0800

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Paul Edwards <address@hidden> writes:

> "Mark D. Baushke" <address@hidden> wrote
> > <#secure method=pgp mode=sign address@hidden>
> >
> > Using google, I found a few repositories that has anonymous CVS access
> > via ssh that Joey Hess originally devised.
> >
> >     http://www.kitenet.net/~joey/sshcvs/
> >
> >     http://ieee.uow.edu.au/~mjp16/prog/anoncvs_ssh
> >
> > If these do not help your testing of :ext: servers, let me know.
> 
> Ah, that leads me into another nightmare.  I've copied my identity
> files in about 50 different possible home directories, but ssh
> doesn't appear to be interested in any of them.  So I have to enter
> my password every time I connect.

What SSHv2 and/or SSHv1 client are you using? If you are using Putty,
then you would download the private key from one of the servers given
above and put it in a file. Then you would use the "Private key file for
authentication (see section 4.18.5 and chapter 8)

http://the.earth.li/~sgtatham/putty/0.53b/htmldoc/Chapter4.html#4.18
http://the.earth.li/~sgtatham/putty/0.53b/htmldoc/Chapter8.html#8 

and/or use Pagent (see section 9.2.2)

http://the.earth.li/~sgtatham/putty/0.53b/htmldoc/Chapter9.html#9.2.2

to keep you credentials.

> So now when I tried out the ieee site above, it asked for my
> password, which of course I don't know.

Correct, you need to engage private key authentication using the
downloaded private key from that site. As the private keys on those
sites do not actually have a pass phrase, you will not need to type
anything to use the keys.

> The only way I can test CVS in the short term is if you can give
> me a userid and password (to kerravon at bigpond ...
> net .au).  If I just have access to do a cvs rlog of some module,
> that will do the trick.

Hmmm... okay, that is a bit more work, I'll have to create a special
account and set its password, so it will probably have to wait until
Monday. I'll also need you to send me private e-mail to mdb at cvshome
dot org with some way to get you the password for the account. If you
use GPG (or PGP), you could encrypt the password you want me to use
in the public key 0x161913F8 that you can download from 
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x161913F8 ...

> Alternatively, maybe now is the time to write a script that will
> copy my identity file into every single subdirectory on my system,
> so that no matter where ssh would like it to be, it will be there.

That is just NOT how SSH authentication works.

If you go and download Putty which is able to do SSHv1 and SSHv2, then
you can configure it to point to the one and only directory which
contains your .pub files as well as the private keys you have generated
(section 8.2.1) and you may have Pagent prompt you once per login
session and hold the decrypted key in memory ready to give it to the
hosts that you connect to using Putty.

> I uploaded the indentity.pub to sourceforge a week ago.  This
> ssh stuff is a nightmare.
> 
> BFN.  Paul.

It can be confusing to get things properly setup, but it does not have
to be nightmare.

        Good luck,
        -- Mark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)

iD8DBQE/pSvO3x41pRYZE/gRAj2jAJwKMSdbdyk8eP7y3UHvIRMAHdGCygCfa2Z4
Kgf0ddRvAZeeIjyxaTaa7NM=
=XU0y
-----END PGP SIGNATURE-----




reply via email to

[Prev in Thread] Current Thread [Next in Thread]