Wireshark-dev: Re: [Wireshark-dev] nmake setup target failing for me

From: Graham Bloice <graham.bloice@xxxxxxxxxxxxx>
Date: Thu, 9 Apr 2015 15:35:42 +0100
You should never, ever have Cywgin DLL's or executables in System 32.  Source of much misery.

They should all live in their own bin dir, appropriate for the Cygwin installation.  You can even have multiple Cygwin installations if you're careful to keep the paths appropriate for the applications using them.



On 9 April 2015 at 15:24, Martin Mathieson <martin.r.mathieson@xxxxxxxxxxxxxx> wrote:
Hi Pascal,

I am running Windows Enterprise 7.0 with service pack 1.  It should be up to date with patches, but it may be a week or 2 since I rebooted it.

I did have both the (later version) cygwin wget.exe and what looks like the same, older version in 4 different places.  After replacing the one in C:\Windows\System32 with the Cygwin one, it grumbled about cygwin1.dll and cyggnutls-28.dll, which I'd rather not install.

There was no problem with browsing to the folder with the library files, and for now I have downloaded zip128.zip manually.
Martin


On Thu, Apr 9, 2015 at 2:47 PM, Pascal Quantin <pascal.quantin@xxxxxxxxx> wrote:
2015-04-09 15:28 GMT+02:00 Martin Mathieson <martin.r.mathieson@xxxxxxxxxxxxxx>:
I was prompted to run setup, but am getting this.  Any ideas?
Martin


****** zlib128.zip ******
No HTTP proxy specified (http_proxy and HTTP_PROXY are empty).
Downloading zlib128.zip into '/cygdrive/c/Wireshark-win32-libs', installing into
 .
/packages/zlib128.zip
           => `zlib128.zip'
Resolving anonsvn.wireshark.org... 174.137.42.70
Connecting to anonsvn.wireshark.org|174.137.42.70|:443... connected.
ERROR: Certificate verification error for anonsvn.wireshark.org: unable to get l
ocal issuer certificate
To connect to anonsvn.wireshark.org insecurely, use `--no-check-certificate'.
Unable to establish SSL connection.

15-04-06/packages/zlib128.zip


Hi Martin,

 I do not have any issue on my side. As anonsvn is using a SHA256 certificate, it suggests that your local host does not have the intermediate certificate installed, or deoes not support SHA256. On which Windows version are you running, and is it up-to-date with the latest Windows patch applied? According to http://blogs.technet.com/b/pki/archive/2013/11/12/sha1-deprecation-policy.aspx depending on the version you run, you might require some hotfixes applied.
As a workaround, you can edit win-setup.sh so as to add the --no-check-certificate option as suggested by the output message.

Pascal.

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe


___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe



--
Graham Bloice
Software Developer
Trihedral UK Limited