1 1 # project keyring
2 -the **libk project keyring** contains the public PGP keys of the team members who are authorized to cut an official libk release. for security reasons, the keyring is *not* part of the libk repository itself; only those with root access to the libk server have write access to it. the keyring is always signed by the current project maintainer; always verify this signature before relying on keyring signatures for authentication.
2 +the **libk project keyring** contains the public signify keys of the team members who are authorized to cut an official libk release. for security reasons, the keyring is *not* part of the libk repository itself; only those with root access to the libk server have write access to it. the keyring is always signed by the current project maintainer; always verify this signature before relying on keyring signatures for authentication.
3 3
4 4 * **keyring URL:** [https://c.comint.su/keyring/libk](https://c.comint.su/keyring/libk)
5 5
6 -you can find individual developer PGP fingerprints on the [personnel roster](/wiki?name=roster), but **never** use that page to authenticate a release; always use the dedicated project keyring. not all developers are authorized to issue a release tarball.
6 +you can find individual developer PGP fingerprints on the [personnel roster](/wiki?name=roster), but **never** use that page (or PGP) to authenticate a release; always use the dedicated project signify keyring. not all developers are authorized to issue a release tarball.