lucenenet-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hook, John" <jlh...@regenstrief.org>
Subject RE: bug fixed in lucene.Net 4.8 ?
Date Mon, 17 Jul 2017 13:52:37 GMT
Roj,

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

<configuration>
    <runtime>
        <enforceFIPSPolicy enabled="false"/>
    </runtime>
</configuration>

Additional information can be found at https://docs.microsoft.com/en-us/dotnet/framework/configure-apps/file-schema/runtime/enforcefipspolicy-element

John

-----Original Message-----
From: Roj Goldfarb [mailto:goldfrhj@comcast.net] 
Sent: Monday, July 17, 2017 9:40 AM
To: user@lucenenet.apache.org
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()
call:


".. 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

Mime
View raw message