Skip to main content
10 events
when toggle format what by license comment
Sep 12, 2020 at 8:59 comment added mbarkhau Can somebody link to a working implementation of this, preferably in python?
Jan 2, 2018 at 17:17 comment added Paŭlo Ebermann @SqueamishOssifrage thanks for the edit, it looks a lot nicer now.
Dec 16, 2017 at 22:35 history edited Squeamish Ossifrage CC BY-SA 3.0
My god, this kerning is killing me. One of us has _got_ to go.
Sep 20, 2013 at 17:36 comment added Maxthon Chan @tylo Packaged and published, but with a strong disclaimer and deprecation mark. I submitted this algorithm to some academic institution for evaluation though.
Sep 19, 2013 at 19:24 vote accept Maxthon Chan
Sep 19, 2013 at 13:36 comment added tylo I hope you are not going to actually use this... I was assuming that this is just bouncing ideas around or for practice. Implementing your own crypto is really really bad, if you are not an absolute expert for that. And considering your last sentence, I don't think you are. AES (even 128 bit) is considered secure - unless you have to assume sidechannel attacks (e.g. via cache/timing), related key attacks and such.
Sep 19, 2013 at 11:33 comment added Maxthon Chan @tylo I have two alternatives that is almost the same: one use SHA512-HMAC as CSPRNG and operate on 512-bit blocks and keys (The SHA512 hashing at the input of key and IV is to normalise lengths), another based on AES with 128-bit blocks and 256-bit keys. To me the 256-bit key length is a little too short.
Sep 19, 2013 at 10:40 comment added tylo Unlinking IV and Key does not really change much. It is still a mode of operation, where you swap the fast symmetric block cipher to a slow hash function (due to its unnecessary properties).
Sep 19, 2013 at 8:41 comment added Maxthon Chan Key and IV is unlinked now.
Sep 18, 2013 at 19:43 history answered Paŭlo Ebermann CC BY-SA 3.0