Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
On booting up a redhat 7 server, the Gnome Display Manager GDM does not start. A blank black screen appears.
The last thing to be done before it stopped working was applying a STIG to harden it. Which among the many STIGs which broke it is unknown.
On boot up am able to see that gdm attempted to start. I don't seen any errors in messages.
Was thinking that a change to ../dconf/local.d/db caused the problem. So I reinstalled package deconf and removed all those files - made no difference.
Don't think it is the graphical card because I am able to start a desktop with startx.
STIG is US goverernmentese for "Security Technical Implementation Guidelines" and is a hardening guide. Some are OK, some have been put together by people in a closed environment that have no clue. I am not familiar with the Red hat one, only the web app one so can't speak to the Red Hat one.
Back off the changes you made until you find which one caused the issue and then add that change to a POA&M.
Unsure if this is what your issue is but could be related. I had commented the line in /etc/pam.d/postlogin that was listed as optional and didn't meet the STIG setting. After uncommenting the line back to the original, the GUI started fine.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.