-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Inconsistent handling of signatures, keys, etc. #63
Labels
Milestone
Comments
samuelwilliams
added a commit
that referenced
this issue
Oct 5, 2020
samuelwilliams
added a commit
that referenced
this issue
Oct 5, 2020
samuelwilliams
added a commit
that referenced
this issue
Oct 6, 2020
samuelwilliams
added a commit
that referenced
this issue
Oct 6, 2020
samuelwilliams
added a commit
that referenced
this issue
Oct 6, 2020
samuelwilliams
added a commit
that referenced
this issue
Oct 6, 2020
samuelwilliams
added a commit
that referenced
this issue
Oct 6, 2020
* Added method for calculating the digest. * Update README * Issue-63: CERT now only accepts binary certificates. * Simplify TimeFormat class. * DHCID digest now only accepts raw binary. * Issue #63: IPSECKEY::publicKey is raw binary only. * Issue #63 - Next hashed owner is expected as binary * Added method to calculate next owner hash. * Set the next owner name. * Issue #63: Signature must be binary. * Issue #63. SSHFP fingerprint to be inputted as raw binary.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The handling of cryptographic keys, signatures and other data that is ultimately represented as Base16, 32, or 64 encoded string is inconsistent across all Rdata type classes. These should be handled the same.
Signatures et al inputted into Rdata classes SHOULD be setted and getted in raw binary form; the only time it is outputted to a text encoding is when
$rdata->toText()
is called.This would be a backward-compatibility breaking change, so will not be implemented until v4.0
These are the classes that are affected:
KEYDNSKEYCDNSKEYDSCDSDLVTACERTDHCIDHIPIPSECKEYNSEC3RRSIGSIGSSHFPTKEYTLSATSIGThe future code should look like:
The downside of this would be that you would need to be careful to decode already Base64 encoded strings.
The text was updated successfully, but these errors were encountered: