summaryrefslogtreecommitdiffstats
path: root/core/ajax/update.php
Commit message (Collapse)AuthorAgeFilesLines
* Revert "Wait for cron to finish before running upgrade command"Morris Jobke2018-11-011-5/+1
| | | | | | This reverts commit 18e9631810ad1d3d72c2b4bbee330169808108ad. Signed-off-by: Morris Jobke <hey@morrisjobke.de>
* Use numeric placeholders if there are multiple, so that RTL languages can ↵Joas Schilling2018-10-091-1/+1
| | | | | | operate better Signed-off-by: Joas Schilling <coding@schilljs.com>
* Use ellipsis instead of triple dotJoas Schilling2018-06-221-1/+1
| | | | Signed-off-by: Joas Schilling <coding@schilljs.com>
* Wait for cron to finish before running upgrade commandMorris Jobke2018-06-191-1/+5
| | | | | | * fixes #9562 Signed-off-by: Morris Jobke <hey@morrisjobke.de>
* move log constants to ILoggerArthur Schiwon2018-04-261-1/+3
| | | | Signed-off-by: Arthur Schiwon <blizzz@arthur-schiwon.de>
* Merge pull request #7918 from nextcloud/properly-log-exceptionsRoeland Jago Douma2018-01-231-0/+4
|\ | | | | Properly log the full exception instead of only the message
| * Properly log the full exception instead of only the messageMorris Jobke2018-01-231-0/+4
| | | | | | | | Signed-off-by: Morris Jobke <hey@morrisjobke.de>
* | Merge pull request #7354 from nextcloud/refacor-update-page-printblizzz2018-01-221-1/+1
|\ \ | |/ |/| Refactor method to check if update is needed
| * Refactor method to check if update is neededMorris Jobke2017-11-301-1/+1
| | | | | | | | | | | | There was only one call, that actually needed the parameter to be set to true. So this change moved the print of the page to that location and replaces all other occurences with a direct call to the underlying OCP API. Signed-off-by: Morris Jobke <hey@morrisjobke.de>
* | Remove not needed 3rdparty app disabling during upgrade for PHP 5.xMorris Jobke2018-01-191-7/+0
|/ | | | Signed-off-by: Morris Jobke <hey@morrisjobke.de>
* Get the Installer via DIMorris Jobke2017-11-251-1/+2
| | | | Signed-off-by: Morris Jobke <hey@morrisjobke.de>
* Update license headersMorris Jobke2017-11-061-0/+1
| | | | Signed-off-by: Morris Jobke <hey@morrisjobke.de>
* Stricter phan config fixesLukas Reschke2017-08-011-1/+5
| | | | Signed-off-by: Lukas Reschke <lukas@statuscode.ch>
* Proper logging for appstore updatesMorris Jobke2017-05-111-0/+9
| | | | Signed-off-by: Morris Jobke <hey@morrisjobke.de>
* Check that set_time_limit is not disabled before calling itKo-2017-03-111-1/+4
| | | | Signed-off-by: Ko- <k.stoffelen@cs.ru.nl>
* Update with robinJoas Schilling2016-07-211-1/+1
|
* Fix othersJoas Schilling2016-07-211-2/+3
|
* Update license headersLukas Reschke2016-05-261-2/+2
|
* Adding progress to web upgradeThomas Müller2016-04-281-6/+58
|
* Fix web updater - fixes #24115Thomas Müller2016-04-201-3/+3
|
* Merge pull request #23911 from owncloud/split-upgrade-commandChristoph Wurst2016-04-181-1/+0
|\ | | | | Move version check code out of class Updater
| * Move version check code out of class UpdaterThomas Müller2016-04-181-1/+0
| |
* | Suggest cli based updater in case the instance is bigger - #23913Thomas Müller2016-04-181-1/+9
|/
* Fix verbose output of upgrade command - not progressbar in this case and the ↵Thomas Müller2016-04-041-0/+5
| | | | schema migration test has one progressbar now for all tables - before we had one progressbar for each table
* Add detailed logs hidden and show them on requestMorris Jobke2016-04-041-3/+0
|
* Show individual sql schema migration steps during upgrade - on web as well ↵Thomas Müller2016-04-041-0/+12
| | | | as on the command line
* Revert "setting to skip migration tests by default"Morris Jobke2016-02-031-6/+0
|
* setting to skip migration tests by defaultMorris Jobke2016-02-031-0/+6
| | | | | | | * if you install owncloud via package it is not possible to skip migration tests * this also allows to disable migration tests for an instance by default
* Happy new year!Thomas Müller2016-01-121-2/+2
|
* don't show previous log level in upgrade messageBjörn Schießle2016-01-041-2/+2
|
* Add code integrity checkLukas Reschke2015-12-011-0/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* Replace some OC_Config calls with ILogger methodsMorris Jobke2015-10-301-3/+4
|
* Revert "setting to skip migration tests by default"Morris Jobke2015-10-271-10/+1
| | | | This reverts commit 7cbdd9b90bcea3566b7d0198f23da3d427e6ef45.
* Update license headersLukas Reschke2015-10-261-0/+1
|
* Merge pull request #19918 from owncloud/send-begin-messageThomas Müller2015-10-211-0/+12
|\ | | | | 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/+12
| |
* | Update - Only add one section for disabled appsJoas Schilling2015-10-211-6/+9
|/
* setting to skip migration tests by defaultMorris Jobke2015-10-011-1/+10
| | | | | | | * if you install owncloud via package it is not possible to skip migration tests * this also allows to disable migration tests for an instance by default
* [upgrade] switch to debug logging on upgradeMorris Jobke2015-09-291-0/+6
| | | | | * resets afterwards * adds output about the previous log level
* Properly show update exceptionVincent Petry2015-08-261-1/+7
|
* Properly show token errors in ajax/update.php event sourceVincent Petry2015-08-261-5/+13
|
* Remove 3rd party text for disabled apps on updateVincent Petry2015-07-071-1/+1
|
* Remove OC_LogThomas Müller2015-07-031-1/+2
|
* update license headers and authorsMorris Jobke2015-06-251-0/+1
|
* Persist the state of the maintenance after an upgradeMorris Jobke2015-05-191-2/+5
| | | | | | * if maintenance mode was enabled before an upgrade it will be enabled afterwards too * fixes #16429
* Update license headersJenkins for ownCloud2015-03-261-0/+25
|
* Merge pull request #13513 from owncloud/repair-legacystoragenofatalfailMorris Jobke2015-03-111-0/+6
|\ | | | | Do not abort when meeting unfixable legacy storages
| * Properly forward repair errors and warningsVincent Petry2015-02-271-0/+6
| | | | | | | | | | This makes repair errors and warnings visible for the user when upgrading on the command line or in the web UI.
* | Verify CSRF token already in update.php and not the EventSource codeLukas Reschke2015-03-091-0/+2
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Issue report: > Hum, well I upgraded the package then visited the web interface to trigger the update and it failed; the UI would say there was a possible CSRF attack and after that it'd be stuck in maintenance mode. Tried a few times (by editing maintenance to false in owncloud.conf) and same result each time. That smells partially like an issue caused by our EventSource implementation, due to legacy concerns the CSRF verification happens within the EventSource handling and not when the actual endpoint is called, what happens here then is: 1. User has somehow an invalid CSRF token in session (or none at all) 2. User clicks the update button 3. Invalid CSRF token is sent to update.php - no CSRF check there => Instance gets set in maintenance mode 4. Invalid CSRF token is processed by the EventSource code => Code Execution is stopped and ownCloud is stuck in maintenance mode I have a work-around for this problem, basically it verifies the CSRF token already in step 3 and cancels execution then. The same error will be shown to the user however he can work around it by refreshing the page – as stated by the error. I think that’s an acceptable behaviour for now: INSERT LINK To verify this test: 1. Delete your ownCloud cookies 2. Increment the version in version.php 3. Try to upgrade => Before the patch: Instance shows an error, is set to upgrade mode and a refresh does not help => After the patch: Instance shows an error, a refresh helps though. This is not really the best fix as a better solution would be to catch such situations when bootstrapping ownCloud, however, I don’t dare to touch base.php for this sake only, you never know what breaks then… That said: There might be other bugs as well, especially the stacktrace is somewhat confusing but then again it installing ownCloud under /usr/share/owncloud/ and I bet that is part of the whole issue ;-)
* Revert "Updating license headers"Morris Jobke2015-02-261-25/+0
| | | | This reverts commit 6a1a4880f0d556fb090f19a5019fec31916f5c36.
generated by cgit v1.2.3 (git 2.39.1) at 2025-01-09 21:38:40 +0000