From: Pavlos Ratis <dastergon@gentoo.org>
To: gentoo-soc@lists.gentoo.org, gentoo-keys@lists.gentoo.org
Subject: [gentoo-soc] Gentoo Keys: Expansion and improvements -- weekly report #7
Date: Mon, 7 Jul 2014 00:06:27 +0300 [thread overview]
Message-ID: <CAOgmxWw43LC02mxJC=nFdnNCt7d=eALZpgxSHXv+sJJn3ZCDqQ@mail.gmail.com> (raw)
Hello,
This year I am working on improving and expanding the features of Gentoo Keys.
Gentoo Keys is a Python based project that aims to manage the GPG
keys used for validation on users and Gentoo's infrastructure
servers. These keys will be any/all of the release keys, developer keys
and any other third party keys or keyrings available or needed.
Source code: https://github.com/gentoo/gentoo-keys
Week #7
=======
Status: on schedule
Tasks done:
* Manage installed keys with separate seed files on each folder
* basic template: $keydir/devs/$name/gkey.seeds
* Implementation that checks/lists installed keys
* Complete key removal action
* Safely remove developer after a check in the proper seed file
* Testing with pypgpgme
Goals for the next week:
* Complete GPG key template
* Document process
* Testing
* Minor fixes
* Begin implementation of binary keyring support
Best regards,
Pavlos Ratis
reply other threads:[~2014-07-06 21:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAOgmxWw43LC02mxJC=nFdnNCt7d=eALZpgxSHXv+sJJn3ZCDqQ@mail.gmail.com' \
--to=dastergon@gentoo.org \
--cc=gentoo-keys@lists.gentoo.org \
--cc=gentoo-soc@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox