-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Hi Werner,
Given that the default for smartcards is to store the backup on disk and
ask the user to move it to a safer place, we might as well do something
similar for revocation certificates. Comments?
my vote: yes. Non-intrusive
On Tue, 26 Feb 2013 12:45, o...@enigmail.net said:
my vote: yes. Non-intrusive information about what next steps should be. When
creating a key using Enigmail, it asks the user to save a rev cert. CLI should
do the same.
You mean printing a hint to create a recovation certificate would be
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Hi Werner,
When creating a key using Enigmail, it asks the user to save a rev cert.
CLI should do the same.
You mean printing a hint to create a recovation certificate would be
enough?
well, first it's just my opinion. Second, I'd vote
Am Di 26.02.2013, 14:37:49 schrieb Olav Seyfarth:
well, first it's just my opinion. Second, I'd vote for a hint _at least_.
I am a big fan of hints, too. If these get improved / extended an option like
--no-hints=all
--no-hints=noencryptionkey,norevocationcertificate,...
may be offered for
On Tue, 26 Feb 2013 15:16, mailinglis...@hauke-laging.de said:
I am a big fan of hints, too. If these get improved / extended an option like
--no-hints=all
Well, we have the --expert option. If it is used we could assume that a
hint is not required.
Salam-Shalom,
Werner
--
Die
