-
-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Certificate is not valid #4852
Comments
For security reasons, we had to stop shipping another root authority not under our control. If you want to use the OCC code signing tool you need to either use the Nextcloud issued certificate or none at all. (updates from the Nextcloud app store are protected using a more secure approach than the integrity checker, we check the whole TAR file) Sorry that I don't have better news here. The easiest would probably be to have two bundles one with code integrity check file in /appinfo/signatures.json and one without code integrity check file. |
@LukasReschke, so in future all app developers have to maintain a release with an When I remove remove the
|
...or is a the integrity check not mandatory in NC 12 when the app was downloaded from the NC store? |
ping @LukasReschke |
Hello my friends at NC. 馃樃
Steps to reproduce
php occ integrity:check-app ownbackup
Expected behaviour
No error should be thrown. :)
Actual behaviour
If you repeat the same test with NC 11, no error will be shown.
I got the certificate for signing the app with
occ integrity:sign-app
from ownCloud back in the days where NC was not "born" and I still need that certificate for signing the app for ownCloud. I think it is not very desirable to maintain two different releases of an app for oC and NC because of a certificate.Was it really necessary to disallow the oC certificate in 5a6e29e (if that was the point when it happend)?
Happy weekend and kind regards from Graz.
The text was updated successfully, but these errors were encountered: