I can answer that one - nope, he didn't.
Also - re: the key. Sorry, that was my fault. Turns out my install
accidentally switched to using the wrong version of the SSH protocol and
thuse used DSA instead of the RSA-key that I had stored. Starting cvs
from the correct environment fixed the issue.
The docs says I need to do SSH1, but it seems the server supports SSH2.
Can someone confirm which is correct?
//Magnus
>-----Original Message-----
>From: Gavin M. Roy [mailto:gmr@ehpg.net]
>Sent: den 11 juni 2004 23:15
>To: Dave Page
>Cc: pgsql-www@postgresql.org; Magnus Hagander
>Subject: Re: [pgsql-www] CVS access on pgFoundry broken (DSA
>key changed??)?
>
>
>Did you wait about half a day for the cron to update everything?
>
>Gavin
>
>Dave Page wrote:
>
>>Hi guys,
>>
>>I'm getting the following when trying to logon anonymously to the
>>pgFoundry CVS:
>>
>>cvs -z9 -d :pserver:anonymous@cvs.pgfoundry.org:/cvsroot/pginstaller
>>login
>>Logging in to
>>:pserver:anonymous@cvs.pgfoundry.org:2401:/cvsroot/pginstaller
>>cvs [login aborted]: initgroups failed: Invalid argument
>>
>>So, Magnus added me to the project as a developer:
>>
>>cvs -z9 -d
>:pserver:dpage@cvs.pgfoundry.org:/cvsroot/pginstaller login
>>Logging in to
>:pserver:dpage@cvs.pgfoundry.org:2401:/cvsroot/pginstaller
>>Fatal error, aborting.
>>cvs [login aborted]: dpage: no such user
>>
>>And then tried it himself:
>>
>>cvs update: warning: unrecognized response `The authenticity of host
>>'cvs.pgfoundry.org (200.46.204.130)' can't be established.' from cvs
>>server
>>cvs update: warning: unrecognized response `DSA key fingerprint is
>>cb:08:ee:77:f4:01:88:14:41:2a:bf:a9:49:3b:4b:65.' from cvs server
>>
>>If the key has changed it should probably be posted as news. If not,
>>someone's hijacked the server!!
>>
>>Regards, Dave
>>
>>---------------------------(end of
>broadcast)---------------------------
>>TIP 1: subscribe and unsubscribe commands go to
>majordomo@postgresql.org
>>
>>
>
>
