On Thu, Feb 14, 2013 at 5:58 AM, Ashok C ash@gmail.com wrote:
Hi,
As part of implementing certificate expiry related alarms for my SSL
application, I would kindly require few suggestions and clarifications from
the community.
Does that include OSCP checking? On a continuous basis? The CA
Hi,
I am trying to build a shared library that statically links to a fips
enabled openssl library under Linux. When I try to build my shared library
using:
'make CC=/usr/local/ssl/fips-2.0/bin/fipsld FIPSLD_CC=gcc'
I get an error saying:
/usr/local/ssl/fips-2.0/bin/fipsld: line 137:
Hi all,
I've been experimenting with the DTLS support in OpenSSL recently and
discovered that my application was receiving garbage data when packets
were lost or reordered. Closer inspection explained why: I was only
enabling cipher suites which either used stream ciphers like RC4 or block
I tried to set the FIPS_SIG environment variable to point to the incore
script in the 'util' directory of the fips distribution. The error message
is now that my .so is not cross compiler aware.
- Roar
--
View this message in context:
Thanks Jeff,
My response inline.
On Thu, Feb 14, 2013 at 5:31 PM, Jeffrey Walton noloa...@gmail.com wrote:
On Thu, Feb 14, 2013 at 5:58 AM, Ashok C ash@gmail.com wrote:
Hi,
As part of implementing certificate expiry related alarms for my SSL
application, I would kindly require few
On Thu, 14 Feb 2013, Tom Cocagne wrote:
Thanks for the quick reply Joe. I am definitely interested in seeing your
example, I've been unable to find many DTLS examples at all and certainly
none that use an alternative transport mechanism.
Also, have you taken into account the timer for dropped
Ah, that sounds like a very sensible approach. Worst case, you have an
optimization issue that can be fixed at a later time. I like it.
Thanks Joel.
Tom
On Fri, Feb 15, 2013 at 9:43 AM, Joel Dice joel.d...@gmail.com wrote:
On Thu, 14 Feb 2013, Tom Cocagne wrote:
Thanks for the quick reply
Thanks for the clarification and pointing me to the testing docs. One
part of your reply I don't understand --
The Security Policy documents the command as ./config, not ./config no-asm
The build works without no-asm, but I don't understand how the
Security Policy does not allow ./config
Hi,
I'm new to the mailing list and didn't found, archives, internet or docs, the
answer to my question:
Is it known that the make -j gives compilations errors?
If not I can provide more details about my environments.
Best Regards,
- KA
On 02/15/2013 02:48 PM, Zeke Evans wrote:
Thanks for the clarification and pointing me to the testing docs. One
part of your reply I don't understand --
The Security Policy documents the command as ./config, not ./config
no-asm
The build works without no-asm, but I don't understand how
On Thu, 14 Feb 2013, Dr. Stephen Henson wrote:
On Thu, Feb 14, 2013, Joel Dice wrote:
Although OpenSSL seems to allow CBC-based suites with DTLS, from
what I've read a block in a CBC stream can't be properly decoded
without the prior block being available
On Fri, 15 Feb 2013, Joel Dice wrote:
On Thu, 14 Feb 2013, Dr. Stephen Henson wrote:
On Thu, Feb 14, 2013, Joel Dice wrote:
Although OpenSSL seems to allow CBC-based suites with DTLS, from
what I've read a block in a CBC stream can't be properly decoded
without the prior block being
12 matches
Mail list logo