More specifically, if I was to attach my public key to every email — even when the recipient doesn’t use PGP.

My assumption is that “life would carry on” and there would be basically no difference but I’m not entirely sure.

the process of using PGP for encrypting content (text messages for example) is something I’m only just started understanding after some reading and practicing

EDIT

Since a couple of people have mentioned it, my email provider provides E2EE between users but it I want to have E2EE with non-users and via my aliases (SimpleLogin) with custom domains I’ll need PGP

  • PassingThrough@lemmy.world
    link
    fedilink
    English
    arrow-up
    5
    ·
    edit-2
    3 months ago

    One thing I can think of is an overzealous corporate security solution blocking or holding back your email purely for having an attachment, or because it misunderstands/presumes the cipher-looking text file to be an attempt to bypass filtering.

    Other than that might be curious questions from curious receivers of the key/file they may not understand, and will not be expecting. (“What’s this for? Is this part of the contract documents? Oh well, I’ll forward it to the client anyway”)

    Other than that it’s a public key, go for it. Hard (for me anyway) to decide to post them to public keychains when the bot-nets read them for spam, so this might be the next best thing?