This is the mail archive of the cygwin mailing list for the Cygwin project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On Jul 26, 2013, at 12:51 PM, J. P. Abelanet <jp@basissw.com> wrote: > >> >>> I've since tried the following: >>> - running ssh-host-config on (a) and rebooting, with no effect >>> - completely removing CYGWIN and all traces of sshd >>> (http://cygwin.wikia.com/wiki/Uninstalling_Cygwin) and reinstalling on >>> (a), with no effect >> >> We discourage people from following Cygwin advice from ad-hoc sites. In >> this case, it provides a synopsis of how to do this and then points to a >> link in the Cygwin FAQ from where the synopsis came. Two things should >> make anyone think twice about the information at this site: >> >> 1. It points to the Cygwin FAQ as the source. >> 2. The link to the Cygwin FAQ is broken. > > Thanks for the warning - I'll try to be more diligent in the future. > >> >>> - completely removing VS 2010 and all related packages (I think), and >>> trying to build using the untouched version of VS 2008 I had previously been >>> using, and now building debug across CYGWIN/ssh/pub key with VS 2008 fails >>> as well >> >> Yeah, that of course assumes that the uninstall undid all that the install >> did. There's not a good way to verify that. If you can narrow down the >> time-frame (with the Cygwin Time Machine for example - Google it) when you >> see the problem appear, that could help find a solution, assuming you're >> still seeing the problem with 1.7.22. >> > > Understood. And yes, the problem still occurs with 1.7.22. > > As I mentioned originally, I'm using a local (non-domain) account, > and it has administrator privileges. What is the fundamental difference between > public key authentication and password authentication in this context? > Here is the source of the problem, and I'm virtually certain that these problems occurred as a result of running setup.exe on the two machines as part of the upgrade (note that I did not, for various reasons, run setup.exe on the two machines that still work). Here are the USER* variables on machines (a) and (b), the two problem machines, when logging in via ssh/pub key: gessh@niven $ set | grep USER USER=gessh USERDOMAIN='NT AUTHORITY' USERNAME=SYSTEM USERPROFILE='C:\Documents and Settings\gessh' gessh@salinger -bash-4.1$ set | grep USER USER=gessh USERDOMAIN=salinger USERNAME=cyg_server USERPROFILE='C:\Users\gessh.salinger' Here are the two problem machines when using ssh with password authentication: gessh@niven $ set | grep USER USER=gessh USERDOMAIN=NIVEN USERNAME=gessh USERPROFILE='C:\Documents and Settings\gessh' gessh@salinger -bash-4.1$ set | grep USER USER=gessh USERDOMAIN=salinger USERNAME=gessh USERPROFILE='C:\Users\gessh.salinger'
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |