From b0b3be76cccf07f5c1b5050b8c53389c46a05bf5 Mon Sep 17 00:00:00 2001 From: joe Date: Wed, 23 Apr 2014 23:09:06 -0400 Subject: notes from discussion were added to bugs.txt UI proposal --- bugs.txt | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) diff --git a/bugs.txt b/bugs.txt index 2ba2c68..330f091 100644 --- a/bugs.txt +++ b/bugs.txt @@ -67,3 +67,22 @@ Yet Another UI Proposal to allow them to be created with SHELL_CMD. If that is what the user intends, he can simply run SHELL_CMD manually and then run kiki using only the SPEC=file. + Note: + sync-secret is equivelent to the currently implemented 'sync' command. + Therefore, it accepts keyring files consisting of only public keys. + Thus, the user should beware, -secret versions of commands are not prohibited + from altering the public key database. + + For consistency, import-secret will also be capable of importing public keyring + files. + + The SPEC=file syntax is only useful for importing PEM files, and so the + import-public command, which is for importing other people's pgp keys, need + not accept this syntax. + Question: Since all supplied files to import-public are public keyrings, + is it necessary to document (or even implement) the --keyrings + option since no other mode is possible? + + The SPEC=file syntax is useful for the import-secret command which can be + identical to sync-secret except that it does not attempt to lock or write + any files outside of GNUPGHOME. -- cgit v1.2.3