- Jul 29, 2016
-
-
Roeland Jago Douma authored
-
- Jul 20, 2016
-
-
Lukas Reschke authored
Fixes https://github.com/nextcloud/server/issues/50
-
- Jul 11, 2016
-
-
Roeland Jago Douma authored
* getMock is deprecated. * \PDOStatement mocking fails hard on phpunit 4.8
-
- May 20, 2016
-
-
Joas Schilling authored
* Move a-b to PSR-4 * Move c-d to PSR-4 * Move e+g to PSR-4 * Move h-l to PSR-4 * Move m-r to PSR-4 * Move s-u to PSR-4 * Move files/ to PSR-4 * Move remaining tests to PSR-4 * Remove Test\ from old autoloader
-
- May 18, 2016
-
-
Joas Schilling authored
-
- Apr 22, 2016
-
-
Roeland Jago Douma authored
-
- Apr 15, 2016
-
-
Lukas Reschke authored
First step on getting the authorisation stuff cleaned up. This is only for the login form, all other stuff is still where it is.
-
- Jan 28, 2016
-
-
Lukas Reschke authored
Allows to inject something into the default content policy. This is for example useful when you're injecting Javascript code into a view belonging to another controller and cannot modify its Content-Security-Policy itself. Note that the adjustment is only applied to applications that use AppFramework controllers. To use this from your `app.php` use `\OC::$server->getContentSecurityPolicyManager()->addDefaultPolicy($policy)`, $policy has to be of type `\OCP\AppFramework\Http\ContentSecurityPolicy`. To test this add something like the following into an `app.php` of any enabled app: ``` $manager = \OC::$server->getContentSecurityPolicyManager(); $policy = new \OCP\AppFramework\Http\ContentSecurityPolicy(false); $policy->addAllowedFrameDomain('asdf'); $policy->addAllowedScriptDomain('yolo.com'); $policy->allowInlineScript(false); $manager->addDefaultPolicy($policy); $policy = new \OCP\AppFramework\Http\ContentSecurityPolicy(false); $policy->addAllowedFontDomain('yolo.com'); $manager->addDefaultPolicy($policy); $policy = new \OCP\AppFramework\Http\ContentSecurityPolicy(false); $policy->addAllowedFrameDomain('banana.com'); $manager->addDefaultPolicy($policy); ``` If you now open the files app the policy should be: ``` Content-Security-Policy:default-src 'none';script-src yolo.com 'self' 'unsafe-eval';style-src 'self' 'unsafe-inline';img-src 'self' data: blob:;font-src yolo.com 'self';connect-src 'self';media-src 'self';frame-src asdf banana.com 'self' ```
-
- Nov 30, 2015
-
-
Lukas Reschke authored
Otherwise this leads to an endless redirection in case of a CSRF exception. Also sets user expectation right.
-
- Oct 21, 2015
-
-
Lukas Reschke authored
-
- Aug 13, 2015
-
-
Lukas Reschke authored
While BREACH requires the following three factors to be effectively exploitable we should add another mitigation: 1. Application must support HTTP compression 2. Response most reflect user-controlled input 3. Response should contain sensitive data Especially part 2 is with ownCloud not really given since user-input is usually only echoed if a CSRF token has been passed. To reduce the risk even further it is however sensible to encrypt the CSRF token with a shared secret. Since this will change on every request an attack such as BREACH is not feasible anymore against the CSRF token at least.
-
- Feb 16, 2015
-
-
Lukas Reschke authored
This changeset removes the static class `OC_Request` and moves the functions either into `IRequest` which is accessible via `\OC::$server::->getRequest()` or into a separated `TrustedDomainHelper` class for some helper methods which should not be publicly exposed. This changes only internal methods and nothing on the public API. Some public functions in `util.php` have been deprecated though in favour of the new non-static functions. Unfortunately some part of this code uses things like `__DIR__` and thus is not completely unit-testable. Where tests where possible they ahve been added though. Fixes https://github.com/owncloud/core/issues/13976 which was requested in https://github.com/owncloud/core/pull/13973#issuecomment-73492969
-
- Feb 09, 2015
-
-
Lukas Reschke authored
When `mod_unique_id` is enabled the ID generated by it will be used for logging. This allows for correlation of the Apache logs and the ownCloud logs. Testplan: - [ ] When `mod_unique_id` is enabled the request ID equals the one generated by `mod_unique_id`. - [ ] When `mod_unique_id` is not available the request ID is a 20 character long random string - [ ] The generated Id is stable over the lifespan of one request Changeset looks a little bit larger since I had to adjust every unit test using the HTTP\Request class for proper DI. Fixes https://github.com/owncloud/core/issues/13366
-
- Nov 19, 2014
-
-
Joas Schilling authored
-
- Nov 15, 2014
-
-
Lukas Reschke authored
Fixes https://github.com/owncloud/core/issues/12188 for AppFramework apps
-
- Jul 01, 2014
-
-
Morris Jobke authored
-
- May 28, 2014
-
-
Bernhard Posselt authored
-
Bernhard Posselt authored
-
- May 11, 2014
-
-
Bernhard Posselt authored
-
Bernhard Posselt authored
-
- Apr 20, 2014
-
-
Bernhard Posselt authored
-
- Feb 19, 2014
-
-
Scrutinizer Auto-Fixer authored
This patch was automatically generated as part of the following inspection: https://scrutinizer-ci.com/g/owncloud/core/inspections/cdfecc4e-a37e-4233-8025-f0d7252a8720 Enabled analysis tools: - PHP Analyzer - JSHint - PHP Copy/Paste Detector - PHP PDepend
-
- Oct 23, 2013
-
-
Thomas Tanghus authored
To avoid having to use OCP\Appframework\Http\Http in the public - and stable - API OCP\Appframework\Http is now both a class and a namespace.
-
- Oct 16, 2013
-
-
Thomas Müller authored
-
- Oct 11, 2013
-
-
Thomas Tanghus authored
-
- Oct 07, 2013
-
-
Thomas Müller authored
-
- Oct 01, 2013
-
-
Thomas Tanghus authored
-
- Aug 20, 2013
-
-
Thomas Müller authored
-
Thomas Müller authored
@PublicPage - No user logon is expected @NoAdminRequired - the login user requires no admin rights @NoCSRFRequired - the incoming request will not check for CSRF token
-
- Aug 17, 2013
-
-
Thomas Müller authored
-