[19.09] nextcloud: 16.0.8 -> 16.0.9 #82697
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation for this change
https://nextcloud.com/security/advisory/?id=nC-SA-2020-015
I'm not sure if Nextcloud 16.0.9 already fixes this. Their advisory says it should be fixed by 16.0.10, but the advisory is dated from 2020-02-07, and 16.0.9 was released at 2020-03-13.I also opened nextcloud/server#19976 upstream for clarification,
we should probably still update to this version no matter if it fixes the issue or not.TLDR: This was indeed a typo upstream. Adressed in nextcloud/security-advisories#21
Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)