How to get a public key registered with a key server

Prerequisites

You need a personal or company GPG key. If you don't have one, this explains how to generate a GPG key.

Export your public key

gpg --export --armor john@example.com > john_doe.pub

-----BEGIN PGP PUBLIC KEY BLOCK-----
mQGiBEm7B54RBADhXaYmvUdBoyt5wAi......=vEm7B54RBADh9dmP
-----END PGP PUBLIC KEY BLOCK-----

About the arguments:

--export Export the public key information of the key belonging to john@example.com
--armor Create a base64 encoded ascii string rather than using a binary format
john@example.com The key id to export
> john_doe.pub Save the output into this file

The Rockyou Wordlist Github Updated Fix Guide

The RockYou wordlist is a foundational tool in cybersecurity, containing millions of real-world passwords leaked in a 2009 breach . While the original file contained 14.3 million entries, it has since evolved through massive community-driven updates into versions like RockYou2021, RockYou2024, and the recent RockYou2025 . 📈 Evolution of the Wordlist

repository remains the industry standard for curated lists, including various versions of RockYou and common credentials. OneListForAll six2dez/OneListForAll the rockyou wordlist github updated

It has been the go-to resource for over a decade, but passwords have evolved. An updated version has surfaced on GitHub, cleaning up the data and adding modern password variations to reflect current user habits. The RockYou wordlist is a foundational tool in

Seasonal patterns (Spring2024, Winter2023!)
Breached corporate passwords (from public leaks of other firms)
Common keyboard walks (1qaz2wsx#EDC)

The RockYou wordlist has evolved from its humble 2009 origins into a massive, multi-generational digital archive used by cybersecurity professionals and hobbyists alike. The latest major iteration, RockYou2025, has officially superseded the previous 2024 record-holder, bringing the total number of entries to a staggering 16 billion credentials. 📈 Evolution of the Wordlist Seasonal patterns ( Spring2024 , Winter2023

Alternate way to submit your public key to the key servers using the CLI

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]

The next step is to use this Key-ID to send it to the keyserver, in our case the MIT one.

gpg --keyserver keyserver.ubuntu.com --send-keys ABCDEF0123456789

Congratulations, you published your public key.

Please allow a couple of minutes for the servers to replicate that information before starting to use the key.

General notes on Security

A keyserver does not make any claims about authenticity. It merely provides an automated means to get a public key based on its ID. It's up to the user to decide whether the result is to be trusted, as in whether or not to import the public key to the local chain. Do not blindly import a key but at least verify its fingerprint. The phar.io fingerprint information can be found in the footer.
Instead of using a keyserver, public keys can of course also be imported directly. Linux distributions for example do that by providing their keys in release-packages or the base OS installation image. Phive will only contact a keyserver in case the key used for signing is not already known, a.k.a can not be found in the local chain.