nextcloud

Graphique des révisions

Auteur	SHA1	Message	Date
Morris Jobke	f5a1f4bc1b	Revert "Wait for cron to finish before running upgrade command" This reverts commit `18e9631810`. Signed-off-by: Morris Jobke <hey@morrisjobke.de>	il y a 5 ans
Morris Jobke	18e9631810	Wait for cron to finish before running upgrade command * fixes #9562 Signed-off-by: Morris Jobke <hey@morrisjobke.de>	il y a 6 ans
Morris Jobke	c70927eaa0	Remove not needed 3rdparty app disabling during upgrade for PHP 5.x Signed-off-by: Morris Jobke <hey@morrisjobke.de>	il y a 6 ans
Morris Jobke	0e2f00ec59	Get the Installer via DI Signed-off-by: Morris Jobke <hey@morrisjobke.de>	il y a 6 ans
Joas Schilling	18d7701d09	Prevent migration from ownCloud 11 to Nextcloud 12 Signed-off-by: Joas Schilling <coding@schilljs.com>	il y a 7 ans
Vincent Petry	da0cea404d	Kill update simulation Signed-off-by: Lukas Reschke <lukas@statuscode.ch>	il y a 7 ans
Joas Schilling	7c0951244a	Deprecate getEditionString()	il y a 7 ans
Joas Schilling	5c34346479	Allow downgrades of maintenance accross vendors	il y a 8 ans
Joas Schilling	9a4253ef7c	Fix lib/	il y a 8 ans
Thomas Müller	5c3183cedd	Move version check code out of class Updater	il y a 8 ans
Joas Schilling	fd7ed93937	Allow downgrades for our brave developers, that switch between branches	il y a 8 ans
Morris Jobke	ed98cdf532	Use OCP\Util::getVersion instead of the internal private implementation	il y a 8 ans
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 :wink:). 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: ![2015-11-04_12-02-57](https://cloud.githubusercontent.com/assets/878997/10936336/6adb1d14-82ec-11e5-8f06-9a74801c9abf.png) 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.	il y a 8 ans
Thomas Müller	4cb5970947	Always pass in ILogger	il y a 8 ans
Vincent Petry	2b08659f7d	Restrict upgrades to explicit allowed version version.php now contains the previous ownCloud version from which upgrades are allowed. Any other upgrades will show a message that the upgrade/downgrade is not supported.	il y a 8 ans
Lukas Reschke	422d088bb9	Do not rely on actual time in unit tests Ref https://github.com/owncloud/core/pull/17238#issuecomment-116724055	il y a 9 ans
Lukas Reschke	03498c0b2c	Build base URL	il y a 9 ans
Lukas Reschke	04fe9e05f0	Use new updater URL + add unit tests Uses the new updater url "https://updates.owncloud.com/server/"	il y a 9 ans
Lukas Reschke	5f044ebf1b	Add wrapper for Guzzle	il y a 9 ans
Thomas Müller	bbf7f56f94	3rd-party apps are disabled on upgrade - refs #14026	il y a 9 ans
Bjoern Schiessle	24993280ed	Next step in server-to-server sharing next generation, see #12285 Beside some small improvements and bug fixes this will probably the final state for OC8. To test this you need to set up two ownCloud instances. Let's say: URL: myPC/firstOwnCloud user: user1 URL: myPC/secondOwnCloud user: user2 Now user1 can share a file with user2 by entering the username and the URL to the second ownCloud to the share-drop-down, in this case "user2@myPC/secondOwnCloud". The next time user2 login he will get a notification that he received a server-to-server share with the option to accept/decline it. If he accept it the share will be mounted. In both cases a event will be send back to user1 and add a notification to the activity stream that the share was accepted/declined. If user1 decides to unshare the file again from user2 the share will automatically be removed from the second ownCloud server and user2 will see a notification in his activity stream that user1@myPC/firstOwnCloud has unshared the file/folder from him.	il y a 9 ans
Victor Dubiniuk	adab0ca98a	Remove leftover	il y a 9 ans
Victor Dubiniuk	c9fd3c9d29	Inject config	il y a 9 ans
Victor Dubiniuk	81d5712419	Fix tests. Add two more test cases	il y a 9 ans
Victor Dubiniuk	2a3f5ccae3	Test OC\Updater::check	il y a 9 ans
Lukas Reschke	5f6f54e785	Rename providers to not begin with test Fixes https://github.com/owncloud/core/issues/12347	il y a 9 ans
Joas Schilling	cb3a598cdb	Make root tests extend the \Test\TestCase	il y a 9 ans
Lukas Reschke	a71af58535	Prevent updates between multiple major versions Ref https://github.com/owncloud/core/issues/11078	il y a 9 ans

9 Révisions (d17b32afd713f9f94ea24eba2ba7a753b3270e44)