Opened 3 years ago

Closed 3 years ago

#1315 closed enhancement (invalid)

Nginx's enforced permissions

Reported by: Mostafa Hussein Owned by:
Priority: minor Milestone:
Component: nginx-core Version: 1.13.x
Keywords: Cc:
uname -a:
nginx -V: nginx version: nginx/1.12.0
built by gcc 4.8.5 20150623 (Red Hat 4.8.5-11) (GCC)
built with OpenSSL 1.1.0f 25 May 2017
TLS SNI support enabled
configure arguments: --sbin-path=/usr/local/sbin --lock-path=/var/lock/nginx.lock --pid-path=/var/run/nginx.pid --with-openssl=../openssl --with-http_flv_module --with-http_gzip_static_module --with-http_mp4_module --with-http_realip_module --with-http_ssl_module --with-http_stub_status_module --with-http_v2_module --with-http_sub_module --add-module=../mod_security/nginx/modsecurity --add-module=../ngx_cache_purge --with-file-aio

Description

Hello,
I would like to know which part of Nginx's code is responsible for preventing or chmod the created directories by nginx when we restart it

This https://trac.nginx.org/nginx/browser/nginx/src/core/ngx_file.c#L607 should be the premission of the created folders but somehow if I changed it to 777 and then rebuild and compiled nginx the created auto created directories will be 755. I have ensured that it is not system related so i am wondering if there is something within nginx code doing this part

Change History (1)

comment:1 by Maxim Dounin, 3 years ago

Resolution: invalid
Status: newclosed

For questions, please use the support options available.

Note: See TracTickets for help on using tickets.