From: "Frank Ch. Eigler" <fche@redhat.com>
To: Lee Millward <lee.millward@gmail.com>
Cc: overseers@gcc.gnu.org
Subject: Re: Logging in failure
Date: Thu, 02 Feb 2006 22:46:00 -0000 [thread overview]
Message-ID: <20060202224635.GB25856@redhat.com> (raw)
In-Reply-To: <9784d3ab0602021441xec3253dg6d9e2fc950546c63@mail.gmail.com>
Hi -
> [...] I'm experiencing failure with "permission denied".
Something messed up your .ssh/authorized_keys file here on sourceware
(by adding "Approved2:Approved" right to the key data ?!). Please try
it now, if it still doesn't work, send me your id_dsa.pub file.
- FChE
next prev parent reply other threads:[~2006-02-02 22:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-02 22:41 Lee Millward
2006-02-02 22:46 ` Frank Ch. Eigler [this message]
[not found] ` <9784d3ab0602021501s6c5f445ei447e00422a0e486a@mail.gmail.com>
2006-02-02 23:05 ` Lee Millward
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=20060202224635.GB25856@redhat.com \
--to=fche@redhat.com \
--cc=lee.millward@gmail.com \
--cc=overseers@gcc.gnu.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.
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).