summaryrefslogtreecommitdiffstats
path: root/lib/private/updater.php
Commit message (Collapse)AuthorAgeFilesLines
* [stable9] Use custom updater URLLukas Reschke2016-06-121-1/+1
|
* Make sure that installed is a booleanJoas Schilling2016-05-231-0/+1
|
* Make update server URL configurableLukas Reschke2016-05-111-5/+2
| | | | Currently testing the updates is a big problem and not really super easy possible. Since we now have a new updater server we should also make this configurable so that people can properly test updates.
* Do not abort with an exception when a default app can not be enabledJoas Schilling2016-03-221-1/+6
|
* Install new shipped apps after upgrading all existing appsThomas Müller2016-02-231-4/+4
|
* Before installing new shipped apps we need to load authentication apps - ↵Thomas Müller2016-02-231-1/+1
| | | | fixes #22508
* More fixesJoas Schilling2016-02-091-1/+0
|
* Scrutinizer Auto-FixesScrutinizer Auto-Fixer2016-02-081-2/+1
| | | | This commit consists of patches automatically generated for this project on https://scrutinizer-ci.com
* Merge pull request #21668 from ↵Thomas Müller2016-01-131-2/+2
|\ | | | | | | | | owncloud/add-super-evil-and-hidden-config-switch-to-disable-integrity-checks-really-just-do-not-use-this Add hidden config switch to disable code integrity checking
| * Add hidden config switch to disable code integrity checkingLukas Reschke2016-01-121-2/+2
| | | | | | | | | | | | | | | | | | | | | | This adds a hidden config flag that allows somebody to disable the code integrity check. If `integrity.check.disabled` is set to `true` in the config file: 1. The integrity check functions will return always an empty result 2. The integrity check is not performed when installing apps 3. The integrity check is not performed when updating apps 4. The integrity check is not performed when updating the core Furthermore this adds support for a list of channels that the code checker will run on. At the moment this is only stable because I didn't want to break any build scripts that we have. Once we have a proper CA setup and updated the build process to sign the releases we can add the RC, alpha, beta as well as daily releases. So everything except "git" basically.
* | Happy new year!Thomas Müller2016-01-121-2/+2
|/
* Allow downgrades for our brave developers, that switch between branchesJoas Schilling2016-01-071-1/+1
|
* Use OCP\Util::getVersion instead of the internal private implementationMorris Jobke2015-12-181-5/+5
|
* Clear xml errors in updaterThomas Müller2015-12-171-0/+2
|
* Add code integrity checkLukas Reschke2015-12-011-0/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* Update license headersLukas Reschke2015-10-261-0/+1
|
* Merge pull request #19918 from owncloud/send-begin-messageThomas Müller2015-10-211-0/+6
|\ | | | | Update: state which step we are going to start and warn if it might b…
| * Update: state which step we are going to start and warn if it might be slowJoas Schilling2015-10-211-0/+6
| |
* | Install new shipped apps on upgrade -fixes #19925Thomas Müller2015-10-211-0/+3
|/
* Always pass in ILoggerThomas Müller2015-10-091-3/+1
|
* Clean codeThomas Müller2015-10-091-2/+2
|
* Catch exceptions during app upgrade - fixes #16240Thomas Müller2015-10-091-4/+8
|
* [upgrade] switch to debug logging on upgradeMorris Jobke2015-09-291-0/+16
| | | | | * resets afterwards * adds output about the previous log level
* Move certificate bundle into resources/config/Lukas Reschke2015-09-221-7/+0
|
* Improved update version detection logicVincent Petry2015-08-311-7/+1
|
* Simplify comparison algoVincent Petry2015-08-311-15/+1
|
* Restrict upgrades to explicit allowed versionVincent Petry2015-08-301-6/+34
| | | | | | 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.
* Add warning for not existing CA bundle when updatingLukas Reschke2015-08-191-0/+7
| | | | For newer releases we shall use an integrity check. But that's a good alternative for now.
* Merge pull request #17088 from owncloud/add-verbosity-to-upgradeMorris Jobke2015-07-011-0/+6
|\ | | | | [upgrade] add verbosity check and show repair info & steps
| * [upgrade] add verbosity check and show repair info & stepsMorris Jobke2015-06-241-0/+6
| |
* | Use new updater URL + add unit testsLukas Reschke2015-06-281-13/+22
| | | | | | | | Uses the new updater url "https://updates.owncloud.com/server/"
* | update license headers and authorsMorris Jobke2015-06-251-0/+1
|/
* Merge pull request #17095 from owncloud/proper-error-handlingMorris Jobke2015-06-231-3/+8
|\ | | | | Proper error handling
| * [updater] keep maintenance active on failure and mark failure in redMorris Jobke2015-06-231-1/+1
| |
| * [updater] propagate error case properlyMorris Jobke2015-06-231-2/+7
| | | | | | | | | | | | * add $success to the updateEnd hook * add new return code for a update failure * add exception class to failure hook message
* | [upgrade] print update message before running the update codeMorris Jobke2015-06-231-0/+1
|/ | | | * otherwise you don't know during which app update something failed
* Merge pull request #16434 from owncloud/persist-maintenance-stateThomas Müller2015-06-031-4/+14
|\ | | | | Persist the state of the maintenance after an upgrade
| * Persist the state of the maintenance after an upgradeMorris Jobke2015-05-191-4/+14
| | | | | | | | | | | | * if maintenance mode was enabled before an upgrade it will be enabled afterwards too * fixes #16429
* | Skip disable3rdParty AppsSteffen Lindner2015-05-201-4/+19
|/
* Use internally \OCP\ILogger instead of \OC\LogMorris Jobke2015-04-301-3/+4
| | | | | | * this is the preparation for some upcoming logger related changes * also fixes an issue in the public interface where we request an internal class as parameter
* Update license headersJenkins for ownCloud2015-03-261-4/+27
|
* Add spacesMorris Jobke2015-03-161-1/+1
|
* [WIP] upgrade app store apps during console upgradeThomas Müller2015-03-131-1/+21
|
* Merge pull request #14357 from owncloud/fix/1373Morris Jobke2015-03-111-7/+7
|\ | | | | Run `updateDataDirectory` after Update
| * Run `updateDataDirectory` after UpdateLukas Reschke2015-03-021-7/+7
| | | | | | | | Fixes https://github.com/owncloud/core/issues/13731
* | Properly forward repair errors and warningsVincent Petry2015-02-271-0/+16
|/ | | | | This makes repair errors and warnings visible for the user when upgrading on the command line or in the web UI.
* Revert "Updating license headers"Morris Jobke2015-02-261-26/+5
| | | | This reverts commit 6a1a4880f0d556fb090f19a5019fec31916f5c36.
* 3rd-party apps are only disabled in case core is upgradedThomas Müller2015-02-241-0/+14
|
* shipped and 3rd-party apps of type authentication and session will remain ↵Thomas Müller2015-02-241-3/+11
| | | | enabled during update
* 3rd-party apps are disabled on upgrade - refs #14026Thomas Müller2015-02-241-38/+55
|
generated by cgit v1.2.3 (git 2.39.1) at 2025-02-28 22:01:46 +0000