[
https://issues.apache.org/jira/browse/LUCENENET-535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shad Storhaug resolved LUCENENET-535.
-------------------------------------
Resolution: Not A Problem
I am closing this as there is no longer a Cryptography.cs file in Lucene.Net
4.8.0 or any such file that requires FIPS compliance. Lucene.Net 3.0.3 is no
longer being maintained.
> Add FIPS-Compliant flag that can be set at runtime
> --------------------------------------------------
>
> Key: LUCENENET-535
> URL: https://issues.apache.org/jira/browse/LUCENENET-535
> Project: Lucene.Net
> Issue Type: Improvement
> Components: Lucene.Net Core
> Reporter: Drew Mace
> Assignee: Itamar Syn-Hershko
> Priority: Critical
> Attachments: LUCENENET-535.patch
>
>
> Systems that run in environments where MD5 is disallowed (DoD and various
> public corporations) that utilize Lucene.Net will encounter an issue with MD5
> being used in the Cryptography.cs class.
> By introducing a runtime flag, the user will be able to make the app FIPS
> compliant.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
