Invalid Key: setup.exe authenticity

2011-09-04 Thread carpe_diem
Upon running the detached signature file through PGP it reports the file setup.exe was signed on 12/7/2010 with an "Invalid Key". Could you confirm the origin and safety of setup.exe posted on http://cygwin.com/install.html ? The file downloaded has the following MD5: 2ece86924bf59c82b3c1936760ef

Re: Different error on socket while connecting to a box behind firewall

2011-09-04 Thread Andrey Repin
Greetings, Corinna Vinschen! > However, even with this fix, you might not get EHOSTUNREACH either. In > my testing, the error returned by the underlying Winsock getsockopt > function is not WSAEHOSTUNREACH, but WSAETIMEDOUT. This will be > translated into ETIMEDOUT == "Connection timed out". To

Re: More on Cygwin package naming

2011-09-04 Thread Larry Hall (Cygwin)
On 9/4/2011 11:15 PM, Luke Kendall wrote: It would be /nice/ if someone could confirm that the upstream project name is used for the @-names, or at least that cygwin does not use any existing Freshmeat project name and apply it to different software. FWIW, I think it's fair to say that there is

More on Cygwin package naming

2011-09-04 Thread Luke Kendall
In my previous mail I may have used the wrong term ("package"): the term "package" seems to refer to each .tar.bz2 file (for the source and install files of each version). So perhaps I should instead be talking about "@-names" - the name that appears after an "@" in setup.ini. Anyway, this is