-
Notifications
You must be signed in to change notification settings - Fork 8
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
crypto-bigint #1
Comments
Cool, thanks for the heads up. I'll check it out. The first I notice is I need the ability to represent negative numbers which often affects how computations happen in groups of unknown order. |
Crypto-bigint will be a nice addition for going to no-std environments and constant-time operations. Let me know how I can help. |
What is the current status on this? |
There’s some methods missing from crypto-bigint I’m working to add then it will be quick |
Cool! Is there anything specific I could help with? |
You stub it in for now and implement what can be done |
hi, wondering if this will help with some of the no_std. trying to use this unknown_order presently and getting a std error from num-traits |
I'm actually close to having crypto-bigint almost integrated. Expect it within a week or two |
rad. super stoked on your timing. thanks |
1 similar comment
rad. super stoked on your timing. thanks |
checking in on this to see if there is anything that we can test? thanks |
Just finishing some testing. I'll push what I have. Also doing some code cleanup |
awesome stoked to try it out. |
Sorry I'm slow on this. Been traveling a ton and had zero time. Just a minor issue with serialization then I think I've got it |
Published an RC candidate `unknown_order = "0.7.0-rc0". The one issue I'm having is when you try to serialize to json or toml or anything human readable I get serializer is human readable, which requires the Have you ever seen this @tarcieri with crypto-bigint? |
hi. any updates. i noticed the repo is now with hyperledger. are you still working on it? thanks much. |
Yes I've just been really busy. Take a look and see if you can figure out why the serialize bug happens. That's the only hinderance right now. |
Addressed in #9 |
Hello!
I thought you might be interested in the
crypto-bigint
crate we've been working on as part of RustCrypto, which we are slowly beginning to use in our elliptic curve crates:We're targeting Rust 1.51+ with it and aggressively trying to leverage both const generics and
const fn
as much as is possible on stable Rust.We're targeting constant-time operation by default, with some secondary variable-time implementations explicitly called out as
*_vartime
.I'm not sure we yet provide the functionality you need, or if the approach we're using (fixed-width, stack-allocated,
no_std
friendly big integers) actually maps well to this particular problem, but I thought I'd give it a mention.If there's missing functionality you'd like to see implemented first, that's definitely something we'd like to know about:
https://github.com/RustCrypto/utils/issues/453
The text was updated successfully, but these errors were encountered: