-
Notifications
You must be signed in to change notification settings - Fork 463
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deterministic ECDSA - RFC6979 #441
Comments
Yeah, it'd be a useful feature to support. If it can wait a week or two, I can find some time to work on it... the RFC is quite hard to follow but at the core it's only really a couple of chained HMAC operations, if memory serves, and there are a load of test vectors. |
No problem, it can wait a month (or two). |
OK, pretty sure I can find the time to do this, then 😄 |
Hi, |
Hi @danzadok! Sorry, some stuff came up at the end of last year and I wasn't able to work on it. I've read through all the details in the RFC and I'm working on it now :) |
Thanks a lot.
Please let me know when done.
I will be your beta :)
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon>
Virus-free.
www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
…On Mon, Dec 31, 2018 at 6:12 PM Russ Williams ***@***.***> wrote:
Hi @danzadok <https://github.com/danzadok>!
Sorry, some stuff came up at the end of last year and I wasn't able to
work on it. I've read through all the details in the RFC and I'm working on
it now :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#441 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AYXLb7kXW_M7UEp2v8QdPjUY3acZFF6wks5u-jdegaJpZM4XFwAK>
.
--
:) Danny Zadok
|
Hi
Any news about that?
Danny
…On Mon, Dec 31, 2018, 10:17 PM Danny Zadok ***@***.*** wrote:
Thanks a lot.
Please let me know when done.
I will be your beta :)
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon> Virus-free.
www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link>
<#m_983535513776717579_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
On Mon, Dec 31, 2018 at 6:12 PM Russ Williams ***@***.***>
wrote:
> Hi @danzadok <https://github.com/danzadok>!
>
> Sorry, some stuff came up at the end of last year and I wasn't able to
> work on it. I've read through all the details in the RFC and I'm working on
> it now :)
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#441 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AYXLb7kXW_M7UEp2v8QdPjUY3acZFF6wks5u-jdegaJpZM4XFwAK>
> .
>
--
:) Danny Zadok
|
Hi |
Sorry, I've been really short on time recently :( It's still not working correctly, I need to dig into the results of the hash chain and check that it's coming up with the correct results/keys. |
Deterministic signatures should be added in future versions of Libtomcrypt, which is used by CryptX. Ticket link: libtom/libtomcrypt#441
Hey, any news? Is anyone working on this? |
This seems stalled? |
It would be nice to support deterministic ecc signatures - see https://tools.ietf.org/html/rfc6979
It is related only to
ecc_sign_hash_ex
as the verification works as usual.It can be done without any API change, simply when
prng
parametr ofecc_sign_hash_ex
is passedNULL
then we will not throw an error but create the deterministic signature as described in RFC6979.Any takers?
Cc: @rmw42 - what do you think? IMO you have pretty impressive ECDSA-related traction during last few weeks 😄
The text was updated successfully, but these errors were encountered: