Found the problem!
Thanks to Selva for pointing the way.
The compiler was looking for opensslconf.h (and only this file, not any
other header files) at /usr/include/x86_64-linux-
gnu/openssl/opensslconf.h when I copied
/usr/include/openssl/opensslconf.h to that location, everything worked.
The
On Mon, 2018-10-22 at 17:52 +, Salz, Rich via openssl-users wrote:
> > Yes the macro is there, its just not being expanded by the pre-
>
> compiler.
>
> That makes no sense.
I am stumped, FYI here is the the relevant output of the precompiler
(cpp)
# 261
That's very odd. Are you *sure* the one you're looking at is the one
actually included?
Cheers,
Richard
In message <1540230631.4886.20.ca...@taygeta.com> on Mon, 22 Oct 2018 10:50:31
-0700, Skip Carter said:
> Yes the macro is there, its just not being expanded by the pre-
> compiler.
>
>
On Mon, Oct 22, 2018 at 1:51 PM Skip Carter wrote:
>
> Yes the macro is there, its just not being expanded by the pre-
> compiler.
All these tests say the same thing that you are picking up a wrong (old) header.
So do:
gcc -E your-program.c | grep opensslconf.h
Then check whether the one it
You're surely looking in the wrong header file. The compiler
is using a different one in which the macro is NOT defined.
> On Oct 22, 2018, at 1:50 PM, Skip Carter wrote:
>
> Yes the macro is there, its just not being expanded by the pre-
> compiler.
>
>
> On Mon, 2018-10-22 at 08:55 +0100,
>Yes the macro is there, its just not being expanded by the pre-
compiler.
That makes no sense.
Please look at your compiler manpages and figure out how to turn on verbose
compiler output. Something is strange in your environment.
--
openssl-users mailing list
To unsubscribe:
Yes the macro is there, its just not being expanded by the pre-
compiler.
On Mon, 2018-10-22 at 08:55 +0100, Matt Caswell wrote:
>
> On 21/10/2018 20:01, Skip Carter wrote:
>
> Does your opensslconf.h have the DEPRECATEDIN_1_2_0 macro defined in
> it?
>
> Matt
--
Skip Carter
Taygeta
On 21/10/2018 20:01, Skip Carter wrote:
> Thats what I originally thought.
>
> I experimented with manually invoking the pre-compiler (cpp) and this
> is what I get:
>
>
> DEPRECATEDIN_1_2_0(int EC_GROUP_get_curve_GF2m(const EC_GROUP *group,
>
>DEPRECATEDIN_1_2_0(int EC_GROUP_get_curve_GF2m(const EC_GROUP *group,
That is "proof" that the pre-processor doesn’t have the right -I flags. Try
running with the -v option or something.
--
openssl-users mailing list
To unsubscribe:
Thats what I originally thought.
I experimented with manually invoking the pre-compiler (cpp) and this
is what I get:
DEPRECATEDIN_1_2_0(int EC_GROUP_get_curve_GF2m(const EC_GROUP *group,
BIGNUM *p,
>And I still have the problem with those macros.
The problem is almost definitely this: the files that you are compiling (not
openssl) are picking up the wrong header files from openssl.
--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
from 0:
tar xvf openssl-1.1.1.tar.gz
cd openssl-1.1.1/
./Configure --prefix=/usr --openssldir=/usr/lib/ssl shared linux
generic64
make
sudo make install
...no errors, no complications
And I still have the problem with those macros.
I am using gcc version 6.3.0 20170516 (Debian 6.3.0-18
On 10/20/2018, 21:41, "openssl-users on behalf of Skip Carter"
wrote:
Yes, that works just fine for me too. But if I include ssl.h I have
the problem. The various DEPRECATED.. macros don't get pre-compiled
and get handed to the compiler. I think I improperly installed the
You probably do not have the headers installed into the right include path.
You should do "make install" and not cp things by hand, as you'll need the
headers and the libraries, etc.
--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
Uri,
Yes, that works just fine for me too. But if I include ssl.h I have
the problem. The various DEPRECATED.. macros don't get pre-compiled
and get handed to the compiler. I think I improperly installed the
headers.
On Sun, 2018-10-21 at 00:36 +, Blumenthal, Uri - 0553 - MITLL
wrote:
>
I'm not sure I understand what you're doing, but:
$ cat ttt.c
#include
#include
int main(void)
{
printf("OPENSSL_VERSION_NUMBER %lx\n",OPENSSL_VERSION_NUMBER);
return 0;
}
$ gcc -o ttt ttt.c -lcrypto
$ ./ttt
OPENSSL_VERSION_NUMBER 1000210f
$ gcc -o ttt -I$HOME/openssl-1.1/include ttt.c
All,
I am thinking that the DEPRECATED... macros are not expanded by the
pre-parser so the compiler sees them as a weirdly formed function and
doesn't like it.
I "installed" the header files with 'cp' was there a make command that
I was supposed to use ?
On Fri, 2018-10-19 at 16:54 -0700,
On Fri, 2018-10-19 at 22:54 +0100, Matt Caswell wrote:
>
>
> It looks like its not picking up the definition of the
> DEPRECATEDIN_1_2_0 macro for some reason.
>
> That macro should be defined in opensslconf.h (which is included from
> ec.h), and looks like this:
>
> /*
> * Do not deprecate
On 19/10/2018 20:03, Skip Carter wrote:
> Hello all,
>
> I recently installed from source, openssl-1.1.1 on a Debian box (like
> most distributions the Debian version is quite old and my application
> needs very recent libraries). It built and installed without warnings
>
Hello all,
I recently installed from source, openssl-1.1.1 on a Debian box (like
most distributions the Debian version is quite old and my application
needs very recent libraries). It built and installed without warnings
or errors (Thanks to all concerned in creating software that can do
:name=crlDistributionPoints, value=
Please help me with these latest errors.
Start with a less exotic ".cnf" file. These are all configuration errors,
unrelated to ed25519. Get a working RSA config file, and then switch
algorithms.
I am using a working ecdsa config file
It is a
,section=
>>> 3065065488:error:22098080:X509 V3 routines:X509V3_EXT_nconf:error in
>>> extension:crypto/x509v3/v3_conf.c:47:name=crlDistributionPoints, value=
>>>
>>> Please help me with these latest errors.
>> Start with a less exotic ".cnf" file.
routines:do_ext_nconf:invalid extension
string:crypto/x509v3/v3_conf.c:93:name=crlDistributionPoints,section=
3065065488:error:22098080:X509 V3 routines:X509V3_EXT_nconf:error in
extension:crypto/x509v3/v3_conf.c:47:name=crlDistributionPoints, value=
Please help me with these latest errors.
Start with a less exotic
do_ext_nconf:invalid extension
> string:crypto/x509v3/v3_conf.c:93:name=crlDistributionPoints,section=
> 3065065488:error:22098080:X509 V3 routines:X509V3_EXT_nconf:error in
> extension:crypto/x509v3/v3_conf.c:47:name=crlDistributionPoints, value=
>
> Please help me with these latest
69:X509 V3 routines:do_ext_nconf:invalid
extension
string:crypto/x509v3/v3_conf.c:93:name=crlDistributionPoints,section=
3065065488:error:22098080:X509 V3 routines:X509V3_EXT_nconf:error in
extension:crypto/x509v3/v3_conf.c:47:name=crlDistributionPoints, value=
Please help me with these latest error
Thanks for the response Matt. The SSL 3 switch was one of many that were
tried just for the sake of testing. I tried a few other switches, but am
getting the same results.
I did a tcpdump of the attempted connection, and you can see that the
initial connection is established, but the connection
On 11/10/17 03:57, Paul Greene wrote:
> [root@hostname ~]# wget https://domain.name.com:8443
> --secure-protocol=SSLv3 --debug
> DEBUG output created by Wget 1.14 on linux-gnu.
The "--secure-protocol=SSLv3" bit looks suspect. According to the wget
man page this forces only SSLv3 to be
the connectivity tests, these are the errors I'm getting - you
can see the commands run, the output that comes back (hostname and ip
address are obfuscated)
Any suggestions?
PG
[root@hostname ~]# wget https://domain.name.com:8443
--secure-protocol=SSLv3 --debug
DEBUG output created by Wget 1.14 on linux-gnu
On 09/15/2017 05:35 PM, security veteran wrote:
Hi All:
I was using the fipsalgtest.pl utility for running tests with some input
vectors.
Somehow I ran into the following errors:
Any suggestions will be greatly appreciated.
Thanks.
The format of the test vectors changes constantly so
Hi All:
I was using the fipsalgtest.pl utility for running tests with some input
vectors.
Somehow I ran into the following errors:
Any suggestions will be greatly appreciated.
Thanks.
*Running ECDSA2 tests*
DEBUG: KeyPair, Pass=240, Fail=0
ERROR: PKV mismatch:
&qu
/[ Further below I quote my first two messages including my original
questions and tentative code,//
// since Cc'ing to openssl-users did not work when I tried first. In
this way I hope to get further, //
// more detailed responses by people with specific experience on the
issues I mentioned,//
//
Here is the URL for the paper fromusenix:
https://www.usenix.org/system/files/conference/usenixsecurity12/sec12-final228.pdf
I would like to find a more recent work as well.
On 09/01/2017 06:32 PM, Salz, Rich via openssl-users wrote:
FWIW, there’s a ‘libtls’ library from the libre folks that
FWIW, there’s a ‘libtls’ library from the libre folks that might be worth
looking at.
If you come up with useful snippets we can start by posting them to the wiki,
for example
--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
In message <20161108.083722.982336643109774878.levi...@openssl.org> on Tue, 08
Nov 2016 08:37:22 +0100 (CET), Richard Levitte said:
levitte> In message
on Mon, 7
Nov 2016 21:50:13 +0300, Dmitry Belyavsky
In message
on Mon, 7 Nov 2016 21:50:13 +0300, Dmitry Belyavsky said:
beldmit> Hello Rich,
beldmit>
beldmit> On Mon, Nov 7, 2016 at 8:34 PM, Salz, Rich wrote:
beldmit>
beldmit> > I
Hello Rich,
On Mon, Nov 7, 2016 at 8:34 PM, Salz, Rich wrote:
> > I can find no evidence of "excessive bounces .." so I am just asking
> here, is
> > this a standard clean up of the ML or have you really received excessive
> > bounces from my email address ?
>
> The latter.
>
Hi all,
Same here. I got the message but I see no evidence of issues in this email
account.
I changed my password just in case anyway.
Thanks!
Sent from my mobile
> On Nov 7, 2016, at 12:40 PM, debbie10t wrote:
>
>
>
> On 07/11/16 17:34, Salz, Rich wrote:
>>> I can
On 07/11/16 17:34, Salz, Rich wrote:
I can find no evidence of "excessive bounces .." so I am just asking here, is
this a standard clean up of the ML or have you really received excessive
bounces from my email address ?
The latter.
We have seen some more reports of this recently, and are
> I can find no evidence of "excessive bounces .." so I am just asking here, is
> this a standard clean up of the ML or have you really received excessive
> bounces from my email address ?
The latter.
We have seen some more reports of this recently, and are increasing the logging
to determine
Hi,
today I received an email from openssl-users-requ...@openssl.org
Your membership in the mailing list openssl-users has been disabled
due to excessive bounces ..
I can find no evidence of "excessive bounces .." so I am just asking
here, is this a standard clean up of the ML or have you
Using openssl 1.0.2h with FIPS , we get the following two errors intermittently
2D07107B:FIPS routines:FIPS_drbg_generate:in error state
error code: 0x2d071086 fips_drbg_lib.c line 391. (FIPS Self test failed,
DRBG)
This hits the application midway. After having established a TLS session
c5 no-ec2m no-gost no-srp enable-deprecated shared linux-x86_64
>
> produces errors, including
>
> crypto/evp/e_idea.c: In function 'idea_ecb_cipher':
> crypto/evp/e_idea.c:85: warning: implicit declaration of function
> 'idea_ecb_encrypt'
>
> That seems to be caused by 0
On 27/06/16 00:00, Carl Byington wrote:
>
> Do you want comments like this on this -users list, or the -dev list?
Bug reports should either be raised as an issue in github
(https://github.com/openssl/openssl/issues) or sent to r...@openssl.org.
Matt
signature.asc
Description: OpenPGP
no-srp enable-deprecated shared linux-x86_64
produces errors, including
crypto/evp/e_idea.c: In function 'idea_ecb_cipher':
crypto/evp/e_idea.c:85: warning: implicit declaration of function
'idea_ecb_encrypt'
That seems to be caused by 0x00101000L rather than 0x1010L testing
the api level.
grep
This is happening with all Linux distributions in OpenStack cloud instances
where OpenStack has been installed via Packstack on Centos 7 in a VMware
virtual machine. There don't seem to be any references to problems of this
nature on the forums.
$ sudo wget
with the output of the
> ???openssl verify??? command.
>
> This is output I get while verifying three certificates in a chain:
>
> minfrin@localhost:~$ openssl verify -issuer_checks -trusted root-ca.crt
> -untrusted intermediate.crt cert.crt
> Is there a way to suppress these spurious mes
lookup:subject issuer mismatch
[stuff]
error 29 at 0 depth lookup:subject issuer mismatch
OK
In theory the command just told me everything is ok. In practise, that command
told the person running the script that 4 separate errors are present, which
obviously in this case is not the case.
Is there a way
On 12/04/16 09:45, Chris Puttick wrote:
> Hi
>
> Our schools filtering product utilises OpenSSL with Squid; we're seeing
> issues connecting to some sites which seem OpenSSL related. Two sites with
> known issues are:
>
> https://www.spellanywhere.co.uk/
>
> https://www.mymaths.co.uk/
>
>
Hi
Our schools filtering product utilises OpenSSL with Squid; we're seeing issues
connecting to some sites which seem OpenSSL related. Two sites with known
issues are:
https://www.spellanywhere.co.uk/
https://www.mymaths.co.uk/
Connecting to either of these Squid returns the error:
(71)
On 2016-04-07 01:18, Matěj Cepl wrote:
On 2016-04-06, 12:16 GMT, Tomasz Chmielewski wrote:
error: File not found by glob:
/root/rpmbuild/BUILDROOT/openssl-1.0.2g-1.x86_64/usr/lib/*.so*
This is something really really weird. x86_64 package should
never ever write anything to /usr/lib/ , but
On 2016-04-06, 12:16 GMT, Tomasz Chmielewski wrote:
> error: File not found by glob:
> /root/rpmbuild/BUILDROOT/openssl-1.0.2g-1.x86_64/usr/lib/*.so*
This is something really really weird. x86_64 package should
never ever write anything to /usr/lib/ , but only to /usr/lib64.
You have to have
.x86_64/usr/share/doc/openssl-1.0.2g
+ exit 0
RPM build errors:
File not found by glob:
/root/rpmbuild/BUILDROOT/openssl-1.0.2g-1.x86_64/usr/lib/*.so*
Tomasz Chmielewski
http://wpkg.org
--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
>
> Hi Team,
>
> I am trying to build 'openssl-1.0.2f' on my Ubuntu 14.04 and I end up
> seeing the "
> Error: no such instruction: `vpclmulqdq $0,%xmm6,%xmm14,%xmm0'" errors on
> my machine(Please see the complete error at the end of this mail.).
&
On 11/02/16 01:03, Alex Chen wrote:
> I tried to build openssl 1.0.2f on MacOS with the following
> configuration options "Configure no-bf" but it failed because there is
> no header file blowfish.h in include/openssl directory.
> This does not happen in 1.0.2d where include/openssl/blowfish.h
wisemo.com
Transformervej 29, 2860 Søborg, Denmark. Direct +45 31 13 16 10
This public discussion message is non-binding and may contain errors.
WiseMo - Remote Service Management for PCs, Phones and Embedded
--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
IO, Partner, WiseMo A/S. https://www.wisemo.com
> Transformervej 29, 2860 Søborg, Denmark. Direct +45 31 13 16 10
> This public discussion message is non-binding and may contain errors.
> WiseMo - Remote Service Management for PCs, Phones and Embedded
>
>
> --
> openssl-users mailin
I checked the libcrypto.so which was built right before this, and was able
to find these symbols. Still not sure why these errors showed up.
Any suggestions and possible solutions are greatly appreciated.
On Wed, Feb 10, 2016 at 5:34 PM, cloud force <cloud.force...@gmail.com>
wrote:
&g
Yes, I did. It still failed. I manually made the symbolic links and the
compilation completed without problem.
But this should have been taken care of by Configure, should it not?
Alex
On 2/11/16, 1:07 AM, "openssl-users on behalf of Matt Caswell"
Anyone saw these errors before?
On Wed, Feb 10, 2016 at 5:34 PM, cloud force <cloud.force...@gmail.com>
wrote:
> Hi All:
>
> I tried to build a FIPS capable OpenSSL Ubuntu package (using the Ubuntu
> 12.04 debian meta file).
>
> The Ubuntu package uses Configure for con
Hi,
I built the FIPS capable OpenSSL library on Ubuntu 12.04.
When I run the command "OPENSSL_FIPS=1 openssl ciphers", I saw the
following error:
140073969415840:error:2D06B06F:FIPS
routines:FIPS_check_incore_fingerprint:fingerprint
does not match:fips.c:232:
I tried few other openssl commands
I tried to build openssl 1.0.2f on MacOS with the following configuration
options "Configure no-bf" but it failed because there is no header file
blowfish.h in include/openssl directory.
This does not happen in 1.0.2d where include/openssl/blowfish.h is a
symbolic link to
Do an initial config to get the symlinks copied, then do your 'real' config.
This will be fixed next time :)
--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
/lib/ssl --libdir=lib/$(DEB_HOST_MULTIARCH) fips no-idea
no-mdc2 no-rc5 zlib enable-tlsext no-ssl2 $(ARCH_CONFARGS)*
I ran into the following errors near the end of the build:
*shlib_target=; if [ -n "libcrypto.so.1.0.0 libssl.so.1.0.0" ]; then \
shlib_tar
I know the OS is a bit old, but thought I’d better upgrade OpenSSL on it in now.
To configure I used:
./Configure --prefix=/usr/local shared darwin64-x86_64-cc
Running make gives lots of errors like this:
cc -I.. -I../.. -I../modes -I../asn1 -I../evp -I../../include -fPIC
-fno-common
Hello,
(0.9.8zh, 1.0.0t, 1.0.1q, 1.0.2e)
I try to extract the tarballs and receive errors like:
tar: openssl-1.0.2e/apps/md4.c:
Cannot create symlink to `openssl-1.0.2e/../crypto/md4/md4.c':
No such file or directory
tar: Exiting with failure status due to previous errors
$ gpg
Hello,
I still have symlink errors with 4 latest uploads.
$ gpg --verify openssl-1.0.2e.tar.gz.asc openssl-1.0.2e.tar.gz
gpg: Signature made 12/03/15 12:01:26
gpg:using RSA key 0xD5E9E43F7DF9EE8C
gpg: Good signature from "Richard Levitte <rich...@levitte.org>&q
We Have the problems when linking test project with OpenSSl Libraries using
Visual Studio 2015 (RTM).
OpenSSL Version is 1.0.1j 15 Oct 2014
The errors are following:
-- Build started: Project: test, Configuration: Release Win32 --
1libeay32.lib(x86cpuid.obj) : error LNK2026: module
We Have the problems when linking test project with OpenSSl Libraries using
Visual Studio 2015 (RTM).
OpenSSL Version is 1.0.1j 15 Oct 2014
The errors are following:
-- Build started: Project: test, Configuration: Release Win32 --
1libeay32.lib(x86cpuid.obj) : error LNK2026: module
Dear Members,
In the file ssl_ openssl-1.0.1g\ssl\ssl_sess.cssl_sess.c there are some
routines that I do not understand their prototpye.
For example:
1. void SSL_CTX_sess_set_new_cb(SSL_CTX *ctx, int (*cb)(struct ssl_st
*ssl,SSL_SESSION *sess))
Return value is void. First parameter is
2015-05-09 21:47 GMT+02:00 Salz, Rich rs...@akamai.com:
After getting into building and especially configuring my own CA again I'm
nearly at the end and I've noticed some errors in the documentation I want
to report.
I like the again :)
Yeah, once upon a time I had done a comprehensive
Hello list!
After getting into building and especially configuring my own CA again
I'm nearly at the end and I've noticed some errors in the
documentation I want to report.
1) On https://www.openssl.org/docs/apps/ca.html for the -md option not
all possible values (sha256, sha384, etc.) are list
After getting into building and especially configuring my own CA again I'm
nearly at the end and I've noticed some errors in the documentation I want
to report.
I like the again :)
3) On https://www.openssl.org/docs/apps/req.html the option -subj is listed
twice with a slightly different
Hi,
I try to compile the latest openssl (1.0.2a) with Mingw-w64. The compiling part
looks fine.
If there only wasn't this nasty link problem at the end (see end of mail).
I configured it with:
./Configure mingw64 shared --prefix=/usr/local
My build environment and configuration cannot be that
May I answer my own question? Problem solved (sort of). I did not have yasm
installed.
Adding no-asm to ./Configure fixed the linker problem. Now trying to get yasm
:-)
Guido
Hi,
I try to compile the latest openssl (1.0.2a) with Mingw-w64. The compiling
part looks fine.
If there only
On Sun, Apr 12, 2015 at 12:30 PM, Yoom Nguyen y...@misoccer.us wrote:
Can the following error to be ignore?
The self tests are important, and I probably would not ignore them.
I received the following errors after ran make test:
/usr/bin/ld: cannot find -lssl
make[2
Can the following error to be ignore?
I received the following errors after ran make test:
/usr/bin/ld: cannot find -lssl
make[2]: *** [link_app.gnu] Error 1
make[2]: Leaving directory '/opt/software/openssl-1.0.2a/test'
make[2]: *** [bntest] Error 2
make[2]: Leaving directory '/opt
On Wed, Apr 01, 2015, jonetsu wrote:
Hello,
As part of development, still using the fips_hmac test code, this time on a
target unit using 1.0.1e, the following errors are shown at the console:
3069614096:error:2D088086:FIPS
routines:FIPS_selftest_x931:selftest
Hello,
As part of development, still using the fips_hmac test code, this time on a
target unit using 1.0.1e, the following errors are shown at the console:
3069614096:error:2D088086:FIPS
routines:FIPS_selftest_x931:selftest
failed:fips_rand_selftest.c:171:
3069614096:error:2D082086:FIPS
Thanks, Scott, your solution works!
Cheers
Alex
2014-11-25 17:34 GMT+01:00, Alexander Raiola alexander.rai...@gmail.com:
Dear Sirs or Madams,
I have the problem that I keep getting undefined reference errors
whenever I try to access pretty much any OpenSSL-related command. I
elaborated
Dear Sirs or Madams,
I have the problem that I keep getting undefined reference errors
whenever I try to access pretty much any OpenSSL-related command. I
elaborated on my problem in the following thread:
http://stackoverflow.com/questions/27106580/undefined-reference-to-err-load-crypto-strings
errors, e.g. to `ERR_load_crypto_strings'
Dear Sirs or Madams,
I have the problem that I keep getting undefined reference errors whenever I
try to access pretty much any OpenSSL-related command. I elaborated on my
problem in the following thread:
http://stackoverflow.com/questions/27106580
Hello,
I am attempting to use the tests provided in the 'test' directory of the
openssl-fips-2.0.7 software. I am under the impression that I should be able to
build these tests, transport them to our target hardware and execute them in
order to test our port of the openssl and fips software.
rsa_st*}’ to ‘RSA {aka rsa_st}’
../src/aerorp/model/aerorp-routing-protocol.cc:1323:3: error: control
reaches end of non-void function [-Werror=return-type]
cc1plus: all warnings being treated as errors
i need help please
--
Warmest regards and best wishes for a good health,*urs sincerely *
*mero*
On Fri, Aug 15, 2014, Kevin Pease wrote:
Hi all,
I'm trying to compile a FIPS-capable version of OpenSSL on Ubuntu 12.04,
based on the latest debian package from Ubuntu (1.0.1-4ubuntu5.16).
Please use the standard version of OpenSSL downloaded from www.openssl.org,
distro specificy
Hi all,
I'm trying to compile a FIPS-capable version of OpenSSL on Ubuntu 12.04, based
on the latest debian package from Ubuntu (1.0.1-4ubuntu5.16).
I've successfully built the openssl-fips module and it's installed, and I added
the 'fips' option to the config call. However, during testing,
Hello,
at startup after SSL_library_init I correctly call SSL_load_error_strings and
every time I have an SSL error I try to log useful data using
ERR_error_string_n.
The problem is that the output never contains error messages but only numeric
code like:
err = SSL_get_error(client-ssl, r2);
if (err != 0) {
char str[2048];
ERR_error_string_n(err, str, sizeof(str));
printf(%s, str);
ERR_print_errors_fp (stdout);
}
The first function produces:
What's the value of err (%ul)?
--
Principal Security Engineer
Akamai Technologies, Cambridge MA
IM: rs...@jabber.memailto:rs...@jabber.me Twitter: RichSalz
It is 1.
--
Marco Bambini
http://www.sqlabs.com
http://twitter.com/sqlabs
http://instagram.com/sqlabs
On 11 Aug 2014, at 16:24, Salz, Rich rs...@akamai.com wrote:
What’s the value of err (“%ul”)?
--
Principal Security Engineer
Akamai Technologies, Cambridge MA
IM: rs...@jabber.me
Try printing r2 in your original code. SSL_get_error isn't doing what you
think it does; see the docs.
--
Principal Security Engineer
Akamai Technologies, Cambridge MA
IM: rs...@jabber.memailto:rs...@jabber.me Twitter: RichSalz
-WIN64A no-asm fips
--with-fipslibdir=C:\Pradeep\Builds\openssl\1_2\out32dll
Here C:\Pradeep\Builds\openssl\1_2\out32dll contains fipscanister.lib
2) ms\do_ms.bat
3) nmake -f ms\ntdll.mak
I get the following errors
Building OpenSSL
perl util/copy.pl .\crypto\buildinf.h tmp32dll\buildinf.h
and indeed
everything appears to work on the surface despite the errors. I was just
wondering if they can be safely ignored or, better yet, if there's a way
to get rid of them if they aren't a real problem.
Chad
__
OpenSSL Project
that we should look out for
NetStatisticsGet?
--
View this message in context:
http://openssl.6102.n7.nabble.com/UAC-related-errors-on-windows-7-64-bit-with-Application-Verifier-tp48377p48402.html
Sent from the OpenSSL - User mailing list archive at Nabble.com
Application Verifier that comes along with the certification kit. When the
application is ran under this tool with luaPriv(UAC) related tests, 2 errors
related to UAC were thrown. This basically tests when the user runs
application with LUA priviliges(as standard user).
I've removed the stack trace
with the certification kit. When the
application is ran under this tool with luaPriv(UAC) related tests, 2 errors
related to UAC were thrown. This basically tests when the user runs
application with LUA priviliges(as standard user). The stack trace is as
following:
*Error 1:*
-avrf:logEntry Severity=Error StopCode
Hi,
When I build openssl source code with gcc 3.4.3 and glibc 2.2.5, I get
undefined symbol errors.
Some of those errors are as follows:
(cryptlib.o)(.text+0x18a): In function `OPENSSL_showfatal':
: undefined reference to `__vfprintf_chk'
(obj_dat.o)(.text+0xf01): In function `OBJ_obj2txt
On 01/22/2014 11:40 PM, Dave Thompson wrote:
Originally it meant the connection is terminated *abnormally* by the other
end,
as opposed to a normal/graceful FIN exchange. Windows sends RST if an
application crashes, but all Unixes I have seen do FIN, unless the
application
forces RST by setting
-us...@openssl.org]
On Behalf Of Dave Thompson
Sent: Tuesday, January 07, 2014 4:08 AM
To: openssl-users@openssl.org
Subject: RE: Open SSL errors increase in Linux compared with Solaris
1: 0.9.8a is VERY old, and contains quite a few security flaws that have been
fixed since.
Even if your
] On Behalf Of Dave Thompson
Sent: Tuesday, January 07, 2014 4:08 AM
To: openssl-users@openssl.org
Subject: RE: Open SSL errors increase in Linux compared with Solaris
1: 0.9.8a is VERY old, and contains quite a few security flaws that have been
fixed since.
Even if your application(s) can't
: owner-openssl-us...@openssl.org [mailto:owner-openssl-
us...@openssl.org] On Behalf Of Dave Thompson
Sent: Tuesday, January 07, 2014 4:08 AM
To: openssl-users@openssl.org
Subject: RE: Open SSL errors increase in Linux compared with Solaris
1: 0.9.8a is VERY old, and contains quite a few
101 - 200 of 516 matches
Mail list logo