Cryptographic Signatures Documentation #13

Merged
thebeanogamer merged 3 commits from signatures into main 2026-04-21 13:36:10 +00:00
Member

This is my best understanding based on reading source code, I'd really appreciate @jcline checking I've understood correctly please. I don't want this to replace the deeper documentation that each tool provides, just to act as a high-level summary with links to where people can learn more.

I believe @jcline is also planning a Flock talk, so we could embed the recording on here once that's done.

Resolves #10.

Signed-off-by: Daniel Milnes daniel@daniel-milnes.uk

This is my best understanding based on reading source code, I'd really appreciate @jcline checking I've understood correctly please. I don't want this to replace the deeper documentation that each tool provides, just to act as a high-level summary with links to where people can learn more. I believe @jcline is also planning a Flock talk, so we could embed the recording on here once that's done. Resolves #10. Signed-off-by: Daniel Milnes <daniel@daniel-milnes.uk>
Signed-off-by: Daniel Milnes <daniel@daniel-milnes.uk>
@ -0,0 +182,4 @@
Written in Rust, Siguldry is the next generation of Fedora's signing infrastructure. Its architecture is heavily based on Sigul, taking advantage of modern features like `systemd-credentials` for the mTLS connections between components.
Currently, Siguldry is only used for signing PE Executables for Secure Boot (by emulating a `pesign` backend), however it is intended to gradually replace the other signing tools discussed here. It is hosted alongside the existing Sigul infrastructure.
First-time contributor

To be a bit more precise sigul-pesign-bridge (in the same repo) is the only bit currently involved and acts as a client to the existing Sigul server.

To be a bit more precise [sigul-pesign-bridge](https://crates.io/crates/sigul-pesign-bridge) (in the same repo) is the only bit currently involved and acts as a client to the existing Sigul server.
Author
Member

Ah, I wasn't sure if the pesign stuff was pointing at Sigul or Siguldry. Thanks for cleaning that up.

I'll update this to clarify.

Ah, I wasn't sure if the pesign stuff was pointing at Sigul or Siguldry. Thanks for cleaning that up. I'll update this to clarify.
thebeanogamer marked this conversation as resolved
@ -0,0 +184,4 @@
Currently, Siguldry is only used for signing PE Executables for Secure Boot (by emulating a `pesign` backend), however it is intended to gradually replace the other signing tools discussed here. It is hosted alongside the existing Sigul infrastructure.
Additional documentation for Siguldry can be found on https://github.com/fedora-infra/siguldry/[GitHub].
First-time contributor

Not sure if it's the final location, but for now I've got it building docs to https://fedora-infra.github.io/siguldry/. Still very patchy, but the design doc with graphs might be helpful if you've not already seen it

Not sure if it's the final location, but for now I've got it building docs to https://fedora-infra.github.io/siguldry/. Still very patchy, but the design doc with graphs might be helpful if you've not already seen it
Author
Member

👀 I didn't see that site (will add a link), but did see the .dot diagrams in the repo. They were very useful, I'm not sure if we can/should embed them in the docs here?

I don't think this is the right home for a detailed explanation of each individual tool's guts, but https://github.com/fedora-infra/siguldry/blob/main/docs/diagrams/architecture.dot is a really nice visual explanation of how this works.

👀 I didn't see that site (will add a link), but did see the `.dot` diagrams in the repo. They were very useful, I'm not sure if we can/should embed them in the docs here? I don't think this is the right home for a detailed explanation of each individual tool's guts, but https://github.com/fedora-infra/siguldry/blob/main/docs/diagrams/architecture.dot is a really nice visual explanation of how this works.
First-time contributor

I think you'll be safe linking to https://fedora-infra.github.io/siguldry/diagrams/architecture.svg directly if you want, it should be a stable link (famously said of all dead links out there, I'm sure)

I think you'll be safe linking to https://fedora-infra.github.io/siguldry/diagrams/architecture.svg directly if you want, it _should_ be a stable link (famously said of all dead links out there, I'm sure)
Author
Member

Added a link to the documentation and embedded the diagram (can swap that for a link if you prefer).

Added a link to the documentation and embedded the diagram (can swap that for a link if you prefer).
thebeanogamer marked this conversation as resolved
thebeanogamer changed title from WIP: Cryptographic Signatures Documentation to Cryptographic Signatures Documentation 2026-04-09 21:28:10 +00:00
Author
Member

Removed the WIP marking as I think this is mostly done, but I'd still like to collect more feedback before merging.

Removed the WIP marking as I think this is mostly done, but I'd still like to collect more feedback before merging.
thebeanogamer deleted branch signatures 2026-04-21 13:36:10 +00:00
Sign in to join this conversation.
No reviewers
No labels
page idea
meeting
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
security/docs!13
No description provided.