The original patch was tested on the same setup:
http://mailman.nginx.org/pipermail/nginx-devel/2014-October/006151.html
Do you insist that it does not work in the current state?
___
nginx-devel mailing list
nginx-devel@nginx.org
Hello,
> Typically engines initialize themselves in bind(), if not, they are
> initialized by openssl.cnf ("default_algorithms"), why use "init = 0" in
> your openssl config and rely this openssl engine stuff to nginx?
Following the OpenSSL documentation, the application is responsible for
Typically engines initialize themselves in bind(), if not, they are initialized
by openssl.cnf ("default_algorithms"), why use "init = 0" in your openssl
config and rely this openssl engine stuff to nginx?
___
nginx-devel mailing list
Hello,
Following there is a test using the engine_pkcs11 [0] and softhsm [1].
The key is referenced in the device using PKCS#11 URI [2].
The test was based on an existing test, ssl_engine_keys.t
[0] https://github.com/OpenSC/libp11
[1] https://github.com/opendnssec/SoftHSMv2
[2]
# HG changeset patch
# User Anderson Toshiyuki Sasaki
# Date 1524670310 -7200
# Wed Apr 25 17:31:50 2018 +0200
# Node ID f916a804d526c1acb493c7c4e5c114d947e0eed1
# Parent 46c0c7ef4913011f3f1e073f9ac880b07b1a8154
SSL: Add ENGINE_init() calls before using engines.
It is
details: http://hg.nginx.org/nginx/rev/46c0c7ef4913
branches:
changeset: 7270:46c0c7ef4913
user: Ruslan Ermilov
date: Wed Apr 25 14:57:24 2018 +0300
description:
SSL: deprecated the "ssl" directive.
diffstat:
src/http/modules/ngx_http_ssl_module.c | 7 ++-
Hello!
On Tue, Apr 24, 2018 at 11:29:18AM +0300, Gena Makhomed wrote:
> On 10.04.2018 20:47, Gena Makhomed wrote:
>
> > # HG changeset patch
> > # User Gena Makhomed
> > # Date 1523382230 -10800
> > # Tue Apr 10 20:43:50 2018 +0300
> > # Node ID
Hi,
On Wed, Apr 25, 2018 at 11:10:21AM +0300, Sorin Manole wrote:
> Hello,
>
> On some systems the IP_TRANSPARENT feature is available, but the
> constant is not defined in glilb.
> Can you consider supporting this setup by defining the constant in
> nginx itself if missing from glib?
>
>
Hello,
On some systems the IP_TRANSPARENT feature is available, but the
constant is not defined in glilb.
Can you consider supporting this setup by defining the constant in
nginx itself if missing from glib?
https://unix.stackexchange.com/questions/58431/ip-transparent-missing-from-glibc-headers