User:Bsoyka/Verification

This page details ways to verify who I am in case my account is compromised.

General notes

• I have enabled two-factor authentication on my account.
• This page was last edited by Bsoyka (talk) 20:36, 24 December 2022 (UTC).
  • This editor is me. However, you should still check this page's history to be sure.
• For any important and unique data on this page, check the footnote after it to verify exactly when it was added by me to the permanent history of a page here.

Keybase

Sending me a message via Keybase is my preferred method of verifying my identity if possible.

I hold a Keybase account, which also holds proofs connected to my accounts on many other services. The message below proves this:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

I am bsoyka on Keybase.io and User:Bsoyka on all Wikimedia Foundation wikis, including the English Wikipedia. The signature on this message proves my identity on Keybase through the PGP key used, and this signed message was added to https://en.wiki.x.io/wiki/User:Bsoyka/Verification from my Wikipedia account on March 22, 2022 (view the history of that page for proof). BLC"*vT?\7u*wkhz;~QY.#u3MK){dc
-----BEGIN PGP SIGNATURE-----

iQGzBAEBCAAdFiEEDKfMFqZLaPMEjuj+pecm1aZSKOoFAmI5RiYACgkQpecm1aZS
KOoQqgwAvxitlo8oJo3fUVG7dvyNxE3DZ+ar1bCnSkF3qOKNwTj+F0HQO2oIujVC
MPxriL9rNyGmHY3xNBm08CvZkpy3+fYuTlaDuo1MzH3fKRoWVCcXw8jQIjt8ltVY
UAXQh52joaTZdd7Rq02lSF2WbzBHnvAQ3U7UfHTeWiRzQW/KL5N8Pp4FM17CfUs0
2Wd6Y5OCDfNqUvbUBJwKAPvtK+UBiSZndA8AWT+LsPAEWi4qTpTYBZd9rdVCvzGf
+ERsK+xXh7rGGUBEPsBeL1wBNhHzKPRRAWSCHDAcjTeAMVZ/kYQcTOpIYuq/kCSX
Xi/bj8qTc+PCmnfTCv686KUUN/MPXW1XaTFaCelWTANza3qfFua0Yb1BEWKY6Ure
MEEpzSlkl/4O/jJVL2yxJMrEMt+4e17GtPUNL9IbdEr9vRns24QThbb9dnx+HF/x
N0X7dSjzpawSCLFQoc/u98Qr5o17+41mbbU4EV/NTF3NDPHtL9R+htk1L6TEdaPw
Dmm7I4OJ
=qWsa
-----END PGP SIGNATURE-----

Steps to verify

1. Use Keybase to verify the signature of the message above at keybase.io/verify.
2. Check that the message was signed by the user bsoyka.

After verifying my Keybase account, there are multiple possible routes you can take. Once you've established a link between my Wikimedia and Keybase accounts, you can either message me through Keybase directly or use Keybase to find alternative forms of reaching me. As of March 21, 2022, my verified accounts on Keybase include Twitter, GitHub, Reddit, and DMOJ. Additionally, my Keybase account is linked to my PGP key, three of my physical devices, a unique token stored in my password manager, and two cryptocurrency addresses.

PGP-encrypted messages

I have held my current PGP key since December 24, 2022. I have held my previous key since January 23, 2021. This newer key is specific to Wikipedia-related matters. For confirmation that this new key is mine, see the signed comment in the source code of the User:Bsoyka/PGP key page.

You can use my key to verify that I wrote a particular signed message, along with when I did so.

Steps to verify

1. Ask me to create a signed and/or encrypted message with my PGP key.
2. Verify that the message was signed with my public key.
   • There are many tools to do this. A quick search revealed PGP tool. To use this one, click the Verify tab and paste in my full PGP key from above and the signed message I gave you.

Committed identities

The following is a SHA-512 commitment that can confirm my identity. Learn more about this method of verification at WP:COMMIT.

• 63172b503dd594b544ec34f7746bd3ae6c3e69f055a3b953c87cc54174ba0a6c4d1cae87e6d2ebb2501517fe69bad4b190570350f294994d8c36dce284c1b300

Steps to verify

1. Request the secret string from me by email or another means.
2. Hash the string using SHA-512. I recommend using Fastily's text2hash tool, but other programs will do the same thing.
3. Verify that the result matches the code above.

Previous commitments

These previous commitments to my identity (listed in reverse chronological order) can link me and my account since May 6, 2019 and were made in the same way as the current commitment above.

• 9acffc24304d20b682ceead98ae6a23816581f61a69a155d3927eb61c947bca4e09ae3e676618692913526907baab3366175ea034ba8c44560f024a993dbdbeb
• d2073a8554325190bf56af565ac1a7c40f609491f7b177602b6cd941e8c15a02ccb7cc7297f213b402ade651774c818a3c8bd8b2b1636f6101e32a8c9eba2fa1