On Sun, Mar 25, 2018 at 02:19:59PM -0400, James Turner wrote: > As it seems this is only trigger when the default permissions on the > .fossil file is changed I think we are fine for the 6.3 release. Also > considering the tree was just locked :).
I agree. pledge() is enforced only on "fossil status" command, and the violation occurs due to umask change between first fossil(1) run (which created ~/.fossil) and next ones. It seems sqlite3 library (fossil is based on it) will enforce some permission on temporary journal file .fossil-journal to be same as .fossil. > I would suggested submitting a bug upstream letting them know they need > the additional pledge when they try to chmod the file back if it gets > changed. I sent a mail yesterday on the fossil-users@ list, but it didn't poped. I subscribed to the list and resent it this morning. > I'll add the # pledge comment on the next update I commit, thanks for > the heads up on that. Thanks. -- Sebastien Marie
