*** R. Martinho Fernandes [2016-11-30 10:50]:
>I can't seem to find any up-to-date documentation on how to deploy DNS
>PKA records for use with `auto-key-locate`.
For me "gpg --export --export-options export-pka KEYID" works fine.
--
Sergey Matveev (http://www.stargrav
*** Paolo Bolzoni [Mon, 21 Mar 2016 10:44:06
+0100]:
>I was wondering if I should always add
>myself as recipient when encrypting a file, of course, in addition of
>the real recipient.
>
>Is there a reason not to?
Without yourself adding to the recipient: only remote party's key
compromising wil
- User brian m. carlson on 2012-01-23 00:47:03 wrote:
>> * sending ciphertext with the same "e" to several recipients
>This depends on a small message. All secure padding schemes avoid this
>problem because the pad the message so it is not small.
>> * no randomness
>All secure padding schemes
- User brian m. carlson on 2012-01-22 18:54:22 wrote:
>GnuPG uses PKCS #1 v1.5. This is specified in RFC 4880.
>You cannot choose a different padding scheme and remain in compliance
>with the OpenPGP standard.
Ah! I see. Thank you! Now I understand.
>If the standard allowed different padding
and other schemes
exist. How can I get which one is used? Trivial grep-ing through the
1.4.10 source code (which one I am using) does not help me much.
Moreover I did not find the way padding can be changed/specified for
example for RSA.
I will be glad to understand what I am missing.
--
Happy hacki
ompiled and built-in and
successfully used. GnuPG supports many other various ciphers such as
CAMELIA, Blowfish, Twofish, AES. You should recompile it with the needed
ones.
--
Happy hacking, Sergey Matveev █▉
FSFE Fellow #1390█▉█▉█▉
FSF Associate m
o any of our queries to send us more information on the mails
> triggering the posting. Thus we need to send these test mails in the
> hope to figure out the culprit.
Well, it is not me. Asure you :-)
--
Happy hacking, Sergey Matveev
FSF Associate member #5968 |
