4 ms·
Oh I would not suggest rolling your own crypto. Rather, just fork openssl and make a very subtle change to each formula. For in-house use of course. Ages ago
by LinuxBender 7y ago
Oh I would not suggest rolling your own crypto. Rather, just fork openssl and make a very subtle change to each formula. For in-house use of course.
Ages ago, I used to change up a rubix-cube for a friend. The more I changed it, the quicker he could solve it. If I made just a very subtle change, it would take him up to an extra 7 seconds to solve it.
- nullc 7y agoThat is likely to introduce vulnerabilities unless you are a subject-matter expert that understands the design of the things you are changing well enough to know which parameters were free choices.
- arcticbull 7y agoMy dude, there aren’t any “extra knobs” you can just turn and expect to maintain the security and integrity of a cryptographic solution. This isn’t some Node/React website we’re talking about. If you move one assembly opcode out of place you may end up disclosing your private key via side-channel attack — and that’s a best case outcome. The fact you’re so cavalier about this tells me you have no idea what you’re talking about. Ask an infosec person, then report back lol This has nothing; and I do mean nothing to do with your Rubik’s cube analogy. One small tweak and the whole thing may be utterly worthless. It’s like if you were tweaking the starting position of the Rubik’s cube with a nuclear warhead.