You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 1, 2023. It is now read-only.
I don't have time to flesh this out entirely, but assuming gpgsync is the client, and there's a role for an authority which signs the list of fingerprints, then you can add some other tools to push people's public keys as DNS records to the organization's domain using DANE, a very nascent standard.
Basically given admin-level API creds to the organization's DNS (cloudflare/route53/gandi) or whatever, this tool would optionally push and synchronize DNS records containing people's latest keys. In fact, it's probably best managed as an Ansible script, or it might be a different project than GPGSync if not in scope.
The text was updated successfully, but these errors were encountered:
Let"s pick this up soon. I want a PoC of RFC7929 sage and this seems like he perfect use case. It will get optional, but just for spreading awareness of the standard. Plus if your domain is signed with DNSSEC then the signed list of fingerprints are moot. :P lmk when you have a day to hack
I don't have time to flesh this out entirely, but assuming gpgsync is the client, and there's a role for an authority which signs the list of fingerprints, then you can add some other tools to push people's public keys as DNS records to the organization's domain using DANE, a very nascent standard.
Basically given admin-level API creds to the organization's DNS (cloudflare/route53/gandi) or whatever, this tool would optionally push and synchronize DNS records containing people's latest keys. In fact, it's probably best managed as an Ansible script, or it might be a different project than GPGSync if not in scope.
The text was updated successfully, but these errors were encountered: