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 have done some searching around but have not been able to find a satisfactory answer to this question, perhaps due to the fact that I am not sure exactly what terms to use in my searching.
When you have not set up xdm, kdm, gdm, etc - and are just using the plain old text login, then using "startx" to begin your xsession, I seem to have found a security "issue" that I cannot find an answer for...
When using either xlock or kde's screen saver/Lock Desktop feature w/ password protection, if you push a button or move the mouse it will prompt for a password, however using the CTRL-ALT-F1 combination brings me to the tty0 where the X session was started from. I can then use Ctrl-Z to background the startx process and kill off the screensaver process, switch back to virtual console 7 and just like that I've defeated the "Lock Desktop" mechanism. At home this is not a concern, however at work I lock my computer every time I step away even for a moment, yet it seems to be wide open to any knowledgeable person.
If this is a common problem/issue that has already been addressed, please at least point me in the right direction, or at most tell me how to secure against this type of workaround.
The disown command throws the child process (startx) out of the shell session so that it is not killed (with HUP) when the shell is closed. exit closes the shell.
(BTW: I'm assuming you are using bash.)