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.
Actually it's much esier than this, you can just set the permissions to mount for only root or remove the ATA drivers from the kernel and re-compile, I would stick with restrict the mounting to root and set a random root password on every boot, it should be the fastest and easiest solution which also prevents sudo'ing and allows for you to use that root account to access the hard drives, why is it you do not want people accessing the HD's btw???
Limiting mount permissions seems to solve part of the problem (this is what I do now)
However, the hard drive still appears in the konquerer file manager under the storage media section - which is undesirable as it gives the impression the hard drives are accessible.
do you think removing the ATA drivers will solve this? do you know how it's done? will it still allow cdrom and usb storage access?
another optin is thought of is somehow modifying the KDE kio_slaves, but i didn't found relevant information.
this also will not disable hotpluggable drives and I'm not sure if it will work with KDE because I don't use KDE.
There is another solution however, you could remove the fs drivers in the kernel which requires re-compiling and reconfiguring the kernel sources. It all seems like alot of work tbh, why do you need to hide drives?
using hal-device I see that the device is marked volume.ignore=true.
However, it appears that konquerer ignores this.
as for the need - it's supposed to some kind of sand box live cd - so I want it to block access to the local hard drive to prevent potential damage.
The fact that the hard drives can be seen, even if they can't be mounted, is also problematic as users might not trust the system to be secure enough.
okay... which KDE are you using that you have konqueror, I was pretty sure Dolphin was now the standard but anywho, other solutions include, uninstall konqueror and dolphin and use nautillus this should solve all of your problems within the GUI, furthermore if you would like to block all devices and loose all your data when you reboot you can use
this should work although it won't stop you e-mailing your data to yourself or ftp'ing it and you can be sure you definately won't injure your HD's, personally I'd just use more caution as i'm sure a shell script could still damage the drives