4 ms·
So what are the implications for application DESIGN? None. It was just a mistake in not using SSL. Next.
by kyberias 13y ago
So what are the implications for application DESIGN? None. It was just a mistake in not using SSL. Next.
- mannykannot 13y agoI am curious as to what you think design is. And what 'just' means, for that matter.
- cmiles74 13y agoPerhaps this means that is was "just" poorly "designed".
- venomsnake 13y agoAlso 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.
- DanBC 13y ago> 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."
- kyberias 13y agoLook, 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?
- al2o3cr 13y ago"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.
- judk 13y agoI too am curious what the next security flaw will be. Clearly their design does not include validation or testing