Yes, it certainly is: ...
$ENV{OPENSSL_ENGINES} = top_dir("engines");
$ENV{OPENSSL_ia32cap} = '~0x200000200000000';
my $proxy = TLSProxy::Proxy->new(
\&extension_filter,
cmdstr(app(["openssl"])),
top_file("apps", "server.pem"),
1
);
plan tests => 1;
...
--
Regards,
Uri Blumenthal
On 9/18/15, 15:46 , "Richard Levitte" <rich...@levitte.org> wrote:
>In message <d221dc6b.1f354%...@ll.mit.edu> on Fri, 18 Sep 2015 19:23:09
>+0000, "Blumenthal, Uri - 0553 - MITLL" <u...@ll.mit.edu> said:
>
>uri> On 9/18/15, 15:15 , "Richard Levitte" <rich...@levitte.org> wrote:
>uri>
>uri> >Did you apply the full patch? The was a part for
>uri> >test/recipes/70-test_sslextension.t that should have had it generate
>uri> >debugging output...
>uri>
>uri> Yes I’m sure I did. And I’m as surprised as you are to not see the
>uri> expected output from at least “Message.pm”…
>
>You can look for yourself, $proxy should be assigned like this:
>
>my $proxy = TLSProxy::Proxy->new(
> \&extension_filter,
> cmdstr(app(["openssl"])),
> top_file("apps", "server.pem"),
> 1 # <========= This is what turns on the debugging output
>);
>
>--
>Richard Levitte rich...@levitte.org
> http://richard.levitte.org/
>
>"Life is a tremendous celebration - and I'm invited!"
>-- from a friend's blog, translated from Swedish
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
