Hello!
On Wed, Apr 23, 2014 at 08:32:57PM +0200, Aleksandar Lazic wrote:
Hi.
Am 23-04-2014 18:19, schrieb Maxim Dounin:
Hello!
On Wed, Apr 23, 2014 at 05:34:10PM +0200, Aleksandar Lazic wrote:
Dear nginx developers.
What is necessary that you take hands on the topic 'private key
Hi.
Am 24-04-2014 10:54, schrieb Maxim Dounin:
Hello!
On Wed, Apr 23, 2014 at 08:32:57PM +0200, Aleksandar Lazic wrote:
Hi.
Am 23-04-2014 18:19, schrieb Maxim Dounin:
[snipp]
I also agree that this is a very hard task.
So the question is: why do you need it?
If you want to get a
Dear nginx developers.
What is necessary that you take hands on the topic 'private key
passphrase'?
e.g.: http://trac.nginx.org/nginx/ticket/433
[ ] donation
[ ] time
[ ] leasure
[ ] other: ..
Maybe not as much options as in apache httpd
On Wednesday 23 April 2014 17:34:10 Aleksandar Lazic wrote:
[..]
Maybe you can start again a nginx deployments survey as in 01.2013,
to see what a year later the new or old goals of the nginx community is.
http://mailman.nginx.org/pipermail/nginx/2013-January/037113.html
There is one
Hello!
On Wed, Apr 23, 2014 at 05:34:10PM +0200, Aleksandar Lazic wrote:
Dear nginx developers.
What is necessary that you take hands on the topic 'private key passphrase'?
e.g.: http://trac.nginx.org/nginx/ticket/433
[ ] donation
[ ] time
[ ] leasure
[ ] other: ..
Maybe not
Am 23-04-2014 18:06, schrieb Valentin V. Bartenev:
On Wednesday 23 April 2014 17:34:10 Aleksandar Lazic wrote:
[..]
Maybe you can start again a nginx deployments survey as in 01.2013,
to see what a year later the new or old goals of the nginx community
is.
Hi.
Am 23-04-2014 18:19, schrieb Maxim Dounin:
Hello!
On Wed, Apr 23, 2014 at 05:34:10PM +0200, Aleksandar Lazic wrote:
Dear nginx developers.
What is necessary that you take hands on the topic 'private key
passphrase'?
[snipp]
Igor explained his position on this more than once: unless
Igor and Maxim positions, I suppose, are based on the fact that, unless
using an external system to authenticate the user of a certificate, storing
both certificate + passphrase on thel same system, accessed by the same
user (the one running nginx which loads the certificate and needs to
decrypt
