I am setting up web servers for best practice TLS.
The issue is TLS 1.0 which is deprecated
I want to remove it from the available protocols and have done the usual
##
# SSL Settings
##
ssl_protocols TLSv1.1 TLSv1.2; # Dropping SSLv3, ref: POODLE
ssl_pref
Hi!
I have a particular use-case for a nginx server which is used for
downloading big files (1-3 GBs).
Services call this server and start downloading, which usually takes ~2
minutes @ 1gbps server connection and 10 concurrent clients.
Let's say I want to have a 10min timeout for this download (if
Hi Roger,
On 16-11-18 07:02, Roger Fischer wrote:
Hi Alex,
our device is unattended, not always on, and in some cases in only
semi-secured locations. Besides preventing root access, we also need to
protect against the hacking of a stolen device (or disk).
Human interaction is not practical
Hello!
On Thu, Nov 15, 2018 at 11:59:31AM -0800, Roger Fischer wrote:
> I have an NGINX instance that listens on a tunnel (and some
> other interfaces). When NGINX was restarted while the tunnel was
> down (tun device and address did not exist), NGINX failed to
> start.
>
> [emerg] 1344#1344:
Maxim Dounin Wrote:
---
> > [...]
>
> [...]
>
> Upgrade to nginx 1.15.3+, this problem is expected to be addressed by
> this commit:
>
> http://hg.nginx.org/nginx/rev/7ad0f4ace359
>
> Alternatively, you can modify (and/or disable via the OPEN
Am 2018-11-16 07:02, schrieb Roger Fischer:
Hi Alex,
our device is unattended, not always on, and in some cases in only
semi-secured locations. Besides preventing root access, we also need
to protect against the hacking of a stolen device (or disk).
Human interaction is not practical (other tha
On 11/16/18 1:29 AM, Roger Fischer wrote:
> Hello,
>
> I have an NGINX instance that listens on a tunnel (and some other
> interfaces). When NGINX was restarted while the tunnel was down (tun
> device and address did not exist), NGINX failed to start.
>
> [emerg] 1344#1344: bind() to 38.88.78
