I suppose you really want to have a file system primitive which says 'open a temporary file for writing as a new version of this other file'. When you close the temporary file the filesystem would atomically replace the contents of the original file with the temporary file, preserving all attributes such as ACLs (unless you modified them on the temporary version). You could go further and arrange that the temporary file started off with the same contents as the original file - so the entire update sequence became a single transaction.
The only thing that's worse is that they might feel secure when they're not.
That is exactly what an ISP would want. You would have the correct URL, the correct IP address and everything would look correct. But your traffic would be monitored by the ISP (in some kind of transparent proxy).
Being able to save a certificate and not having a message pop up every time it is seen would be useful. The first time you came across a certificate you should get a warning message. But if you can manually verify the certificate then you should be able to silently accept it in the future.
Work is the crab grass in the lawn of life. -- Schulz