Skip to content

Conversation

@ctz
Copy link
Member

@ctz ctz commented Dec 21, 2025

No description provided.

Comment on lines +196 to +217
cert_serial: String,

/// The SHA256 hash of the issuer's SubjectPublicKeyInfo structure.
///
/// This must be the base64 encoding of precisely 32 bytes.
issuer_spki_hash: String,

/// The Certificate Transparency logs and inclusion timestamps extracted
/// from the end-entity certificate.
///
/// Ths option should be supplied once for each log.
///
/// The format should be the base64 encoding of the CT log id, followed by
/// a colon, followed by the decimal encoding of the timestamp.
ct_timestamps: Vec<String>,

/// Return an error, and exit with code 2, if the certificate is not covered
/// by the filter set.
///
/// The default behaviour is to treat the certificate as unrevoked.
#[arg(long)]
error_if_uncovered: bool,
Copy link
Member

Choose a reason for hiding this comment

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

How about we use more specific types here and wire up clap to understand how to parse these?

For error-if-uncovered, maybe a more concise and less specific name like strict?

@@ -0,0 +1,74 @@
import base64
Copy link
Member

Choose a reason for hiding this comment

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

Would you like me to port this to Rust?

Copy link
Member Author

Choose a reason for hiding this comment

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

Yes please, eventually I would like to stuff everything into a singular rust program in revoke-test with the same output JSON, so switching over from the python version produces no change in output (which also checks that our rust code agrees with pyca's rust code).

@@ -0,0 +1,36 @@
//! NB. these tests require an up-to-date `revoke-test/decorated.json` input, and
//! a that the fetched revocation data set matches. They run `upki fetch` into
Copy link
Member

Choose a reason for hiding this comment

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

Nit: dangling "into".

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants