Escaping passwords

[Wognath]

Very interesting Scooby's topic Bash removing passwords safely from RAM, but over my head. It might be useful to start a topic on simpler password visibility issues. I can contribute two.
1) After using fpm2, usernames and passwords that had been pasted into the browser were visible in glipper clipboard manager. Solution: kill glipper before starting fpm2
2) I recently used aescrypt to encrypt some text files, after which the passwords were visible in the history file. Solution: erase /root/.history

I'm a relatively naive user, so although I caught these, there are probably others I have missed. Are there similar situations to watch out for?

[disciple]

Some clipboard managers have a feature to "pause" them without closing them, and also to remove entries from the history.

[proebler]

I have posted about the issue with fpm2 a long time ago.
Since I do like this simple password manager, I prevent glipper/parcellite from starting by default.
see:
http://www.murga-linux.com/puppy/viewto ... &start=510

edit 1

[disciple]

I might be confused (maybe I'm thinking of the fork which has had most of its work merged back in), but I thought parcellite was one of the ones which enables you to pause recording the clipboard, as well as of course allowing you to manually remove an entry.

[Wognath]

Sylpheed stores email passwords as plain text in .sylpheed/accountrc

@proebler Sorry I missed your post about fpm2