[openssl-dev] openssl 1.0.2 20160816 snap

2016-08-15 Thread The Doctor
This error showed up /usr/local/bin/clang38 -I.. -I../.. -I../modes -I../asn1 -I../evp -I../../include -fPIC -DOPENSSL_PIC -DZLIB_SHARED -DZLIB -DOPENSSL_THREADS -pthread -D_THREAD_SAFE -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -DL_ENDIAN -O3 -Wall -DOPENSSL_EXPERIMENTAL_JPAKE -DOPENSSL_EXPERIME

Re: [openssl-dev] Partially- vs. full- reduced inputs to ecp_nistz256_neg

2016-08-15 Thread Andy Polyakov
>> No, it subtraction subroutine uses *borrow* to determine if modulus is >> to be added. I.e. (a >= b) ? (a - b) : (P - (b - a)). If both a and b >> are less than P, then result is less than P. > > Consider the case where a > P and a >= b and b is very small (e.g. 1). > For example, a == P + 2 an

Re: [openssl-dev] Partially- vs. full- reduced inputs to ecp_nistz256_neg

2016-08-15 Thread Brian Smith
Andy Polyakov wrote: > No, it subtraction subroutine uses *borrow* to determine if modulus is > to be added. I.e. (a >= b) ? (a - b) : (P - (b - a)). If both a and b > are less than P, then result is less than P. Consider the case where a > P and a >= b and b is very small (e.g. 1). For example,

Re: [openssl-dev] Partially- vs. full- reduced inputs to ecp_nistz256_neg

2016-08-15 Thread Andy Polyakov
>>> Note in particular that, IIUC, ecp_nistz256_neg will never get an >>> unreduced input when applied to the the based point multiples, because >>> those are already fully reduced. But, when it is used in >>> ecp_nistz256_windowed_mul, it isn't clear whether or how the input Y >>> coordinate is fu

Re: [openssl-dev] Partially- vs. full- reduced inputs to ecp_nistz256_neg

2016-08-15 Thread Andy Polyakov
> C-callables are wrappers around inlined subroutines. The only thing they > do is load input into designated registers and call inlines, those used > in point functions. It's true for modules other than x86_64, but not x86_64 one. Sorry about confusion. -- openssl-dev mailing list To unsubscrib

Re: [openssl-dev] Partially- vs. full- reduced inputs to ecp_nistz256_neg

2016-08-15 Thread Brian Smith
Andy Polyakov wrote: >> Note in particular that, IIUC, ecp_nistz256_neg will never get an >> unreduced input when applied to the the based point multiples, because >> those are already fully reduced. But, when it is used in >> ecp_nistz256_windowed_mul, it isn't clear whether or how the input Y >>

Re: [openssl-dev] Partially- vs. full- reduced inputs to ecp_nistz256_neg

2016-08-15 Thread Andy Polyakov
> Note in particular that, IIUC, ecp_nistz256_neg will never get an > unreduced input when applied to the the based point multiples, because > those are already fully reduced. But, when it is used in > ecp_nistz256_windowed_mul, it isn't clear whether or how the input Y > coordinate is fully reduce

Re: [openssl-dev] [PATCH] crypto/ui/ui_openssl.c: let new-line through after query in Windows path.

2016-08-15 Thread Andy Polyakov
>> Originally new-line was suppressed, because double new-line was >> observed under wine. But it appears rather to be a wine bug, >> because on real Windows new-line is much needed. >> >> Reviewed-by: Richard Levitte > > Hm, this commit comment needs an explicit reference to the mentioned > bug

Re: [openssl-dev] [PATCH] crypto/ui/ui_openssl.c: let new-line through after query in Windows path.

2016-08-15 Thread David Woodhouse
On Mon, 2016-08-01 at 10:48 +0200, Andy Polyakov wrote: > Originally new-line was suppressed, because double new-line was > observed under wine. But it appears rather to be a wine bug, > because on real Windows new-line is much needed. > > Reviewed-by: Richard Levitte Hm, this commit comment nee

Re: [openssl-dev] weird linker warnings on solaris 11

2016-08-15 Thread Andy Polyakov
> the issue appears to be not in the compiler, but the newer Soalris linker (ld) > I switched back to using 12.4 compiler, issue went away BUT now the issue > surfaces > if building OpenSSL using GCC. Some examples during the test suite What I was going to comment before I've read this message wa