I was able to resolve the issue, but am unaware of the implications in other environments.
I added... [Net. ServicePointManager]:: SecurityProtocol = [System.Net.SecurityProtocolType]]::Tls12 After the statements... function DownloadFile ... { and if (-not($script:proxy)) { This forces powershell to run tls1.2. This was mentioned in an ansible thread from 8/16/2016 opened by arunjohn and mikecurrancs provided the information if you would like to see it in context. Regards, Tony On Wed, Aug 7, 2019, 1:25 PM Tony Lay <tony...@gmail.com> wrote: > Our issue occurred when we were building the development environment. The > cmake portion doesn't like the proxy, I think we are running in to a bug in > dotnet/corefx (#16695). > > We were able to get to the anonsvn.wireshark.org site and manually > download the packages under the corresponding build directory and complete > the setup. > > This is not an issue with Wireshark. We were hoping that somebody had a > workaround. It looks like grabbing the build files was fine and the other > aspects of the setup properly account for the proxy or can have it > configured. > > Hopefully this will help somebody else out down the road. > > Regards, > > -Tony > > On Wed, Aug 7, 2019, 8:00 AM <wireshark-users-requ...@wireshark.org> > wrote: > >> Send Wireshark-users mailing list submissions to >> wireshark-users@wireshark.org >> >> To subscribe or unsubscribe via the World Wide Web, visit >> https://www.wireshark.org/mailman/listinfo/wireshark-users >> or, via email, send a message with subject or body 'help' to >> wireshark-users-requ...@wireshark.org >> >> You can reach the person managing the list at >> wireshark-users-ow...@wireshark.org >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of Wireshark-users digest..." >> >> >> Today's Topics: >> >> 1. Wireshark SVN (Tony Lay) >> >> >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Tue, 6 Aug 2019 09:00:21 -0400 >> From: Tony Lay <tony...@gmail.com> >> To: wireshark-users@wireshark.org >> Subject: [Wireshark-users] Wireshark SVN >> Message-ID: >> <CAP7f9CTJ4K_hqh2p5V5DmQ7YjM= >> ypkkfiyh44hmqcm8plk9...@mail.gmail.com> >> Content-Type: text/plain; charset="utf-8" >> >> I see that Wireshark switched to Git in 2014, but documentation shows that >> there is an SVN repo at: http://anonrepo.wireshark.org/wireshark/trunk >> >> Is the Subversion repo still in existence? I was unable to access it from >> a >> few different locations. >> >> Regards, >> >> -Tony >> -------------- next part -------------- >> An HTML attachment was scrubbed... >> URL: < >> https://www.wireshark.org/lists/wireshark-users/attachments/20190806/b50e63b8/attachment.html >> > >> >> ------------------------------ >> >> Subject: Digest Footer >> >> _______________________________________________ >> Wireshark-users mailing list >> Wireshark-users@wireshark.org >> https://www.wireshark.org/mailman/listinfo/wireshark-users >> >> >> ------------------------------ >> >> End of Wireshark-users Digest, Vol 159, Issue 4 >> *********************************************** >> >
___________________________________________________________________________ Sent via: Wireshark-users mailing list <wireshark-users@wireshark.org> Archives: https://www.wireshark.org/lists/wireshark-users Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-users mailto:wireshark-users-requ...@wireshark.org?subject=unsubscribe