Timeline for Implement GPG Verification (Bitcoin-OTC)
Current License: CC BY-SA 3.0
17 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 6, 2015 at 23:14 | comment | added | AJAr | Let's chat about it (chat.stackexchange.com/rooms/20905/…). Getting crowded on the comments here. | |
| Feb 6, 2015 at 23:08 | comment | added | Maros | That makes sense. How would this work if I got the user to decrypt a message? Wouldn't I first need to encrypt it in a way that only he can decrypt it as the holder of the secret token? Wouldn't I also need access to that secret token to do the encryption? Sorry, I'm pretty new to GPG. | |
| Feb 6, 2015 at 23:02 | comment | added | AJAr | I think the reason why #bitcoin-otc checks GPG the way it does (sig request instead of decryption request) is because sig verification is a much, much faster op than encryption. That said, one is IRC and the other is a website; it can't very easily use a CAPTCHA, but you can to mitigate the risk of DOS attacks. | |
| Feb 6, 2015 at 21:58 | comment | added | AJAr | They can't sign with just the public key. | |
| Feb 6, 2015 at 21:57 | comment | added | Maros | But isn't it possible for an attacker to grab another user's key and sign the message with that to claim to be that user? | |
| Feb 6, 2015 at 21:42 | comment | added | AJAr | Oh, alright. In that case, I think it might be better to have them decrypt a message than encrypt one. The margin for error is a bit lower, plus (depending on your audience) some users may not know how to sign messages even though they know how to encrypt them. A lot of different interfaces out there for PGP. | |
| Feb 6, 2015 at 21:35 | comment | added | Maros | It's a typical Rails app. I just made that script for testing purposes. | |
| Feb 6, 2015 at 21:32 | comment | added | AJAr | What kind of app are you making, btw? Just curious since at first I thought it was a web app. | |
| Feb 6, 2015 at 21:28 | comment | added | Maros | Haha. What a coincidence. | |
| Feb 6, 2015 at 21:25 | comment | added | AJAr | Hah, made edits at almost the same time. | |
| Feb 6, 2015 at 21:24 | history | edited | AJAr | CC BY-SA 3.0 |
deleted 70 characters in body
|
| Feb 6, 2015 at 21:23 | comment | added | Maros | Thanks for your response. This seems like a good solution. Though I've posted an edit with a new idea involving just plain old GPG concepts. Would you mind taking a look and seeing if it's valid? | |
| Feb 6, 2015 at 21:17 | history | edited | AJAr | CC BY-SA 3.0 |
deleted 70 characters in body
|
| Feb 6, 2015 at 21:03 | history | edited | AJAr | CC BY-SA 3.0 |
added 264 characters in body
|
| Feb 6, 2015 at 20:51 | history | edited | AJAr | CC BY-SA 3.0 |
added 364 characters in body
|
| Feb 6, 2015 at 20:36 | history | edited | AJAr | CC BY-SA 3.0 |
added 45 characters in body
|
| Feb 6, 2015 at 20:31 | history | answered | AJAr | CC BY-SA 3.0 |