Live data from Hacker News

Telegram protocol defeated. Authors are going to modify crypto-algorithm

translate.google.com

11–20 of 223 posts

Re: Telegram protocol defeated. Authors are going to modify crypto-algorithm

#12
I hope this person will get the full $200,000. I definitely don't think we can ever trust Telegram's strength again. They won't be paying him the full $200,000 even though he has rendered the Telegram to be weak. Major, major backfire for Telegram stakeholders.

Re: Telegram protocol defeated. Authors are going to modify crypto-algorithm

#13
post #6
post #3

Earlier quoted context omitted.

Why not the 200K? Was it outside the parameters of the contest or something?

Yes, outside. Although the underground of this contest was to prove security and inability to read messages by 3rd parties contest was about decrypting Durov's chat. Chat is not decrypted and as many say - it's nearly impossible ( http://thoughtcrime.org/blog/telegram-crypto-challenge/ ). But "bookmark" is found and it means that all the PR was shit. Telegram already removed 'xor nonce' from their documentation and a…

old copy of their doc which has 'xor nonce' inside: http://webcache.googleusercontent.com/search?q=cache:FAntx8l...

Re: Telegram protocol defeated. Authors are going to modify crypto-algorithm

#17
post #14

Why does Telegram provide the generator (g and p) and then suggest validation and caching? These can be hardcoded parameters

in cryptography nothing is hardcoded (or at least hardcoded values should have enough entropy) :) if client doesnt use caching - then every message user sends should obtain a new pair of p/g (which is expensive) - and it will make telegram not only insecure but also "slow" messenger :P

Re: Telegram protocol defeated. Authors are going to modify crypto-algorithm

#20
post #17
post #14

Why does Telegram provide the generator (g and p) and then suggest validation and caching? These can be hardcoded parameters

in cryptography nothing is hardcoded (or at least hardcoded values should have enough entropy) :) if client doesnt use caching - then every message user sends should obtain a new pair of p/g (which is expensive) - and it will make telegram not only insecure but also "slow" messenger :P

The only things that aren't hardcoded in your typical secure cryptosystem is your key and a few nonces. In ECC the analogous components to p and g are defined extremely carefully and certainly wouldn't be changed willy nilly. I'm aware classic DH parameters are more liberal, but changing them for every session seems unnecessary.
Post reply on HN