Useradd/groupadd fails: failure while writing changes to /etc/passwd and /etc/group. Contexts...

Are babies of evil humanoid species inherently evil?

How did Alan Turing break the enigma code using the hint given by the lady in the bar?

When traveling to Europe from North America, do I need to purchase a different power strip?

Signed and unsigned numbers

How to secure an aircraft at a transient parking space?

Conservation of Mass and Energy

Accepted offer letter, position changed

How strictly should I take "Candidates must be local"?

How is the wildcard * interpreted as a command?

What's the "normal" opposite of flautando?

Recommendation letter by significant other if you worked with them professionally?

An alternative proof of an application of Hahn-Banach

Can I pump my MTB tire to max (55 psi / 380 kPa) without the tube inside bursting?

PTIJ: wiping amalek’s memory?

List elements digit difference sort

Difference on montgomery curve equation between EFD and RFC7748

When a wind turbine does not produce enough electricity how does the power company compensate for the loss?

What are the practical Opportunty Attack values for a bugbear, holding a reach weapon, with Polearm Mastery?

Rewrite the power sum in terms of convolution

What wound would be of little consequence to a biped but terrible for a quadruped?

When stopping and starting a tile job, what to do with the extra thinset from previous row's cleanup?

'The literal of type int is out of range' con número enteros pequeños (2 dígitos)

Do I really need to have a scientific explanation for my premise?

Was Luke Skywalker the leader of the Rebel forces on Hoth?



Useradd/groupadd fails: failure while writing changes to /etc/passwd and /etc/group. Contexts problem


Permission denied while writing a file in var/www in spite of adding me to user groupRename /etc/passwd and /etc/shadow for security reasonsFixing smb login, disk permissions, and remote accessHow can I prevent unprivileged users from accessing /etc/passwd, /etc/group, etcBoot failure: can't start TOR service and permission denied for locale-check in /etc/profile













0















Good day, ladies and gentlemen, I need your help. I have a virtual machine with Ubuntu 18.04 LTS, and I'm trying to enforce in with SELinux. I had to build and install a custom kernel out of current generic ver. for LTS with some extra flags. There were no support of SELinux in standard kernel. The first problem is: I cannot add users and groups while SELinux is enforcing or permissive. If I disable it and reboot - everything is fine.
No matter if I'm real root, or use sudo su, or unconfined user, I face the same problems.



root@hometest:~# id -Z
staff_u:staff_r:staff_t:s0

root@hometest:~# useradd testuser
useradd: failure while writing changes to /etc/passwd


Not out of space on /



root@hometest:~# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda2 20G 6.4G 13G 35% /


Permissions



root@hometest:~# ls -alsdZ /etc /etc/passwd /etc/group /etc/shadow
12 drwxr-xr-x. 136 root root system_u:object_r:etc_t:s0 12288 Jul 27 16:25 /etc
4 -rw-rw-rw-. 1 root root system_u:object_r:etc_t:s0 977 Jul 25 10:25 /etc/group
4 -rw-rw-r--. 1 root root system_u:object_r:etc_t:s0 2184 Jul 25 10:17 /etc/passwd
4 -rw-r-----. 1 root shadow system_u:object_r:shadow_t:s0 1291 Jul 25 10:17 /etc/shadow


root@hometest:~# lsattr -d /etc /etc/passwd /etc/group
-----------I--e--- /etc
--------------e--- /etc/passwd
--------------e--- /etc/group
--------------e--- /etc/shadow


Found no SELinux booleans, which could help. System is labeled according to the default policy. Tried to restore contexts of /etc/passwd, /etc/shadow and /etc/grpup - nothing changes.



root@hometest:~# sestatus 
SELinux status: enabled
SELinuxfs mount: /sys/fs/selinux
SELinux root directory: /etc/selinux
Loaded policy name: default
Current mode: permissive
Mode from config file: permissive
Policy MLS status: enabled
Policy deny_unknown status: allowed
Memory protection checking: requested (insecure)
Max kernel policy version: 31


Some info from logs:



type=AVC msg=audit(1532674348.442:472): avc:  denied  { map } for  pid=1060 comm="useradd" path="/etc/passwd" dev="sda2" ino=131866 scontext=root:sysadm_r:useradd_t:s0 tcontext=system_u:object_r:etc_t:s0 tclass=file permissive=1
Was caused by:
Missing type enforcement (TE) allow rule.

You can use audit2allow to generate a loadable module to allow this access.

type=AVC msg=audit(1532685061.535:1239): avc: denied { write } for pid=2759 comm="useradd" path="/etc/passwd.2759" dev="sda2" ino=131279 scontext=staff_u:staff_r:staff_sudo_t:s0 tcontext=staff_u:object_r:etc_t:s0 tclass=file permissive=1
Was caused by:
Missing type enforcement (TE) allow rule.

You can use audit2allow to generate a loadable module to allow this access.


I compiled a full module with all of the allow rules that were found in audit log, installed it, reloaded the policy and it solved nothing. A checked the log for one more time, found some new entries and made one more module. I tried to change context of /etc/passwd from etc_t to some others - it didn't help. Tried to use strace, but the output is really long. What else can I check o try? There is no problem on Ubuntu 16.04 LTS, what's wrong with 18.04 LTS?
What am I doing wrong? Any help is appreciated.










share|improve this question



























    0















    Good day, ladies and gentlemen, I need your help. I have a virtual machine with Ubuntu 18.04 LTS, and I'm trying to enforce in with SELinux. I had to build and install a custom kernel out of current generic ver. for LTS with some extra flags. There were no support of SELinux in standard kernel. The first problem is: I cannot add users and groups while SELinux is enforcing or permissive. If I disable it and reboot - everything is fine.
    No matter if I'm real root, or use sudo su, or unconfined user, I face the same problems.



    root@hometest:~# id -Z
    staff_u:staff_r:staff_t:s0

    root@hometest:~# useradd testuser
    useradd: failure while writing changes to /etc/passwd


    Not out of space on /



    root@hometest:~# df -h
    Filesystem Size Used Avail Use% Mounted on
    /dev/sda2 20G 6.4G 13G 35% /


    Permissions



    root@hometest:~# ls -alsdZ /etc /etc/passwd /etc/group /etc/shadow
    12 drwxr-xr-x. 136 root root system_u:object_r:etc_t:s0 12288 Jul 27 16:25 /etc
    4 -rw-rw-rw-. 1 root root system_u:object_r:etc_t:s0 977 Jul 25 10:25 /etc/group
    4 -rw-rw-r--. 1 root root system_u:object_r:etc_t:s0 2184 Jul 25 10:17 /etc/passwd
    4 -rw-r-----. 1 root shadow system_u:object_r:shadow_t:s0 1291 Jul 25 10:17 /etc/shadow


    root@hometest:~# lsattr -d /etc /etc/passwd /etc/group
    -----------I--e--- /etc
    --------------e--- /etc/passwd
    --------------e--- /etc/group
    --------------e--- /etc/shadow


    Found no SELinux booleans, which could help. System is labeled according to the default policy. Tried to restore contexts of /etc/passwd, /etc/shadow and /etc/grpup - nothing changes.



    root@hometest:~# sestatus 
    SELinux status: enabled
    SELinuxfs mount: /sys/fs/selinux
    SELinux root directory: /etc/selinux
    Loaded policy name: default
    Current mode: permissive
    Mode from config file: permissive
    Policy MLS status: enabled
    Policy deny_unknown status: allowed
    Memory protection checking: requested (insecure)
    Max kernel policy version: 31


    Some info from logs:



    type=AVC msg=audit(1532674348.442:472): avc:  denied  { map } for  pid=1060 comm="useradd" path="/etc/passwd" dev="sda2" ino=131866 scontext=root:sysadm_r:useradd_t:s0 tcontext=system_u:object_r:etc_t:s0 tclass=file permissive=1
    Was caused by:
    Missing type enforcement (TE) allow rule.

    You can use audit2allow to generate a loadable module to allow this access.

    type=AVC msg=audit(1532685061.535:1239): avc: denied { write } for pid=2759 comm="useradd" path="/etc/passwd.2759" dev="sda2" ino=131279 scontext=staff_u:staff_r:staff_sudo_t:s0 tcontext=staff_u:object_r:etc_t:s0 tclass=file permissive=1
    Was caused by:
    Missing type enforcement (TE) allow rule.

    You can use audit2allow to generate a loadable module to allow this access.


    I compiled a full module with all of the allow rules that were found in audit log, installed it, reloaded the policy and it solved nothing. A checked the log for one more time, found some new entries and made one more module. I tried to change context of /etc/passwd from etc_t to some others - it didn't help. Tried to use strace, but the output is really long. What else can I check o try? There is no problem on Ubuntu 16.04 LTS, what's wrong with 18.04 LTS?
    What am I doing wrong? Any help is appreciated.










    share|improve this question

























      0












      0








      0








      Good day, ladies and gentlemen, I need your help. I have a virtual machine with Ubuntu 18.04 LTS, and I'm trying to enforce in with SELinux. I had to build and install a custom kernel out of current generic ver. for LTS with some extra flags. There were no support of SELinux in standard kernel. The first problem is: I cannot add users and groups while SELinux is enforcing or permissive. If I disable it and reboot - everything is fine.
      No matter if I'm real root, or use sudo su, or unconfined user, I face the same problems.



      root@hometest:~# id -Z
      staff_u:staff_r:staff_t:s0

      root@hometest:~# useradd testuser
      useradd: failure while writing changes to /etc/passwd


      Not out of space on /



      root@hometest:~# df -h
      Filesystem Size Used Avail Use% Mounted on
      /dev/sda2 20G 6.4G 13G 35% /


      Permissions



      root@hometest:~# ls -alsdZ /etc /etc/passwd /etc/group /etc/shadow
      12 drwxr-xr-x. 136 root root system_u:object_r:etc_t:s0 12288 Jul 27 16:25 /etc
      4 -rw-rw-rw-. 1 root root system_u:object_r:etc_t:s0 977 Jul 25 10:25 /etc/group
      4 -rw-rw-r--. 1 root root system_u:object_r:etc_t:s0 2184 Jul 25 10:17 /etc/passwd
      4 -rw-r-----. 1 root shadow system_u:object_r:shadow_t:s0 1291 Jul 25 10:17 /etc/shadow


      root@hometest:~# lsattr -d /etc /etc/passwd /etc/group
      -----------I--e--- /etc
      --------------e--- /etc/passwd
      --------------e--- /etc/group
      --------------e--- /etc/shadow


      Found no SELinux booleans, which could help. System is labeled according to the default policy. Tried to restore contexts of /etc/passwd, /etc/shadow and /etc/grpup - nothing changes.



      root@hometest:~# sestatus 
      SELinux status: enabled
      SELinuxfs mount: /sys/fs/selinux
      SELinux root directory: /etc/selinux
      Loaded policy name: default
      Current mode: permissive
      Mode from config file: permissive
      Policy MLS status: enabled
      Policy deny_unknown status: allowed
      Memory protection checking: requested (insecure)
      Max kernel policy version: 31


      Some info from logs:



      type=AVC msg=audit(1532674348.442:472): avc:  denied  { map } for  pid=1060 comm="useradd" path="/etc/passwd" dev="sda2" ino=131866 scontext=root:sysadm_r:useradd_t:s0 tcontext=system_u:object_r:etc_t:s0 tclass=file permissive=1
      Was caused by:
      Missing type enforcement (TE) allow rule.

      You can use audit2allow to generate a loadable module to allow this access.

      type=AVC msg=audit(1532685061.535:1239): avc: denied { write } for pid=2759 comm="useradd" path="/etc/passwd.2759" dev="sda2" ino=131279 scontext=staff_u:staff_r:staff_sudo_t:s0 tcontext=staff_u:object_r:etc_t:s0 tclass=file permissive=1
      Was caused by:
      Missing type enforcement (TE) allow rule.

      You can use audit2allow to generate a loadable module to allow this access.


      I compiled a full module with all of the allow rules that were found in audit log, installed it, reloaded the policy and it solved nothing. A checked the log for one more time, found some new entries and made one more module. I tried to change context of /etc/passwd from etc_t to some others - it didn't help. Tried to use strace, but the output is really long. What else can I check o try? There is no problem on Ubuntu 16.04 LTS, what's wrong with 18.04 LTS?
      What am I doing wrong? Any help is appreciated.










      share|improve this question














      Good day, ladies and gentlemen, I need your help. I have a virtual machine with Ubuntu 18.04 LTS, and I'm trying to enforce in with SELinux. I had to build and install a custom kernel out of current generic ver. for LTS with some extra flags. There were no support of SELinux in standard kernel. The first problem is: I cannot add users and groups while SELinux is enforcing or permissive. If I disable it and reboot - everything is fine.
      No matter if I'm real root, or use sudo su, or unconfined user, I face the same problems.



      root@hometest:~# id -Z
      staff_u:staff_r:staff_t:s0

      root@hometest:~# useradd testuser
      useradd: failure while writing changes to /etc/passwd


      Not out of space on /



      root@hometest:~# df -h
      Filesystem Size Used Avail Use% Mounted on
      /dev/sda2 20G 6.4G 13G 35% /


      Permissions



      root@hometest:~# ls -alsdZ /etc /etc/passwd /etc/group /etc/shadow
      12 drwxr-xr-x. 136 root root system_u:object_r:etc_t:s0 12288 Jul 27 16:25 /etc
      4 -rw-rw-rw-. 1 root root system_u:object_r:etc_t:s0 977 Jul 25 10:25 /etc/group
      4 -rw-rw-r--. 1 root root system_u:object_r:etc_t:s0 2184 Jul 25 10:17 /etc/passwd
      4 -rw-r-----. 1 root shadow system_u:object_r:shadow_t:s0 1291 Jul 25 10:17 /etc/shadow


      root@hometest:~# lsattr -d /etc /etc/passwd /etc/group
      -----------I--e--- /etc
      --------------e--- /etc/passwd
      --------------e--- /etc/group
      --------------e--- /etc/shadow


      Found no SELinux booleans, which could help. System is labeled according to the default policy. Tried to restore contexts of /etc/passwd, /etc/shadow and /etc/grpup - nothing changes.



      root@hometest:~# sestatus 
      SELinux status: enabled
      SELinuxfs mount: /sys/fs/selinux
      SELinux root directory: /etc/selinux
      Loaded policy name: default
      Current mode: permissive
      Mode from config file: permissive
      Policy MLS status: enabled
      Policy deny_unknown status: allowed
      Memory protection checking: requested (insecure)
      Max kernel policy version: 31


      Some info from logs:



      type=AVC msg=audit(1532674348.442:472): avc:  denied  { map } for  pid=1060 comm="useradd" path="/etc/passwd" dev="sda2" ino=131866 scontext=root:sysadm_r:useradd_t:s0 tcontext=system_u:object_r:etc_t:s0 tclass=file permissive=1
      Was caused by:
      Missing type enforcement (TE) allow rule.

      You can use audit2allow to generate a loadable module to allow this access.

      type=AVC msg=audit(1532685061.535:1239): avc: denied { write } for pid=2759 comm="useradd" path="/etc/passwd.2759" dev="sda2" ino=131279 scontext=staff_u:staff_r:staff_sudo_t:s0 tcontext=staff_u:object_r:etc_t:s0 tclass=file permissive=1
      Was caused by:
      Missing type enforcement (TE) allow rule.

      You can use audit2allow to generate a loadable module to allow this access.


      I compiled a full module with all of the allow rules that were found in audit log, installed it, reloaded the policy and it solved nothing. A checked the log for one more time, found some new entries and made one more module. I tried to change context of /etc/passwd from etc_t to some others - it didn't help. Tried to use strace, but the output is really long. What else can I check o try? There is no problem on Ubuntu 16.04 LTS, what's wrong with 18.04 LTS?
      What am I doing wrong? Any help is appreciated.







      permissions security selinux






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Jul 30 '18 at 20:20









      Igor KlyuchnikovIgor Klyuchnikov

      12




      12






















          1 Answer
          1






          active

          oldest

          votes


















          0














          It seems to be a bug. I have also been hit by it.



          Running strace on groupadd, the failures is after groupadd writting to /proc/thread-self/attr/fscreate



          SELinux is not very well supported in either Debian or Ubuntu. If you like SELinux, consider using Redhat or Centos.





          share








          New contributor




          Ramón García is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.




















            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "89"
            };
            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: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            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%2faskubuntu.com%2fquestions%2f1060897%2fuseradd-groupadd-fails-failure-while-writing-changes-to-etc-passwd-and-etc-gr%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














            It seems to be a bug. I have also been hit by it.



            Running strace on groupadd, the failures is after groupadd writting to /proc/thread-self/attr/fscreate



            SELinux is not very well supported in either Debian or Ubuntu. If you like SELinux, consider using Redhat or Centos.





            share








            New contributor




            Ramón García is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
            Check out our Code of Conduct.

























              0














              It seems to be a bug. I have also been hit by it.



              Running strace on groupadd, the failures is after groupadd writting to /proc/thread-self/attr/fscreate



              SELinux is not very well supported in either Debian or Ubuntu. If you like SELinux, consider using Redhat or Centos.





              share








              New contributor




              Ramón García is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
              Check out our Code of Conduct.























                0












                0








                0







                It seems to be a bug. I have also been hit by it.



                Running strace on groupadd, the failures is after groupadd writting to /proc/thread-self/attr/fscreate



                SELinux is not very well supported in either Debian or Ubuntu. If you like SELinux, consider using Redhat or Centos.





                share








                New contributor




                Ramón García is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.










                It seems to be a bug. I have also been hit by it.



                Running strace on groupadd, the failures is after groupadd writting to /proc/thread-self/attr/fscreate



                SELinux is not very well supported in either Debian or Ubuntu. If you like SELinux, consider using Redhat or Centos.






                share








                New contributor




                Ramón García is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.








                share


                share






                New contributor




                Ramón García is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.









                answered 1 min ago









                Ramón GarcíaRamón García

                1




                1




                New contributor




                Ramón García is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.





                New contributor





                Ramón García is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.






                Ramón García is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Ask Ubuntu!


                    • 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%2faskubuntu.com%2fquestions%2f1060897%2fuseradd-groupadd-fails-failure-while-writing-changes-to-etc-passwd-and-etc-gr%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

                    List of shipwrecks in 1808...

                    Is there a lightweight tool to crop images quickly?Cropping Images using Command Line Tools OnlyHow to crop...

                    Unit packagekit.service is masked Announcing the arrival of Valued Associate #679: Cesar...