20,766 reputation
32575
bio website
location
age
visits member for 3 years, 4 months
seen 2 days ago

Jul
10
comment Choosing primes in the Paillier cryptosystem
I can't understand what you are asking. What does "Give me a reference if proof for above equation complex otherwise provide a proof." mean? Also, what research have you done? Did you read the original research paper?
Jul
2
comment Password-based encrypted key storage?
@otus, RFC 5959 only uses AES in ECB mode if the plaintext is exactly 128 bits long. That is not malleable (not in any useful way that would enable related-key attacks).
Jun
26
comment RSA: Common modulus attack problem
CGFox, rather than editing your question here, it would be better to propose an edit to the answer on the other thread that adds a clarification of how to deal with a negative exponent, i.e., what it means to raise to the $s_1$ power if $s_1$ is negative.
Jun
25
comment Choose a random number that is different from a bunch of other secret numbers
@CedricMartin, the standard commutative encryption algorithms (e.g., Pohlig-Hellman) do not require a TTP to hold any keys. The prime $p$ is public and shared by everyone; each participant's exponent is secret and is their key and is generated by them and known only to them. No TTP is needed. If you have questions how to use commutative encryption in practice, I suggest reading the existing questions, then posting a new question if it's not covered by the ones that are already on this site.
Jun
25
comment Choose a random number that is different from a bunch of other secret numbers
@CedricMartin, you are aware that this scheme (from otus) doesn't require a TTP, right?
Jun
25
comment Choose a random number that is different from a bunch of other secret numbers
Very nice! Thank you for elaborating. This looks to me like the best answer I've seen.
Jun
24
comment Choose a random number that is different from a bunch of other secret numbers
(...) in the first place, and could we change that procedure? Also, you might want to post a separate question where you take a step back and look at your application's requirements (what problem you want to use this protocol to solve) and ask about how to solve that problem, without assuming this protocol is the best way to do it. I suspect there might be other very different approaches that are possible, but without knowing the application, it's hard for tell.
Jun
24
comment Choose a random number that is different from a bunch of other secret numbers
I've been thinking about this some more, and I think there are a lot of options here. Cedric, can you tell us more? Will this protocol be repeated many times (with the same secret values for the participants), and if so, what are the requirements (a different random number each time, or it's OK for them to repeat) and how many times (more than $x-n$?)? What security property does your application need for the random numbers? Is there a trusted third party? Is there a trusted dealer (a TTP who can provide initial setup/keys)? How did the participants choose their secret values (...)
Jun
24
comment Choose a random number that is different from a bunch of other secret numbers
This is not a great scheme. The problem is that any time a participant vetos a candidate random number, everyone learns what that participant's secret number was (it must have been the same as the candidate random number we were considering). See my answer for a scheme that is a bit better, because it doesn't reveal which participant vetoed the candidate.
Jun
24
comment Choose a random number that is different from a bunch of other secret numbers
Thanks, nice edit! Here's one more intereseting fact. Proving that two numbers are different can actually be done efficiently, using the proper scheme. See my answer (you use a scheme that is homomorphic for 2-DNF formulas, noticing that $C$ computes a 2-DNF formula).
Jun
23
comment Fastest random number generator
Are you looking for true random numbers, a cryptographic-strength pseudorandom number generator, or a non-cryptographic pseudorandom generator? Please edit the question to state explicitly. Also please edit the question to respond to the other questions in the comments.
Jun
23
comment What would make it impossible to deny that decryption of a package has taken place?
package? What do you mean by that? Do you mean packet?
Jun
23
comment Which concrete applications benefit from Oblivious RAM constructions?
This paper is a great find and very relevant. On the other hand, its threat model makes some assumptions that might not be realistic in practice. It requires that the server know some of the queries (a known-plaintext setting) and have a priori knowledge on some frequency statistics concerning the unencrypted emails. I find it hard to tell whether their attacks will be realistic in the real world or not.
Jun
23
comment how to truncate a PRF on n bits to PRF on t bits where t < n?
Better, in what way? The construction Boneh provides is a perfectly reasonable choice. Unless you can define in what objective metric/criteria you would use to define "better", I don't think this question is well-defined.
Jun
23
comment Cryptography: Oblivious Transfer with at most one transfer?
I am finding this question hard to follow. What do you mean by a "transfer method"? What is $Sc$? Do you mean $s_c$? What counts as bits transferred to Bob? Can they invoke $F$ as many times as they want? Who provides the inputs to $F$ (does $x$ come from Alice and $y$ from Bob)? Are we guaranteed that $p,q$ are chosen randomly subject to the condition that $p \oplus q = x \times y$? Please edit the question to make the problem statement clearer.
Jun
23
comment How to prove NIZK proof of knowledge?
A standard way to prove that your protocol is a NIZK proof of knowledge is to show that a suitable variant is an (interactive) ZK proof of knowledge, then apply the Fiat-Shamir heuristic to it, and use the result.
Jun
21
comment Pseudo Random Generator with fixed Hamming Weight
Use the output of a crypto-quality PRG as your seed. Done. Yes, it'll be secure if the PRG is secure.
Jun
21
comment Pseudo Random Generator with fixed Hamming Weight
As it stands this question does not meet my quality expectations for this site. In the future please explain in greater detail what you want (e.g., what your specific requirements are), explain the context/motivation, do some research on your own, and show us what research you have done and what you have tried and where you got stuck. And pick just one question: a block cipher is very different from a PRG. P.S. What you want is obviously impossible if the length of the output is equal to the length of the input, as in your example.
Jun
20
comment Public and private key lengths
Thanks, BENZ.404! No need to acknowledge me or worry about my comment; I'll be happy to delete it once it no longer makes sense. For padding, normally we'd expect the library to do whatever is needed to make key generation secure. (For what it's worth, no padding is needed during RSA key generation, and depending upon how the private key is represented, it will often be of different length than the public key.)
Jun
20
comment Could scrypt salts contribute to entropy if passwords & salts are only stored in human memory?
@Gracchus, I'm going to give you some advice that might sound nasty, but I mean it in the best possible way: I don't think you should be designing cryptocurrency wallet software at this stage. This crypto stuff is subtle, and if you get it wrong, people could lose money. This kind of approach to design of cryptocurrency software is the sort of thing that causes people to lose money. It's exactly this sort of "let's just throw together some code and hope it works" that has caused multiple Bitcoin exchanges to lose lots of money. (For instance, there's a reason why we use a salt.)