diff options
-rw-r--r-- | bugs.txt | 19 |
1 files changed, 19 insertions, 0 deletions
@@ -67,3 +67,22 @@ Yet Another UI Proposal | |||
67 | to allow them to be created with SHELL_CMD. If that is what the user intends, | 67 | to allow them to be created with SHELL_CMD. If that is what the user intends, |
68 | he can simply run SHELL_CMD manually and then run kiki using only the SPEC=file. | 68 | he can simply run SHELL_CMD manually and then run kiki using only the SPEC=file. |
69 | 69 | ||
70 | Note: | ||
71 | sync-secret is equivelent to the currently implemented 'sync' command. | ||
72 | Therefore, it accepts keyring files consisting of only public keys. | ||
73 | Thus, the user should beware, -secret versions of commands are not prohibited | ||
74 | from altering the public key database. | ||
75 | |||
76 | For consistency, import-secret will also be capable of importing public keyring | ||
77 | files. | ||
78 | |||
79 | The SPEC=file syntax is only useful for importing PEM files, and so the | ||
80 | import-public command, which is for importing other people's pgp keys, need | ||
81 | not accept this syntax. | ||
82 | Question: Since all supplied files to import-public are public keyrings, | ||
83 | is it necessary to document (or even implement) the --keyrings | ||
84 | option since no other mode is possible? | ||
85 | |||
86 | The SPEC=file syntax is useful for the import-secret command which can be | ||
87 | identical to sync-secret except that it does not attempt to lock or write | ||
88 | any files outside of GNUPGHOME. | ||