9,586 reputation
12347
bio website github.com/CodesInChaos
location Frankfurt, Germany
age
visits member for 3 years, 1 month
seen yesterday

Sep
6
comment Is javascript RSA signing safe?
Are you using HTTPS? Without HTTPS a webapplication has no hope of being secure.
Sep
6
comment Distributed Asymmetric Key Decryption with threshold
You can create a random symmetric key for each message, apply shamir secret sharing to it (symmetric secret sharing) and then encrypt each share with a different public key.
Sep
4
revised One-way function and $EXP$
edited tags
Sep
4
reviewed Approve suggested edit on One-way function and $EXP$
Sep
2
comment Key Refresh in Diffie-Hellman
"that an attacker would get an amount of ciphertext for the same key for cryptoanalysis and breaking the encryption." As long as you use strong encryption, you shouldn't worry about that. The added complexity is a far greater risk than AES getting broken. But if you insist, you should HKDF with different info strings on the shared key to derive the individual keys instead of re-running DH. Or, my preferred way of encrypting files, use a new random key for each file, and encrypt that key with the master key.
Sep
2
comment Key Refresh in Diffie-Hellman
How would you get your partners public key with respect to the new generator?
Sep
2
comment Key Refresh in Diffie-Hellman
Why do you want to change the key? In your question it sounds like you change keys for changes sake.
Sep
2
revised Where can I double check my elliptic curve results?
added 3 characters in body
Sep
2
comment Initialization vector in symmetric-key encryption
What is the underlying issue behind "there is no way to create an initialization vector for each encryption"? Do you need length preserving encryption? Or deterministic encryption? Or is there no CSPRNG?
Sep
1
revised Storing Credentials for a Third Party
added 258 characters in body
Aug
31
comment Is there a cryptographic function or system in which it becomes HARDER to break as time passes?
Doesn't seem useful in practice. It's easy to design huge security margins against brute-force into a system. Crypto doesn't get broken by brute-force nowadays. It's either broken by analysis (finding a flaw in the crypto) or circumvented (finding flaws in the software). The only potential brute-force attack that's not easy to prevent is a quantum computer, but we'll solve that in a few years as well.
Aug
31
reviewed Approve suggested edit on Feedback requested on a method of posting a message without revealing the author
Aug
16
reviewed Approve suggested edit on Voting scheme where the votes become public when a threshold is reached
Aug
16
comment Types of Cryptography for a 4-8 bit microcontroller
Why do you mention diffie-hellman? Your code doesn't have anything in common with DH. DH takes at least million cycles. If you can afford DH, you can afford a sane symmetric algo. There is also the whole field of lightweight crypto that attempts to construct cheap but secure crypto. Unlike your system which seems about as secure as caesar encryption.
Aug
16
comment Any practical uses of machine learning for cryptography?
The closest thing to automated cryptoanalysis are SAT solvers.
Aug
16
comment One Time Pad Question
Take the ciphertext you have and the message you want, xor them. That gives you the key which decrypts the message to that given message. Obviously this only works with OTPs, not with short key stream-ciphers.
Aug
16
reviewed Approve suggested edit on Could this be a valid variation of the Schnorr protocol?
Aug
15
comment Is there any research about cryptography on nondeterministic Turing machines?
BTW quantum computers can only solve problems in BQP efficiently, which is much smaller than MA (the probabilistic equivalent of NP). (At least as far as we know, obviously we can't prove that ATM since we don't even know for sure if P!=NP)
Aug
15
comment Is there any research about cryptography on nondeterministic Turing machines?
I'm not an expert on complexity theory, but I'd expect a straight forward proof that an attack against an encryption scheme on a non deterministic turing machine can't take longer than the legitimate operation on a normal machine.
Aug
14
comment Vulnerabilities if encrypting the same data with 2 different keys
As long as the encryption used with k1 and k2 is secure Eve won't be able to learn kaes1. But there are two risks here: 1) Charlie will be able to decrypt messages sent before he joined the group 2) If Eve ever learns kaes1 she can decrypt all messages. I prefer shorter lived keys to limit the window of exposure.