dmarcator 1.2.0 → 1.2.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 48797112128c5187471c9c2ad1f907c73450cf8ef0f6910e2a22815d74221222
-  data.tar.gz: 89727b4555cc67beddbcb53dbbfb4845dc69e6cb8c66e37b8549fa7a4ec2ec36
+  metadata.gz: c588b9e28df99c70cd55c29c83854064092e2ff74436c9be680afc2b2a77824c
+  data.tar.gz: 3e6692aa15ea2aa28fa451dc847c3cadbd0cb36cdaf237e8bcb6e591206f92d0
 SHA512:
-  metadata.gz: b6305c8a45f78711592f6a68b61236241d68a45410de08eaeeaa8e158b6337421e9b5d6c78b21ace4b0b38109fa74f3eec198ba4b5bbe6c2a49e5127ff2e69ff
-  data.tar.gz: 20111fdcf9bd38ff20f48a2be10ffdf4aa946850643fca2a48696fa10c041f5b3a4d49d37f6deed32f9767ed758828fce1ade967a8c12fc52cd0c1adc2ede6a2
+  metadata.gz: 890fe93593dd8ae6cc2888910070d73606f2700ce3e6548b09cbfcca29f86067788894dbdd23d984a23a7662059514564f955ffdf476656d94110289603b8d4c
+  data.tar.gz: b3357457dbeb21bcd40dee7a412eacc9df9d60b148eae9b0f753c2ca6534d299f4ff6bd7585fcfcf67d4482eabc4f6227ac0878af1d839721de1e2cd7334853f

data/ChangeLog.md

@@ -1,3 +1,10 @@
+### 1.2.1 / 2026-10-30
+
+* Add a record-parser corpus regression net: 143 records (published real-world records plus edge cases) with their accepted outcomes in lenient and strict mode, replayed by the test suite. A parser change that alters how any record parses now fails with a diff. Regenerate with `script/generate_record_corpus.rb`.
+* Report a TCP response body shorter than its declared length as `short DNS response (expected N bytes, got M)`, instead of the opaque `malformed DNS response: limit exceeded`.
+
+No public API changes.
+
 ### 1.2.0 / 2026-10-30
 
 * Plaintext lookups now use DNS over TCP (`DMARCator::Resolver::Plain`) instead of `Resolv::DNS`. `Resolv` reads UDP replies into a 512-byte buffer, so a larger answer cannot be decoded, is discarded, and the resulting timeout is swallowed. Any TXT set over 512 bytes — common for SPF and for domains with several DKIM keys — was therefore returned as an empty array, which is indistinguishable from "no records published". TCP has no such limit, and failures raise `ResolutionError`.

data/README.md

@@ -367,6 +367,21 @@ To run the RSpec tests:
 rake spec
 ```
 
+### Record parser corpus
+
+`spec/support/record_corpus.txt` holds representative records — real-world
+published records and edge cases — and `spec/support/record_corpus.json` the
+outcomes they produced when the corpus was last accepted. The suite replays both
+in lenient and strict mode, so a parser change that alters how any of them parses
+fails with a diff.
+
+If such a change is intentional, regenerate the file and review the JSON diff in
+the commit:
+
+```sh
+ruby -Ilib script/generate_record_corpus.rb
+```
+
 ## Releasing
 
 Every published version must have an annotated tag pointing at the commit that

data/lib/dmarcator/resolver/plain.rb

@@ -107,8 +107,13 @@ module DMARCator
         header = socket.read(2)
         raise ResolutionError, 'short DNS response' if header.nil? || header.bytesize < 2
 
-        body = socket.read(header.unpack1('n'))
-        raise ResolutionError, 'short DNS response' if body.nil?
+        length = header.unpack1('n')
+        body = socket.read(length)
+
+        if body.nil? || body.bytesize != length
+          raise ResolutionError,
+                "short DNS response (expected #{length} bytes, got #{body&.bytesize || 0})"
+        end
 
         body
       ensure

data/lib/dmarcator/version.rb

@@ -2,5 +2,5 @@
 
 module DMARCator
   # dmarcator version
-  VERSION = '1.2.0'
+  VERSION = '1.2.1'
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: dmarcator
 version: !ruby/object:Gem::Version
-  version: 1.2.0
+  version: 1.2.1
 platform: ruby
 authors:
 - Noah Berman