This is that release which contains a fix for the CRITICAL CVE, right? Is there any info on what it is? Do we know if normal Nextcloud setups are vulnerable?
There were multiple CVEs, and the fixes happened to coincide with a feature release. This Lobsters story seems to be more focused on new features (here's what's new in 8.6), whereas the security-focused story was this one from the other day (not sure if it meets the criteria for merging these stories or not).
I have not dug into any of the fixes yet, but there is at least one critical CVE that received a cutesy name ("phpAfterShell"), so I presume that one's kind of important? From their description it sounds like they claim the default configuration is vulnerable, which kind of contradicts what the PHP team said the other day.
mort | 4 hours ago
This is that release which contains a fix for the CRITICAL CVE, right? Is there any info on what it is? Do we know if normal Nextcloud setups are vulnerable?
proctrap | 3 hours ago
See the old thread, I posted the changelog I got in https://lobste.rs/c/jhpvbn
bitshift | 2 hours ago
There were multiple CVEs, and the fixes happened to coincide with a feature release. This Lobsters story seems to be more focused on new features (here's what's new in 8.6), whereas the security-focused story was this one from the other day (not sure if it meets the criteria for merging these stories or not).
I have not dug into any of the fixes yet, but there is at least one critical CVE that received a cutesy name ("phpAfterShell"), so I presume that one's kind of important? From their description it sounds like they claim the default configuration is vulnerable, which kind of contradicts what the PHP team said the other day.