-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
> Optionally, later on you can also do a (again, you have to pick
> whether to "revuid" or "deluid) (a "#" indicates a comment):
This will not work if you've sent your key to a keyserver, as is
recommended. It will also not work if you've sent yo
David Shaw wrote:
> You select the user id with "uid x" where x is the number of
> the user ID. Then "revuid".
Optionally, later on you can also do a (again, you have to pick
whether to "revuid" or "deluid) (a "#" indicates a comment):
$ gpg --edit-key 98E6705C
Command> uid
# shows uids so yo
Hi,
I've installed a tool to verify signed mail, enigmail,
that signals lots of bad signatures, using gpg. When
I verified those messages "manually" they were all ok.
Disagreement happens after the tool combines text and
signature into a unique file. I reproduced it as follows:
D:\tmp>gpg --ver
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
> ``never'' is in this case based on one case of provable secure scheme
> (that was notably difficult in implementation)?
I wouldn't be so quick to place blame on the difficulty of
implementing the one-time pad. Implementing the OTP is really pre
On 200704201113, Robert J. Hansen wrote:
> > Yeah, again. I completely agree on the practical aspect of it, but
> > would nevertheless like to see proofs of complexity that weren't
> > dependent on the current models of computations.
>
> I don't mean to sound flip, but as soon as you invent a hype
Hi,
Thanks to Werner and Sven your howto worked perfect !!
Fetch an Verify worked as expected after setting the URL.
Thanks again !
Ciao
Matze
Sven Radde wrote:
> Matthias Barmeier schrieb:
>> I tried to investigate what the URL should look like, but I cannot find
>> an example.
>> Cou
