Added a note about NSEC3 hash cracking for zone file data

2024-03-06 14:16:05 -05:00 · 2024-03-06 14:16:05 -05:00 · cba51ca2dd
parent 654e4a8667
commit cba51ca2dd
1 changed files with 5 additions and 0 deletions
--- a/ingestors/ingest_zone.py
+++ b/ingestors/ingest_zone.py
@ -146,4 +146,9 @@ Will be indexed as:
        "seen"    : "2021-09-01T00:00:00Z" # Zulu time added upon indexing
    }
 }
+'''
+
+'''
+Notes:
+- How do we want to handle hashed NSEC3 records? Do we ignest them as they are, or crack the NSEC3 hashes first and ingest?
 '''