Chris,
I suspect that the problems with SSH2 might be to do with the way Putty
represents SSH2 keys. The format of the Putty file is different from
the openssh format, even though they contain compatible data. I think
Putty has an option to import openssh format keys, and I seem to
remember
Jeremias Maerki wrote:
I've had my problems with using SSH2. I finally tried SSH1 and it worked.
I suggest you create a SSH1 key pair and retry with this.
Thanks for the fast response Jeremias. I have managed to get SSH1 working.
There are two ways you can work with putty. Either you create a tun
Chris Bowditch wrote:
[..]
Thinking that SSH is not strictly required for write access, I had a go
Wrong!
You either need to make a frsh checkout with your commiiter id
or change your already checked out module as shown here:
http://www.apache.org/dev/committers.html#general
Christian
I've had my problems with using SSH2. I finally tried SSH1 and it worked.
I suggest you create a SSH1 key pair and retry with this.
There are two ways you can work with putty. Either you create a tunnel
for CVS which has the benefit that the connection is always there as
soon as you have connected
I know this subject has come up before, but I still cant quite get
things working after trawling through the archives.
I'm using WinCVS 1.3 and Putty to connect to the cvs.apache.org. My
understanding was that using SSH keys was optional but strongly
encouraged. So I had a go at creating the pr
