Quantcast
Channel: VMware Communities : Popular Discussions - VMware Studio
Viewing all articles
Browse latest Browse all 24650

SUSE hardcoding group id for polkituser

$
0
0

In the autoyast file for SLES (suse.xsl), the polkituser is predefined to a specific group id.  So far I have tested this out on SLES11 SP1 and SP2 on VMware Studio 2.1, 2.5 and 2.6 which produced similar incorrect user-group entries.  At the moment the two packages show up are ntp and uuidd.

# id polkituser
uid=103(polkituser) gid=104(ntp) groups=104(ntp)

 

Since the package will add this in anyways, is it ok to remove this from suse.xsl?  There are many extra users and groups that probably aren't needed potentially that can cause erroneous user-group relationships.

 

 

--- suse.xsl.orig       2012-03-16 16:43:54.000000000 +0000
+++ suse.xsl    2012-03-16 16:44:52.000000000 +0000
@@ -335,11 +335,6 @@
       <userlist>u1</userlist>
     </group>
     <group>
-      <group_password>!</group_password>
-      <groupname>polkituser</groupname>
-      <userlist></userlist>
-    </group>
-    <group>

       <group_password>x</group_password>
       <groupname>wheel</groupname>
       <userlist></userlist>
@@ -840,24 +835,6 @@
       <username>man</username>
     </user>
     <user>
-      <encrypted config:type="boolean">true</encrypted>
-      <fullname>PolicyKit</fullname>
-      <gid>104</gid>
-      <home>/var/run/PolicyKit</home>
-      <password_settings>
-        <expire></expire>
-        <flag></flag>
-        <inact></inact>
-        <max>99999</max>
-        <min>0</min>
-        <warn>7</warn>
-      </password_settings>
-      <shell>/bin/false</shell>
-      <uid>103</uid>
-      <user_password>*</user_password>
-      <username>polkituser</username>
-    </user>
-    <user>

       <fullname>SSH daemon</fullname>
       <gid>65</gid>
       <home>/var/lib/sshd</home>

Viewing all articles
Browse latest Browse all 24650

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>