From: William Cohen <wcohen@redhat.com>
To: Ian Lance Taylor <ian@airs.com>
Cc: overseers@sources.redhat.com
Subject: Re: Problems with read/write cvs access
Date: Mon, 21 Mar 2005 17:40:00 -0000 [thread overview]
Message-ID: <4238686F.7010601@redhat.com> (raw)
In-Reply-To: <m3mzt34k17.fsf@gossamer.airs.com>
[-- Attachment #1: Type: text/plain, Size: 2088 bytes --]
Ian Lance Taylor wrote:
> William Cohen <wcohen@nc.rr.com> writes:
>
>
>>I am attempting to check out systemtap related material with
>>read/write permission from sources.redhat.com. So far I have been
>>unsuccessful. I have an gcc.gnu.org account (should be wcohen) that
>>had read/write access. However, I have not used the gcc.gnu.org
>>account for a while. I was told that things should be available if I
>>had the gcc.gnu.org account. Below is the problem I encounter when I
>>attempt to check things out.
>>
>>$ echo $CVS_RSH
>>ssh
>>$ cvs -d :ext:wcohen@sources.redhat.com:/cvs/systemtap co htdocs
>>Permission denied (publickey,keyboard-interactive).
>>cvs [checkout aborted]: end of file from server (consult above
>>messages if any)
>>
>>I don't even get a chance to enter my pass phrase. What needs to be
>>done so to obtain read/write access to systemtap cvs. Just in case I
>>have attached .ssh/id_dsa.pub.
>>
>>-Will
>>
>>ssh-dss AAAAB3NzaC1kc3MAAACBAJMoDLBCnoeshox4azclNzqB+xc8XD/Imb3aCpuYa9MvP3dRUiexGFQPH2H/TiCZpBeC9E6jrz6/fIz8wLYUpQJXJO20HHuq6pPeYQOTLELxghsWifzxQJYGLkfIPyzPtumuwjGROOM3Q5m57bgkFnuT2KsEW7fqfD42vTk8fPElAAAAFQCx0lmih2FmkkbOHYoXe7J0NPV7LwAAAIBCikkxVC3TNR62tbUtlONat05GoIaNfE2Oji31MmMpagQ9d0zlv/cfP4pbxDVmt0pYYUBGRrnlf+LqhPBc+QfTPMU79iEobPeWJ6i/DuaAGLx1AgaHybQLAsB+I0EtZ9aUvIa6otLBvx2/Kf9joM/FXlWMBCiOumE8IrxBLe1TxwAAAIBSe5AqQ5hIDw86FU/f7NqLbnStUJGKRvrgMrSzL5dWwti78iH7jxJvpedLj3AixEyhBahfDvoNWeWwuCJqt9cVTyc9OdwQzwXkuo/g8/N4MI4lxUE5CbeM1ZRMBIW/4vIGqb4wr+ZRkP7/KdVnYyhnZq3PytmvaJTH3ADVWZD8fg== wcohen@wcohen
>
>
> That is not the public key which you have on gcc.gnu.org. The two on
> gcc.gnu.org start with "1024 35" (i.e., is an SSHv1 key). One ends
> with wcohen@wcohen.devel.redhat.com and one ends with wcohen@wcohen.
>
> I'm never too sure what to do in this sort of situation. Are you sure
> you are the same William Cohen?
Unfortunately, my web browser picked the wrong email account to mail
things from. I am the same wcohen@wcohen.devel.redhat.com
The identity.pub is attached. I must have used that rather than the
id_dsa.pub.
-Will
[-- Attachment #2: identity.pub --]
[-- Type: text/plain, Size: 332 bytes --]
1024 35 117473504790147691912552951022766511992158021701738276087354997688403450215214736492609263098393281820740171767986032637833353880969758327991594947058715511327882686719027408090573375687823609430222718684434675120440252267352378112620627321401871676765486610084049385742498315764348799334956994495736403397651 wcohen@wcohen
next prev parent reply other threads:[~2005-03-16 17:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-20 19:11 William Cohen
2005-03-20 23:19 ` Ian Lance Taylor
2005-03-21 17:40 ` William Cohen [this message]
2005-03-22 7:55 ` Ian Lance Taylor
2005-03-22 12:56 ` Frank Ch. Eigler
2005-03-22 13:08 ` William Cohen
2005-03-22 13:29 ` Ian Lance Taylor
2005-03-22 14:19 ` Frank Ch. Eigler
2005-03-22 17:04 ` William Cohen
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=4238686F.7010601@redhat.com \
--to=wcohen@redhat.com \
--cc=ian@airs.com \
--cc=overseers@sources.redhat.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).