Re: Master-P POSSIBLE SCAM. I lost complete faith in this forum now.
BTW, have anyone bothered to verify his signed messages from his Keybase account? He din't even know how to sign a message, instead he just encrypted them! I was trying to verify all his signed messages and got the same error as follows:
This is how a signed messaging via PGP key is done:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
This is an example of how a signed message from PGP key should look like.
P.S. This message is signed by notaek from bitcointalk.org on December 29, 2015 at 08:48:21 PM Forum Time.
You can verify this message and all other PGP signed messages here => https://keybase.io/verify
-----BEGIN PGP SIGNATURE-----
Version: Keybase OpenPGP v2.0.49
Comment: https://keybase.io/crypto
wsBcBAABCgAGBQJWgvHLAAoJEBI9bCdjrvBErdkH/38QQDk7YXZeZrSfLwCz5gZM
4nQUd8A7IiLQUSba9GZCgjq24hRIbLr7n+uRfWg7OS3ZWlG00cseTj5vtN001+DO
zFZYSXWM69Ot5nXHFf8WVaQ1Z+GKVZ5Fzw+Hcyy5YteBmjC4sASxO48yoCwMdqS/
PVVwxPm/LsOeV9Zop+o01ktyF9261fJpe5I63UooUHy0hpzA//d7k+qiNc1kEogy
SVNlK0j4IE0Nu+/72ujH4uQiIWVmOcSArLN/QhxRG8ZknzsbxFfs/dtn6W4yhrwS
Ib9L7fA4DuEa2Mka9fI02FzLrBQeXqo0WnDfxT73Qw6SJVB7jgdoQyXqhcEL7Uo=
=b2iZ
-----END PGP SIGNATURE-----
And for everyone's kind information, this error is also found in his signed message that was done first on January 29, 2015, 03:34:40 PM . So you all can conclude the rest!
I have verified his signed messages before, and they always came out correctly. But now they aren't.Quote
Error: you cannot process a message that was encrypted for someone else.
This is how a signed messaging via PGP key is done:
Code:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
This is an example of how a signed message from PGP key should look like.
P.S. This message is signed by notaek from bitcointalk.org on December 29, 2015 at 08:48:21 PM Forum Time.
You can verify this message and all other PGP signed messages here => https://keybase.io/verify
-----BEGIN PGP SIGNATURE-----
Version: Keybase OpenPGP v2.0.49
Comment: https://keybase.io/crypto
wsBcBAABCgAGBQJWgvHLAAoJEBI9bCdjrvBErdkH/38QQDk7YXZeZrSfLwCz5gZM
4nQUd8A7IiLQUSba9GZCgjq24hRIbLr7n+uRfWg7OS3ZWlG00cseTj5vtN001+DO
zFZYSXWM69Ot5nXHFf8WVaQ1Z+GKVZ5Fzw+Hcyy5YteBmjC4sASxO48yoCwMdqS/
PVVwxPm/LsOeV9Zop+o01ktyF9261fJpe5I63UooUHy0hpzA//d7k+qiNc1kEogy
SVNlK0j4IE0Nu+/72ujH4uQiIWVmOcSArLN/QhxRG8ZknzsbxFfs/dtn6W4yhrwS
Ib9L7fA4DuEa2Mka9fI02FzLrBQeXqo0WnDfxT73Qw6SJVB7jgdoQyXqhcEL7Uo=
=b2iZ
-----END PGP SIGNATURE-----
And for everyone's kind information, this error is also found in his signed message that was done first on January 29, 2015, 03:34:40 PM . So you all can conclude the rest!
BTW, this is not encrypting messages. It is signed. If the message was encrypted, it wouldn't have anything like PGP signature. It would be just a block of random characters. I think that is just Keybase giving a bad error message.
Edit: I think he changed his PGP key in Keybase. I verified the message on my computer and it was signed by a key with the id 0x138D7CA49E301A44. However the id of the one on Keybase is 0xDF139C3C23784CED.
Edit2: This is interesting, the email of the PGP key now on Keybase is zinoxenxe.reddit@gmail.com.