On Wed, 14 Nov 2012 00:27, r...@sixdemonbag.org said:
Including random_seed? I've always been under the impression that's a
big no-no.
Well, it is a backup and assumed to be used after a loss of data and not
to replicate the data to several sites.
random_seed is a cache file to speed up
On 11/14/2012 10:52 AM, Werner Koch wrote:
On Wed, 14 Nov 2012 00:27, r...@sixdemonbag.org said:
Including random_seed? I've always been under the impression that's a
big no-no.
Well, it is a backup and assumed to be used after a loss of data and not
to replicate the data to several
How do I decrypt my backup in case of a disaster, if the secret key is in
the encrypted backup?
Am 14.11.2012 11:08 schrieb Werner Koch w...@gnupg.org:
On Wed, 14 Nov 2012 00:27, r...@sixdemonbag.org said:
Including random_seed? I've always been under the impression that's a
big no-no.
On Wed, 14 Nov 2012 11:34, kue...@googlemail.com said:
How do I decrypt my backup in case of a disaster, if the secret key is in
the encrypted backup?
You surely have your secret key somewhere on a CD or a printout
(cf. paperkey), right?
Salam-Shalom,
Werner
--
Die Gedanken sind frei.
On Wed, 14 Nov 2012 12:15, kristian.fiskerstr...@sumptuouscapital.com
said:
Is there any configuration option to force the use of /dev/random? I'm
You mena, not to use the seed file?
gpg --no-random-seed-file
Shalom-Salam,
Werner
--
Die Gedanken sind frei. Ausnahmen regelt ein
On 11/14/2012 10:03 PM, Werner Koch wrote:
On Wed, 14 Nov 2012 12:15, kristian.fiskerstr...@sumptuouscapital.com
said:
Is there any configuration option to force the use of /dev/random? I'm
You mena, not to use the seed file?
gpg --no-random-seed-file
I do indeed, thank you :)
--
On Tue, 13 Nov 2012 15:40, melvincarva...@gmail.com said:
So I assume when backing up a key you should always back up trustdb too?
Yes. Actually eyerything in ~/.gnupg and below should be go into the
backup.
Salam-Shalom,
Werner
--
Die Gedanken sind frei. Ausnahmen regelt ein
On 11/13/12 12:45 PM, Werner Koch wrote:
Yes. Actually eyerything in ~/.gnupg and below should be go into the
backup.
Including random_seed? I've always been under the impression that's a
big no-no.
___
Gnupg-users mailing list
On Sat, 10 Nov 2012 20:33, melvincarva...@gmail.com said:
gpg --import-ownertrust trustdb.gpg
That does not work. --import-ownertrust expects the format as produced
by --export-ownertrust. What you can do is to put trustdb.gpg into an
empty directy and run the export command:
cp
On 8 November 2012 14:01, Werner Koch w...@gnupg.org wrote:
On Thu, 8 Nov 2012 09:37, melvincarva...@gmail.com said:
Does anyone know if there's a safe way to recover my web of trust, or
should I make an ultimately trusted key first, and start from scratch?
ssh otherbox rm
I've just managed to recover my gpg key from an old machine that died.
But the trust db was not imported.
Does anyone know if there's a safe way to recover my web of trust, or
should I make an ultimately trusted key first, and start from scratch?
___
On Thu, 8 Nov 2012 09:37, melvincarva...@gmail.com said:
Does anyone know if there's a safe way to recover my web of trust, or
should I make an ultimately trusted key first, and start from scratch?
ssh otherbox rm .gnupg/trustdb.gpg
gpg --export-ownertrust | ssh otherbox gpg
12 matches
Mail list logo
