Configure nginx with HTTP JavaScript module using the --add-module option:
./configure --add-module=<path-to-njs>/nginx
Alternatively, you can build a dynamic version of the njs module
./configure --add-dynamic-module=<path-to-njs>/nginx
Configure nginx with HTTP JavaScript module using the --add-module option:
./configure --add-module=<path-to-njs>/nginx
Alternatively, you can build a dynamic version of the njs module
./configure --add-dynamic-module=<path-to-njs>/nginx
Create a MakeFile in the root of your git project.
This MakeFile will recursively look through all dirs for any .html file, starting at the root. It will then sign the file and create a detached signature contained in a .html.asc file.
More on ECDSA
Info on bit length and complexity
From it you may gather that using 256 bit ECDSA key should be enough for next 10-20 years.
To view your available curves
Install Kodi then...
# Navigate to System > File Manager
# Add http://fusion.tvaddons.ag
# Name it 'Fusion;
# Go to System > Add-Ons > Install From Zip
# Select 'Fusion'
# Install the Add-On-Manager
Generate from your letsencrypt certs.
HKPK (RFC7469) is a standard that tells browser to cache a certain TLS certificate’s signature, and validate that future visits use that certificate. Please read Extended Info as losing your pins may result in migraines (if you use your leaf) You can check or generate your hashes with this tool
letsencrypt renews your certificates every few months, so if you pin against your cert.pem and it changes (or you lose it), the browser will still expect to see the old one.
Thanks to: https://www.rosehosting.com/blog/install-ghost-with-nginx-on-centos-7/
Ghost is a free and open source blogging platform written in JavaScript and built on Node.js, designed to simplify the process of online publishing for individual bloggers as well as online publications.
As always, make sure your server is fully up-to-date. Also install unzip and a text editor of your choice. We will use nano:
Thanks to http://garthkerr.com/multiple-ssl-domains-on-elb-with-nginx/
If you are also (likely) handling standard requests over port 80, you do not need to enable Proxy Protocol for non-secure traffic. The HTTP traffic can remain unaffected while adding HTTPS to an existing ELB.
First, we need an ELB instance.