Merge RT4241 here as these are best handled together.
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4393
Please log in as guest with password guest if prompted
--
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
On Tue, Mar 29, 2016 at 12:17 PM Emilia Käsper wrote:
> While we're at this, shouldn't we then also check the length in oct2priv?
> (And
> either reject or reduce mod n.) Afaics it accepts arbitrary BNs currently,
> which means some keys can be parsed but cannot be re-encoded?
Merged. (Please reopen if you think we should also follow up in the other
direction.)
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4393
Please log in as guest with password guest if prompted
--
openssl-dev mailing list
To unsubscribe:
While we're at this, shouldn't we then also check the length in oct2priv? (And
either reject or reduce mod n.) Afaics it accepts arbitrary BNs currently,
which means some keys can be parsed but cannot be re-encoded?
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4393
Please log in
The private key is a scalar and should be sized by the order, not the
degree.
(Unlike my other recent emails, this has nothing to do with BoringSSL
tests. :-) )
David
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4393
Please log in as guest with password guest if prompted