nextcloud-server.git - Nextcloud server, a safe home for all your data: https://github.com/nextcloud/server

	Commit message (Collapse)	Author	Age	Files	Lines
*	Add "Order" to assure that no parental "Allow" can grant access	MichaIng	2019-09-26	1	-0/+2
\| \| \|	Signed-off-by: MichaIng <micha@dietpi.com>
*	Apache 2.5 will be released as 2.6	MichaIng	2019-08-19	1	-2/+2
\| \| \| \| \|	+ Ref: https://github.com/nextcloud/server/pull/16792/files#r315206147 Signed-off-by: Micha Felle <micha@dietpi.com>
*	Use syntax with cases according to official docs	MichaIng	2019-08-19	1	-12/+12
\| \| \| \| \|	+ Ref: https://github.com/nextcloud/server/pull/16792/files#r315207691 Signed-off-by: Micha Felle <micha@dietpi.com>
*	Harden config protection .htaccess	MichaIng	2019-08-19	1	-6/+15
\| \| \| \| \| \| \| \| \| \| \|	+ Set "Satisfy All" whenever available, as well on Apache 2.4+. This is required to override possible "Satisfy Any" on parent dir, which otherwise would allow direct access to data, regardless of "Require" directive. + Set "Deny from all" as well whenever available, to block access regardless of which access control directive takes priority. + Assume Apache 2.2 only, if mod_authz_core and mod_access_compat are both not available, to avoid doubled directives. In this case set "Deny from all" directive only if the providing mod_authz_host module is available. "Satisfy" is a core directive on Apache 2.2. + Update Apache version strings. Regarding the used directives/modules, Apache 2.4 and 2.5 behave the same. + Add ordering spaces to better reflect the nested directives and to match style of other .htaccess files. Fixes: #6449 (for the config directory) Signed-off-by: Micha Felle <micha@dietpi.com>
*	Only request "IndexIgnore" if mod_autoindex is loaded	Robert Scheck	2017-02-20	1	-0/+2
\| \| \| \|	Signed-off-by: Robert Scheck <robert@fedoraproject.org>
*	Reference module with `.c`	Lukas Reschke	2015-01-28	1	-2/+2
\| \| \| \|	Fixes https://github.com/owncloud/core/issues/13657
*	Make files non executable	Lukas Reschke	2014-10-24	1	-0/+0
\| \| \| \|	There is not much sense in having these files marked executable, we should avoid that.
*	if file doesn't exist, check parent folder	Bjoern Schiessle	2014-06-14	1	-0/+0
\|
*	Preventing access to the config folder	Lukas Reschke	2014-04-24	1	-0/+12
	It isn't uncommon that admins create a backup file of the config (i.e. `config.php.bak`) before performing any changes. This would allow everybody to read the backup of the configuration file which contain several secret and critical values. I don't believe this is worth a backport or getting added to the installer. It's just a nice to have. People that create public readable backups of their configuration are the one to blame, not us :-)