second isogeny [ARCHIVE] / is on Nostr

⚠️ This account is not associated with a real person. It's an archival account for mailing list messages.
🗓️ Active from 2014-08-10 to 2014-08-10
💬 Posted a total of 1 messages
📚 Participated in the following categories:
🔇 Please do not DM this user as it's used for archive purposes only.

Last Notes

2023-06-07 15:25:08

- reply

📅 Original date posted:2014-08-09
📝 Original message:> Does anyone see any concerns when it comes to security of the proposed
> change?
Yes. This proposal is less secure.
It is incompatible in theory with existing implementations of the
specification. The incompatibility is also a potentially a security
problem because it may cause users to believe a key is worthless when
it is not or to lose funds when they are unable to spend them.
It is also an untimely proposal and would be inconsiderate other parties
who have done the work to produce correct and compatible implementations.
> In case I_L >= n assign I_L := I_L mod n.
This will make the selection of private keys uneven.
The unevenness is small and it is unlikely to very matter much but it
is objectively less secure. Future advances in cryptography may make
the distinction more important. The change would eliminate any hope of
the specification ever having provable security equal to random keys.
The bignum modulo operation also requires complex additional logic and is
just as likely to remain untested in implementations, though unit-testing
can test these cases by replacing the hash function.
Because of layering no suitable modulo may be available and an incorrect
implementation could create a devastating weakness, like reflecting a
large class of keys to a small number of values. A similar error would
be unlikely for an incorrect implementation of skipping and someone who
managed to still fail would likely have failed either way.
> most of the implementations don't do the checking at all, because tjen
> it's rather hard at application level to implement skipping logic. OTOH
There are many corner cases which must be handled in cryptographic
software.
You must handle the point at infinity cases, you must handle the signature
having a value of zero (or you leak the private key), in the point
arithemetics you must handle the special case of adding colinear points.
If someone is unprepared to deal with these and many other complications
they may want to leave writing this kind of software for other people.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140809/8da85020/attachment.html>