Diodon - GTK+ Clipboard Manager

How do I prevent Diodon to not save history in disk?

Asked by Jorge Peixoto on 2013-04-02

I usually copy-and-paste password while running Diodon. How do I gently ask Diodon to not save my plain password in disk?

Question information

Language:
English Edit question
Status:
Solved
For:
Diodon Edit question
Assignee:
No assignee Edit question
Solved by:
Oliver Sauder
Solved:
2013-04-11
Last query:
2013-04-11
Last reply:
2013-04-02
Oliver Sauder (sao) said : #1

This is a good question. Unfortunately for Diodon it is really difficult to determine whether a clip is a password or not.

There are some ideas on the way though which might help you. E.g. a plugin to remove clips see https://blueprints.launchpad.net/diodon/+spec/ideas-for-plugins or a possible zeitgeist integration which would make it possible if it works to black list application to be adding clips to the history (e.g. black list your password manager application if you have such).

Currently though the only thing what you can do is to Clear the history completely. What I did is to encrypt my home directory with eCryptfs which makes storing of the password less critical as well.

Of course, if there are any other ideas how to overcome this issue let me know and we can see what we can do.

Best Oliver Sauder (sao) said : #2

Just after writing another idea came to my mind. What you can do if you do not want to store any history on the hard disc is to symlink storage.xml to /dev/null by doing the following (first close diodon):

cd ~/.local/share/diodon
rm storage.xml
ln -s /dev/null storage.xml

Open Diodon again. The history is empty but will fill up again. After every reboot or restart of Diodon of course the history is empty.

Jorge Peixoto (jrglz) said : #3

Thanks Oliver Sauder, that solved my question.

Paladin24 (happyworm24) said : #4

I think it will be a good function to add. It is not too safe to store history on disk. I don't know is it possible to add such check box - Delete history on close or system shut down, but this is I really lack of.

Oliver Sauder (sao) said : #5

For now the workaround will be as explained in comment 2.

We are currently working on replacing the xml history with a zeitgeist backend. We will need to reassess how such can be done with Zeitgeist as there are already Privacy options available.