[m-dev.] remote CVS access

[Fergus Henderson]

Currently many people are using the `pserver' password-based remote CVS
access method, since that is what is recommended on our web page.
However, this method is not very secure.  In the long term I plan to
phase it out, in favour of ssh-based remote CVS access.

Could everyone who is using pserver-based remote CVS access
please (1) let me know who you are and (2) email me a copy of your ssh
public key (which is in ~/.ssh/identity.pub; use ssh-keygen if you don't
have one already)?

For ssh-based remote cvs access, just use

	:ext:<your user id>@cvs.mercury.cs.mu.oz.au:/home/mercury1/repository

e.g.

	:ext:fjh at cvs.mercury.cs.mu.oz.au:/home/mercury1/repository

as the CVSROOT.  You don't need to `cvs login'.
Instead, you need

	- ssh installed on your client machine (of course)

	- an ssh key pair (generated with ssh-keygen) on your client machine

	- an account on cvs.mercury.cs.mu.oz.au, with a copy of your
	  ssh public key(s) in ~/.ssh/authorized_keys.
	  Note that the account does not need a password (the sysad can put
	  "*" in the password field of /etc/passwd) or a login shell.

-- 
Fergus Henderson <fjh at cs.mu.oz.au>  |  "I have always known that the pursuit
The University of Melbourne         |  of excellence is a lethal habit"
WWW: <http://www.cs.mu.oz.au/~fjh>  |     -- the last words of T. S. Garp.
--------------------------------------------------------------------------
mercury-developers mailing list
Post messages to:       mercury-developers at cs.mu.oz.au
Administrative Queries: owner-mercury-developers at cs.mu.oz.au
Subscriptions:          mercury-developers-request at cs.mu.oz.au
--------------------------------------------------------------------------