When a user forces vim to write a read-only file (:w!), vim may silently replace the original file with a new one owned by the current user. This behavior can have serious security implications that are not communicated in the warning message shown to the user.
E45: 'readonly' option is set (add ! to override)
ESC ESC
:w!
ESC ESC
:w!
Do you really want to write to it (y/n)?
y
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
I suppose this depends on the 'backupcopy' option and I guess this is just a consequence how Unix permissions work in general. There is already a warning so you should be careful. I don't think there is anything to be done here
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
—
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()