Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Environment:

      CLR 2.0; DOT.NET

      Description

      The FSDirectory.cs is the only place it have to be modified to apply FIPS compliance.

      I think, changing to use a FIPS compliant algorithm in general for the NET port of lucene to calc the lock
      file name is "safe" (mean: java-compat.) - the only case where I can see the
      may have to use the same algorithm is if a java-lucene impl. access the
      index with a writer at the same time as lucene.net - that would be rarely
      the case: writing to the same index is only allowed by one writer.

      First change required was to switch
      private static System.Security.Cryptography.MD5 DIGESTER; to
      private static readonly System.Security.Cryptography.HashAlgorithm DIGESTER;

      Last change is this:
      #if FIPS_COMLIANT
      // use a FIPS compliant algorithm (see also http://blog.aggregatedintelligence.com/2007/10/fips-validated-cryptographic-algorithms.html )
      DIGESTER = System.Security.Cryptography.SHA1.Create();
      #else
      // use the java compatible hash algorithm:
      DIGESTER = System.Security.Cryptography.MD5.Create();
      #endif

      I will attach the .patch to.

        Attachments

        1. FIPS_COMLIANCE.patch
          1.0 kB
          Torsten Rendelmann
        2. LUCENENET-175.rar
          1 kB
          Digy
        3. LUCENENET-175.rar
          0.9 kB
          Digy

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                torstenr Torsten Rendelmann
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 0.25h
                  0.25h
                  Remaining:
                  Remaining Estimate - 0.25h
                  0.25h
                  Logged:
                  Time Spent - Not Specified
                  Not Specified