История изменений

<@dol-sen> the gentoo-keys project uses the source philosophy, it has seed key info, then imports the keys from a server and checks the fingerprints match what was expected

<@dol-sen> there will be a layman seed key file once there are overlays that require it, dev overlays will have the dev gpg keys available already

<@dol-sen> Currently, I am starting to work on the git hook for verifying git commits for the git migration

<@dol-sen> the layman repositories list is slated to be gpg signed, and moved to a different server/url

<@dol-sen> so it will authenticate the repo list it downloads

<@dol-sen> like i said there is preliminary support in layman-9999 already, but I will change it to use the gentoo-keys as the dep which will use the same lib I created to interface gpg for layman, so should be a simple migration

<@dol-sen> it shouldn't be hard to add gpg support into portage using the gentoo-keys project for verification too

<@dol-sen> the gentoo-keys project uses the source philosophy, it has seed key info, then imports the keys from a server and checks the fingerprints match what was expected

<@dol-sen> there will be a layman seed key file once there are overlays that require it, dev overlays will have the dev gpg keys available already

<@dol-sen> Currently, I am starting to work on the git hook for verifying git commits for the git migration

<@dol-sen> the layman repositories list is slated to be gpg signed, and moved to a different server/url

<@dol-sen> so it will authenticate the repo list it downloads

<@dol-sen> like i said there is preliminary support in layman-9999 already, but I will change it to use the gentoo-keys as the dep which will use the same lib I created to interface gpg for layman, so should be a simple migration