unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
Cc: eliz@elta.co.il, emacs-devel@gnu.org, handa@m17n.org
Subject: Re: Emacs project on Savannah
Date: 24 Dec 2003 13:53:41 +0100	[thread overview]
Message-ID: <x5ekuunzqi.fsf@lola.goethe.zz> (raw)
In-Reply-To: <20031224.134421.253172493.wl@gnu.org>

Werner LEMBERG <wl@gnu.org> writes:

> > I've just recovered the write access to CVS.  I did the
> > followings.
> > 
> > (1) Visit http://savannhah.gnu.org
> > (2) Click "Login via SSL".
> > (3) Click "[Lost your password?]
> > (4) Enter my login name "handa" and click "Send Lost PW Hash".
> > (5) Receive a mail from savannah-hackers@gnu.org.  Visit the
> >     URL specified in the mail.
> > (6) Type my new password.
> > (7) Visit http://savannhah.gnu.org
> > (8) Click "Login via SSL".
> > (9) Enter login name and password and click "Login".
> > (10) Click "My Account Conf"
> > (11) Click "Enter the 1 SSH Public key(s) Registered.
> > (12) Enter the contents of my ~/.ssh/id_rsa.pub in the box, and
> >      click "Update".
> > 
> > After a few minutes, I got a write access to CVS, and I
> > commited changes in lisp/mule-cmds.el and
> > lisp/ucs-tables.el.
> 
> I did the same, but I still can't access the CVS (the same is true for
> the other projects).  Some notes:
> 
>   . I haven't registered a SSH Public Key before, so it was the first
>     time.  Does this matter?

How were you able to use CVS before?  You need a version of OpenSSH
that supports protocol 2 (note that ssh2 has a _different_
protocol).  You also have to use protocol 2 by default, so if you
have a manual protocol 1 override in your .ssh/config file as was
needed previously, you have to remove it.

>   . Which password shall I use while doing e.g. `cvs update'?  The
>     password specified during the call to ssh-keygen?

You must not use any password at all (that is a fallback attempt if
the public key authentication fails, and the fallback will surely fail
since Savannah allows only public key).  If your key was generated
with a passphrase (mainly mandatory when your secret key is stored on
a machine for which you have not sole access), then you'll want to use
the ssh-agent for password entry.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

  reply	other threads:[~2003-12-24 12:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-23 10:45 Emacs project on Savannah Eli Zaretskii
2003-12-24  2:19 ` Kenichi Handa
2003-12-24  8:25   ` Jason Rumney
2003-12-24 12:01     ` Kenichi Handa
2003-12-24 17:18       ` Eli Zaretskii
2003-12-24 12:44   ` Werner LEMBERG
2003-12-24 12:53     ` David Kastrup [this message]
2003-12-24 13:42       ` Werner LEMBERG
2003-12-24 17:55     ` Eli Zaretskii
2003-12-25  2:26 ` Miles Bader
2003-12-25  5:41   ` Eli Zaretskii
2003-12-25  8:50     ` [Savannah-hackers] " Rudy Gevaert
2003-12-25 11:06       ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=x5ekuunzqi.fsf@lola.goethe.zz \
    --to=dak@gnu.org \
    --cc=eliz@elta.co.il \
    --cc=emacs-devel@gnu.org \
    --cc=handa@m17n.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).