On Sun, Feb 21, 2016 at 11:23:02AM +0200, Thierry wrote:
Hi there,
> After I have executed the curl command, it seems that I have an answer
> from my Apache2 back end server (apache2.conf)
> Yes I do see the "Public-Key-Pins:" line... And yes I do have the
> content that I expect.
That's
Dear sir,
After I have executed the curl command, it seems that I have an answer
from my Apache2 back end server (apache2.conf)
Yes I do see the "Public-Key-Pins:" line... And yes I do have the
content that I expect.
Public-Key-Pins:
On Sun, Feb 21, 2016 at 10:22:31AM +0200, Thierry wrote:
Hi there,
> Thx for your help, but I still do have the same problem.
>
> Public Key Pinning (HPKP) No
>
> I don't know what to do anymore ...
curl -I https://your-server/your-test-url
Every line in that response comes from your
Dear Andreas,
Thx for your help, but I still do have the same problem.
Public Key Pinning (HPKP) No
I don't know what to do anymore ...
Thierry
Le samedi 20 février 2016 à 13:10:16, vous écriviez :
> Thierry:
>> Nginx: front end - reverse proxy
>> Apache2: Back end - web server
>
Thierry:
Nginx: front end - reverse proxy
Apache2: Back end - web server
hpkp is an header served to the client as response to an https request
I would add the Public-Key-Pins on the instance terminating the HTTPS request.
without rproxy I have this in /etc/nginx/sites-enabled/example.org
Dear all,
I have installed few weeks ago the couple Nginx/Apache2.
Nginx: front end - reverse proxy
Apache2: Back end - web server
Things are working smoothly ... But I am a bit lost concerning the
config of the Key pinning.
WhentestingmySSL config through the web
