sigul

#21 Document how secret binding works
Opened by ertzing. Modified

Open
Close Issue

Sigul seems to have a concept of secret binding to real with keyphrases in a more secure manner.
Besides what's in the code I've not been able to turn up any documentation/examples of how this is supposed to be used in practice.
There seem to be client and server bindings? Why? What do either of those do? Do they have to be the same? How does one create a binding in the first place? The grant-key-access command seems to have the ability to generate bindings, but I've not been able to make that work.
Some clarity around this (preferably with some examples) would be much appreciated.

Right now, for my playground installation integrating with koji via robosignatory I've found out that using a passphrase file like [{"method": "test", "value": "<passphrase>", "may_unbind": "1"}] and binding methods of test on server and client works, but clearly that's not ideal.
carriestrothers commented

Sigul seems to have the secret sauce for secure linking, but I haven't found any specific documentation. Can anyone explain what client-server links are and how to create them? Thanks!
tomb of the mask
Metadata
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.