public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: Please upload: xemacs-21.4.19-2/xemacs-tags-21.4.19-2/xemacs-emacs-common-21.4.19-2
Date: Tue, 05 Dec 2006 02:12:00 -0000	[thread overview]
Message-ID: <20061205021230.GC19987@trixie.casa.cgf.cx> (raw)
In-Reply-To: <82psazei58.fsf@vzell-de.de.oracle.com>

On Mon, Dec 04, 2006 at 05:32:35PM +0100, Dr. Volker Zell wrote:
>>>>>> Charles Wilson writes:
>
>    > Corinna Vinschen wrote:
>    >> On Dec  3 18:40, Dr. Volker Zell wrote:
>    >>> debug1: Authentications that can continue: publickey,gssapi-with-mic
>    >>> debug1: Next authentication method: publickey
>    >>> debug1: Offering public key: /home/vzell/.ssh/id_rsa
>    >>> debug1: Authentications that can continue: publickey,gssapi-with-mic
>    >>> debug1: Offering public key: /home/vzell/.ssh/id_dsa
>    >>> debug1: Authentications that can continue: publickey,gssapi-with-mic
>    >>> debug1: No more authentication methods to try.
>    >>> Permission denied (publickey,gssapi-with-mic).
>    >>> 
>    >>> Anything wrong here ?
>    >> Is .ssh/id_dsa actually the correct private key for the pubkey you
>    >> sent
>    >> to overseers?  I can't see anything wrong on sourceware.  I'm not that
>    >> fluent with the sourceware installation.  Cgf can tell more.
>
>    > AFAIK, sourceware supports only ssh1 protocol (identity[.pub]), which
>    > is why my ~/.ssh/config file has this:
>
>    > Host sources.redhat.com
>    >     Protocol 1
>
>Maybe that's the problem. But Chris explicitly asked me for version 2
>key. Chris ??

No.  We haven't required version 1 keys for some time and are actually
actively trying to move away from them.

I really don't know why you can't login unless you are having another
problem with your key.  As you recall, you sent me another key after
filling out the form for the second time.

cgf

      reply	other threads:[~2006-12-05  2:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-30  0:44 Dr. Volker Zell
2006-11-30  8:48 ` Corinna Vinschen
2006-11-30 10:19   ` Dr. Volker Zell
2006-11-30 10:51     ` Corinna Vinschen
2006-11-30 11:14       ` Dr. Volker Zell
2006-11-30 12:10         ` Corinna Vinschen
2006-11-30 15:51     ` Corinna Vinschen
2006-12-03 17:40       ` Dr. Volker Zell
2006-12-04  9:13         ` Corinna Vinschen
2006-12-04 15:10           ` Charles Wilson
2006-12-04 15:30             ` Corinna Vinschen
2006-12-04 16:43               ` Dr. Volker Zell
2006-12-04 16:33             ` Dr. Volker Zell
2006-12-05  2:12               ` Christopher Faylor [this message]

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

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

  git send-email \
    --in-reply-to=20061205021230.GC19987@trixie.casa.cgf.cx \
    --to=cgf-use-the-mailinglist-please@cygwin.com \
    --cc=cygwin-apps@cygwin.com \
    /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.
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).