| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
| |
Signed-off-by: MichaIng <micha@dietpi.com>
|
|
|
| |
Signed-off-by: MichaIng <micha@dietpi.com>
|
|
|
|
|
|
|
| |
+ Use Apache syntax with cases according to official docs: https://github.com/nextcloud/server/pull/16792/files#r315207691
+ Add missing whitespace for concatenating strings to variable: https://github.com/nextcloud/server/pull/16792/files#r315207520
+ Apache 2.5 will be released as 2.6: https://github.com/nextcloud/server/pull/16792/files#r315206147
Signed-off-by: Micha Felle <micha@dietpi.com>
|
|
|
|
|
| |
+ Remove unnecessary spaces from code
Co-Authored-By: Daniel Kesselberg <mail@danielkesselberg.de>
|
|
|
|
|
|
|
|
|
|
|
| |
+ 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: https://github.com/nextcloud/server/issues/6449
Signed-off-by: Micha Felle <micha@dietpi.com>
|
|
|
|
| |
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|
|
|
| |
Signed-off-by: Georg Ehrke <developer@georgehrke.com>
|
|\
| |
| | |
Update Encryption.php
|
| |
| |
| |
| | |
Signed-off-by: martink-p <47943787+martink-p@users.noreply.github.com>
|
| |
| |
| |
| | |
Signed-off-by: martink-p <47943787+martink-p@users.noreply.github.com>
|
| |
| |
| |
| |
| | |
Co-Authored-By: Daniel Kesselberg <mail@danielkesselberg.de>
Signed-off-by: martink-p <47943787+martink-p@users.noreply.github.com>
|
| |
| |
| |
| | |
Signed-off-by: martink-p <47943787+martink-p@users.noreply.github.com>
|
|\ \
| | |
| | | |
instead of upsert query, fallback to default on PSQL <= 9.4
|
| | |
| | |
| | |
| | |
| | |
| | | |
because there is no upsert yet
Signed-off-by: Arthur Schiwon <blizzz@arthur-schiwon.de>
|
|\ \ \
| |/ /
|/| | |
Fix loading of the syslog logging class
|
| | |
| | |
| | |
| | | |
Signed-off-by: Julius Härtl <jus@bitgrid.net>
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Some user backends (like the database backend) allow us to obtain a user
case insensitive. However the UID itself is case sensitive.
Example:
* create a user User1
* login as User1
- This results the data/User1 folder to be created etc
* now have some code somewhere that obtains the userFolder (from
IRootFolder) but pas in 'uSER1' as uid
- The code will check if that is a valid user. And in this case it is
since User1 and uSER1 both map to the same user
- However the the UID in the user object is used for the folder a new
folder fill be create data/uSER1
With this PR this is avoided now. Since we obtain the real UID casing in
the backend before creating the user object.
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
|
|\ \
| | |
| | | |
Correctly handle emtpy string in proxyuserpwd config
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
As documented, the default value for config value proxyuserpwd is ''.
However, that value results in the error:
"cURL error 5: Unsupported proxy syntax in '@'".
This patch handles the values of '' and null (the default in the code)
the same for config values proxyuserpwd and proxy.
Signed-off-by: Scott Shambarger <devel@shambarger.net>
|
|\ \ \
| | | |
| | | | |
Add X-Frame-Options header to .htaccess
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: J0WI <J0WI@users.noreply.github.com>
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: J0WI <J0WI@users.noreply.github.com>
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: J0WI <J0WI@users.noreply.github.com>
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This adds the events and the classes to modify the feature policy.
It also adds a default restricted feature policy.
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
|
|/ / /
| | |
| | |
| | | |
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
|
|\ \ \
| | | |
| | | | |
Bugfix: user is not allowed
|
| |\ \ \ |
|
| |\ \ \ \ |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Signed-off-by: Vitor Mattos <vitor@php.rio>
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Signed-off-by: Vitor Mattos <vitor@php.rio>
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
The created user don't has permission to connect to database. I changed the code to give permission
Signed-off-by: Vitor Mattos <vitor@php.rio>
|
| |_|_|/ /
|/| | | |
| | | | |
| | | | |
| | | | |
| | | | | |
fixes #16684
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Fix permission check on incoming federated shares
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Since federated shares have their permissions set on the node, we do not need
to check for parent share permissions. Otherwise reshares of incoming federated
have no permission variable defined and creating them will fail
Signed-off-by: Julius Härtl <jus@bitgrid.net>
|
|/ / / / /
| | | | |
| | | | |
| | | | | |
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This will be removed in a future version of Nextcloud.
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
nextcloud/tech-debt/noid/remove-unused-checkPasswordProtectedShare
Remove unused OC\Share\Share::checkPasswordProtectedShare
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Signed-off-by: Morris Jobke <hey@morrisjobke.de>
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Add proper PostLoginEvent
|
| |/ / / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This can be used by othr mechanisms to listen for this event in a lazy
fashion.
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Check the if we can actually access the storage cache for recent files
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Signed-off-by: Julius Härtl <jus@bitgrid.net>
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Signed-off-by: Julius Härtl <jus@bitgrid.net>
|
| |/ / / / /
|/| | | | |
| | | | | |
| | | | | | |
Signed-off-by: Morris Jobke <hey@morrisjobke.de>
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Split up security middleware
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
With upcoming work for the feature policy header. Splitting this in
smaller classes that just do 1 thing makes sense.
I rather have a few small classes that are tiny and do 1 thing right
(and we all understand what is going on) than have big ones.
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
|
|\ \ \ \ \ \ \
| |/ / / / / /
|/| | | | | | |
Supress warnings touch can generate
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
We already catch the result value. Having the warning being logged
explicitly doesn't help and polutes the log.
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
|
|\ \ \ \ \ \ \
| |/ / / / / /
|/| | | | | | |
Do not log all locked exceptions
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
This can happen for valid reasons (multiple users writing at the same
time) with for example the text app. Apps should properly handle it. No
reason to log it by default.
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
|