News for hackers. Stuff that matters.
Re:Text Shredder: Peer-to-peer message-based encryption utility by lucb1e on Friday March 14, 2014 @11:50AM (#7399607)
Uhm, why this if we have GPG? I've never heard of Text Shredder and automatically distrust any new crypto (just look at Telegram), whereas GPG is very well known and much more battle tested.

Edit: The download button gives me some .exe file and the source code is Microsoft shit. Not gonna work.

Edit2: It seems to use AES ECB. Definitely secure... not https://en.wikipedia.org/wiki/File:Tux_ecb.jpg

Pseudocode of what it does:

    function EncryptBlock(data, password)
      encrpytedMessage = aes.Encrypt(data, passwd, salt, pbkdf2RoundsCount);
      return encrpytedMessage; // sic
    
    function aes.Encrypt(data, pwd, salt, pwd_rounds)
      hash = pbkdf2(pwd, salt, rounds);
      IV = hash.getBytes(16);
      passwd = hash.getBytes(32);
      encrypted = aes(data, passwd, IV);
      return encrypted;
Re:Text Shredder: Peer-to-peer message-based encryption utility by simplyinfinity on Friday March 14, 2014 @12:04PM (#7399724)
Microsoft shit? you realize this is an open source project, right? this didn't come from microsoft, instead someone used the tools they provided to give you a way of secure communication, and you go about and bash them because of what? The tools they used are from Microsoft ?
Re:Text Shredder: Peer-to-peer message-based encryption utility by lucb1e on Friday March 14, 2014 @12:09PM (#7399763)
> The tools they used are from Microsoft ?

That's the point. Microsoft doesn't release .NET compilers for any other platform than their own, and since I don't use Windows I'm not going to execute this application. Anyone sending messages to me can install GnuPG, something that is available across platforms.

Re:Text Shredder: Peer-to-peer message-based encryption utility by sp332 on Friday March 14, 2014 @12:52PM (#7400097)
I just tested it, and the executable runs perfectly fine in Mono. Look ma, no Microsoft!
Re:Text Shredder: Peer-to-peer message-based encryption utility by sweis on Friday March 14, 2014 @01:43PM (#7400489)
As far as I can tell, the AesCryptoServiceProvider they are using inherits the default CBC mode from here:

http://msdn.microsoft.com/en-us/library/system.security.cryp...

So, it appears to be using CBC. However, their ciphertext is not authenticated so is still insecure.

Re:Text Shredder: Peer-to-peer message-based encryption utility by stevehaunts on Friday March 14, 2014 @02:55PM (#7400973)
I will add hmac authentication of the cipher text.
Re:Text Shredder: Peer-to-peer message-based encryption utility by abemassry on Friday March 14, 2014 @01:13PM (#7400266)
I've attempted to solve this problem for the command line with https://github.com/abemassry/wsend-gpg

I haven't had any ideas on how to make it easier to use for people that use windows / don't use the command line. Maybe some type of GPG implementation in javascript for the browser, looking for any ideas / help

Re:Text Shredder: Peer-to-peer message-based encryption utility by danbruc on Friday March 14, 2014 @12:17PM (#7399820)
The default mode is CBC [1]. Still the fact alone that the mode is not set explicitly and makes it look like the author did not know or think about it gives me a bad enough feeling that I would never use it.

[1] http://msdn.microsoft.com/en-us/library/system.security.cryp...

Re:Text Shredder: Peer-to-peer message-based encryption utility by lucb1e on Friday March 14, 2014 @12:20PM (#7399846)
Okay that would solve a lot. I hope he passes the entire text into his EncryptBlock method instead of just a block.

I'm not sure, but even if it uses CBC internally, the encryptions might still be broken by comparing the first block of each encrypted message, if messages are encrypted with the same password (which is very likely). I've always heard that the IV may never be static.

Re:Text Shredder: Peer-to-peer message-based encryption utility by danbruc on Friday March 14, 2014 @12:24PM (#7399886)
He uses a unique initialization vector obtained from a cryptographically secure random number generator for each message, so there is no obvious issue with the first block, too.

UPDATE: Not entirely correct, see https://news.ycombinator.com/item?id=7400183.