7 ms·
Crypto: speck – remove Speck
- danielhlockard 8y agoThis is interesting... If speck isn't used I'm all for less poor crypto that can be used in the kernel... Just like OpenSSL removing Export ciphers (thanks FREAK attack)
- hexsprite 8y agoI love deleting unused code
- zokier 8y agoWell, this is not exactly cleaning up old legacy code. Its more of undoing a patch that should haven not been merged in the first place.
- anilakar 8y agoDeleting whole deprecated features is even better. Often it's an indication of a modular architecture and proper upgrade path when an old, unused piece of code has been superseded without breaking any major parts of the whole system.
- dmitrygr 8y agoI actually used speck in a project of mine. It compiles to very very tight code even on an 8-bit micro, much smaller than AES. Since my attack profile does not include nation-states I see no issues in using it in my use case. Sometimes even speck may be the right tool for the job.
- craftyguy 8y ago> Sometimes even speck may be the right tool for the job. I disagree. Proliferation of very-likely-backdoored crypto is dangerous. By using it you're demonstrating that it is OK to use crap the NSA is pushing. If it gains in popularity, you'll have people trying to use it for sensitive communications, etc, without understanding why it is a terrible idea.
- mistaken 8y agoEven if it comes from the NSA it doesn't necessarily mean it's backdoored. Speck is a good algorithm for performance constrained devices. It was removed from the kernel since it couldn't be included into Android systems due to political reasons, and the authors of the module wrote an implementation of an alternative algorithm for this use-case.
- craftyguy 8y ago> Even if it comes from the NSA it doesn't necessarily mean it's backdoored I suppose you could say the same thing about someone with a history of robbing banks.. just because they walked into your bank doesn't mean they are about to rob it (but it's highly likely they are).
- tptacek 8y agoIf someone with a history of robbing banks arrived at my bank with a ski mask and a bulging duffle bag, I would say "go away, bank robber". The analogy to cryptography would be the NSA proposing yet another PKRNG, of any kind. On the other hand, if someone with a history of robbing banks called me on the phone and asked me what the interest rates on my checking accounts were, I would tell them, because they can't rob my bank over the phone. The analogy here would be to the NSA suggesting a streamlined, simplified ARX block cipher transform, a backdoor in which would imply some fundamentally unknown property of block ciphers that would presumably jeopardize a whole variety of other academic ciphers, and would not accomplish the NOBUS property that NSA requires of backdoors in things they encourage USG assets to use themselves.
- betterunix2 8y agoThe NSA actually has a history of solid block cipher and hash function proposals: https://en.wikipedia.org/wiki/Data_Encryption_Standard https://en.wikipedia.org/wiki/Data_Encryption_Standard https://en.wikipedia.org/wiki/SHA-1 https://en.wikipedia.org/wiki/SHA-1 https://en.wikipedia.org/wiki/Skipjack_(cipher) https://en.wikipedia.org/wiki/Skipjack_(cipher)
- 8y ago
- LadyNike 8y agoFor those interested, Eric Biggers, the author of the patch which added Speck support, sent an RFC the previous day to add HPolyC support to the kernel. http://lkml.iu.edu/hypermail/linux/kernel/1808.0/05226.html http://lkml.iu.edu/hypermail/linux/kernel/1808.0/05226.html
- deleted 8y ago[deleted]
- cjhanks 8y agoSo is the presumption that Google would write a more honest and correct encryption algorithm than the NSA? The irony is at least a little funny. People distrust the NSA because they use highly invasive technology to identify suspicious behavior. But Google is trusted, and they use highly invasive technology for profit. Honestly, I generally trust both of them. But, technology politics are very confusing.
- bjoli 8y agoGoogle's track record regarding crypto is high. NSA has done a lot of good, but recently behaved bad (backdoored random number generator) weird (not explaining uncommon design decisions) and counterproductive (representatives either being or acting stupid on various cryptography standard body mailing lists). Google on the other hand has been doing a very nice job
- CamouflagedKiwi 8y agoNo, as explained in the RFC (linked in the article) they're trying to get disk encryption on low-end devices that aren't capable of supporting AES. It's not an argument that AES is in any way incorrect. I suppose it could be an elaborate scheme to add a backdoor, although presumably it will see significant review and anyway that hardly seems necessary given that the current alternative on those devices is no encryption at all.