You are missing another point, which is that -in addition to the
gpg.conf client preferences- the keys you are encrypting to have
preferences, too.
In fact, it is noted in the SE answer you linked:
> Per default, GnuPG will read the recipient's algorithm preferences and
> take the first algorithm
On Mon, 21 Jan 2019 23:09:10 +0100, Ángel stated:
>On 2019-01-19 at 11:09 -0500, Jerry wrote:
>> gpg> showphoto
>> Displaying jpeg photo ID of size 88074 for key 3873063887DEC564 (uid
>> 3)
>>
>> After a few seconds, an error message pops up on the screen.
>>
>> C:\Users\Gerard\AppData\Local\
On 2019-01-19 at 11:09 -0500, Jerry wrote:
> gpg> showphoto
> Displaying jpeg photo ID of size 88074 for key 3873063887DEC564 (uid 3)
>
> After a few seconds, an error message pops up on the screen.
>
> C:\Users\Gerard\AppData\Local\Temp\gpg-62cno9\87DEC564.jpg contains an
> invalid path.
>
> I
On Mon 2019-01-21 08:29:35 -0900, justina colmena via Gnupg-users wrote:
> How can people be so insufferably rude?
How indeed.
Justina, please keep discussion on-topic and friendly for this mailing
list. Too many of your posts to the list are full of invective,
threating assault, or incoherently
> On 21 Jan 2019, at 17:29, justina colmena via Gnupg-users
> wrote:
>
> How can people be so insufferably rude?
O_o
A
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
On Mon, 21 Jan 2019 08:29:35 -0900, justina colmena via Gnupg-users wrote:
[flush]
Regards
Stefan
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
On Montag, 21. Januar 2019 18:29:35 CET justina colmena via Gnupg-users wrote:
[snip]
> You've got email problems at KDE.
>
> X-Authenticated-User?
This header has been added by my email provider, not by KMail.
Regards,
Ingo
___
Gnupg-users mailing
On January 19, 2019 9:56:00 AM AKST, "Ingo Klöcker" wrote:
>On Samstag, 19. Januar 2019 17:10:38 CET Stefan Claas wrote:
>> Method used with GnuPG:
>>
>> In gpg.conf i put: photo-viewer "cat > %K.%t"
>>
>> and then i used this one liner:
>>
>> for filename in ./*.pgp; do gpg --list-keys --list-
On Mon, 21 Jan 2019 14:21:53 +0100, Peter Lebbing wrote:
Hi Peter,
> - Take the User Attribute Packet
> - Strip off the header: 1 byte tag, and in my case, 2 bytes length
> (lengths are encoded on 1, 2 or 5 bytes)
> - Hash what's left
>
> So:
>
> $ gpg --export KEYID | gpgsplit
>
> Take a fi
Hello Stefan,
On 21/01/2019 12:46, Stefan Claas wrote:
> To compute the hash of an image one has to add a 22bytes header
> to the image and then the hash will be properly computed.
Since I didn't exactly follow the "22 bytes" part I looked at it one
more time; I got curious. It turned out I accid
On Sun, 20 Jan 2019 20:27:33 +0100, Stefan Claas wrote:
> On Sun, 20 Jan 2019 19:22:10 +0100, Peter Lebbing wrote:
> > On 20/01/2019 17:07, Peter Lebbing wrote:
> > > I had a quick scan through the source code, but couldn't find it.
> >
> > Oops! I was looking at ancient code instead of the
On 20/01/2019 22:26, Frank Hrebabetzky wrote:
> It took me quite some time until I got aware of this. A term like
> "key" or "encryption key" would have made it easier for me, the
> "session" was somewhat misleading.
Yes, it is somewhat unfortunate. It is due to the mechanics of
symmetrically-encr
On 1/20/19 5:34 PM, Peter Lebbing wrote:
Hi Frank,
On 03/01/2019 15:25, Frank Hrebabetzky wrote:
gpg: AES256 encrypted data
gpg: encrypted with 1 passphrase
gpg: decryption failed: Bad session key
This is also the error message you get when you specify the wrong
passphrase. Perhaps you mistyp
13 matches
Mail list logo
