Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then 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.
Well, actually kerberos works differently from what you have described above. Kerberos is a secret key authentication mechanism, whereby the client and the server hold a secret symmetric key (ticket) for some previously negotiated encryption algorithm. This link explains it in more detail: http://web.duke.edu/~rob/kerberos/kerbdetails.html. The exact spec of how AD deals with kerberos I am not sure of, but i do know you can setup AD clients to 'cache' recently authenticated sessions for exactly ther reason you talk about:
I am particularly interested in the root login, if it differs from a normal user - as I had an issue not being able to login as root after a power outage (with AD temporarily unavailable).
Which appears to show that for all local accounts, including root, an initial attempt will be made to authenticate with AD. Only then will the Kerberos process itself kick in (if authentication is successful).
I might try caching login details, but would prefer root to bypass the process above.
what happens is PAM checks if a kerberos ticket exists or can be found for root. If not, it checks local unix/linux accounts. So if you can't log in as root, where root is a local account, it's nothing to do with AD, so far as I unserstand it. YMMV.