Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Ability to remove specific text from db #60

irhs opened this Issue Feb 22, 2013 · 5 comments


None yet
3 participants

irhs commented Feb 22, 2013

It is good that selfspy stores the captured keystrokes in an encrypted db and requires password for accessing plaintext key values. But I think the ability to remove some specific text (say passwords) that was captured by selfspy is very useful.


adamclerk commented Apr 11, 2014

@irhs I dont think having a file of black-listed words would be appropriate.

Do you any more thoughts about the specific implementation?

irhs commented Apr 11, 2014

I agree having a black-listed words in inappropriate. I was thinking of taking the sensitive word through CLI as an argument and then remove it from the selfspy db. This is to clean up things if user accidentally enters sensitive password when selfspy is running.

Have you give any thoughts to removing sensitive passwords captured by selfspy? Encrypted DB might be good enough solution and what I am proposing might be overkill and not really solve the problem if the user backups selfspy database at other places.


adamclerk commented Apr 12, 2014

Honestly, once I have the metrics I need from selfspy...I delete the db...and let selfspy recreate it. That's why I think issue #59 would probably take priority for me.


gurgeh commented Apr 12, 2014

Taking a sensitive word through the CLI would in most cases be much worse than leaving it in an encrypted DB, since it would be added to the plaintext shell history.

irhs commented Apr 12, 2014

Good point. I forgot about the shell history.

Thinking more about this, maybe this isn't necessary. Encrypted db with a strong password or passphrase should provide reasonable security and #59 provides some flexibility on removing recently captured sensitive information.

I'm fine with closing this issue. Thanks for the responses.

@gurgeh gurgeh closed this Apr 12, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment