Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* In func (zl *zlexer) Next() (lex, bool) make max token size buffers str and com something we can grow. Why? Because. Reasons: When experimenting with OPENPGPKEY records, which themselves are basically a key, if my zone file already has an RSA 4096 public key record, this lib goes boom: dns: bad OPENPGPKEY PublicKey: "token length insufficient for parsing" at line: ..... The key is good. Testing against bare ed25519 keys whose base64 length is ~320 characters and there are no problems Testing against a bare RSA4096 key whose base64 length is ~3100 characters and: problems. Bare is the key word here, since for DNS, one ideally publishes as bare a key as possible, minus signatures, minus photos, minus extra metadata beyond the essential that will push a record length up. A typical public key with two RSA 4K subkeys and several signatures may rise to > ~21000 bytes. * Test case for OPENPGPKEY (valid, test pgp public keys) Reverse TLSA test record fail logic TestNewRRCommentLengthCrasherString: ...
- Loading branch information
1 parent
4bdf302
commit f07f1e6
Showing
2 changed files
with
25 additions
and
13 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters