Re:Telegram secret chat geolocation leak
by kyberias on Wednesday December 25, 2013 @10:07AM
(#6963112)
So what are the implications for application DESIGN? None. It was just a mistake in not using SSL. Next.
[ Parent
| on HN ]
Re:Telegram secret chat geolocation leak
by DanBC on Wednesday December 25, 2013 @11:27AM
(#6963285)
> It was just a mistake in not using SSL.
In a secure, crypto, application?
You can see how that's a bit concerning?
I'm not quite sure why programmers release crypto apps as "SECURE", instead of "We'd like this to be secure, so we're releasing this beta edition with a bug bounty. Don't use it for safety critical applications yet."
Re:Telegram secret chat geolocation leak
by kyberias on Wednesday December 25, 2013 @05:38PM
(#6964539)
Look, I'm not saying it's not concerning. I'm saying this does not imply anything on the design of the application. If the only lesson I can get from this is "to use SSL", then the design lesson wasn't very illuminating. Get it?
Re:Telegram secret chat geolocation leak
by al2o3cr on Wednesday December 25, 2013 @11:30AM
(#6963300)
"None" is a bit strong - after all, we're talking about people who have assured us that their boffins are smart enough to roll a new cryptosystem who then turn around and fail Security 101.
Re:Telegram secret chat geolocation leak
by mannykannot on Wednesday December 25, 2013 @10:23AM
(#6963158)
I am curious as to what you think design is. And what 'just' means, for that matter.
Re:Telegram secret chat geolocation leak
by venomsnake on Wednesday December 25, 2013 @11:18AM
(#6963266)
Also any company that had credit card and password info stolen were just made a mistake of not using proper KDF.
Those types of errors are scary not just because what they are but because it is interesting what else is wrong.