Search Results for "encrypt"

...It is distributed as a single binary or as a docker container. Both HTTP and HTTPS are supported. For HTTPS, static certificates can be used as well as automated ACME (Let’s Encrypt) certificates. An optional assets server can be used to serve static files. Starting reproxy requires at least one provider defined. The rest of the parameters are strictly optional and have sane default.

...It runs NGINX as a dedicated reverse proxy embedding powerful WAF engines: ModSecurity 3, using OWASP® ModSecurity Core Rule Set (CRS) rules, and NAXSI. It uses acme.sh for Let's Encrypt and other free CA support. A lot of people are self-hosting their own cloud infrastructure (using Nextcloud, Synology, QNAP, a cloud lease server or home-made solutions...), but we can never be too much paranoid about web security for a lot of good reasons. Too much time security is left on the background, or only by using some basic - but not sufficient - options and applications are front-faced to the big bad Internet.