Sabst,
I've just uploaded REST-Client-171 to CPAN with a fix for your issue,
should be on the mirrors in a few minutes.
I don't have a PKCS12-speaking server to test my patch with - could you
let me know if the new PKCS12 options work for you?
Thanks!
-miles
On Sat Jul 17 18:22:34 2010, sabst@free.fr wrote:
Show quoted text> Hi Miles,
> Thanks for taking the time.
> I missed the second option when I read the code...
> This second option may interfer with your processing (PEM parameters
> still have
> to be passed) but this is worth a try!
> I'd rather not change your code/create my own code branch.
> The "bug" can be closed even if I still think native PKCS12 support
> should be
> there.
> Stéphane.
>
> Miles Crawford via RT a écrit :
>
> <URL:
https://rt.cpan.org/Ticket/Display.html?id=59415 >
>
> You have a couple options, I think:
>
> One: You can use SSL utilities to convert a PKCS12 certificate into
> x509 cert/key pairs and use the API as is.
>
> Two: Looks like just by setting the right environment variables,
> Crypt::SSLeay will pick up your PKCS12 cert:
>
http://search.cpan.org/~dland/Crypt-SSLeay-
> 0.57/SSLeay.pm#PKCS12_support This is the same method REST::Client
> uses for X509, you'll just have
> to do it manually for PKCS12
>
> I may add PKCS12 support via the same %ENV method at some point, but
> I
> think for now you can workaround pretty easily.
>
> -miles
>
> On Thu, Jul 15, 2010 at 8:50 AM, Sabst via RT <bug-REST-
> Client@rt.cpan.org> wrote:
>
>
> Thu Jul 15 11:50:05 2010: Request 59415 was acted upon.
> Transaction: Ticket created by sabst@free.fr Queue:
> REST-Client
> Subject: REST-client/X509 API
> Broken in: (no value)
> Severity: (no value)
> Owner: Nobody
> Requestors: sabst@free.fr Status: new
> Ticket <URL:
https://rt.cpan.org/Ticket/Display.html?id=59415
> >
>
>
> Hi,
> Is there a plan to support PKCS12 certificates (apparently
> supported by
> Crypt-SSLeay)?
> Browser or other HTTPS clients tend to use that approach.
>
> How do you set the passphrase by program? Through stdin??
>
> Thanks for your answers,
> Stephane.
>
>
>
>
>
>
>