lucenenet-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shad Storhaug <>
Subject RE: bug fixed in lucene.Net 4.8 ?
Date Tue, 18 Jul 2017 09:04:50 GMT

I believe the correct fix for this would be to set 

Cryptography.FIPSCompliant = true;

at application startup. That will enable FIPS compliant (SHA1) hashes rather than disabling
detection of MD5 hashes.

However, I can confirm there are no longer any references to System.Security.Cryptography
in Lucene.Net 4.8, so this issue no longer exists.

Shad Storhaug (NightOwl888)

-----Original Message-----
From: Hook, John [] 
Sent: Monday, July 17, 2017 8:53 PM
To:; Roj Goldfarb
Subject: RE: bug fixed in lucene.Net 4.8 ?


The easy work around for this issue is to add the following to your app.config

        <enforceFIPSPolicy enabled="false"/>

Additional information can be found at


-----Original Message-----
From: Roj Goldfarb [] 
Sent: Monday, July 17, 2017 9:40 AM
Subject: bug fixed in lucene.Net 4.8 ?

Not sure if this should be sent to this list or dev list.  If the dev list, please let me
know and i will send an email there.

I stopped using Lucene.Net 3.0.3 because I was getting the following exception on the FSDirectory.Open()

".. Exception has been thrown by the target of the invocation, System.InvalidOperationsException:
This implementation is not part of the windows Platform FIPS validated cryptographic algorithms."

This problem occurs on Windows 7 using a Visual Studio 13 developed application.

The FIPS compliance setting cannot be disabled.

Will Lucene.Net 4.8 fix this problem ?

Robert Goldfarb

View raw message