Skip to content

Conversation

@MorrisJobke
Copy link
Member

Before the resources/config/ca-bundle.crt was only used when the list of custom
certificates was empty and the instance was not installed. But it should also
be used when the list is empty and the instance is installed.

This is inverting the logic to stop if the instance is not installed to use the
default bundle. And it also does this when the list is empty.

Noticed while debugging user creation on an instance with object storage.

@MorrisJobke MorrisJobke added bug 3. to review Waiting for reviews labels May 25, 2020
@MorrisJobke MorrisJobke added this to the Nextcloud 20 milestone May 25, 2020
@MorrisJobke
Copy link
Member Author

/backport to stable19

@MorrisJobke
Copy link
Member Author

/backport to stable18

@MorrisJobke
Copy link
Member Author

/backport to stable17

@MorrisJobke
Copy link
Member Author

/backport to stable16

@kesselb kesselb added 4. to release Ready to be released and/or waiting for tests to finish and removed 3. to review Waiting for reviews labels May 25, 2020
Before the resources/config/ca-bundle.crt was only used when the list of custom
certificates was empty and the instance was not installed. But it should also
be used when the list is empty and the instance is installed.

This is inverting the logic to stop if the instance is not installed to use the
default bundle. And it also does this when the list is empty.

Signed-off-by: Morris Jobke <[email protected]>
@MorrisJobke MorrisJobke force-pushed the bug/noid/do-not-read-cert-from-datadir-by-default branch from f748d1d to 18b0d75 Compare May 25, 2020 14:58
@MorrisJobke
Copy link
Member Author

I fixed the tests. They required the listCertificates called once in the case the system is not installed (was changed in here on purpose to improve the code readability).

@blizzz
Copy link
Member

blizzz commented Nov 13, 2020

This one was reverted on the stable branches, but not on master (and now 20). Why so?

@MorrisJobke
Copy link
Member Author

This one was reverted on the stable branches, but not on master (and now 20). Why so?

@rullzer Was this because we want to do the #21693 in 20 as well? Or was this due to something else?

@MorrisJobke
Copy link
Member Author

Indeed - broken on stable20 as well: #24556

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

4. to release Ready to be released and/or waiting for tests to finish bug

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants