I checked utility 'openssl' built by my in solaris 11.1 and the default
'openssl' installed in Solaris 11.1. I noticed that my 'openssl' does NOT
have SPARC T4 engine support. This may be the reason why my 'openssl' is
much slower. Now the question is how to build 'openssl' to let it to have
On Wed, Jul 15, 2015 at 01:33:08AM +, Salz, Rich wrote:
if ASN1_TINE_set_string() avoids that limitation, despite Victor's
suggestion to never use it.
It does avoid the limitation, using only |struct tm| to hold parsed fields,
and not building a |time_t| from it. Not sure why Viktor
On Tue, 14 Jul 2015 20:35:31 +0200
Jakob Bohm jb-open...@wisemo.com wrote:
Does ASN1_TIME_set_string() support dates outside the
time_t range of the local libc?
Why do yo need time dates outside of 64-bit integer range?
Sun would explode into red giant sooner than that amount of time passes.
On 07/15/2015 01:34 PM, Philip Bellino wrote:
Hello,
We are testing our FIPS implementation which is based on openssl-1.0.2a
and openssl-fips-2.0.9.
We are executing tests on the target machine (which doesn't support
running perl scripts so we cannot run fipsalgtest.pl)
that are
One more item of note:
The code appears to be erroring out on the keyword SEED.
Looking at the source code there appears to be no provision to accept that
word, hence the parse error.
Hello,
We are testing our FIPS implementation which is based on openssl-1.0.2a and
openssl-fips-2.0.9.
On 15/07/2015 11:13, Victor Wagner wrote:
On Tue, 14 Jul 2015 20:35:31 +0200
Jakob Bohm jb-open...@wisemo.com wrote:
Does ASN1_TIME_set_string() support dates outside the
time_t range of the local libc?
Why do yo need time dates outside of 64-bit integer range?
Sun would explode into red
On Wed, Jul 15, 2015, Philip Bellino wrote:
One more item of note:
The code appears to be erroring out on the keyword SEED.
Looking at the source code there appears to be no provision to accept that
word, hence the parse error.
The seed line appears on provable prime generation
IMAP is probably based on the Telnet protocol, so the server is
expecting CRLF instead of just CR. Try running s_client with the -crlf
option.
On Wed, 2015-07-15 at 19:34 +0200, Henrie Cuijpers wrote:
Hi all,
i try to connect to the gmail imap service, but after the connection has
been set
Hi all,
i try to connect to the gmail imap service, but after the connection has
been set up the server responds to nothing. Is there a way to
investigate this further?
I use this command line:
openssl s_client -connect imap.gmail.com:993
After connection you should be able to type a
Hello,
We are testing our FIPS implementation which is based on openssl-1.0.2a and
openssl-fips-2.0.9.
We are executing tests on the target machine (which doesn't support running
perl scripts so we cannot run fipsalgtest.pl)
that are included in the openssl-fips-2.0.9/fips directory, using
Hi Daniel,
You are totally right. Google must have changed this, because i'm pretty
sure it worked before! Thanks anyway.
Henrie
Sands, Daniel schreef op 15-07-15 om 19:49:
IMAP is probably based on the Telnet protocol, so the server is
expecting CRLF instead of just CR. Try running
11 matches
Mail list logo
