You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are some patches in AOSC community made back in 2019 against an imported repository dating as far as version 2017.3.23. From what I can tell, they never made it here upstream. And at least one patch is a nice quality of life improvement regarding suid handling. Should we try to accept these patches now?
(There was some issue with the ML in that JPA and I forgot to click "reply all". So I will be quoting nonexistent stuff, sorry.)
I think AOSC-Archive/ntfs-3g@9189a4a and AOSC-Archive/ntfs-3g@c918fb7 are the two worth cherry-picking. The former is trivial and may have been independently fixed. The latter was proposed in the ML; the gist of my argument was that a system libfuse2 would be about as safe as a static libfuse-lite since the setuid on ntfs-3g prevents LD_PRELOAD and other shenanigans.
The big_writes thing is already upstream. My two commits were a bit misguided in that I basically ported libfuse3 features (the even bigger 1MB buffer) to the internal libfuse2 copy. That was obviously a bad idea compared to porting to libfuse3 wholesale, but neither Tuxera nor I had the combined energy+intention to do it.
There are some patches in AOSC community made back in 2019 against an imported repository dating as far as version 2017.3.23. From what I can tell, they never made it here upstream. And at least one patch is a nice quality of life improvement regarding suid handling. Should we try to accept these patches now?
https://github.com/AOSC-Dev/ntfs-3g/commits/master
The text was updated successfully, but these errors were encountered: