![]() I think they should be encoding \n as to facilitate copying and pasting. This is a bug with Twitter's web and mobile-web sites. When copying from a browser, it is possible that newlines will not be preserved - this may cause your decryption app to think that the message is corrupted. ![]() It should be fairly easy to decrypt a message that you have been sent - but it will depend on your Twitter client. Ok, this is where it gets a bit more technical. So, no DMing Harry Potter length novels! Decrypting In addition, you may only send up to 1,000 Direct Messages per day. PGP is a relatively efficient way of encrypting text so, depending on your message, you can fit around 9,000 plain text characters into a 10,000 character encrypted message. Twitter touts DMs as being "unlimited" - in reality, there's a limit of 10,000 characters. ![]() The Twitter website preserve newlines when you send a message - make sure that your app also does so. Not like this: -BEGIN PGP MESSAGE- Version: Keybase OpenPGP v2.0.43 Comment: wcFMAz8xGBvPCGIHAQ//aaPuyglRhwo0hzeVuyDC8pgIGyS7f5oyp99wMRsIh8G0 i6kuo9 dPVNJ gGLC2B5eMuoYE0Bjv/2YfBkxaJ6HTacniUEgD9x7OxNnQY2PCyi I6kuo9 dPVNJ gGLC2B5eMuoYE0Bjv/2YfBkxaJ6HTacniUEgD9x7OxNnQY2PCyi WcFMAz8xGBvPCGIHAQ//aaPuyglRhwo0hzeVuyDC8pgIGyS7f5oyp99wMRsIh8G0 A proper PGP message should look like this: -BEGIN PGP MESSAGE. Some Twitter clients will "helpfully" remove line breaks. A rogue space, or missed character, will render the message completed undecipherable. In order for PGP encrypted messages to work, it is important that they are not altered in any way. It's as simple as copying the entire block of encrypted text and pasting it into a Twitter Direct Message. Hey presto! A big blob of text which can only be decrypted by me. Just type what you want to send and hit the "Encrypt" button. Keybase gives you the option of encrypting a message to me. You can visit Keybase.io/edent to see mine. The website Keybase.io contains a list of people's public keys. This is a digital lock which only I can open. In order to encrypt, you need to know my Public Key. If you encrypt the message to me, only I will be able to read it. Suppose you want to send me a message - but you are worried about the contents being seen by someone else. I've written this article with a non-technical audience in mind - feel free to point out any areas where I can make my explanations more simple. So, I want to demonstrate how it can be done successfully. There is a minor bug in Twitter's web interface - but PGP seems to work perfectly in apps. I read an article yesterday which seemed to imply that Twitter was mangling PGP encrypted messages (albeit unintentionally). This is a quick tutorial on how to encrypt your Twitter messages using PGP with the help of Keybase.io.
0 Comments
Leave a Reply. |