Skip to main content

How to enable root login in gnome on Debian 6 or 7

Root user login in gnome is disabled on Debian system by default for security reasons. If you want to enable it for specific reasons then follow the below steps :

1. Login into Debian system
2. launch the Root Terminal from Applications -> Accessories.
3. Authenticate with password to launch the Root Terminal.
4. Open "/etc/pam.d/gdm3" with vi.
    
    #vi /etc/pam.d/gdm3
5. Look for "auth     required     pam_succeed_if.so  user  != root   quiet_success"  , comment it out as below.

    #auth     required     pam_succeed_if.so  user  != root   quiet_success
6. Save the modification with Esc+w+q+Enter keystroke.
7. Restart or reboot Debian system.
8. Login with root user in gnome. You should be now able to login successfully.


  

Comments

  1. hi i dont have the following file in my debian 7 OS.

    /etc/pam.d/gdm3;

    Please suggest if I am missing any package?

    ReplyDelete
    Replies
    1. Good tutorial to enable root accoun on debian 7 gdm3 uh NO someone answer the question please.

      SJThursday, September 19, 2013

      hi i dont have the following file in my debian 7 OS.

      /etc/pam.d/gdm3;

      Please suggest if I am missing any package?

      Delete
    2. In Debian 8 the file name is: /etc/pam.d/gdm-password

      Delete
  2. working on it now...vi escape key on my debian system is the : also need to have insert key on to modify inline...at least on my system.

    It worked like a charm... now to do the Apache server admin and get out.

    ReplyDelete
  3. Good tutorial to enable root accoun on debian 7 gdm3

    ReplyDelete
  4. No need to reboot afterward. GDM re-reads the file when it next-launches (e.g. after you log-out)

    ReplyDelete
  5. i found that vi wouldnt let me edit ? .... i used #gedit /etc/pam.d/gdm3 .... via the root terminal, saved and rebooted and worked just fine

    ReplyDelete
  6. i found that vi wouldnt work for some reason. i used #gedit /etc/pam.d/gdm3 ... saved and rebooted ... works just fine now

    ReplyDelete
  7. You are the MAN thanks a million, This was driving me crazy, Thanks again.

    ReplyDelete
  8. Thank you. This was the answer I was looking for!

    ReplyDelete

Post a Comment

Popular posts from this blog

How to find firmware or boot ROM version in Mac OS X

Firmware and boot ROM version of your mac can be found in two ways. Way 1 : 1. From "Apple" menu , choose "About This Mac" menu item. 2. Click " More Info " to open "System Profiler" application. 3. Under Contents -> Select Hardware Tree item. On the right side panel Under hardware overview section, we can see Boot ROM Version and SMC (Firmware) Version. Way 2 : Run the below command in terminal to get boot ROM version and SMC(firmware) version : $ system_profiler SPHardwareDataType | grep -i "Version" | awk -F ':' '{print $1 $2}'

How to extract signing certificates from macOS binary files

Code signing is a macOS security technology that you use to certify that an app was created by you. Once an app is signed, the system can detect any change to the app—whether the change is introduced accidentally or by malicious code. As Apple Developer site says ( click here for more details  on code signing) : code signing allows the operating system to: Ensure that a piece of code has not been altered since it was signed.  The system can detect even the smallest change, whether it was intentional (by a malicious attacker, for example) or accidental (as when a file gets corrupted). When a code signature is intact, the system can be sure the code is as the signer intended. Identify code as coming from a specific source (a developer or signer).  The code signature includes cryptographic information that unambiguously points to a particular author. Determine whether code is trustworthy for a specific purpose.  Among other things, a developer can use a code signature to s

What are the useful nvram settings in macOS ?

The OS X boot arguments are useful for troubleshooting problems with system startup and how the system behaves when running. sudo nvram boot-args="-v" :  This command will set the system to always boot to verbose mode, so we do not need to hold Command + V at system startup. sudo nvram boot-args="-x" :  This will set the system to always boot into Safe Mode. sudo nvram boot-args="-s" :  This command will boot the system into single user mode without needing to hold Command-S at system startup. sudo nvram boot-args="iog=0x0"  :   when you close the display but connect the system to an external monitor and keyboard the system will stay awake. After running this command, when connecting an external monitor, the internal display will be disabled, which can be beneficial in some situations such as those where you are mirroring your desktop but wish to run the external display at a higher resolution than your laptop can run. sudo nvram b