Saw an article about changing SHA256Managed to SHA256Cng and now the powershell script seems to get past that error.
win-setup.ps1 - line 212: $sha256 = New-Object Security.Cryptography.SHA256Cng
Not sure how it'll eventually work, since I've run into another issue, but that seems to get me past the previous error about FIPS.
Thanks,
John D.
________________________________________
From: John Dill
Sent: Tuesday, March 5, 2019 12:40 PM
To: Developer support list for Wireshark
Subject: Windows Platform FIPS error?
Trying to build 3.0 on Windows 10, x64 for first time. Ran into this error. Not sure what the proper fix is, has anyone run into this yet? Could be something driven by an IA issue since I'm not the master of my machine. Thanks, John D.
---
C:\Users\dillja\Desktop\wsbuild64>cmake -G "Visual Studio 15 2017 Win64" ..\wireshark-3.0-test
-- Selecting Windows SDK version 10.0.17763.0 to target Windows 10.0.17134.
-- Generating build using CMake 3.13.3
-- Building for win64 using Visual Studio 15 2017 Win64
Working in C:\Wireshark-win64-libs-3.0
Tag 2019-01-23 not found. Refreshing.
Found 7-zip at C:\Program Files\7-Zip\7z.exe
New-Object : Exception calling ".ctor" with "0" argument(s): "This implementation is not part of the Windows Platform
FIPS validated cryptographic algorithms."
At C:\Users\dillja\Desktop\wireshark-3.0-test\tools\win-setup.ps1:212 char:19
+ $sha256 = New-Object Security.Cryptography.SHA256Managed
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (:) [New-Object], MethodInvocationException
+ FullyQualifiedErrorId : ConstructorInvokedThrowException,Microsoft.PowerShell.Commands.NewObjectCommand
CMake Error at CMakeLists.txt:110 (message):
Windows setup (win-setup.ps1) failed.
-- Configuring incomplete, errors occurred!
See also "C:/Users/dillja/Desktop/wsbuild64/CMakeFiles/CMakeOutput.log".
