maxtaco

15 ms·

121.
by maxtaco 13y ago
Yes, it's in Section 15.8 of the 2nd edition of Applied Cryptography. This is basically that scheme, but we're not inflating ciphertexts as he suggests (which is a good thing).
122.
by maxtaco 13y ago
There is no way this construction is weaker than the weakest of the three. To convince yourself of this, assume one of the ciphers is 100% broken and spits out all 0s. Then you're XOR'ing your ciphertext with all 0s (or some other
123.
by maxtaco 13y ago
For PBKDF2, we use SHA-512 XOR SHA3 as the inner PRF. But you're right, it would be interesting to stack bcrypt and scrypt too. That's a good idea in the name of maximum paranoia. My slight reservation here is that I haven'
124.
by maxtaco 13y ago
Version 3, compatible with the latest test vectors published here: http://keccak.noekeon.org/KeccakKAT-3.zip . Our hope is that the algorithm won't change, but if it does, we'll bump version numbers and support d
125.
by maxtaco 13y ago
It's all on GitHub. Please let me know of any bugs you find, and thanks. I did test the implementation against whatever test vectors I could find, but obviously carry code is tricky and error-prone. Link here: https://gith
126.
by maxtaco 13y ago
In my experience, speed isn't an issue. The only slow part of any of this is PBKDF2, unless you're dealing with huge files (not the case in chat).
127.
by maxtaco 13y ago
It scares me to use something other than something random here because any scheme to remember which nonces you've used before seems bug-prone and vulnerable. As for whether it's called a nonce or IV, I've seen it written as
128.
by maxtaco 13y ago
Agreed.
129.
by maxtaco 13y ago
SJCL is good software and has good defaults for its high-level encrypt function `sjcl.json.encrypt`. It uses CCM so you don't have to MAC in addition to encrypting (as TripleSec does). Depending on what parameters and degree of safet
130.
by maxtaco 13y ago
Hi, Max here. I'm happy to answer questions about TripleSec, so let me know.
131.
by maxtaco 13y ago
I wrote a little wrapper while at OkCupid for dealing with adhoc JSON objects in Go, available here: https://github.com/okcupid/jsonw
132.
by maxtaco 15y ago
Thanks for the 1.3 release, I was running out of lowercase letters. I'll try to reply to these concerns in the pull-request, but have been busy. Also, looks like I have rebasing work to do.... The good news is that ICS is working well in p
133.
by maxtaco 15y ago
A key advantage of fibers of course is that they preserve exception semantics, whereas tame can't in all cases. I'm not too interested in reviving the stalemated thread v. event religious war. I prefer explicitly-managed events, but if oth
134.
by maxtaco 15y ago
It's on the list of todos to preserve the input line-numbering in the output code. This would mean some changes to the code emitter, and also to the code emitted to preserve the ordering of statements. In tame/C++, debugging either compile
135.
by maxtaco 15y ago
My first thought for implementing tame.js was with yield, but V8 doesn't currently support it (though it's reserved as a "future" keyword). A direct use of yield (without anything like twait) would probably make node code look more like Py
136.
by maxtaco 16y ago
Send an email to userfeedback@okcupid.com, subject: gdulli, and I'll ask you to visit a few links. Thanks a lot, I really appreciate the help!
137.
by maxtaco 16y ago
Manual memory management is for the birds. Use something like Boost's shared pointers and you never need to worry about it.
138.
by maxtaco 16y ago
We rarely get complaints such as this one. Would you mind helping me debug it?