Really, I want to recommend Delta. It's *great* for people who want a chat-style email client with automatic encryption support. But it seems the moment you want to do something like *not* have a different PGP key on every client, it all falls apart, because it feels like the import/export features haven't been properly tested.
@tek_dmn it's true that there was not very much effort spend on key management as the primary focus is on people who don't want to, or can't, care for key management. It makes sense to revisit this area and improve it, though.
@delta Honestly, I'd start with checking your Autocrypt setup handling. Because that could solve most of the headache if it would either accept a message, or give a more descriptive error.
Unfortunately, I'm nowhere near capable enough to try to submit a contribution myself.
(What I'd really like would be a *few* clients to try, to see if it's Delta being weird, or K9 being weird.. even though it technically seems correct)
@Sandra I mean, I could try stripping out the JPEG UID and the EC keys.
But if it's not processing RSA4096 (as a GitHub issue claims) then there's no point, I'd basically have to create a new keypair, which is what I'm trying to expressly avoid.
@Sandra Just checked - no photo. No extra keys. No password.
set_self_key: rPGP error: no matching packet found.
On further check: it needs NON-armored keys. But exports armored keys.
That's... even weirder.
@Sandra So then I take my 100% full key, photo and everything, and try to stuff it in there. And now it claims there's "no private keys" with the binary version, but now it imports the ascii-armored version???
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!