38 Commits (311531ecce497663960877fc536ba94deff27bc0)

Author	SHA1	Message	Date
Joas Schilling	0f06034239	Replace more vendor naming ... Signed-off-by: Joas Schilling <coding@schilljs.com>	9 years ago
Arthur Schiwon	44f3fcc187	fix internal links in security & setup warnings, resolves #1048	9 years ago
Derek	b236100619	Alters 'No Internet Connection' error message. #181	10 years ago
Vincent Petry	97f1813695	Don't reload page in case of auth errors during setup checks ... If an error occurs during setup checks, do not let the global ajax error handler reload the page.	10 years ago
Vincent Petry	fb087a0261	Use temporary htaccesstest.txt for data dir security check	10 years ago
Morris Jobke	e03d289b70	Use 6 months as SSL STS header threshold ... * this uses 6 months (6 * 30 * 24 * 60 * 60 = 15552000) * old value was half a year (365 / 2 * 24 * 60 * 60 = 15768000) * fixes #23957	10 years ago
Lukas Reschke	6ad957906e	Consistently use rel=noreferrer ... When linking to external entities we should consistently use rel=noreferrer	10 years ago
Lukas Reschke	2ca3c0d461	Adjust wording a bit ... **Before:** > Your PHP version (5.4.16) is no longer supported by PHP. We encourage you to upgrade your PHP version to take advantage of performance and security updates provided by PHP. **After:** > You are currently running PHP 5.4.0. We encourage you to upgrade your PHP version to take advantage of performance and security updates provided by the PHP Group as soon as your distribution supports it. Fixes https://github.com/owncloud/enterprise/issues/1170	10 years ago
Thomas Müller	8abdcb8085	Fix error ins source language strings ... https://www.transifex.com/owncloud-org/owncloud/translate/#en_GB/core/50786279 https://www.transifex.com/owncloud-org/owncloud/translate/#en_GB/settings-1/50555028	10 years ago
Vincent Petry	b8b77709c0	Add handler for global ajax errors	10 years ago
Lukas Reschke	5ba6148bfe	Add check for content ... The response may be a redirect which is always followed by jQuery. Thus leading to false positives depending on the server configuration (e.g. when it issues a 302) To prevent that there is also a check performed on the response content.	10 years ago
Vincent Chan	faf48e42b7	Move data protection check to javascript ... fixes #20199	10 years ago
Lukas Reschke	4d0dcd3c53	Add X-Download-Options and X-Permitted-Cross-Domain-Policies ... Two small security hardenings for our IE users and those with Adobe products. Aligns it more with https://github.com/twitter/secureheaders#secureheaders---	10 years ago
Morris Jobke	8b6b042ffd	Add config switch to disable the .well-known URL check	10 years ago
Morris Jobke	a6c7cdd75e	Show the well-known URL check as info instead of error ... * ref https://github.com/owncloud/core/pull/21562#issuecomment-170344549	10 years ago
Morris Jobke	0161928fc3	Add check for .well-known URL in the root of the webservers URL ... * fixes #20012	10 years ago
Renaud Fortier	83899a5fa1	add _blank to href	10 years ago
Lukas Reschke	4971015544	Add code integrity check ... This PR implements the base foundation of the code signing and integrity check. In this PR implemented is the signing and verification logic, as well as commands to sign single apps or the core repository. Furthermore, there is a basic implementation to display problems with the code integrity on the update screen. Code signing basically happens the following way: - There is a ownCloud Root Certificate authority stored `resources/codesigning/root.crt` (in this PR I also ship the private key which we obviously need to change before a release 😉). This certificate is not intended to be used for signing directly and only is used to sign new certificates. - Using the `integrity:sign-core` and `integrity:sign-app` commands developers can sign either the core release or a single app. The core release needs to be signed with a certificate that has a CN of `core`, apps need to be signed with a certificate that either has a CN of `core` (shipped apps!) or the AppID. - The command generates a signature.json file of the following format: ```json { "hashes": { "/filename.php": "2401fed2eea6f2c1027c482a633e8e25cd46701f811e2d2c10dc213fd95fa60e350bccbbebdccc73a042b1a2799f673fbabadc783284cc288e4f1a1eacb74e3d", "/lib/base.php": "55548cc16b457cd74241990cc9d3b72b6335f2e5f45eee95171da024087d114fcbc2effc3d5818a6d5d55f2ae960ab39fd0414d0c542b72a3b9e08eb21206dd9" }, "certificate": "-----BEGIN CERTIFICATE-----MIIBvTCCASagAwIBAgIUPvawyqJwCwYazcv7iz16TWxfeUMwDQYJKoZIhvcNAQEF\nBQAwIzEhMB8GA1UECgwYb3duQ2xvdWQgQ29kZSBTaWduaW5nIENBMB4XDTE1MTAx\nNDEzMTcxMFoXDTE2MTAxNDEzMTcxMFowEzERMA8GA1UEAwwIY29udGFjdHMwgZ8w\nDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBANoQesGdCW0L2L+a2xITYipixkScrIpB\nkX5Snu3fs45MscDb61xByjBSlFgR4QI6McoCipPw4SUr28EaExVvgPSvqUjYLGps\nfiv0Cvgquzbx/X3mUcdk9LcFo1uWGtrTfkuXSKX41PnJGTr6RQWGIBd1V52q1qbC\nJKkfzyeMeuQfAgMBAAEwDQYJKoZIhvcNAQEFBQADgYEAvF/KIhRMQ3tYTmgHWsiM\nwDMgIDb7iaHF0fS+/Nvo4PzoTO/trev6tMyjLbJ7hgdCpz/1sNzE11Cibf6V6dsz\njCE9invP368Xv0bTRObRqeSNsGogGl5ceAvR0c9BG+NRIKHcly3At3gLkS2791bC\niG+UxI/MNcWV0uJg9S63LF8=\n-----END CERTIFICATE-----", "signature": "U29tZVNpZ25lZERhdGFFeGFtcGxl" } ``` `hashes` is an array of all files in the folder with their corresponding SHA512 hashes (this is actually quite cheap to calculate), the `certificate` is the certificate used for signing. It has to be issued by the ownCloud Root Authority and it's CN needs to be permitted to perform the required action. The `signature` is then a signature of the `hashes` which can be verified using the `certificate`. Steps to do in other PRs, this is already a quite huge one: - Add nag screen in case the code check fails to ensure that administrators are aware of this. - Add code verification also to OCC upgrade and unify display code more. - Add enforced code verification to apps shipped from the appstore with a level of "official" - Add enfocrced code verification to apps shipped from the appstore that were already signed in a previous release - Add some developer documentation on how devs can request their own certificate - Check when installing ownCloud - Add support for CRLs to allow revoking certificates **Note:** The upgrade checks are only run when the instance has a defined release channel of `stable` (defined in `version.php`). If you want to test this, you need to change the channel thus and then generate the core signature: ``` ➜ master git:(add-integrity-checker) ✗ ./occ integrity:sign-core --privateKey=resources/codesigning/core.key --certificate=resources/codesigning/core.crt Successfully signed "core" ``` Then increase the version and you should see something like the following:  As you can see a failed code check will not prevent the further update. It will instead just be a notice to the admin. In a next step we will add some nag screen. For packaging stable releases this requires the following additional steps as a last action before zipping: 1. Run `./occ integrity:sign-core` once 2. Run `./occ integrity:sign-app` _for each_ app. However, this can be simply automated using a simple foreach on the apps folder.	10 years ago
Morris Jobke	b519965408	[admin] check for correct PHP memcached module	10 years ago
Roeland Jago Douma	8eefc5c4e1	Move remaining setupchecks to new fomat	11 years ago
Robin McCorkell	2579999373	Add setup check for reverse proxy header configuration	11 years ago
Roeland Jago Douma	8bde72c4bd	All setup messages are now properly types	11 years ago
Roeland Jago Douma	5d15051da4	Allow setupchecks to specify a warning level	11 years ago
Roeland Jago Douma	72ba67815e	Display warning in security & setup warnings if php version is EOL	11 years ago
Lukas Reschke	0d515de13e	Detect old NSS and OpenSSL versions ... This will detect old NSS and OpenSSL versions and show appropriate errors in the admin interface. Fixes https://github.com/owncloud/core/issues/17901	11 years ago
Lukas Reschke	eec8d776b7	Align recommended settings ... This aligns the recommended setting with the max-age of `15768000` as described in our documentation. Furthermore it fixes some logical problems with the code, unit tests has been added as well. Fixes https://github.com/owncloud/core/issues/16673	11 years ago
Lukas Reschke	bc6d17ed74	Add check for availability of /dev/urandom ... Without /dev/urandom being available to read the medium RNG will rely only on the following components on a Linux system: 1. MicroTime: microtime() . memory_get_usage() as seed and then a garbage collected microtime for loop 2. MTRand: chr((mt_rand() ^ mt_rand()) % 256) 3. Rand: chr((rand() ^ rand()) % 256) 4. UniqId: Plain uniqid() An adversary with the possibility to predict the seed used by the PHP process may thus be able to predict future tokens which is an unwanted behaviour. One should note that this behaviour is documented in our documentation to ensure that users get aware of this even without reading our documentation this will add a post setup check to the administrative interface. Thanks to David Black from d1b.org for bringing this again to our attention.	11 years ago
Joas Schilling	81ec1c8a1a	Remove hardcoded link to performance docs	11 years ago
Lukas Reschke	65202d2a18	Add check for activated local memcache ... Also used the opportunity to refactor it into an AppFramework controller so that we can unit test it. Fixes https://github.com/owncloud/core/issues/14956	11 years ago
Lukas Reschke	9d1ce53cb1	Add some generic default headers as well via PHP	11 years ago
Lukas Reschke	bbd5f28415	Let users configure security headers in their Webserver ... Doing this in the PHP code is not the right approach for multiple reasons: 1. A bug in the PHP code prevents them from being added to the response. 2. They are only added when something is served via PHP and not in other cases (that makes for example the newest IE UXSS which is not yet patched by Microsoft exploitable on ownCloud) 3. Some headers such as the Strict-Transport-Security might require custom modifications by administrators. This was not possible before and lead to buggy situations. This pull request moves those headers out of the PHP code and adds a security check to the admin settings performed via JS.	11 years ago
cmeh	09a0bf22df	Update setupchecks.js ... Changed *"won't work"* to "will not work" (as proposed by @DeepDiver1975).	11 years ago
cmeh	d89cf737ae	Message clean-up ... *Changes:* * "… is not yet properly setup" in line 24 is changed to " … is not yet set up properly" (better word order and space in the middle of "set up", as it is a participle of the verb "to set up"). * "internet" is corrected to "Internet" with a capitalized "I" in lines 54 and 59. * Also in line 54: "3rd party" is changed to "third-party" to for a more coherent spelling across the different ownCloud components. * "… apps don´t work" is corrected to "… apps won't work" (with a proper (and hopefully correctly escaped) (apostrophe)[http://en.wikipedia.org/wiki/Apostrophe#Typographic_form] instead of the (acute accent)[http://en.wikipedia.org/wiki/Acute_accent]). * Still in line 54: The negation is corrected from "… might also not work" to "… might not work, either".	11 years ago
Lukas Reschke	2b76227180	Check for working .htaccess via AJAX ... Fixes https://github.com/owncloud/core/issues/12650	11 years ago
Vincent Petry	e65ceb08fc	Moved WebDAV and internet checks to client side JS ... - Added setup checks in JavaScript - Moved isWebDAVWorking to JS using SetupChecks - Moved internet connection checks to an ajax call that goes through the server	11 years ago