On 4:41:52 pm 2005-08-13 Greg Chicares <chicares@...> wrote:
> On 2005-8-11 12:07 UTC, Earnie Boyd wrote:
> > On 11:56:53 am 2005-08-10 "Earnie Boyd" <earnie@...
> et> wrote:
> >> On 12:46:20 am 2005-08-10 Greg Chicares <chicares@...> wrote:
> >>> It seems likely that MSYS's openssh is old enough to have
> >>> become slightly incompatible with savannah.gnu.org :
> >>> https://savannah.gnu.org/support/?func=detailitem&item_id=10453
> >>> Probably I should figure out how to build a more recent
> >>> version and submit it to mingwport; or I could use cygwin.
> >>> But I figured that as a first step I'd ask whether anyone
> >>> else was already planning to work on this.
> >> I don't think the age of openssl is the problem. Try adding the
> >> following:
> >> <file name="/etc/ssh_config">
> >> Host *
> >> ForwardAgent no
> >> ForwardX11 no
> >> FallBackToRsh no
> >> Protocol 1,2
> >> IdentityFile ~/.ssh/identity
> >> IdentityFile ~/.ssh/id_rsa
> >> IdentityFile ~/.ssh/id_dsa
> >> </file>
> >> You'll need to modify to match what your identity files are named.
> > Greg did this help?
> I was out of town for a few days, but a coworker tried that and
> reported that it didn't solve the problem. However, it was solved
> at the server end: the savannah.gnu.org administrator said:
Ok, thanks. The above has helped me accessing SourceForge.
> | I installed MSys and made some tests; apparently UsePAM=yes +
> | EnablePasswordAuthentication=No does the trick.
> and that did solve the problem. Several other people who use MSYS
> have confirmed that it works for them, too.
So the Savannah Admin modified the server configuration and there is no
need to worry about it. Great, that is good news for me.