Multiple versions of OpenSSL can, with an additional source package (the
OpenSSL FIPS module) be built by you to be 140-2 compliant. See
http://openssl.com/fips/
for more info.
From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf Of
Vikram Kamaraj - ERS, HCL Tech
Sent: Wedn
On 08/17/2016 09:10 AM, Vikram Kamaraj - ERS, HCL Tech wrote:
> Hello OpenSSL,
>
>
>
> Which version of OpenSSL is FIPS 140 compliant?
None. A more useful question to ask is "for which versions of OpenSSL
are compatible FIPS modules available?". The answer to that is
1.0.1/1.0.2 with the OpenS
I have used the following snippet (along with some others) in the e_os.h
header file:
# if defined(__ECOS)
# define __INITIAL_POINTER_SIZE 0
# define GETPID_IS_MEANINGLESS
# define NO_CHMOD
# define NO_SYSLOG
# define HAVE_LONG_LONG 1
# define HAVE_LONG_DOUBLE 1
#
Hello OpenSSL,
Which version of OpenSSL is FIPS 140 compliant?
Thanks,
Vikram K
::DISCLAIMER::
The contents of this e-mail and any attachment(s)
Hello,
First, i would like to apologize if his is not the right mailing list for my
question.
I am working on an engine implementation that should provide a
functionality for checking if certificate is valid. As far as I could
understand, an engine can have its own implementation of RSA methods,
Hi,
Best way to do is to modify e_os.h header file.
This file has to do with OS specific changes.
Something like
#ifdef ECOS
#define getpid ecos_task_id_fn
#endif
ecos_task_id_fn is a placed holder, find out actual function name to get
process ID.
GetThreadID is the function in NETWARE.
