Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I am using TrueCrupt 7.1a under Suse 12.3 and for added safety I specified a keyfile for my TC Volume.
That keyfile was carefully renamed by me and hidden among all kinds of other files, to obfuscate it.
And now imagine how grateful I am that, even so TC doesn't remember my last opened file (since I unchecked the "Remember History" option), the Linux operating system does it for me, and *always* displays the list of last used files to select from.
This of course makes utter waste of any obfuscation attempt of mine, when naming/placing the key file - I'd call that a brain damaged "feature" design, specially since I seem to be unable to erase that "used file history".
Anyone got any idea how to remove that file history altogether, and possibly prevent it from being created in the first place?
As do I, but that dreaded file list just keeps popping up, like a bad habit.
I tried almost every "KDE privacy cleanser" I could come up with, but that darn list won't go away.
Did the NSA design that "feature" or what?
Last edited by Timatekore; 08-22-2013 at 03:12 AM.
I think it is your default file manager (or similar) application, and you can find a .<something> dir in your home containing that info.
Also you can try to rename that file again and check if it was still remembered.
Jeez Louis, I've got hundreds of File Managers, Editors and the like installed on my box.
I can't manually inspect each & every subdir they've ever created.
Isn't there a simpler way to figure out where this info is being stored?
If you want security, you need to encrypt the system as a whole. Otherwise, leaks to /tmp, swap, various filesystems or several history registries are nearly unavoidable. Full encryption ensures they will have to crack the whole system or be able to access nothing at all. Even managing to delete the file list does not ensure it won't be recovered with forensic tools.
I agree that many applications make it very hard to delete or disable this kind of history registries. That sucks.