From: "Brian Dolbec" <dolsen@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/gentoo-keys:master commit in: gkeys-gen/gkeygen/
Date: Tue, 6 Jan 2015 21:45:36 +0000 (UTC) [thread overview]
Message-ID: <1420579180.284073e411a75c75efb0426ea444fc8783462bb5.dolsen@gentoo> (raw)
commit: 284073e411a75c75efb0426ea444fc8783462bb5
Author: Brian Dolbec <dolsen <AT> gentoo <DOT> org>
AuthorDate: Tue Jan 6 21:15:32 2015 +0000
Commit: Brian Dolbec <dolsen <AT> gentoo <DOT> org>
CommitDate: Tue Jan 6 21:19:40 2015 +0000
URL: http://sources.gentoo.org/gitweb/?p=proj/gentoo-keys.git;a=commit;h=284073e4
gkeysgen/actions.py: Add gen-key example
---
gkeys-gen/gkeygen/actions.py | 50 +++++++++++++++++++++++++++++++++++++++++++-
1 file changed, 49 insertions(+), 1 deletion(-)
diff --git a/gkeys-gen/gkeygen/actions.py b/gkeys-gen/gkeygen/actions.py
index 740d954..8f8c81a 100644
--- a/gkeys-gen/gkeygen/actions.py
+++ b/gkeys-gen/gkeygen/actions.py
@@ -35,7 +35,55 @@ Action_Map = OrderedDict({
'options': ['spec', 'dest'],
'desc': '''Generate a gpg key using a spec file''',
'long_desc': '''Generate a gpg key using a spec file''',
- 'example': '''''',
+ 'example': '''$ gkey-gen gen-key
+
+ GPG key creator
+ Spec file..: glep-63-recommended
+ Homepage...: https://wiki.gentoo.org/wiki/GLEP:63
+
+Give your Full Name: Foo Barr
+Give your Email: foo@barr.net
+
+Review:
+ Full Name: Foo Barr
+ Email: foo@barr.net
+
+Continue?[y/n]: y
+
+* Creating gpg folder at /home/brian/gkeys-user/gpghome
+
+ * Creating gpg.conf file at /home/brian/gkeys-user/gpghome
+
+
+ ____________________
+ < Generating GPG key >
+ --------------------
+ \ ^__^
+ \ (oo)\_______
+ (__)\ )\/
+ ||----w |
+ || ||
+
+ * Give the password for the key. (Pick a strong one)
+ Please surf the internet, type on your keyboard, etc.
+ This helps the random number generator work effectively
+
+ Your new GLEP 63 based OpenPGP key has been created in /home/brian/gkeys-user/gpghome
+
+
+ GPG key info:
+ Full Name: Foo Barr,
+ Email: foo@barr.net,
+ Fingerprint: CF8F369903999538F79287497AD8F5FEF19A7A69
+
+
+ In order to use your new key, place the new gpghome to your ~/.gnupg folder by running the following command:
+ mv /home/brian/gkeys-user/gpghome ~/.gnupg
+ Important: If you have another old key in ~/.gnupg please make sure you backup it up first.
+
+ Please read the FAQ for post-generation steps that are available in:
+ https://wiki.gentoo.org/wiki/Project:Gentoo-keys/Generating_GLEP_63_based_OpenPGP_keys
+''',
},
'list-specs': {
'func': 'list_specs',
next reply other threads:[~2015-01-06 21:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-06 21:45 Brian Dolbec [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-07-07 5:23 [gentoo-commits] proj/gentoo-keys:master commit in: gkeys-gen/gkeygen/ Brian Dolbec
2016-03-01 16:18 Brian Dolbec
2015-03-10 22:14 Brian Dolbec
2015-01-06 21:45 Brian Dolbec
2015-01-01 17:44 Brian Dolbec
2014-12-26 5:02 Brian Dolbec
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=1420579180.284073e411a75c75efb0426ea444fc8783462bb5.dolsen@gentoo \
--to=dolsen@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@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