/biz/ - Business & Finance

>PGP Signed Messages (Authentication)
In order to verify the Time of creation, authenticity of a message and to ensure the message has not been tampered with, PGP signatures are used. Here's the basic process of how messages are PGP signed.

The process begins by creating a hash of the plaintext message.
User A uses their private key to encrypt the hash.
This encrypted hash is added to the bottom of the plaintext message.
Utilizing User A's known public key, anyone can verify the signature by decrypting it using User A's public key and comparing the hash of the signature to the hash of the plaintext.

>Utilization
If you're still reading, you might be thinking, fuck. This is a lot of individual steps to take, rest easy. The majority of the processes we have covered are conducted by your PGP software, so have a look at a few of the most common software suites that make this possible. This part is really up to the user, research different software and find out which one suits your skill level and needs best.
>Kleopatra - PGP GUI for windows and linux
https://apps.kde.org/kleopatra/

>GnuPG - Strictly CLI for windows and linux
https://www.gnupg.org/index.html

>Final Words
While this is in no way a complete guide to using PGP, the hope here is that even low IQ anon's can have a basic understanding of how PGP works and how it can improve your opsec. Remember to secure your private key with care and good opsec is about continued attention to detail over time.
>https://www.openpgp.org/about/
>https://www.makeuseof.com/tag/pgp-me-pretty-good-privacy-explained/
>https://users.ece.cmu.edu/~adrian/630-f04/PGP-intro.html

>PGP Signed Messages (Authentication)
In order to verify the Time of creation, authenticity of a message and to ensure the message has not been tampered with, PGP signatures are used. Here's the basic process of how messages are PGP signed.

The process begins by creating a hash of the plaintext message.
User A uses their private key to encrypt the hash.
This encrypted hash is added to the bottom of the plaintext message.
Utilizing User A's known public key, anyone can verify the signature by decrypting it using User A's public key and comparing the hash of the signature to the hash of the plaintext.

>Utilization
If you're still reading, you might be thinking, fuck. This is a lot of individual steps to take, rest easy. The majority of the processes we have covered are conducted by your PGP software, so have a look at a few of the most common software suites that make this possible. This part is really up to the user, research different software and find out which one suits your skill level and needs best.
>Kleopatra - PGP GUI for windows and linux
https://apps.kde.org/kleopatra/

>GnuPG - Strictly CLI for windows and linux
https://www.gnupg.org/index.html

>Final Words
While this is in no way a complete guide to using PGP, the hope here is that even low IQ anon's can have a basic understanding of how PGP works and how it can improve your opsec. Remember to secure your private key with care and good opsec is about continued attention to detail over time.
>https://www.openpgp.org/about/
>https://www.makeuseof.com/tag/pgp-me-pretty-good-privacy-explained/
>https://users.ece.cmu.edu/~adrian/630-f04/PGP-intro.html