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
I added a comment to issue #167 to a few days ago, unfortunately a problem with my account meant that I couldn't highlight this further and the comment would not have been displayed on the issue at the time the "patch released" label was added and the issue closed.
I believe that when --fix is used a read-only file may be left writable if:
The file is locked by other process.
The file contains the CVE-2021-45105 vulnerability (requiring an upgrade)
The file is backed up (after setWritable) and later restored
The backup file cannot be truncated
NB: With release 2.5.0, similar edge cases may exist when attempting to --restore a read-only targetFile from a backup.
The text was updated successfully, but these errors were encountered:
I added a comment to issue #167 to a few days ago, unfortunately a problem with my account meant that I couldn't highlight this further and the comment would not have been displayed on the issue at the time the "patch released" label was added and the issue closed.
I believe that when
--fix
is used a read-only file may be left writable if:setWritable
) and later restoredNB: With release 2.5.0, similar edge cases may exist when attempting to
--restore
a read-onlytargetFile
from a backup.The text was updated successfully, but these errors were encountered: