gpg --export --armor john@example.com > john_doe.pub
-----BEGIN PGP PUBLIC KEY BLOCK-----
mQGiBEm7B54RBADhXaYmvUdBoyt5wAi......=vEm7B54RBADh9dmP
-----END PGP PUBLIC KEY BLOCK-----
About the arguments:
Instead of risky "free PDF" links, you can access these excellent resources legally:
Weaknesses / Legal and ethical concerns
became his virtual classroom. He practiced integration while his neighborhood slept and tackled rotational mechanics during his bus rides, scrolling through PDFs on a cracked smartphone screen.
gpg --keyid-format LONG --list-keys john@example.com
pub rsa4096/ABCDEF0123456789 2018-01-01 [SCEA] [expires: 2021-01-01]
ABCDEF0123456789ABCDEF0123456789
uid [ ultimate ] John Doe <john@example.com>
This shows the 16-byte Key-ID right after the key-type and key-size. In this example it's the highlighted part of this line:
pub rsa4096/ABCDEF0123456789 2018-01-01 [SCEA] [expires: 2021-01-01] iit jee books pdf google drive free
The next step is to use this Key-ID to send it to the keyserver, in our case the MIT one. Instead of risky "free PDF" links, you can
gpg --keyserver keyserver.ubuntu.com --send-keys ABCDEF0123456789
Please allow a couple of minutes for the servers to replicate that information before starting to use the key. Instead of risky "free PDF" links
Instead of risky "free PDF" links, you can access these excellent resources legally:
Weaknesses / Legal and ethical concerns
became his virtual classroom. He practiced integration while his neighborhood slept and tackled rotational mechanics during his bus rides, scrolling through PDFs on a cracked smartphone screen.