Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Newbie, recent build Debian 8, will use as home server. I followed an installation guide I found online which suggested using an "encryption password" that encrypts files on the discs for security. I did that. This means I must type in encryption password as part of the boot process.
My concern is this appears to mean the box cannot be truly headless. I cannot connect with my Windows machine until the Linux boot process is complete, and if typing in a password is part of that process, I cannot make the machine headless but must connect a keyboard and monitor every time I boot the Linux machine.
I understand Linux machines are not rebooted often, and if it is used as a home server that will certainly be the case.
Do most people use an encryption password for the disks on a server, or is that mainly for a desktop box? If encryption is used, is there a way to have server boot and require password later? I plan to later install/use SAMBA for home server connecting with Windows machines. Will that provide the security I need?
My wish is to make the machine truly headless so on the rare occasion I do reboot the machine, I can let it boot by itself and then I can connect using my Windows machine to monitor server functions.
When it boots, it also wants a user/password. I have not tried it due to encryption password, but if Linux server needs user/pass does that also mean I can't connect with Windows box until after user/pass is in? How do I get around that if the Linux machine is headless?
What steps do I need to take to ensure machine is truly headless and can boot on its own and I can simply connect with Windows box after automatic boot processes are complete, yet maintain system security?
I've tried some searching but not found anything that addresses this directly. If there are any online resources that directly address this concept, love to hear about it. Thanks
Some methods include installing busybox with dropbear and compile them into the initramfs
which will enable you to ssh in to enter the decryption passphrase.
Note the security implications. You might want to enable this early ssh capability only on an internal non-internet accessible network if you can (Possibly using a second network card (wired) in both the server and the ssh client box).
Hopefully that gives you a start.
All the best,
Last edited by Tim Abracadabra; 12-27-2015 at 08:42 PM.
Reason: alter redundant closing, add wired, only