Hi All, I can access cvs.apache.org through Putty after changing the protocol version from 1 to 2.
I'm using TortoiseCVS 1.6.5 which, I guess, is not support to SSH Version 2. I have to find a CVS client that supports version 2. Regards, Dushshantha -----Original Message----- From: Henri Yandell [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 29, 2005 12:10 PM To: Dushshantha Chandradasa Cc: [EMAIL PROTECTED] Subject: Re: My password is not accepted...[ [NOTICE] minotaur (people, cvs, svn) downtime tomorrow (6/27)] This seems to be a problem that some clients have had after cvs.apache.org was upgraded to the latest version of the OS yesterday (and by association, a later version of OpenSSH). Putty appears to have the problem, which seems to be solvable by switching the protocol version from '1' to '2' on the Connection->SSH settings option. Ant's scp task (and by association JSch) seems to have a problem too, no idea if that one is solvable. What platform/tool are you having connection problems with? I don't think anyone knows for sure what the problem is, but the gut feel seems to be that the later OpenSSH is tighter on the spec than the older version was and some of the clients are having problems where they weren't hitting the spec fully. SSH keys seem to still work fine, it just causes problems to the password entry. Hen On 6/28/05, Dushshantha Chandradasa <[EMAIL PROTECTED]> wrote: > Hi All, > > I am an ASF committer of Axis C++ and my committer account is > dushshantha. From yesterday onwards, I cannot checkout the CVS because > my password is not accepted by the server. I can checkout from > /home/cvspublic as an anonymous user. > > Regards, > Dushshantha > > -----Original Message----- > From: Justin Erenkrantz [mailto:[EMAIL PROTECTED] > Sent: Monday, June 27, 2005 3:05 AM > To: [EMAIL PROTECTED] > Subject: [NOTICE] minotaur (people, cvs, svn) downtime tomorrow (6/27) > > Hi everyone, > > We're going to be taking minotaur (aka people.apache.org, > cvs.apache.org, > svn.apache.org) down tomorrow afternoon (6/27) for an operating system > upgrade. I expect that we'll be back up by the early evening - however, > > unexpected things *could* happen that would stretch the downtime into > Tuesday. > > All public project websites will not be affected during this upgrade. > > If you have any questions, please email [EMAIL PROTECTED] > > Thanks. -- justin >
