[cryptography] Javascript scrypt performance comparison

coderman coderman at gmail.com
Mon May 11 01:19:22 EDT 2015


On 5/9/15, Krisztián Pintér <pinterkr at gmail.com> wrote:
> ...
> there is another option, using a random permutation on the memory
> addresses. a permutation destroys all information except equality
> (accessing the same address twice). however, you need to apply the
> same permutation to the initial writing phase, which leaks information
> about the permutation itself. again, it provides some protection, but
> not all, and comes with some extra cost.

thank you Krisztián,
 application of a permutation itself leaking information highlights
the problem with counter-measures leaking sensitive information. (and
in turn the side-channel "solution" not an easy fix after all...)

best regards,


More information about the cryptography mailing list