I'm trying to learn the pgp packet syntax. I created a new key with gpg2
--gen-key and then gpg2 --export > pubkey.key and then gpg2 --dearmor
pubkey.key. Which left me with a pubkey.key.gpg file. I then did a
hexdump of the file and the first word is `99' which in binary would be
`10011001'. I
On Tue, 10 Apr 2018 17:19, lp...@kde.org said:
> Proxy request sent, awaiting response... 200 OK
> Length: 58162 (57K) [application/pgp-keys]
Okay that works. Now we need to see why dirmngr has a different idea.
When we first talked on IRC, someone else reported that he had no
problems with that
On Wed, 11 Apr 2018 00:00, gnupg-users@gnupg.org said:
> when writing C code using the GPG Made Easy library, the function
> "gpgme_op_createkey" is always throwing the error "Not supported" and I can't
> find any solution to resolve this.
I would suggest to run this with GPGME_DEBUG set. For e
Errata,
3 - Compute SHe = sk^d mod n
of course really meant:
3 - Compute SHe = SH^d mod n
Mike
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
Peter,
Thanks for engaging, and walls of words with way too long sentences are all
too easy to create - I'm also bad at occasionally using the wrong word
(public vs private, for instance) which can render the whole wall confused.
So, my main challenge is that I have to "code and release" this sys
On 11/04/18 14:51, Mike Inman wrote:
> Encrypt the message with a symmetric algorithm, adding salt and a
> hash/checksum to ensure validity.
I'm not sure what you're salting exactly, but anyway, this is not the focal
point of my reply. By the way, there are many ways to do what you describe in
suc
*** Correcting one, somewhat important, word ***
Hi Dirk & Ken,
I'm working on a similar problem... automated decryption "in the field" and
what I have come to is this:
Encrypt the message with a symmetric algorithm, adding salt and a
hash/checksum to ensure validity. Then, taking that result a
when writing C code using the GPG Made Easy library, the function
"gpgme_op_createkey" is always throwing the error "Not supported" and I can't
find any solution to resolve this.
1) Does anyone know why this error is being thrown, or what common causes are
for this error?
2) Does anyone know of
Hello together,
after updating from gnupg 2.2.5 to 2.2.6, I'm facing a possible regression.
We use the gpgme 1.8.0 library to verify the integrity of our update packages.
Two valid signatures need to be present on the checked file.
One unit test checks a file that is signed by two
known keys + u
