-
Notifications
You must be signed in to change notification settings - Fork 202
fix: collaboration rsa #11294
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
base: master
Are you sure you want to change the base?
fix: collaboration rsa #11294
Conversation
Thanks for opening this pull request! The maintainers of this repository would appreciate it if you would create a changelog item based on your changes. |
|
Needs testing. The proof key is generated in the document server (OnlyOffice, Collabora, etc), so I don't think we have control over the algorithm being used. I'm also not sure if the algorithms are compatible with each other. There is a reference for PKCS1.5 in https://learn.microsoft.com/en-us/microsoft-365/cloud-storage-partner-program/online/scenarios/proofkeys#verification-in-python |
Thanks @jvillafanez How this can be tested, any case that would point into right direction? |
https://github.com/owncloud/ocis/blob/master/services/collaboration/pkg/middleware/proofkeys.go#L63 is the debug log to look for. The proofkeys middleware is enabled by default, so if everything is ok the debug log should appear. |
It seems the proofkey verifications fail for me. With OnlyOffice:
With Collabora
I can't test with Microsoft, but I guess it would also fail |
Description
Addresses https://github.com/owncloud/ocis/security/code-scanning/4
Related Issue
Motivation and Context
How Has This Been Tested?
Screenshots (if appropriate):
Types of changes
Checklist: