-
Notifications
You must be signed in to change notification settings - Fork 34
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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
openssl_csr_sign(): Signature did not match the certificate request #424
Comments
I'm having the same issue. Logs are identical expect for my personal settings of course. Anything I can submit to help? |
Same here, made a fresh nextcloud setup, except I'm using Nextcloud 27.0.0.8, Apache and PHP 8.2.8. The relevant nextcloud logs
The relevant Nextcloud client logs:
My server seems well configured, no other problems detected, admin panel shows everything well configured, sync works... |
Issue still uptodate with NC 27.0.1.2. I've intercepted the CSR sent by nextcloud desktop 3.9.0 which decodes to:
So far CSR seems valid.
Validity given to When trying to manually sign the CSR, here's what I get:
I'm pretty sure the subject is somehow malformed in the CSR. Guess this has to be reported to the NC desktop people. |
I've updated my Nextcloud server to 27.0.2.1 and desktop app to 3.9.3 (Mozilla/5.0 (Windows) mirall/3.9.3stable-Win64 (build 20230818) (Nextcloud, windows-10.0.19044 ClientArchitecture: x86_64 OsArchitecture: x86_64)). If I happen to use a local generated CSR file with the private key via openssl, I actually get to sign my certificate. Nextcloud desktop generated CSR (doesn't work):
My generated CSR (works):
From what I see, the CSR generated from nextcloud desktop is still using SHA-1 in 2023 ! Of course, I don't want to, since I'm really not trusting encryption with obsolete algorithms. Anyway, I think this bug report can be closed, since it's obviously an NC desktop issue. |
@prghix Mind to update the issue title by including "SOLVED" ? |
Closing in favor of nextcloud/desktop#5989 since this isn't a server E2EE app matter. Follow progress there / upvote that issue if impacted. |
How to use GitHub
Steps to reproduce
Expected behaviour
The E2EE should become enabled for the user in general/particular folder.
Actual behaviour
Nothing happens from the user point of view, but found in the logs:
Server configuration
Operating system: Rocky 9.1
Web server: NGINX 1.20
Database: maria 10.5
PHP version: PHP 8.2.4
Nextcloud version: 26 + 26.0.1
SELINUX: disabled
WAF: disabled
Updated from an older Nextcloud/ownCloud or fresh install:
fresh
Where did you install Nextcloud from:
Signing status:
Signing status
List of activated apps:
App list
Nextcloud configuration:
Config report
Are you using external storage, if yes which one: local/smb/sftp/...
Are you using encryption: yes/no
Are you using an external user-backend, if yes which one: LDAP/ActiveDirectory/Webdav/...
Client configuration
Browser: Chrome + client
Operating system:
Logs
Web server error log
Web server error log
Nextcloud log (data/nextcloud.log)
Nextcloud log
Browser log
Browser log
The text was updated successfully, but these errors were encountered: