lucenenet-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rob J. Goldfarb" <goldf...@comcast.net>
Subject RE: bug fixed in lucene.Net 4.8 ?
Date Tue, 18 Jul 2017 14:21:21 GMT
thanks John


it works on 3.0.3


yaaaa!


r

> 
>     On July 17, 2017 at 9:52 AM "Hook, John" <jlhook@regenstrief.org> wrote:
> 
>     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
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message