The BCT PGP/GPG Public Key Database: Stake Your PGP Key Here - page 3.

Rath_

legendary

Activity: 1876

Merit: 3131

Quote from: Rath_ on March 09, 2019, 06:36:18 AM

-snip

Here's a revocation certificate for the key from the quote above.

Code:

Here's a new key.

https://keybase.io/bitcryptex/key.asc

Fingerprint: F00C 72BF D0A0 744E 92FB ED4E E24F FD11 6E46 48C4

Code:

Here's a message signed with my staked address using Electrum.

Code:

-----BEGIN BITCOIN SIGNED MESSAGE-----
I am Rath_ (BitCryptex) and today is 19th November 2020. I have revoked my previous PGP key (21F8 C5D6 509F BCC9 8A13 B93E 6A39 19A2 7CB4 9A2F).

My new PGP key has the following fingerprint.

F00C 72BF D0A0 744E 92FB  ED4E E24F FD11 6E46 48C4 
-----BEGIN SIGNATURE-----
bc1qmtv6hyzq8cjmkcldkh8tdef3nv2uc04wxxp8v8
ICoCGha4LtYIuKfmEDrd9Yj+a5z2aFfJTi8j2EUxssm2D4zjWmQZoPyALgC0l6mWqnyw8J8ecwJKX4fPErKPie8=
-----END BITCOIN SIGNED MESSAGE-----

nullius

copper member

Activity: 630

Merit: 2610

If you don’t do PGP, you don’t do crypto!

Quoted for reference.

Quote from: Lauda on October 19, 2020, 01:31:16 AM

Quote from: Lauda on February 17, 2020, 05:12:12 AM

Old key is here: https://bitcointalksearch.org/topic/m.46696549.

Quote

Quote

My only PGP-key has been compromised and revoked.

Quote

Lauda

legendary

Activity: 2674

Merit: 2965

Terminated.

Quote from: Lauda on February 17, 2020, 05:12:12 AM

Old key is here: https://bitcointalksearch.org/topic/m.46696549.

Quote

Quote

My only PGP-key has been compromised and revoked.

Quote

Timelord2067

legendary

Activity: 3626

Merit: 2209

💲🏎️💨🚓

Quote from: NotATether on September 30, 2020, 12:55:10 PM

Good grief, this thread has been inactive for this long?

Well, I updated my PGP key on short notice so I want to ensure that everyone knows that nothing fishy is going on. The new public key is also available on my site for anyone who wants to grab it.

Also, the I mistakenly wrote September as Septermber in the signed messages. (LOL!) Not worth the time to fix the spelling error.

Code:

PGP key: 520A E7DD 0C2F DB5C 4783  8A35 1C3D 1D19 C8E8 B6D8

Code:

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

This is NotATether from bitcointalk.org
Today is Wednesday Septermber 30, 2020

Due to the extreme complexity with managing two keys,
I am retiring both of my PGP keys. My new PGP key is
520A E7DD 0C2F DB5C 4783  8A35 1C3D 1D19 C8E8 B6D8

This key can be used anywhere by me. It may be used
by any purpose and is not subject to any of the
restrictions I put on my old keys.

Please see the associated signed message from the
named key above for confirmation.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQIcBAEBCAAGBQJfdLR4AAoJEMv15LPVdIo3NxAP/1+tGHVqLlBOwPSRBQjc/ms6
DIeIuuYU3883nKayq7JBu/PXxoOekNLPTbB9yesFqvCoRLsggl/HXDiwq+yUbSwb
pqQSXe1OFO/JYrE6vJvlfrr+mooZmDrLtrTGOGNN+gfAoOOE/ZBGI4he1u0Rnius
vd40BEYJAGapOb/VFbWijIzlsjp8AGEYCRMBQ8D6lddr0MQyblLfGBjKS3fbOgmC
xmIKq4vRsE3JvTrpFtTeJLBvogcBrG3XUut0fsCMHX2C/9DXwCMBYtMQowWu7ML0
kCsEbbzg07ALDN8TZSw11ow6c7IFbq2uhOtbG1BdESJwXehwQ6QttuvnKxox9SRw
zHFPZf3S1nZQpn6m+fkeGdCcneEDYhdi2s//S199nQ7pxdedTudweFunUgThHPWF
sviL1xiFtjM6ZLR2B/N6e8oY+h8cG22Nsk//JygOWEkgi4biAfRQRdfdOZiru1KU
1YTjMj+Xmu3wbMkL9LfhJaoMy4SQUfYTZwPRPgBtblo6FDo1EbT8wXlEIvbMwLLR
mSmswaw8bVmfR8cIsVRu2ltDaaqBuyes2mzHhniK4igogMyFDTeYVc3xDx46iRzj
lUU7Gp9jglU7Tvn8a3eapgm8IzGiSOhgSYkx0mvtmumBMEIOev5jdVLPhHolcgPL
1jIznyPh8ybPW4XlHO+g
=JL63
-----END PGP SIGNATURE-----

Code:

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

This is NotATether from bitcointalk.org
Today is Wednesday Septermber 30, 2020

Due to the extreme complexity with managing two keys,
I am retiring both of my PGP keys. My new PGP key is
520A E7DD 0C2F DB5C 4783  8A35 1C3D 1D19 C8E8 B6D8

This key can be used anywhere by me. It may be used
by any purpose and is not subject to any of the
restrictions I put on my old keys.

This is the confirmation message I was referring
to in my other signature.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQIcBAEBCAAGBQJfdLTzAAoJEBw9HRnI6LbYo1EP/Ro6e8U8kgbfbgfTWxjlFPSR
g8WY6l1kPQ7XtjYBZNs++ZmH4gQL9G8lsW101dw3uUTrX8FFkped7pdJD2kb50d8
SYvgI7fhl7I6wemkm3/NPOPxvi9Bl1k9aB6IXRsJn4MWjdImII+lZOSKGwvgSQ/h
Fzh1HsV3NQcjk+szF2FwBtVgqJY2uCCl/7bPuBySJLHxlq4C7E3Pk8fa2Pnh3QYn
dFMbfsswkpw3sLFQIn7mpLzeeQJ7LKSiPe47RN6cyPzGfkk7iEw1YvYO6QZ9T0jk
sS7AXN1XKWH1sGNJyqyIteOSGOkymDplRS+1R4RoyX9RzuVHN56AkA6KX6LxWO3C
2nb/g5XmwJEhqkz9B5Q8z5BNgl70Ycv175suefpx8/YHcp9qYCJu20Zw05TWf68m
CNR6hBRfMY/dq5r4k9fnCsFE/Q7QXW0h7wrAym8xXTjbHNcxRVDJyvaOT4exDAcw
XmR6rXUUgosWII3+yEXgDypx5Z+Fd6aLIpWdFaZb4Ny8IXotEKASIJo++SAxczbb
rR7uiwUsoMOM119NOk9eAQARPxNHT8TigYY+iY3Fs8lEmM0yXpXpcszgEVtSwCSr
aebXk0yIXMzMErORQHW/2Gi8qw/wanBwMFtPjKBnY8xF74KdjuiDBcwjyS5ad9V0
GxxGptwWajfYIth+LC2F
=RBUA
-----END PGP SIGNATURE-----

Message Quoted and Archived [1a], [1b] for future reference.

NotATether

legendary

Activity: 1568

Merit: 6660

bitcoincleanup.com / bitmixlist.org

Good grief, this thread has been inactive for this long?

Well, I updated my PGP key on short notice so I want to ensure that everyone knows that nothing fishy is going on. The new public key is also available on my site for anyone who wants to grab it.

Also, the I mistakenly wrote September as Septermber in the signed messages. (LOL!) Not worth the time to fix the spelling error.

Code:

PGP key: 520A E7DD 0C2F DB5C 4783  8A35 1C3D 1D19 C8E8 B6D8

Code:

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

This is NotATether from bitcointalk.org
Today is Wednesday Septermber 30, 2020

Due to the extreme complexity with managing two keys,
I am retiring both of my PGP keys. My new PGP key is
520A E7DD 0C2F DB5C 4783  8A35 1C3D 1D19 C8E8 B6D8

This key can be used anywhere by me. It may be used
by any purpose and is not subject to any of the
restrictions I put on my old keys.

Please see the associated signed message from the
named key above for confirmation.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQIcBAEBCAAGBQJfdLR4AAoJEMv15LPVdIo3NxAP/1+tGHVqLlBOwPSRBQjc/ms6
DIeIuuYU3883nKayq7JBu/PXxoOekNLPTbB9yesFqvCoRLsggl/HXDiwq+yUbSwb
pqQSXe1OFO/JYrE6vJvlfrr+mooZmDrLtrTGOGNN+gfAoOOE/ZBGI4he1u0Rnius
vd40BEYJAGapOb/VFbWijIzlsjp8AGEYCRMBQ8D6lddr0MQyblLfGBjKS3fbOgmC
xmIKq4vRsE3JvTrpFtTeJLBvogcBrG3XUut0fsCMHX2C/9DXwCMBYtMQowWu7ML0
kCsEbbzg07ALDN8TZSw11ow6c7IFbq2uhOtbG1BdESJwXehwQ6QttuvnKxox9SRw
zHFPZf3S1nZQpn6m+fkeGdCcneEDYhdi2s//S199nQ7pxdedTudweFunUgThHPWF
sviL1xiFtjM6ZLR2B/N6e8oY+h8cG22Nsk//JygOWEkgi4biAfRQRdfdOZiru1KU
1YTjMj+Xmu3wbMkL9LfhJaoMy4SQUfYTZwPRPgBtblo6FDo1EbT8wXlEIvbMwLLR
mSmswaw8bVmfR8cIsVRu2ltDaaqBuyes2mzHhniK4igogMyFDTeYVc3xDx46iRzj
lUU7Gp9jglU7Tvn8a3eapgm8IzGiSOhgSYkx0mvtmumBMEIOev5jdVLPhHolcgPL
1jIznyPh8ybPW4XlHO+g
=JL63
-----END PGP SIGNATURE-----

Code:

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

This is NotATether from bitcointalk.org
Today is Wednesday Septermber 30, 2020

Due to the extreme complexity with managing two keys,
I am retiring both of my PGP keys. My new PGP key is
520A E7DD 0C2F DB5C 4783  8A35 1C3D 1D19 C8E8 B6D8

This key can be used anywhere by me. It may be used
by any purpose and is not subject to any of the
restrictions I put on my old keys.

This is the confirmation message I was referring
to in my other signature.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQIcBAEBCAAGBQJfdLTzAAoJEBw9HRnI6LbYo1EP/Ro6e8U8kgbfbgfTWxjlFPSR
g8WY6l1kPQ7XtjYBZNs++ZmH4gQL9G8lsW101dw3uUTrX8FFkped7pdJD2kb50d8
SYvgI7fhl7I6wemkm3/NPOPxvi9Bl1k9aB6IXRsJn4MWjdImII+lZOSKGwvgSQ/h
Fzh1HsV3NQcjk+szF2FwBtVgqJY2uCCl/7bPuBySJLHxlq4C7E3Pk8fa2Pnh3QYn
dFMbfsswkpw3sLFQIn7mpLzeeQJ7LKSiPe47RN6cyPzGfkk7iEw1YvYO6QZ9T0jk
sS7AXN1XKWH1sGNJyqyIteOSGOkymDplRS+1R4RoyX9RzuVHN56AkA6KX6LxWO3C
2nb/g5XmwJEhqkz9B5Q8z5BNgl70Ycv175suefpx8/YHcp9qYCJu20Zw05TWf68m
CNR6hBRfMY/dq5r4k9fnCsFE/Q7QXW0h7wrAym8xXTjbHNcxRVDJyvaOT4exDAcw
XmR6rXUUgosWII3+yEXgDypx5Z+Fd6aLIpWdFaZb4Ny8IXotEKASIJo++SAxczbb
rR7uiwUsoMOM119NOk9eAQARPxNHT8TigYY+iY3Fs8lEmM0yXpXpcszgEVtSwCSr
aebXk0yIXMzMErORQHW/2Gi8qw/wanBwMFtPjKBnY8xF74KdjuiDBcwjyS5ad9V0
GxxGptwWajfYIth+LC2F
=RBUA
-----END PGP SIGNATURE-----

Timelord2067

legendary

Activity: 3626

Merit: 2209

💲🏎️💨🚓

Quote from: Room101 on May 13, 2020, 09:51:34 PM

Code:

Fingerprint: B99D 4BA6 CB3B 856C F309  D0A5 6C47 012C 5D5D 9612

Code:

Code:

Message Quoted and Archived for future reference: [1a], [1b]

Room101

sr. member

Activity: 541

Merit: 362

Rules not Rulers

Code:

Fingerprint: B99D 4BA6 CB3B 856C F309  D0A5 6C47 012C 5D5D 9612

Code:

Code:

Timelord2067

legendary

Activity: 3626

Merit: 2209

💲🏎️💨🚓

Quote from: NotATether on May 13, 2020, 10:54:04 AM

Changed my password recently so I thought this would be useful to prove I still maintain ownership.

Code:

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

This is NotATether on Bitcointalk.org, Today is May 13th 2020. I am in sole posession of this account and this PGP key.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQIcBAEBCAAGBQJevAmcAAoJEMv15LPVdIo3LtIP/1TRS6bApq4mswgFLSj36vjx
ZqK+k3BmHIT3LWL485fgpj2TFq/io40br/qcypQ4ZGpWS2piwrmoLxY2+hmWm6JD
oAnuefiJqt6tqN3Q+qXJMSeqvteeCRAzVM3HZaI1Oqyf6y+Aat36M6QpdSzf9b3n
N5nqXcz7IeVySXHmpqgPPOgo0MBPcKhH49Wo02sA35TndehGrAFt6L2/6V/9QJkb
ZO9pNmC1F6uiHMY/OXo5vKSRvWW606+Zy1j4gqYlKZUc2o76GXSgLtInZfqVO9cY
l3zRtn1mlFfCtwtwDIqZcu1f9+nj5pkLFozY3w9d0tJn0972kled52557mLSNLny
WT8vkgarnUulB95ymj/ZdYasPqKSJ61bi+Phr4qEh4c73NFHiWCxlLaXAbGEM4Xs
Gp3AOVX+kUwVDeQ09JecuakM6JxCY9hVLoid3qZeDRGIAxj9sivLBtkrrptcFUwt
BC7siEopL9GTf88iA7z/Czs7WWImAGkbJZ18a2zUp0wRTm6d/sQzRC30HrnBpPxV
iRnWp2dolkYRWNFoU+MLxZzZiHyssuBD61ZbbvV16smpCzNtVK7y+mScBezGHLdx
vHbjXCv2CSzE9dze1zrUnVDFrpUJl4RlE/Yi2JRTIDgsfnwxDyoPf2PdKmMm+cBa
EFKXG0e0DYsNrMKseKJ8
=5fYn
-----END PGP SIGNATURE-----

Message quoted and Archived for future reference: [1a], [1b]

NotATether

legendary

Activity: 1568

Merit: 6660

bitcoincleanup.com / bitmixlist.org

Changed my password recently so I thought this would be useful to prove I still maintain ownership.

Code:

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

This is NotATether on Bitcointalk.org, Today is May 13th 2020. I am in sole posession of this account and this PGP key.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQIcBAEBCAAGBQJevAmcAAoJEMv15LPVdIo3LtIP/1TRS6bApq4mswgFLSj36vjx
ZqK+k3BmHIT3LWL485fgpj2TFq/io40br/qcypQ4ZGpWS2piwrmoLxY2+hmWm6JD
oAnuefiJqt6tqN3Q+qXJMSeqvteeCRAzVM3HZaI1Oqyf6y+Aat36M6QpdSzf9b3n
N5nqXcz7IeVySXHmpqgPPOgo0MBPcKhH49Wo02sA35TndehGrAFt6L2/6V/9QJkb
ZO9pNmC1F6uiHMY/OXo5vKSRvWW606+Zy1j4gqYlKZUc2o76GXSgLtInZfqVO9cY
l3zRtn1mlFfCtwtwDIqZcu1f9+nj5pkLFozY3w9d0tJn0972kled52557mLSNLny
WT8vkgarnUulB95ymj/ZdYasPqKSJ61bi+Phr4qEh4c73NFHiWCxlLaXAbGEM4Xs
Gp3AOVX+kUwVDeQ09JecuakM6JxCY9hVLoid3qZeDRGIAxj9sivLBtkrrptcFUwt
BC7siEopL9GTf88iA7z/Czs7WWImAGkbJZ18a2zUp0wRTm6d/sQzRC30HrnBpPxV
iRnWp2dolkYRWNFoU+MLxZzZiHyssuBD61ZbbvV16smpCzNtVK7y+mScBezGHLdx
vHbjXCv2CSzE9dze1zrUnVDFrpUJl4RlE/Yi2JRTIDgsfnwxDyoPf2PdKmMm+cBa
EFKXG0e0DYsNrMKseKJ8
=5fYn
-----END PGP SIGNATURE-----

Timelord2067

legendary

Activity: 3626

Merit: 2209

💲🏎️💨🚓

omegaflare posted this:

Quote from: omegaflare on May 26, 2015, 01:43:06 PM

https://bitcointalk.org/index.php?topic=1070761.new#new

EcuaMobi advised me to publish my public PGP key here.

-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1

mQINBFVkmOsBEADKA8lj+XSEe3uh+fuaBcu42JzRxexzxEB3UtSWVnOGfe+TVntz
p9hJUupzFXGths8/O0lgZHHFnYxyrvOiBlfFvkkPwpzO+ZtISicRzXuddI9E04GR
0b7KHswHGFrn+3oz6D8P3LqjRvBUAtacLcZR73lVIgnmpNBJgMGVufA4jBiwfGj/
j+qyLIRW6ZLqbyqipgOrzDATcrj9b3TEjCFtYaEHfCfenHANvfqp8ja7roD1lYPs
92jR361DsCUKVHHiV4h07dysqfSttfbNmyJyt9q+3oRVb5A0oDSE+FKboFBiDz5e
QRYHPqLjelAdsOMWcRchwmEFjXhLQ6VvTRmIHAU5Qky0QWzxn3WKOaXHQbgIwgkX
pGWQ/QYsuctNk/Ky1o4o5iwbJabPUyOUiLVNbMsRQjmocxw9X3pKEiAYrLbnXaGm
A4WyMw4Xm3oE2Uco20YDBook9XaLBZ7lCDZPgtAFqMsWY3bTCUbLC+Wc5js47fKr
fpZF9x9U9DHuqP/e/QOa0Lz2SqVIM8jtxtjFEUpnwnAnb8WiZYZ3FZ3u2LAPCYGm
Paqw4gr7bHz09bxa7EDVQ2YZgUBEbWiVin0wt5/VGNDq2XO4ccqBjxIjil/OHoSQ
HIFajBmRpJNj1/7Vz3BrcAZQojaxX4D5R/bJF/R6Xjk9axE9HgGstl3ccwARAQAB
tA1PTUVHQV9CSVRUQUxLiQI2BBMBCgAgBQJVZJjrAhsDBQsJCAcDBRUKCQgLBBYC
AQACHgECF4AACgkQlyMaXJHJNBmdWBAAizLcZBjtI3gtLSO4Wgzb30Xn6mNzcgT4
m5qqN1FTCnNT64/EkjMZnj7lrqpFg3/I5Q9gas0GQ3ZUuHZxBzGDai/SxO6o9aNR
OPrrSJXIJ+MkIqm8OskQlZS/B0w3mwgDRGgnQJPiBUWJQbE+Qa1kgjmauE5z3ly8
ZyUh50jBKY8zGH6QE4PvknOnsWCmmD55dwaUWt+Y3PzfO+lNSgHmHrq1qY/OFbOd
MMOOMDfEBxv7ufhNPC18OZy7sQrUIIfzn6K8eIzceZ0x+d8jZSzdi0Tl2SK8FB4Z
O7qRPxURuZachyRpns48bo2kUaZ4HCAbuXv6YorJGa2wy+qrKZDO1F0cEwI0QE+f
eXbvooNaSVtq2Q0262YdwtGdyULQwgfO49qVgpGYqE8+K1E4/q6mYIkyeYtIYLT+
dZceFWE3UO49TqwvkHIfsP1mztumRikNG8yhxxyWWprkT85ATxGDbsHs4C/TXzj5
tMcgyPizN5l3bbf+9RVwARq66TeXWRo/fp3OnSDuNtwIvOlH+Njwhx0e/6BNzIV5
IP/WaeMVFJP3Nyfrg+7np8OPetgEO8046wVZB0If9euXRBqKEmZyl+fqJbrzlbEi
e6Y+2kybG99sMUxFd3gEq61REQfkXrrSrFhUdZpsYBkTvN/YDw0trvIeIQvu7Djk
6EhwOBal4FS5Ag0EVWSY6wEQAMo0YjkyEvzrH2dQkngdaVknGOIHP7tqOrXXT2K6
l4Z6TS4dl7UqObkdvndQBXPB6Hgo+BYClBTJIOn8DJQ3I8kPUT+9GK4OA8VlNU5v
Fvtb+Y+FPPLgsHfFqm/Fnw9SLM+Kmq5Lxhce6v9T1CeE3ZGJXZMBJxwx2NEWNTLQ
+hj6ievCOErfp/QxgCyOAtMMVMUnYWNsuIgavk1Dvj6q75QOBjHOIIXEsajk0VNH
WLPYfFqAvY8GNRbe2H3SOjEaKIk2X2IeBWDZ7qsUs7J/sXtSkFv+8dhGTaTy25eR
SQdQS+rfSvmB+wHj2JSb1QKrH0XwwyyxMoAjzqsKbJHEA2LdpcvfZsAwiLSG3V8I
0qSfu3KjUu25XhpYZWPBwja4Ut7125ee8O38MAqJDJO0w4xHpaQbgfQ3H3/RJIS7
cnLnO65EbAm04igmysiSIydG3b3+LZxFN31ER2FywevpZCFa0P/iqMY8dB+3B7DU
rp5gleQL3P6+EB6t0SGl+SmfSte3m1kD5G48vKbzUozrmosOj89i5J/BFlgiO67V
plFG3XHV/rcfbQNPiXD2ofqfFiZONFYhipV1T3q3BJSj6QmNT8QV1uUHzmTu4bsm
HsoNcsfqBkub1fmwsbRutwkZLvhD7WcbFKZK6cDl8MOQdWzGx4xQ/sz70G6nj1n0
MNjVABEBAAGJAh8EGAEKAAkFAlVkmOsCGwwACgkQlyMaXJHJNBmwkRAAlC5rHbTF
qZ7P7db+5bZTUzGq6ThqkPYWgrSyKj0myURVp4AnZdJfewk0QvMU8on/HVHvCz4p
OlQByVaTLDsB/v8z5naaeHrEzpdTSKOFMLg7WsAO0Z4I1hhHd6GuJ4HwNajIquZj
Ti+0+mcLfuqsSOxCyjJbjlRbNJSrG9yrOeG4ZtcAaUAuKwsuz5ICNZllEXjCFesT
SIlAd9QXxnaZ246huChNm5gX0Lk+Eef2Wg7sscDwC1SECq3wRKtY5pVn8rQ3AwJi
PuOtIHOLC3/XYmEnngogBjqbetMgAXEBT1ntgTn8lDhI8Mc1/Y/rakw0VSAGyAcr
Ja3Qf69Ot1Mhk3tqo3Xc7TO24qUTKoWsrosODQAzJiQInZ6B0LRDd5Igg65j8/0O
h7I8QMtp72dPGvvujuHQua2QZcuoJ+SyQz34Vasy2YmvJAv8blbV/pmq3UR1DKDg
zMH061pA+VeD9DjtMOp4LG3zOJCTRUvuI+5u77CmygfuLxm0hfUec5vOCiuHnfne
uxQpyzTp/cONpExVIqIoygXbAL03HYTy7jbGo358Cw767DZCK/1VguZI3WQQjfrm
0iaHL5ZPorzSDDvy5OVGIa7rqJWSnsNfCFmQo9CEFeeYrnB8vPza++EDpaLm5y1W
BKOIB8snI+ol9XZrQRGbRHP/cXwwY7zBSFw=
=2+FZ
-----END PGP PUBLIC KEY BLOCK-----

Thanks.

Quote from: omegaflare on May 26, 2015, 01:53:23 PM

Sorry, I forgot to add code tag.

Code:

See my signed message:

https://bitcointalksearch.org/topic/m.11456779

Thanks.

The "signed message" was here:

Quote from: omegaflare on May 26, 2015, 01:50:38 PM

This is my public PGP key:

Code:

Here's the signature:

Code:


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hello:

my bitcoin address is: 1BouaUZEcLBUsQDfk6E2oTfRUrzhngqAkF. Is that all I need to do? Let me know if I did it correctly.

Thanks!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCgAGBQJVZLJUAAoJEJcjGlyRyTQZaDQP/3GmybEDX8cVHsZdx+bumhdz
UbnkR+t8yEJ3LAZ6SrKdWlF2Dt9yYt66p0GPhE8OeRXwfZb7Fyn0ZVXrGpiLP4W5
3GQ999cCqmxHFT1EsP6ksoC4paLP9yURJFuvSG7uC760WLAoeD94CTjwM30j6dYh
MOXwEVwKefgkZZ3ccQYxaAiMljXkGEY041HltuvI9oz+UfahUo5Brk22BfFMZIU5
r6nyl3+OTM9guxEeavil0IxRGVz9eGhhEZVhBzqCDC3uB/crg3e+A+RH20/QYpOQ
pTkzBURjzNRnWFFS+gzNmQka/6K9AvxgnFmQyDLk38e+gjexXAxuJBVxQihxADlq
QfFVRe8ilmUp51ygi/whrW0+yaSEdgsvDGmPMDosPld5Y2yXl7ATTRdZ1PjvoVX6
Ed1OwWuB/kqTCjp4hLAb8BFS0wb91F8tz+nZ0LLYlnsn10bRwk9ZPIdsZ5O9h48P
ktYPTcmfXblF97IaP0s9ypwsBtFEzd/RpPSZroliukHHi1e5pvlnvk9R3QKglJ/e
3rBuaijj5QxS3ir9tgAb1rJ6DBbfFcY5kulJ/DDe4tDZJR4Mf8+pU1et4vu5RRR1
x1tGb8t1R0pS3QopmuEaDPleoXT0vJWTol2bLiDgDwcJIjegN/yhY6HQ8e4EgAs8
jMxhLKq+vTpSXxkL6ulB
=tuJr
-----END PGP SIGNATURE-----

Let me know if I did it correctly, thanks!

One post earlier was this one by favdesu:

Quote from: favdesu on May 26, 2015, 01:14:05 PM

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Confirming that I am favdesu @ bitcointalk, bitsharestalk. my PGP + BTC Adr https://keybase.io/fav
IHQ9EbixCbNddSMaLxes2Mn/N3cClyY7j71zPAtUrLDEMEulAI7uOSSZvKI/8MxB4swIxT4iuixhc1tAMD0hCrk=
-----BEGIN PGP SIGNATURE-----
Version: Keybase OpenPGP v2.0.8
Comment: https://keybase.io/crypto

wsFcBAABCgAGBQJVZKnTAAoJEKRF7oTcH7KXfq0P/RxsZFH/x5MWuNCEDXJPzSj4
X9wFCEMr3u+HG/87iCb2W2KyQ53IZjbx9ymMD7XutaDZAM5lhRAzibCJ4hSlggMO
xK779/L9I3+GZ+izuLSyNvCpW8x7qyml/HOz/QyPawR9vOIDdLvCanGywhhEO7xn
2DaHY3duLD8cyG8jYUQQS3lswvxLqZFmhqfMvge12H/Inhh23+y8eyhxGCCRRGCf
NevqAAa8AZUHaB208fzkSLbQarmdCNd9ACHItw5LDkXIPFaSroqIpVSeOrBF2h9w
mtBWBQkUiWMmBsWaLdfxTTCxloCZQR5X7CensA//AyOThqEs69esUc2vYj10nbmF
0dA+QpfdLwN7w8Fu5p2aFID+zJYebRja4IopjTJAegAurj/fwL4uCgwbkJXUCUy9
J0EXKMSAwiCV3dKbzEJwcBw/y7nRlmb4t8E2/Hx8oD4EK/rRpoptE6gBV+xEttt6
38WqCqg5sul7iTxhz3SBd03lOsVAuoY5mdDE9KPxUv3COpo5S36j4M47q5wG+dvx
OzRwsowTX7kmCsFNKz8pKQRWvdsd0iqA5ysdp719pamlM81snmZWKN5xSC77M7dO
mZ25bS+jo1/KSNAUs6oEzF0Gko8xH8tQie+DRI5EQuA/Ny6SQ+Z7+vOcwMm4ryrV
3ZShLoSMdZesgxCfxrSH
=To99
-----END PGP SIGNATURE-----

Quote from: NotATether on April 29, 2020, 08:55:42 PM

[archived]

Well I put my website here so it's useful to validate I actually own it among other rules I would like to establish about using my keys.

Code:

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

NotATether is Ali Sherief in real life.

The PGP key used at present, F97D 7A6F B057 3979 F3F3 D69E CBF5 E4B3 D574 8A37, is strictly for the purpose of producing signed messages on bitcointalk only. It is not to be trusted for any other purpose.

The other PGP key I control, 2789 4325 9F53 D9EB 45CD 9B26 4936 B8C3 ACA7 BEFB, is to be used everywhere else except for Bitcointalk. Do not accept signed messages placed on the forum signed by this key.

The only scenario where the 2789 key is used here and should be trusted here is its use to make encrypted Private Messages (PMs), the key I prefer you send me encrypted email with. Though I will also accept email encrypted with the bitcointalk key but I discourage it.

Information about this event is also in https://zenulabidin.github.io/#/keys. In the event of any conflict, the content in this signed message prevails.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQIcBAEBCAAGBQJeqiF+AAoJEMv15LPVdIo3U2cP/2J2gExEur087bU4geQ7LpYp
j0tAMg9BHBLHsNi/XuZGpbD/PgFoMjcadtFbS0A6Xje8La6sSYZQkc2HBV5/Z8U7
XK02ouKCEMKd+LGs7wqp/HLQVvnk4rTIrsJSVHUyY8sZ72SDmtHW2sXtsL2HYkqC
J9G8K/2BRQKaza3BbGh4kZA5zKzUPCSzmGOreJPjBlr80pttmHH3zut/Yj47qIXl
Uf/hdCbBBkiE2VvFae655RWNmYYqYcCFwWqpLuCRfdVo/hAsnls+nVFj/9t8b4Kd
PKerX8cheOfr4LDrhhMaYMAaoBuJcSivF0ZXvBDyiCWwjW6M3k4GV6NasnOUpO/W
LcXjNxV53o/7sp/9I4ezx06H7IXIxGA9Hr3QMJ7KMD3LqafMwE/igMaQcOHES8nV
utNtXSdh1dyrPRT2+cwYV5HvPDAsg9YjChJF0czlmiYEokQykLsX9bfyIoAUmRd1
lzalTgtLUrwG6VAhUraHP5sMPgllrqZ5M1Dd+IlIRxTMsaZA/qSfJ+zser5yQjd1
r1KPq9XxrhGPxMu2Skxe3OihuqHfLQ2n9/FTirmmsiIUsz5GUc2EO65ZJPo1qaHd
6qs/FL1lgvIDysTpGiw+z3l+AyUh2coSDkpReB4us/RvXn2OB1bWt8Zak+iKh0vc
WQnXY+SYQ0Fn3FTV5liA
=JlG7
-----END PGP SIGNATURE-----

Message quoted and Archived [1a], [1b]

NotATether

legendary

Activity: 1568

Merit: 6660

bitcoincleanup.com / bitmixlist.org

[archived]

Well I put my website here so it's useful to validate I actually own it among other rules I would like to establish about using my keys.

Code:

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

NotATether is Ali Sherief in real life.

The PGP key used at present, F97D 7A6F B057 3979 F3F3 D69E CBF5 E4B3 D574 8A37, is strictly for the purpose of producing signed messages on bitcointalk only. It is not to be trusted for any other purpose.

The other PGP key I control, 2789 4325 9F53 D9EB 45CD 9B26 4936 B8C3 ACA7 BEFB, is to be used everywhere else except for Bitcointalk. Do not accept signed messages placed on the forum signed by this key.

The only scenario where the 2789 key is used here and should be trusted here is its use to make encrypted Private Messages (PMs), the key I prefer you send me encrypted email with. Though I will also accept email encrypted with the bitcointalk key but I discourage it.

Information about this event is also in https://zenulabidin.github.io/#/keys. In the event of any conflict, the content in this signed message prevails.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQIcBAEBCAAGBQJeqiF+AAoJEMv15LPVdIo3U2cP/2J2gExEur087bU4geQ7LpYp
j0tAMg9BHBLHsNi/XuZGpbD/PgFoMjcadtFbS0A6Xje8La6sSYZQkc2HBV5/Z8U7
XK02ouKCEMKd+LGs7wqp/HLQVvnk4rTIrsJSVHUyY8sZ72SDmtHW2sXtsL2HYkqC
J9G8K/2BRQKaza3BbGh4kZA5zKzUPCSzmGOreJPjBlr80pttmHH3zut/Yj47qIXl
Uf/hdCbBBkiE2VvFae655RWNmYYqYcCFwWqpLuCRfdVo/hAsnls+nVFj/9t8b4Kd
PKerX8cheOfr4LDrhhMaYMAaoBuJcSivF0ZXvBDyiCWwjW6M3k4GV6NasnOUpO/W
LcXjNxV53o/7sp/9I4ezx06H7IXIxGA9Hr3QMJ7KMD3LqafMwE/igMaQcOHES8nV
utNtXSdh1dyrPRT2+cwYV5HvPDAsg9YjChJF0czlmiYEokQykLsX9bfyIoAUmRd1
lzalTgtLUrwG6VAhUraHP5sMPgllrqZ5M1Dd+IlIRxTMsaZA/qSfJ+zser5yQjd1
r1KPq9XxrhGPxMu2Skxe3OihuqHfLQ2n9/FTirmmsiIUsz5GUc2EO65ZJPo1qaHd
6qs/FL1lgvIDysTpGiw+z3l+AyUh2coSDkpReB4us/RvXn2OB1bWt8Zak+iKh0vc
WQnXY+SYQ0Fn3FTV5liA
=JlG7
-----END PGP SIGNATURE-----

Timelord2067

legendary

Activity: 3626

Merit: 2209

💲🏎️💨🚓

Quote from: Cence on April 19, 2020, 06:27:19 AM

Please witness my PGP public key and fingerprint for future references.

Fingerprint:

Code:

DC7E D292 B66C 9B2F C162 7600 6935 74EB D9F2 5774

Public Key:

Code:

Message quoted and Archived [1a], [1b] for future reference.

Cence

newbie

Activity: 1

Merit: 0

Please witness my PGP public key and fingerprint for future references.

Fingerprint:

Code:

DC7E D292 B66C 9B2F C162 7600 6935 74EB D9F2 5774

Public Key:

Code:

Timelord2067

legendary

Activity: 3626

Merit: 2209

💲🏎️💨🚓

Quote from: nullius on March 29, 2020, 08:53:06 PM

When time permits, I must catch up with important replies on various threads. First things first: Assuring communications security.

Refreshed key. The only change: New certification signature on the same old encryption subkey. No need to quote; it is the same key as I have been using since 2017, only with a new self-signature omitting the key expiration time (subpacket type 9) for one subkey. As a separate matter, fresh verifications are periodically made here.

Code:

I do not generally recommend setting such short expirations as I had been using on my encryption subkey. I have done that in the expectation that I would upgrade my keymat handling in ways that I do not wish to discuss publicly, and issue a new subkey. Plans have been delayed. Now, as a hedge against future uncertainties (and in view of my own abysmal past performance in keeping this updated), I have removed the expiration date so as to assure that people will always have some means to encrypt a message to me. If or when I complete the upgrade, then I should just revoke the old encryption subkey. It is not known or suspected to be compromised in any way.

Quote from: nutildah on March 16, 2020, 12:09:40 AM

~

I did not reply before, because you gave a substantive response that I think warrants discussion best split off to a new thread; and my attention has been diverted elsewhere, unfortunately.

(It would be good to pick up a technical discussion about practical cryptographic security, instead of wading through another myriad posts about how Bill Gates created the coronavirus to push you to use vaccines instead of taking megadoses of Vitamin C, or whatever—ahem.)

In brief, I think that you have a flawed threat model based on an incomplete understanding of what various uses of signatures do and don’t prove. It is an important issue. I should take it up sometime.

Quote from: nutildah on March 16, 2020, 12:09:40 AM

Like I said earlier, what if somebody created the account and the key pair at the same time, and then passed off the account to somebody else while keeping the key pair for themselves? Was the post with the public key also timestamped at the exact same moment of creation as the account and key pair? Obviously no, it wasn't.

I don’t see any practical freshness problem, whereas the user posted a key containing within itself a signature on a forum account uid within eight hours after that forum account was created.

Timestamps on signatures can be trivially faked, anyway. `man gpg`, look for `--faked-system-time`. In your scenario, why couldn’t the user create a forward-dated signed statement, then pass off the account and the signed statement (but not the private key)? If the new account holder is willing to post a public key (with userid claiming the account) for which he does not control the corresponding private key, then he would also be willing to post a forward-dated signed statement; and in any case, the parties are colluding in a way that is almost impossible to detect or prevent. Moreover, given that both new PGP keys and brand-new forum accounts are easy to create, I do not even see what an attacker would be trying to accomplish in the scenario that you stated.

It is for reason of the ease of forward-dating signature timestamps that in the Nullian Verifiation thread, I include the infeasible-to-predict current information such as the past few Bitcoin block hashes within the signed statement. Satoshi included a current news headline in the Genesis Block for the same purpose. Add OpenTimestamps to prevent backdating, and the time of actual signing is strongly evidenced to be within a very short window.

For example, the signature on 2020-03-15 verification is strongly evidenced to have been created before Bitcoin block height 621774 (per OpenTimestamps), and after block height 621772 (for which the signed message contains the block hash, plus the nine preceding block hashes). I do believe that that is stronger evidence of the time of a signature than anybody has ever provided in these forum PGP threads!

Message Quoted and archived for future reference:

Archive [1a], [1b]

nullius

copper member

Activity: 630

Merit: 2610

If you don’t do PGP, you don’t do crypto!

When time permits, I must catch up with important replies on various threads. First things first: Assuring communications security.

Refreshed key. The only change: New certification signature on the same old encryption subkey. No need to quote; it is the same key as I have been using since 2017, only with a new self-signature omitting the key expiration time (subpacket type 9) for one subkey. As a separate matter, fresh verifications are periodically made here.

Code:

I do not generally recommend setting such short expirations as I had been using on my encryption subkey. I have done that in the expectation that I would upgrade my keymat handling in ways that I do not wish to discuss publicly, and issue a new subkey. Plans have been delayed. Now, as a hedge against future uncertainties (and in view of my own abysmal past performance in keeping this updated), I have removed the expiration date so as to assure that people will always have some means to encrypt a message to me. If or when I complete the upgrade, then I should just revoke the old encryption subkey. It is not known or suspected to be compromised in any way.

Quote from: nutildah on March 16, 2020, 12:09:40 AM

~

I did not reply before, because you gave a substantive response that I think warrants discussion best split off to a new thread; and my attention has been diverted elsewhere, unfortunately.

(It would be good to pick up a technical discussion about practical cryptographic security, instead of wading through another myriad posts about how Bill Gates created the coronavirus to push you to use vaccines instead of taking megadoses of Vitamin C, or whatever—ahem.)

In brief, I think that you have a flawed threat model based on an incomplete understanding of what various uses of signatures do and don’t prove. It is an important issue. I should take it up sometime.

Quote from: nutildah on March 16, 2020, 12:09:40 AM

Like I said earlier, what if somebody created the account and the key pair at the same time, and then passed off the account to somebody else while keeping the key pair for themselves? Was the post with the public key also timestamped at the exact same moment of creation as the account and key pair? Obviously no, it wasn't.

I don’t see any practical freshness problem, whereas the user posted a key containing within itself a signature on a forum account uid within eight hours after that forum account was created.

Timestamps on signatures can be trivially faked, anyway. `man gpg`, look for `--faked-system-time`. In your scenario, why couldn’t the user create a forward-dated signed statement, then pass off the account and the signed statement (but not the private key)? If the new account holder is willing to post a public key (with userid claiming the account) for which he does not control the corresponding private key, then he would also be willing to post a forward-dated signed statement; and in any case, the parties are colluding in a way that is almost impossible to detect or prevent. Moreover, given that both new PGP keys and brand-new forum accounts are easy to create, I do not even see what an attacker would be trying to accomplish in the scenario that you stated.

It is for reason of the ease of forward-dating signature timestamps that in the Nullian Verifiation thread, I include the infeasible-to-predict current information such as the past few Bitcoin block hashes within the signed statement. Satoshi included a current news headline in the Genesis Block for the same purpose. Add OpenTimestamps to prevent backdating, and the time of actual signing is strongly evidenced to be within a very short window.

For example, the signature on 2020-03-15 verification is strongly evidenced to have been created before Bitcoin block height 621774 (per OpenTimestamps), and after block height 621772 (for which the signed message contains the block hash, plus the nine preceding block hashes). I do believe that that is stronger evidence of the time of a signature than anybody has ever provided in these forum PGP threads!

nutildah

legendary

Activity: 2940

Merit: 7892

Quote from: nullius on March 15, 2020, 11:47:31 PM

Quote from: nutildah on March 15, 2020, 11:06:42 PM

Quote from: nullius on March 15, 2020, 04:53:18 PM

The statement claiming a forum uid is digitally signed. What other digital signatures do you want?

An actual signed message from the key. Everything else is just ~~you~~ him wasting everybody's time.

For the nth time: What is the substantial difference between a digital signature on a userid (plus the primary key binding signature from the signing subkey, which I doubt you even understand the significance of)—and a digital signature on a clearsigned text file with substantially the same content, posted together with the initial publication of the key?

You have been wasting my time providing you with patient technical explanations that either you are too lazy to read, or you are too stupid to understand. For you to attempt insulting me is despicable. Either explain in technical terms why I am so terribly wrong, which logically requires answering the above question, or fork off with your security theatre.

Producing a signature using the private key is proof of ownership of the paired public key. Producing a public key in itself is not proof of possession of the paired private key, regardless of what extra features are embedded in that key. This is a logically simple concept and should be fairly easy to understand.

Like I said earlier, what if somebody created the account and the key pair at the same time, and then passed off the account to somebody else while keeping the key pair for themselves? Was the post with the public key also timestamped at the exact same moment of creation as the account and key pair? Obviously no, it wasn't.

You're asking us to assume the public key is theirs because of the embedded data within the key, and that's fine, but if I were serious about cryptography I wouldn't use that as a substitution for production of a signature using the private key. I would ask for more substantial proof of ownership before attempting to send an encrypted message to that person.

Regardless, as I'll never have any interaction with ploney baloney that needs to be encrypted I really don't care, nor do I think they will ever say anything of importance for which their signature is required to authenticate they are the one saying it, so its a moot point.

Others are welcome to disagree with my interpretation, and that's fine.

nullius

copper member

Activity: 630

Merit: 2610

If you don’t do PGP, you don’t do crypto!

Quote from: nutildah on March 15, 2020, 11:06:42 PM

Quote from: nullius on March 15, 2020, 04:53:18 PM

The statement claiming a forum uid is digitally signed. What other digital signatures do you want?

An actual signed message from the key. Everything else is just ~~you~~ him wasting everybody's time.

For the nth time: What is the substantial difference between a digital signature on a userid (plus the primary key binding signature from the signing subkey, which I doubt you even understand the significance of)—and a digital signature on a clearsigned text file with substantially the same content, posted together with the initial publication of the key?

You have been wasting my time providing you with patient technical explanations that either you are too lazy to read, or you are too stupid to understand. For you to attempt insulting me is despicable. Either explain in technical terms why I am so terribly wrong, which logically requires answering the above question, or fork off with your security theatre.

nutildah

legendary

Activity: 2940

Merit: 7892

Quote from: nullius on March 15, 2020, 04:53:18 PM

The statement claiming a forum uid is digitally signed. What other digital signatures do you want?

An actual signed message from the key. Everything else is just ~~you~~ him wasting everybody's time.

nullius

copper member

Activity: 630

Merit: 2610

If you don’t do PGP, you don’t do crypto!

Quote from: nullius on March 15, 2020, 04:53:18 PM

I have a little surprise in store. It is pending blockchain confirmation. It is significant, so I will post when that’s done.

Appropriately made its own thread: Nullian Verification.

Quote from: DireWolfM14 on March 15, 2020, 06:57:49 PM

The forum ID proving ownership of the key. Right now the owner of the key is claiming ownership of the forum account, and that's all we know for certain. The owner of the forum account has not proven ownership of the key. Only a signed message could do that.

If posting the signed message saying, “I am bitcointalk.org u=XYZ” in the same post alongside initial publication of the key would suffice, then so should posting a key containing substantively the same signed message: The cases are indistinguishable from a security perspective.

Would you please explain what type of attack scenario you have in mind, in which a person creates a Brand New forum account, and then within 8 hours thereafter posts a claim to a PGP key that he doesn’t actually control—but in which he somehow procured a digitally signed userid claiming his less-than-8-hours-old forum account, despite his lack of ability to sign with the key?

A general note (not only in response to DireWolfM14):

To avoid a false sense of security requires precise thinking about what each piece of evidence does or does not tend to prove.

What we want is a bidirectional binding between two identities: (A) The forum account claiming the key, and (B) the key claiming the forum account. Unfortunately, as I have repeatedly pointed out, (A) cannot be done cryptographically; the best that can be done is for the person who creates an account to post a claim to a key ASAP, as the user did here. (B) can and must be done cryptographically. (B) is only and exactly what would be proved by a signed statement. It is equally, or even better proved by a certification on an OpenPGP userid; indeed, for a key to claim a non-cryptographic type of account (usually an e-mail address) is the whole purpose of the design of OpenPGP userids!

To be absolutely clear, all of this discussion is orthogonal to the question of what evidence later use of a PGP key can provide. In the future, if the account’s integrity is in question (e.g., allegations that it was hacked), the person who claimed a public key now can then demonstrate continuing possession of the corresponding private key. What we are now doing is trying to establish the initial association of an account with a key and a key with an account.

So, again...

Quote from: nullius on March 15, 2020, 04:53:18 PM

And what, praytell, is the practical difference between a digitally signed OpenPGP userid claiming a forum uid, and a `gpg --clearsign` statement claiming a forum uid?

(Pedantic note: I emphasize the word practical, because the former binding is certified (i.e., signed as a PGP userid) with the user’s certification-only primary key, and the latter would perforce be signed with a signing subkey certified by the certification-only primary key. For the purpose of this discussion, that technical difference should have negligible impact—although I would assume that the certification key is handled with greater security; nobody does the split-key thing unless extreme measures are desired for the primary key.)

DireWolfM14

copper member

Activity: 2170

Merit: 4238

Join the world-leading crypto sportsbook NOW!

Quote from: nullius on March 15, 2020, 04:53:18 PM

And what, praytell, is the practical difference between a digitally signed OpenPGP userid claiming a forum uid, and a `gpg --clearsign` statement claiming a forum uid?

The forum ID proving ownership of the key. Right now the owner of the key is claiming ownership of the forum account, and that's all we know for certain. The owner of the forum account has not proven ownership of the key. Only a signed message could do that.

Topic: The BCT PGP/GPG Public Key Database: Stake Your PGP Key Here - page 3. (Read 66293 times)