News for hackers. Stuff that matters.
Re:How is NSA breaking so much crypto? (2015) by maxerickson on Saturday December 17, 2016 @07:06AM (#13200395)
It depends on if only one of the layers leaks information or not. If the custom layer leaks and the other doesn't, the custom layer is making things worse.

When you take the argument that a big problem with roll your own crypto is the tendency for the implementation to be naive to a bunch of ways for information to leak, well, there you go, gluing a competent implementation to an incompetent one compromises the competent implementation.

Re:How is NSA breaking so much crypto? (2015) by loup-vaillant on Saturday December 17, 2016 @08:35AM (#13200645)
What we need is a construction that is as secure as the strongest underlying primitive. For instance, for symmetric encryption: Let M be the secret message, C1 the first cypher, C2 the second cypher, K1 and K2 two randomly generated, independent keys. Oh, and a nonce, but let's ignore that for now.

I Think it is easy to prove that C1(K1, C2(K2, M)) is at least as hard to break as either C1(K1, M) or C2(K2, M). Because if one of the cypher is easy to crack, the other can still work.

Hashes are different, because they're not reversible. In this case, a bad hash could indeed project the input space into a smaller output space than expected, and previous or subsequent hashes cannot reverse this mistake.

Re:How is NSA breaking so much crypto? (2015) by stolsvik on Saturday December 17, 2016 @07:36PM (#13203637)
Hashes: What about xor'ing together hashes from two or more algos? Even if one just hashed to all-1, it wouldn't matter.
Re:How is NSA breaking so much crypto? (2015) by Natanael_L on Sunday December 18, 2016 @02:33PM (#13207167)
Only if the hash algorithms aren't correlated, they should ideally be of different designs.
Re:How is NSA breaking so much crypto? (2015) by loup-vaillant on Sunday December 18, 2016 @03:21AM (#13204893)
Dunno. Looks promising.