1) I've been considering this, but don't really know - the original request
for read-only actually wanted it to be even more restrictive than it is. Which use-case leads to enabling and then disabling read-only mode?
2) You can already achieve this by choosing "Save As"... I could do a "don't clear passphrase on file->new" option, which would be easy for current version of fSekrit. However, it would be more intuitive for file->new to open a new fSekrit editor window, rather than the current method of just clearing the contents. If/when that is added, the cache feature would require passing the passphrase on the commandline (or some more complicated IPC method), which I don't really feel like doing. Commandline is a security risk, other IPC method is too much code overhead for too little win. I'll ponder a bit about this.
3) yep, and it's something I've wanted to add. Next version will have copy/paste disabled on the passphrase dialogs, but an "unmask password" checkbox (which will obviously clear whatever you've already typed when you unhide).
4) should be, considering I'm using a RichEdit control
- actually I'm currently specifying explicitly that I only want pure text on edit->paste, it'd be less code to acched rich formatted text. I do not
plan on adding rich editing features to fSekrit, but pasting from an external document should be doable.