| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| | |
Add quota restrictions options
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
avoid unlimited quota as default_quota fallback value if unlimited quota is not allowed
avoid getting/setting/displaying unlimited default quota if not allowed
implement tests for unlimited quota restrictions
Signed-off-by: Julien Veyssier <eneiluj@posteo.net>
Signed-off-by: npmbuildbot-nextcloud[bot] <npmbuildbot-nextcloud[bot]@users.noreply.github.com>
|
|/
|
|
| |
Signed-off-by: Carl Schwan <carl@carlschwan.eu>
|
|\ |
|
| |
| |
| |
| |
| |
| | |
the extra '/' breaks things and the filter wouldn't do anything anyway except making the databases job harder
Signed-off-by: Robin Appelman <robin@icewind.nl>
|
|\ \
| | |
| | |
| | |
| | | |
ecsecta/keep_pw_based_authntoken_alive_on_pwlesslogin
Keep pw based auth tokens valid when pw-less login happens
|
| | |
| | |
| | |
| | | |
Signed-off-by: Tobias Assmann <tobias.assmann@ecsec.de>
|
|\ \ \
| | | |
| | | | |
Admin Audit - Sharing: createShare - report the full path
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: szaimen <szaimen@e.mail.de>
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When Redis config is empty, use defaults.
However when a Redis cluster config is specified, the "seeds" attribute
is mandatory.
Signed-off-by: Vincent Petry <vincent@nextcloud.com>
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: John Molakvoæ (skjnldsv) <skjnldsv@protonmail.com>
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: John Molakvoæ (skjnldsv) <skjnldsv@protonmail.com>
|
|\ \ \ \
| | | | |
| | | | | |
Sanitize more functions from the encryption app
|
| |/ / /
| | | |
| | | |
| | | | |
Signed-off-by: Lukas Reschke <lukas@statuscode.ch>
|
|\ \ \ \
| |/ / /
|/| | | |
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: tobiasKaminsky <tobias@kaminsky.me>
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Daniel Kesselberg <mail@danielkesselberg.de>
|
|\ \ \ \
| | | | |
| | | | | |
Introduce ISecureRandom::CHAR_ALPHANUMERIC
|
| | |/ /
| |/| |
| | | |
| | | | |
Signed-off-by: J0WI <J0WI@users.noreply.github.com>
|
|\ \ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | | |
Signed-off-by: Maxime Besson <maxime.besson@worteks.com>
|
| | | | |
| | | | |
| | | | |
| | | | | |
Signed-off-by: Maxime Besson <maxime.besson@worteks.com>
|
| | | | |
| | | | |
| | | | |
| | | | | |
Signed-off-by: Maxime Besson <maxime.besson@worteks.com>
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Allow to get a local cloud id without going through the contacts manager
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Signed-off-by: Julius Härtl <jus@bitgrid.net>
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Signed-off-by: Julius Härtl <jus@bitgrid.net>
|
|\ \ \ \ \ \
| |/ / / / /
|/| | | | |
| | | | | |
| | | | | | |
nextcloud/bugfix/noid/also-hide-group-from-direct-match
Also hide group from direct matches
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
|\ \ \ \ \ \ |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Applies the suggested transformation mentioned in
https://www.php.net/manual/en/migration80.incompatible.php,
> The @ operator will no longer silence fatal errors (E_ERROR,
> E_CORE_ERROR, E_COMPILE_ERROR, E_USER_ERROR, E_RECOVERABLE_ERROR,
> E_PARSE). Error handlers that expect error_reporting to be 0 when
> @ is used, should be adjusted to use a mask check instead
The new code still works on PHP 7, as error_reporting() already
returns 0 when diagnostics are suppressed.
This fixes https://github.com/nextcloud/server/issues/25807 in PHP 8.0.
For PHP 7.x, https://github.com/nextcloud/server/pull/22243 suppresses
the E_NOTICE message from the second session_start() call with the error
suppression operator @, and thus those E_NOTICE messages are still
logged in PHP 8.0.
See also https://github.com/nextcloud/server/issues/25806
Signed-off-by: Chih-Hsuan Yen <yan12125@gmail.com>
|
|\ \ \ \ \ \ \ |
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Signed-off-by: HouraisanNEET <HouraisanNEET@users.noreply.github.com>
|
|\ \ \ \ \ \ \ \
| |_|/ / / / / /
|/| | | | | | |
| | | | | | | | |
nextcloud/bugfix/noid/allow-casting-query-functions
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Signed-off-by: Joas Schilling <coding@schilljs.com>
|
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Signed-off-by: Lukas Reschke <lukas@statuscode.ch>
|
| |_|_|_|/ / /
|/| | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
`dns_get_record` can return false which results in exceptions such as
the ones shown in https://github.com/nextcloud/server/issues/27870.
Signed-off-by: Lukas Reschke <lukas@statuscode.ch>
|
| |_|_|_|_|/
|/| | | | |
| | | | | |
| | | | | | |
Signed-off-by: Sanpi <sanpi@homecomputing.fr>
|
|/ / / / / |
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Ignore subdomain for soa queries
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Signed-off-by: Daniel Kesselberg <mail@danielkesselberg.de>
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
The intention obviously was to check whether $lockingCacheClass is defined, and existing class, and available. It was however checked whether the $distributedCacheClass is an existing class, which would have caused an exception already in the previous distributed cache check.
Signed-off-by: MichaIng <micha@dietpi.com>
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
nextcloud/fix/clarify-lazy-event-listener-container
Clarify that lazy event listeners are built from the server container
|
| |/ / / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Ref https://github.com/nextcloud/server/issues/27793
Signed-off-by: Christoph Wurst <christoph@winzerhof-wurst.at>
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Improve maintenance mode info
|
| | |_|/ / /
| |/| | | |
| | | | | |
| | | | | | |
Signed-off-by: szaimen <szaimen@e.mail.de>
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Throw exception if encrypting the data failed.
|
| | |/ / / /
| |/| | | |
| | | | | |
| | | | | | |
Signed-off-by: Daniel Kesselberg <mail@danielkesselberg.de>
|
|\ \ \ \ \ \ |
|
| |/ / / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Libcurl expects the value of the CURLOPT_RESOLVE configurations to be an
array of strings, those strings containing a comma delimited list of
resolved IPs for each host:port combination.
The original code here does create that array with the host:port:ip
combination, but multiple ips for a single host:port result in
additional array entries, rather than adding them to the end of the
string with a comma. Per the libcurl docs, the `CURLOPT_RESOLVE` array
entries should match the syntax `host:port:address[,address]`.
This creates a function-scoped associative array which uses `host:port`
as the key (which are supposed to be unique and this ensures that), and
the value is an array containing IP strings (ipv4 or ipv6). Once the
associative array is populated, it is then set to the CURLOPT_RESOLVE
array, imploding the ip arrays using a comma delimiter so the array
syntax matches the expected by libcurl.
Note that this reorders the "foreach ip" and "foreach port" loops.
Rather than looping over ips then ports, we now loop over ports then
ips, since ports are part of the unique host:port map, and multiple ips
can exist therein.
Signed-off-by: Aaron Ball <nullspoon@oper.io>
|