Hi SteveM,
Yes we are copycats - thanks for making it possible.
I was also amazed when I received the email very close to our final source code
review and operational testing phase.
I've used the fips_algv tests suite to have the algorithms validated (#3768)
using this lab but I cannot see
> Sorry, I was unclear. What I meant was that it's not a huge step from the XSD
> to full blown ISO 8601.
No, sorry, *I* was unclear. I think it is a huge step to go full-blown. E.g.,
all the missing fields and the 'w' duration.
--
openssl-dev mailing list
To unsubscribe:
In message
<3a1728b8c014426bb3e557832d275...@usma1ex-dag1mb1.msg.corp.akamai.com> on Tue,
6 Sep 2016 19:14:38 +, "Salz, Rich" said:
rsalz>
rsalz> > It's not a huge step to support full blown ISO 8601 (which has a few
more
rsalz> > alternatives to specify time intervals
> It's not a huge step to support full blown ISO 8601 (which has a few more
> alternatives to specify time intervals *). I like the idea.
No, it *is* a huge step. There's a reason why W3C XML schema language (XSD),
not known for being lightweight, profiled the ISO standard.
--
openssl-dev
In message
<490f88be6dcf4d5c9baa3f3b5e4c4...@usma1ex-dag1mb1.msg.corp.akamai.com> on Tue,
6 Sep 2016 17:11:01 +, "Salz, Rich" said:
rsalz> I am thinking of standardizing the syntax for dates, times, and
rsalz> durations used by the applications in the next releases, based
I am thinking of standardizing the syntax for dates, times, and durations used
by the applications in the next releases, based on
http://www.w3schools.com/xml/schema_dtypes_date.asp (with the extension that
lowercase letters can also be used).
Objects that need dates (x509 etc) will have a
Hi Andy,
Your patch DOES work fine with GCC 6.2.0 and -O, both for 32 & 64bits.
It also works fine with XLC v12.1.0.14 and -O in 64bits (was OK in 32bits).
Thanks for your help !
Regards,
Tony
Le 03/09/2016 00:42, Andy Polyakov via RT a écrit :
- GCC 6.1.0 is: KO, 64 & 32 bits:
# Failed
Thanks a lot !!!
-Original Message-
From: openssl-dev [mailto:openssl-dev-boun...@openssl.org] On Behalf Of Matt
Caswell
Sent: Tuesday, September 06, 2016 1:26 PM
To: openssl-dev@openssl.org
Subject: Re: [openssl-dev] APIs to convert a downloaded DER format CRL file to
PEM format
On
On 06/09/16 08:00, Patel, Anirudh (Anirudh) wrote:
> Now can I convert this dlCRL to PEM format? All this needs to be done
> programmatically and not by executing openssl crl commands.
Yes. Use PEM_write_bio_X509_CRL(), or PEM_write_X509_CRL():
Hi Guys,
I have a task to perform where I need to convert a downloaded CRL file which is
in DER format to PEM format. As of now I came across one API which helps me to
read the downloaded CRL file.
BIO* crlBIO = NULL;
X509_CRL* dlCRL = NULL;
bool
Thanks for the notification. Problem fixed, will be visible in a couple of
minutes.
Closing ticket
Cheers,
Richard
On Tue Sep 06 06:44:32 2016, tallev...@yahoo.com wrote:
> Hi,
> I've encountered the following error: "an error occurred while
> processing this directive" when
> opening the news
Hi,
I've encountered the following error: "an error occurred while processing this
directive" when
opening the news log. https://www.openssl.org/news/newslog.html
Thanks.
Tal.
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4672
Please log in as guest with password guest if
12 matches
Mail list logo