Scientific Linux 7x - Too much system hardening!

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP












-3















Some Linux users like my company build Linux servers to use on factory production lines. We write software to load BIOS and FLASH memory and test our products. We constantly need to reboot these production Linux servers and continue testing WITHOUT NEEDING AN OPERATOR to sit there and enter a root PASSWORD on every reboot. There are users out there that don't want or need mandatory root/user password security. It just adds COST to the production processes. How in RHEL 7.x (or more specifically Scientific Linux 7.x) can we simply boot a system into runlevel1 (emergency/rescue mode) without a root password? I've done days of research and have not found a method to disable the root password. Is it possible? (BTW: this was not a problem in 6.x)










share|improve this question


























    -3















    Some Linux users like my company build Linux servers to use on factory production lines. We write software to load BIOS and FLASH memory and test our products. We constantly need to reboot these production Linux servers and continue testing WITHOUT NEEDING AN OPERATOR to sit there and enter a root PASSWORD on every reboot. There are users out there that don't want or need mandatory root/user password security. It just adds COST to the production processes. How in RHEL 7.x (or more specifically Scientific Linux 7.x) can we simply boot a system into runlevel1 (emergency/rescue mode) without a root password? I've done days of research and have not found a method to disable the root password. Is it possible? (BTW: this was not a problem in 6.x)










    share|improve this question
























      -3












      -3








      -3








      Some Linux users like my company build Linux servers to use on factory production lines. We write software to load BIOS and FLASH memory and test our products. We constantly need to reboot these production Linux servers and continue testing WITHOUT NEEDING AN OPERATOR to sit there and enter a root PASSWORD on every reboot. There are users out there that don't want or need mandatory root/user password security. It just adds COST to the production processes. How in RHEL 7.x (or more specifically Scientific Linux 7.x) can we simply boot a system into runlevel1 (emergency/rescue mode) without a root password? I've done days of research and have not found a method to disable the root password. Is it possible? (BTW: this was not a problem in 6.x)










      share|improve this question














      Some Linux users like my company build Linux servers to use on factory production lines. We write software to load BIOS and FLASH memory and test our products. We constantly need to reboot these production Linux servers and continue testing WITHOUT NEEDING AN OPERATOR to sit there and enter a root PASSWORD on every reboot. There are users out there that don't want or need mandatory root/user password security. It just adds COST to the production processes. How in RHEL 7.x (or more specifically Scientific Linux 7.x) can we simply boot a system into runlevel1 (emergency/rescue mode) without a root password? I've done days of research and have not found a method to disable the root password. Is it possible? (BTW: this was not a problem in 6.x)







      security login password root






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Feb 20 at 1:32









      bobbob

      1




      1




















          1 Answer
          1






          active

          oldest

          votes


















          0















          1. Remove the original getty@tty1.service symlink:



            rm /etc/systemd/system/getty.target.wants/getty@tty1.service



          2. Make a copy of the getty@.service file and call it getty@tty1.service



            cp /lib/systemd/system/getty@.service /etc/systemd/system/getty@tty1.service



          3. Edit this file (the last line, must be ADDED):



            [Service]
            ...
            ExecStart=-/sbin/agetty --autologin root --noclear %I
            ...
            [Install]
            ...
            ;Alias=getty@tty1.service



          4. Make a symlink in getty.target.wants



            ln -s /etc/systemd/system/getty@tty1.service /etc/systemd/system/getty.target.wants/getty@tty1.service


          5. Reboot. It everything went fine you will be logged in as root.


          Whole forum found: Here






          share|improve this answer

























          • Edit the service how? Otherwise this would be a "link-only" Answer. Thanks!

            – Jeff Schaller
            Feb 20 at 2:36










          Your Answer








          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "106"
          ;
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function()
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled)
          StackExchange.using("snippets", function()
          createEditor();
          );

          else
          createEditor();

          );

          function createEditor()
          StackExchange.prepareEditor(
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: false,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          imageUploader:
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          ,
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          );



          );













          draft saved

          draft discarded


















          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f501750%2fscientific-linux-7x-too-much-system-hardening%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          0















          1. Remove the original getty@tty1.service symlink:



            rm /etc/systemd/system/getty.target.wants/getty@tty1.service



          2. Make a copy of the getty@.service file and call it getty@tty1.service



            cp /lib/systemd/system/getty@.service /etc/systemd/system/getty@tty1.service



          3. Edit this file (the last line, must be ADDED):



            [Service]
            ...
            ExecStart=-/sbin/agetty --autologin root --noclear %I
            ...
            [Install]
            ...
            ;Alias=getty@tty1.service



          4. Make a symlink in getty.target.wants



            ln -s /etc/systemd/system/getty@tty1.service /etc/systemd/system/getty.target.wants/getty@tty1.service


          5. Reboot. It everything went fine you will be logged in as root.


          Whole forum found: Here






          share|improve this answer

























          • Edit the service how? Otherwise this would be a "link-only" Answer. Thanks!

            – Jeff Schaller
            Feb 20 at 2:36















          0















          1. Remove the original getty@tty1.service symlink:



            rm /etc/systemd/system/getty.target.wants/getty@tty1.service



          2. Make a copy of the getty@.service file and call it getty@tty1.service



            cp /lib/systemd/system/getty@.service /etc/systemd/system/getty@tty1.service



          3. Edit this file (the last line, must be ADDED):



            [Service]
            ...
            ExecStart=-/sbin/agetty --autologin root --noclear %I
            ...
            [Install]
            ...
            ;Alias=getty@tty1.service



          4. Make a symlink in getty.target.wants



            ln -s /etc/systemd/system/getty@tty1.service /etc/systemd/system/getty.target.wants/getty@tty1.service


          5. Reboot. It everything went fine you will be logged in as root.


          Whole forum found: Here






          share|improve this answer

























          • Edit the service how? Otherwise this would be a "link-only" Answer. Thanks!

            – Jeff Schaller
            Feb 20 at 2:36













          0












          0








          0








          1. Remove the original getty@tty1.service symlink:



            rm /etc/systemd/system/getty.target.wants/getty@tty1.service



          2. Make a copy of the getty@.service file and call it getty@tty1.service



            cp /lib/systemd/system/getty@.service /etc/systemd/system/getty@tty1.service



          3. Edit this file (the last line, must be ADDED):



            [Service]
            ...
            ExecStart=-/sbin/agetty --autologin root --noclear %I
            ...
            [Install]
            ...
            ;Alias=getty@tty1.service



          4. Make a symlink in getty.target.wants



            ln -s /etc/systemd/system/getty@tty1.service /etc/systemd/system/getty.target.wants/getty@tty1.service


          5. Reboot. It everything went fine you will be logged in as root.


          Whole forum found: Here






          share|improve this answer
















          1. Remove the original getty@tty1.service symlink:



            rm /etc/systemd/system/getty.target.wants/getty@tty1.service



          2. Make a copy of the getty@.service file and call it getty@tty1.service



            cp /lib/systemd/system/getty@.service /etc/systemd/system/getty@tty1.service



          3. Edit this file (the last line, must be ADDED):



            [Service]
            ...
            ExecStart=-/sbin/agetty --autologin root --noclear %I
            ...
            [Install]
            ...
            ;Alias=getty@tty1.service



          4. Make a symlink in getty.target.wants



            ln -s /etc/systemd/system/getty@tty1.service /etc/systemd/system/getty.target.wants/getty@tty1.service


          5. Reboot. It everything went fine you will be logged in as root.


          Whole forum found: Here







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Feb 20 at 4:37









          Michael Prokopec

          1,545218




          1,545218










          answered Feb 20 at 2:07









          user1133275user1133275

          3,649823




          3,649823












          • Edit the service how? Otherwise this would be a "link-only" Answer. Thanks!

            – Jeff Schaller
            Feb 20 at 2:36

















          • Edit the service how? Otherwise this would be a "link-only" Answer. Thanks!

            – Jeff Schaller
            Feb 20 at 2:36
















          Edit the service how? Otherwise this would be a "link-only" Answer. Thanks!

          – Jeff Schaller
          Feb 20 at 2:36





          Edit the service how? Otherwise this would be a "link-only" Answer. Thanks!

          – Jeff Schaller
          Feb 20 at 2:36

















          draft saved

          draft discarded
















































          Thanks for contributing an answer to Unix & Linux Stack Exchange!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid


          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.

          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f501750%2fscientific-linux-7x-too-much-system-hardening%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown






          Popular posts from this blog

          Peggy Mitchell

          Palaiologos

          The Forum (Inglewood, California)