Hello everyone, I want to contribute my source code to openssl, But I am in
trouble:
When building openssl with MinGW64, make test is hung up
<https://github.com/openssl/openssl/issues/24436>.
For so many days, nobody has replied to me, I value your feedback.
ly load fips code, which
caused the
> error:
>
> >/*80D1CD65667F:error:1C8000D4:Provider
> routines:SELF_TEST_post:invalid /
>
> >/state:../openssl-3.0.9/providers/fips/self_test.c:262:* /
>
>
routines:OSSL_provider_init_int:self test post
failure:../openssl-3.0.9/providers/fips/fipsprov.c:707:*
*80D1CD65667F:error:078C0105:common libcrypto
routines:provider_init:init
fail:../openssl-3.0.9/crypto/provider_core.c:932:name=fips*
*Error loading FIPS provider.*
Code for loading fips:
#include
56:8B:09:E0:18:3A:2E:D6:CC:69:05:04:E1:11
> >
> > install-status = INSTALL_SELF_TEST_KATS_RUN
> >
> > Then we removed the line "activate = 1" from fipsmodule.cnf file. After
> > this we triggered the programatically load fips code, which caused the
code, which caused the
error:
>/*80D1CD65667F:error:1C8000D4:Provider
routines:SELF_TEST_post:invalid /
>/state:../openssl-3.0.9/providers/fips/self_test.c:262:* /
>/*80D1CD65667F:error:1C8000D8:Provider /
>/routines:OSSL_provider_init_int:self test post /
>/failure:.
error:1C8000D4:Provider routines:SELF_TEST_post:invalid
*
>* state:../openssl-3.0.9/providers/fips/self_test.c:262:*
*
>* *80D1CD65667F:error:1C8000D8:Provider
*
>* routines:OSSL_provider_init_int:self test post
*
>* failure:../openssl-3.0.9/providers/fips/fipsprov.c:707:*
*
>* *80D1CD6566
Provider routines:SELF_TEST_post:invalid
> state:../openssl-3.0.9/providers/fips/self_test.c:262:*
> *80D1CD65667F:error:1C8000D8:Provider
> routines:OSSL_provider_init_int:self test post
> failure:../openssl-3.0.9/providers/fips/fipsprov.c:707:*
> *80D1CD65667F:error:078C010
routines:OSSL_provider_init_int:self test post
failure:../openssl-3.0.9/providers/fips/fipsprov.c:707:*
*80D1CD65667F:error:078C0105:common libcrypto
routines:provider_init:init
fail:../openssl-3.0.9/crypto/provider_core.c:932:name=fips*
*Error loading FIPS provider.*
Steps:
Followed the steps @
https
Hi team,
I compile OpenSSL 3.0.5 and 3.0.7 on AIX 7100, make and make install succeed,
but make test failed at very beginning when doing "00-prep_fipsmodule_cnf.t".
This is my config options: ./Configure -Wl,-R,/.uvlibs1 aix64-cc enable-fips
enable-acvp-tests no-mdc2 no-idea shared
, June 22, 2022 1:40 AM
> To: openssl-users@openssl.org
> Subject: Test failure for 1.1.1p - 10-test_bn
>
> Our test process for 10-test_bn went into a hard loop when building using
> IEEE float. This has not happened in prior tests or when using platform
> floating point (defaul
On June 21, 2022 7:40 PM, I wrote:
>Our test process for 10-test_bn went into a hard loop when building using
IEEE
>float. This has not happened in prior tests or when using platform floating
point
>(default). The situation does not occur in 3.0.4 - only 1.1.1p. At 1.1.1o
there was no
>
Our test process for 10-test_bn went into a hard loop when building using
IEEE float. This has not happened in prior tests or when using platform
floating point (default). The situation does not occur in 3.0.4 - only
1.1.1p. At 1.1.1o there was no issue. I am concerned that there are
assumptions
This is a known issue:
https://github.com/openssl/openssl/issues/18456
You can just ignore the failure for now, it will be fixed in the next
release.
Tomas
On Fri, 2022-06-10 at 14:08 +0430, Mohammad Ghasemi wrote:
> I'm trying to build openssl 3 in Windows 10 using msvc 143
>
>
On 10/06/2022 10:38, Mohammad Ghasemi wrote:
I'm trying to build openssl 3 in Windows 10 using msvc 143
Test Summary Report
---
80-test_ssl_new.t (Wstat: 256 Tests: 30 Failed: 1)
Failed test: 12
Non-zero exit status: 1
Files=243, Tests=3106,
I'm trying to build openssl 3 in Windows 10 using msvc 143
Test Summary Report
---
80-test_ssl_new.t(Wstat: 256 Tests: 30 Failed: 1)
Failed test: 12
Non-zero exit status: 1
Files=243, Tests=3106, 2594 wallclock secs (21.45 usr + 2.69 sys = 24.14
CPU)
R
"make test" and
got several failures:
Failed 1/3 subtests
# Failed test 'Revoke certificate and generate CRL: notimes'
Failed 10/15 subtests
# ExpectedResult mismatch: expected Success, got ClientFail.
# ExpectedResult mismatch: expecte
the entire API and the client apps to support GCM and stronger
> > keys. Yes, I'm aware... but I'm focusing on baby steps for now.
> >
> > To make sure I'm not breaking anything, I'm trying to add test coverage
> > (including test vectors) fo
ff uses ECB and 128 bit keys... That's a larger issue of
> redesigning the entire API and the client apps to support GCM and stronger
> keys. Yes, I'm aware... but I'm focusing on baby steps for now.
>
> To make sure I'm not breaking anything, I'm trying to
rt GCM and stronger keys. Yes, I'm
aware... but I'm focusing on baby steps for now.
To make sure I'm not breaking anything, I'm trying to add test coverage
(including test vectors) for both.
AES-ECB is easy, because it's 100% reproducible.
RSA is turning out to be tri
Hi team,
I using the openssl-1.0.2u.tar.gz and downloading from below link
https://www.openssl.org/source/old/1.0.2/openssl-1.0.2u.tar.gz
And I am observing that the *test script* is missing in*
"openssl-1.0.2u/crypto/des/t/" *location from openssl-1.0.2e.tar.gz onward.
Is there an
Maybe it's not always true?
Works fine on linux-x86_64, but seems to fail for cross compile cases,
such as:
https://github.com/mcr/openssl/runs/5616934201?check_suite_focus=true
This test case explicitely does no-dgram, yet it tries to run
my test case which hasn't been built.
http
Hi, could/should someone run sort on util/other.syms?
signature.asc
Description: PGP signature
Tomas Mraz wrote:
>> Perhaps my use of: IF[{- !$disabled{dgram} -}]
>>
>> is wrong in some way.
> You've included the bio_write_test and bio_read_test also on the bare
> PROGRAMS{noinst} assignment. You need to remove them from there.
> Interestingly the http_test is
On Fri, 2022-03-18 at 05:24 -0400, Michael Richardson wrote:
>
> Tomas Mraz wrote:
> >> Should the test *ALSO* ifdef itself out if OPENSSL_NO_DGRAM is
> >> defined?
>
> > No, that's not necessary as they won't be built at all with the
>
Tomas Mraz wrote:
>> Should the test *ALSO* ifdef itself out if OPENSSL_NO_DGRAM is
>> defined?
> No, that's not necessary as they won't be built at all with the
> build.info change above.
I didn't find this to be true. The source file stil
On Thu, 2022-03-17 at 10:17 -0400, Michael Richardson wrote:
>
> Tomas Mraz wrote:
> >> I figured out that this means that ./Configure should have
> "no-dgram"
> >> appended to it. That seems to result in OPENSSL_NO_DGRAM
> being
>
Tomas Mraz wrote:
>> I figured out that this means that ./Configure should have "no-dgram"
>> appended to it. That seems to result in OPENSSL_NO_DGRAM being
>> defined.
>>
>> My test case naturally does not compile for that.
quot;
> appended to it. That seems to result in OPENSSL_NO_DGRAM being
> defined.
>
> My test case naturally does not compile for that.
>
> Should my test case just be surrounded by #ifndef OPENSSL_NO_DGRAM
> from top
> to bottom (leaving...?), or is there something more sop
One of the run checkers is marked "no dgram".
https://github.com/mcr/openssl/runs/5563998914?check_suite_focus=true
I figured out that this means that ./Configure should have "no-dgram"
appended to it. That seems to result in OPENSSL_NO_DGRAM being defined.
My test cas
Thanks for your information.
Issue have raised:
https://github.com/openssl/openssl/issues/17681
-邮件原件-
发件人: Dr. Matthias St. Pierre [mailto:matthias.st.pie...@ncp-e.com]
发送时间: 2022年2月10日 0:03
收件人: Chenxinping ; openssl-users@openssl.org
主题: RE: How run the specific test case //答复: How to
The problem lies with the Perl script, not the C program.
The perl script generates the file 17-renegotiate.cnf.default from the template
file 17-renegotiate.cnf.in.
The environment variable “${ENV::TEST_CERTS_DIR}” should have been replaced by
Perl.
Please open an issue on GitHub, it’s easier
Thanks for the information.
NCONF_load will failed with “./test/ssl_test
./test-runs/test_ssl_new/17-renegotiate.cnf.default”. As strdup will failed in
case of “${ENV::TEST_CERTS_DIR}/*” .
Maybe the ENV should be setted before run the test case.
Error information:
# ERROR: (int) 'NCONF
Ah ok, maybe I slightly misunderstood your question. From your transcript I
infer that the testsuite ran the perl script `generate_ssl_tests.pl`, which
generated some test files an then ran the binary `ssl_test` as follows:
./test/ssl_test ./test-runs/test_ssl_new/17-renegotiate.cnf.default
If
Thanks for your information, simple test case means some specific test case.
Some error reported from some specific test case in case of “make V=1
TESTS='test_ssl_new*' test”, the error information could not help to local the
issue, So I need run and debug the specific test ca
The README file in the test directory contains a detailed explanation.
https://github.com/openssl/openssl/blob/master/test/README.md
In a nutshell, you run `make test`, passing `V=1` to turn on verbose output
and `TESTS=...` to select one or more tests:
make V=1 TESTS= test
HTH,
Matthias
The config file have some ENV variable and will result fail to load the config
file, How to run a simple test case?
Example:
./test/ssl_test ./test-runs/test_ssl_new/17-renegotiate.cnf.default
ERROR: @ test/ssl_test.c:553
ers@openssl.org
Subject: Re: undefined symbol: OSSL_provider_init when running "make test" for
OpenSSL 3.0
On 21/12/2021 15:09, Lee Staniforth wrote: > ./Configure linux-x86_64 no-shared
-m64 -fPIC -fvisibility=hidden Try dropping "-fvisibility=hidden". I can
replicate this pro
On 21/12/2021 15:09, Lee Staniforth wrote:
./Configure linux-x86_64 no-shared -m64 -fPIC -fvisibility=hidden
Try dropping "-fvisibility=hidden". I can replicate this problem when
using no-shared and -fvisibility=hidden. If I drop the
"-fvisibility=hidden" the problem goes away.
Matt
ned symbol: OSSL_provider_init when running "make test" for
OpenSSL 3.0
CAUTION: This email originated from outside of the Advantech organization. Do
not click any link or open any attachment unless you recognize the sender and
know the content is 100% safe! If you are not sure this email is
I have not compiled OpenSSL 3.0 yet, but I am pretty sure that
-fvisibility=hidden will at least break the temporary shared objects created by
the unit tests, if not everything else in OpenSSL.
Hi,
I have been building the 1.1.1 stream of OpenSSL for a while, and am now
starting to look at moving to using 3.0.
Building works fine, but testing fails (via "make test").
A number of the tests fail with undefined symbol: OSSL_provider_init:
02-test_internal_ctype.t ...
The README file in the test directory contains some hints how to troubleshoot
test failures.
Look which test is failing and rerun it in verbose mode:
make tests V=1 TESTS=testname
https://github.com/openssl/openssl/blob/master/test/README.md#test-failures
Hope that helps,
Matthias
From
I suggest working out why they failed and getting them working again.
You've broken something with your modifications, you need to understand
what's broken and why before continuing.
Paul Dale
On 14/8/21 9:56 am, Ma Zhenhua wrote:
Hi team,
I modified openssl code and make t
Hi team,
I modified openssl code and make test failed. What should I do with the failed
cases. Thx in advance.
Best regards,
Allen
\
FIPSKEY="f4556650ac31d35461610bac4ed81b1a181b2d8a43ea2854cbae22ca74560813" \
EXE_EXT= \
/opt/bw/bin/perl ./test/run_tests.pl )
00-prep_fipsmodule_cnf.t .. skipped: FIPS module config file only
supported in a fips build
Files=1, Tests=0, 1 wallclock secs ( 0.03 usr 0.01 sys + 0.89 cusr
0.04 csys = 0.97 CPU
Anyone knows why 04-test_encoder_decode_legacy.t is spinning its wheels?
--
Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca
Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist rising!
Look at Psalms 14 and 53 on Atheism https://www.empire.kre
>
>> I am trying openssl+ktls on ubuntu 20.04.
>> I have tried openssl-3.0.0-alpha8 from
>> https://www.openssl.org/source/openssl-3.0.0-alpha8.tar.gz
>> and also the current master branch from the github repo.
>> The kernels I have tried are v5.9 and v5.9.8.
>
> and also the current master branch from the github repo.
> The kernels I have tried are v5.9 and v5.9.8.
> On every combination, same group of test case could not pass.
Please can you open this as a github issue?
Thanks
Matt
>
> Test Summary Report
> ---
are v5.9 and v5.9.8.
On every combination, same group of test case could not pass.
Test Summary Report
---
70-test_key_share.t (Wstat: 1536 Tests: 22 Failed: 6)
Failed tests: 1, 4, 6-7, 13-14
Non-zero exit status: 6
70-test_sslextension.t (Wstat: 256
Greetings, I am trying openssl+ktls on ubuntu 20.04.I have tried openssl-3.0.0-alpha8 from https://www.openssl.org/source/openssl-3.0.0-alpha8.tar.gz and also the current master branch from the github repo.The kernels I have tried are v5.9 and v5.9.8.On every combination, same group of test case
On Fri, 26 Jun 2020 16:01:09 +0200,
David Harris wrote:
> Is there a standard (i.e, approved) way of using the static RTLs instead of
> the
> DLL ones? Or is my only option to modify the applink code so that it checks
> its
> environment in a different way? The problem with the dynamic RTLs is
On 26 Jun 2020 at 11:55, Matt Caswell wrote:
> No - this is not normal output. We would expect the self tests to pass
> on Windows
> > The ONLY
> > non-standard thing I do is change the /MD switch (link to the DLL
> > versions of the runtime libraries) to /MT (static link the runtimes)
> > becau
On 26/06/2020 10:45, David Harris wrote:
> Is this just the way it is? I would have thought that 50% self-test failure
> would be
> ringing alarm bells everywhere if it were common, so I can only conclude that
> there's
> something odd about my environment, or that
that, while it compiles and links cleanly, it fails about 50% of its
self tests when
I perform "nmake test". It has been this way for several releases. By "fail" I
mean
that there's a stream of "dubious..." outputs that look like this excer
ctory to get
> the tests to run at all.
Do you have any other OPENSSL relevant environment variables set, such
as OPENSSL_ENGINES or OPENSSL_CONF (if so please mention this in the
github issue)?
Matt
>
>
>
>
>
> normg@sky>gmake test
> make depend && ma
t all.
normg@sky>gmake test
make depend && make _tests
( SRCTOP=. BLDTOP=.
PERL="/export/localnew/RISC6000.AIX/perl-5.24.0/bin/perl" EXE_EXT=
/export/localnew/RISC6000.AIX/perl-5.24.0/bin/perl ./test/run_tests.pl )
01-test_abort.t ....
s to run at all.
>
>
>
>
>
> normg@sky>gmake test
> make depend && make _tests
> ( SRCTOP=. BLDTOP=.
> PERL="/export/localnew/RISC6000.AIX/perl-5.24.0/bin/perl" EXE_EXT=
> /export/localnew/RISC6000.AIX/perl-5.24.0/bin/perl ./t
All tests on AIX fail like this. Is this a known issue? What debugging
information is needed? Should I open an issue on github?
Also note I had to set LD_LIBRARY_PATH to the SSL build directory to get
the tests to run at all.
normg@sky>gmake test
make depend &&
On Wed, Apr 22, 2020 at 11:02:47AM +0200, Michael Tuexen wrote:
> > On 22. Apr 2020, at 10:38, Matt Caswell wrote:
> >
> >
> >
> > On 21/04/2020 23:45, Michael Tuexen wrote:
> >>> Looks like the failing call is here:
> >>>
> >>> if (setsockopt(sock, IPPROTO_IPV6, IPV6_V6ONLY,
> >>>
> On 22. Apr 2020, at 10:38, Matt Caswell wrote:
>
>
>
> On 21/04/2020 23:45, Michael Tuexen wrote:
>>> Looks like the failing call is here:
>>>
>>> if (setsockopt(sock, IPPROTO_IPV6, IPV6_V6ONLY,
>>> (const void *)&on, sizeof(on)) != 0) {
>> Can you provide a pointe
On Tue, Apr 21, 2020, Matt Caswell wrote:
> changes in this area. Were you successfully able to run the tests with
> previous versions of OpenSSL?
It's the first time I compiled 1.1.1 on that host. Just to check I
tried 1.1.1d and it shows the same problem, so it's not a regression.
On 21/04/2020 23:45, Michael Tuexen wrote:
>> Looks like the failing call is here:
>>
>>if (setsockopt(sock, IPPROTO_IPV6, IPV6_V6ONLY,
>> (const void *)&on, sizeof(on)) != 0) {
> Can you provide a pointer to the code?
Yes, its here:
https://github.com/openssl/ope
t using IPv6 on that host and this is the only test failure
then it can probably be safely ignored.
Matt
Not sure what the complaints are however here on the most strict POSIX
risc environment with a really strict compiler :
.
.
.
All tests successful.
Files=155, Tests=1460, 1378 wallclock se
sn't understand them when used.
>
> If you're not using IPv6 on that host and this is the only test failure
> then it can probably be safely ignored.
>
> Matt
On Tue, Apr 21, 2020 at 10:49:25PM +0100, Matt Caswell wrote:
>
> Looks like the failing call is here:
>
> if (setsockopt(sock, IPPROTO_IPV6, IPV6_V6ONLY,
>(const void *)&on, sizeof(on)) != 0) {
>
> To which we get an errno indicating "Invalid argument". So it loo
t has the relevant IPV6 macros defined (otherwise we would have
got a compilation failure) - but doesn't understand them when used.
If you're not using IPv6 on that host and this is the only test failure
then it can probably be safely ignored.
Matt
Summary: The OpenSSL 1.1.1g test suite contains at least two bugs:
TestBug#1: Test suite fails if local network has no IPv6, error message
(non-
verbose) doesn't say that's the issue. [ Testing IPv6 makes sense,
rejecting
regression tests on inadequate machines is importan
On Tue, Apr 21, 2020, Benjamin Kaduk via openssl-users wrote:
> On Tue, Apr 21, 2020 at 07:22:38PM +0200, Claus Assmann wrote:
> > ../test/recipes/80-test_ssl_old.t ..
> > Dubious, test returned 1 (wstat 256, 0x100)
> Please run again with `make V=1 TESTS=test
On Tue, Apr 21, 2020 at 07:22:38PM +0200, Claus Assmann wrote:
> Note sure whether this is already known (a search didn't bring up
> anything meaningful):
>
> ../test/recipes/80-test_ssl_old.t ..
> Dubious, test returned 1 (wstat 256, 0x100)
> Failed 1/6 s
Note sure whether this is already known (a search didn't bring up
anything meaningful):
../test/recipes/80-test_ssl_old.t ..
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/6 subtests
Test Summary Report
---
../test/recipes/80-test_ssl_
You probably already noticed, but if not…
MacOS Mojave 10.14.6, Xcode 11.3.1. Current OpenSSL master (OpenSSL 3.0 dev)
with PR 11193 applied (latest variant).
Test Summary Report
---
25-test_req.t(Wstat: 512 Tests: 15 Failed: 2)
Failed tests: 14-15
Non
On 25/09/2019 12:18, shiva kumar wrote:
> Hi,
> I'm getting error while running test case "90-test_shlibload.t" in openssl
> 1.1.1c make test.
>
> ../test/recipes/90-test_shlibload.t (Wstat: 1024 Tests: 10 Failed: 4)
> Failed tests: 2, 4, 6,
Hi,
I'm getting error while running test case "90-test_shlibload.t" in openssl
1.1.1c make test.
../test/recipes/90-test_shlibload.t (Wstat: 1024 Tests: 10 Failed: 4)
Failed tests: 2, 4, 6, 8
in file test/recipes/90-test_shlibload.t
*ok(check_atexit($fh));*
when i checked
Hello,
since we got a few bug reports by now about this issue on GitHub,
I thought it might be a good idea to spread the information a little bit:
It is a known issue that the 20-test_enc.t test fails in OpenSSL
version 1.1.1d if zlib support is enabled (see [1]).
Meanwhile, the bug has been
On Thu, 12 Sep 2019 10:31:51 +0200,
Dr. Matthias St. Pierre wrote:
>
> > > I think this is a problem with the 20-test_enc.t Test and not with
> > > OPENSSL.
> > >
> > > Can you please help me to fix the Test ?
> > >
> >
> &g
> > I think this is a problem with the 20-test_enc.t Test and not with OPENSSL.
> >
> > Can you please help me to fix the Test ?
> >
>
> Did you enable zlib by any chance? If so it could be this:
>
> https://github.com/openssl/openssl/issues/9866
>
>
On 12/09/2019 08:58, zahn wrote:
> Hello
>
> After building openssl-1.1.1d I run a Test and it failed:
>
> ../test/recipes/20-test_enc.t .. Dubious, test returned 1
> (wstat 256, 0x100)
>
> Test Summary Report
> ---
>
Hello
After building openssl-1.1.1d I run a Test and it failed:
../test/recipes/20-test_enc.t .. Dubious, test
returned 1 (wstat 256, 0x100)
Test Summary Report
---
../test/recipes/20-test_enc.t (Wstat: 256 Tests: 172
Failed: 1
On 8/7/19, 10:57 AM, "openssl-users on behalf of Matt Caswell"
wrote:
> >> ../test/recipes/15-test_ec.t (Wstat: 256 Tests: 5
Failed: 1)
> >
> > Assuming you are building with enable-ec_nistp_64_gcc_128 then the fix
On 07/08/2019 15:49, Matt Caswell wrote:
>
>
> On 07/08/2019 15:48, Blumenthal, Uri - 0553 - MITLL wrote:
>> Test Summary Report
>>
>> ---
>>
>> ../test/recipes/15-test_ec.t (Wstat: 256 Tests: 5
>> Failed: 1)
On 07/08/2019 15:48, Blumenthal, Uri - 0553 - MITLL wrote:
> Test Summary Report
>
> ---
>
> ../test/recipes/15-test_ec.t (Wstat: 256 Tests: 5 Failed:
> 1)
>
> Failed test: 2
>
> Non-zero exit status: 1
>
> Files
Test Summary Report
---
../test/recipes/15-test_ec.t (Wstat: 256 Tests: 5 Failed: 1)
Failed test: 2
Non-zero exit status: 1
Files=174, Tests=1660, 122 wallclock secs ( 1.27 usr 0.34 sys + 81.53 cusr
29.91 csys = 113.05 CPU)
Result: FAIL
Does it
Manish asked:
> There is DRBG kat test data in fips_drbg_selftest.h. (Openssl-fips-2.0.16)
> Can anyone let me know, What is the source of this constant arrays. NIST
> link or any other source will be helpful?
I'm pretty sure that the test data for the DRBG KAT (known answer test)
Hi
There is DRBG kat test data in fips_drbg_selftest.h. (Openssl-fips-2.0.16)
Can anyone let me know, What is the source of this constant arrays. NIST
link or any other source will be helpful?
Regards
Manish
On 26/06/2019 08:46, syed moulana via openssl-users wrote:
> Hi
> Is there any test application scripts bundled with openssl_1.1.1b ? If yes.
> How to compile it.
> Is it possible use that test application to verify SSL handshake ?
I think you are probably wanting to use s_ser
Hi Is there any test application scripts bundled with openssl_1.1.1b ? If yes.
How to compile it.Is it possible use that test application to verify SSL
handshake ?
Thank youSyed
Sent from Yahoo Mail on Android
;libcrypto.a", to link archive files instead of
> shared
> > files.
> > and then make executed normally
> > but when I run make test I'm getting this error.
> > why I'm getting this error ?
>
> If you want static linking why not
d "-lcrypto" to "libcrypto.a", to link archive files instead of shared
> files.
> and then make executed normally
> but when I run make test I'm getting this error.
> why I'm getting this error ?
If you want static linking why not just build with "no-sh
On 19/06/2019 11:07, shiva kumar wrote:
> Hi,
> In the OpenSSL 1.1.1b build after make test I'm getting error as follows
> /*../test/recipes/70-test_comp.t (Wstat: 35584 Tests: 0
> Failed: 0)
> Non-zero exit status: 139
> Parse errors: No p
Hi,
In the OpenSSL 1.1.1b build after make test I'm getting error as follows
*../test/recipes/70-test_comp.t (Wstat: 35584 Tests: 0
Failed: 0) Non-zero exit status: 139 Parse errors: No plan found in TAP
output../test/recipes/70-test_key_share.t (
Hi All,
I am trying to build a regression suite for the known vulnerabilities
published by OpenSSL. For some of the CVEs, I am facing issues to generate
test data.
Is there anywhere test data available for the known CVEs for re-use.
Any help would be appreciated.
--
Regards,
Girish
On 4/4/19 3:32 AM, ramakrushna mishra wrote:
> Hi,
>
> Could anyone please help me get the following information.
>
> -- How to verify that the openssl is using the assembly code ( when asm
> is enabled) instead of the c code for the algorithms ?
> -- I m observing a small degradation (2 % for
Hi,
Could anyone please help me get the following information.
-- How to verify that the openssl is using the assembly code ( when asm is
enabled) instead of the c code for the algorithms ?
-- I m observing a small degradation (2 % for 16 byte size) for des-ede3 on
openssl1.1.1 for Solaris. This
Hi
Not sure if any of the build / test process of OpenSSL utilise inbuilt KORN
Arithmetic & Test functions.
https://community.ubuntu.com/t/inbuilt-korn-arithmetic-test-functions-broken-under-windows-subsystem-for-linux/10089
<https://community.ubuntu.com/t/inbuilt-korn-arithmet
Richard Levitte wrote:
>> Running LDD on the binaries in test/* shows that they appear to link
against
>> the "system" copies of libssl and libcrypto.
>>
>> Perhaps something I'm missing is setting up LD_PRELOAD or some such so
that
&g
> On Feb 27, 2019, at 11:04 AM, Michael Richardson wrote:
>
> Running LDD on the binaries in test/* shows that they appear to link against
> the "system" copies of libssl and libcrypto.
With no environment overrides of LD_LIBRARY_PATH or similar, the test cases
in the buil
On 27/02/2019 17:04, Michael Richardson wrote:
Running LDD on the binaries in test/* shows that they appear to link against
the "system" copies of libssl and libcrypto.
Perhaps something I'm missing is setting up LD_PRELOAD or some such so that
the tests run the local copy of l
On Wed, 27 Feb 2019 17:04:09 +0100,
Michael Richardson wrote:
>
> Running LDD on the binaries in test/* shows that they appear to link against
> the "system" copies of libssl and libcrypto.
>
> Perhaps something I'm missing is setting up LD_PRELOAD or some such so
Running LDD on the binaries in test/* shows that they appear to link against
the "system" copies of libssl and libcrypto.
Perhaps something I'm missing is setting up LD_PRELOAD or some such so that
the tests run the local copy of libssl/libcrypto, but I can't find that.
Am
I'm seeing the following link failure on Solaris, both SPARC and x86_64
with 1.1.1a. 1.1.1 does not have this problem. Adding -lcrypto to the
link line makes the problem go away.
Any suggestions on how to proceed?
Norm Green
rm -f test/rsa_complex
${LDCMD:-/opt/studio12.5/bin/cc}
1 - 100 of 677 matches
Mail list logo
