Skip to content

Remove incorrect logic for determining the apex from signing function. #521

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

Open
wants to merge 10 commits into
base: main
Choose a base branch
from

Conversation

ximon18
Copy link
Member

@ximon18 ximon18 commented May 8, 2025

Instead require the apex name to be passed in.

This fixes issues such as signing wrongly identifying an out-of-zone name (such as a glue that sorts earlier than the zone) as the apex instead of the zone itself.

Also update Rust Doc strings to more closely match current behaviour of the signing APIs.

…s, instead require the apex name to be passed in. This fixes issues such as signing wrongly identifying an out-of-zone name (such as a glue that sorts earlier than the zone) as the apex instead of the zone itself.

Also update Rust Doc strings to more closely match current behaviour of the signing APIs.
@ximon18 ximon18 requested a review from a team May 9, 2025 10:27
@ximon18 ximon18 marked this pull request as ready for review May 9, 2025 10:35
@@ -470,6 +486,10 @@ where
last_nent_stack.push(name.clone());
}

let Some(nsec3param_ttl) = nsec3param_ttl else {
return Err(SigningError::SoaRecordCouldNotBeDetermined);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this the wrong error here?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants