search for: chcon

...#39;'m running puppet-0.24.6-1.el5 on Centos 5.2. [ddb@prcapp02 ~]$ sudo service puppet start Starting puppet: /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:735:in `use'': Got 16 failure(s) while initializing: change from absent to system_u failed: Execution of ''/usr/bin/chcon -h -u system_u /var/log/puppet'' returned 1: /usr/bin/chcon: can''t apply partial context to unlabeled file /var/log/puppet (RuntimeError) ; change from absent to object_r failed: Execution of ''/usr/bin/chcon -h -r object_r /var/log/puppet'' returned 1: /usr/bin/chc...

...ckage ownership. This guest starts without activating any Ethernet i/f if that has any bearing on the matter. # sealert -a /var/log/audit/audit.log | more found 1 alerts in /var/log/audit/audit.log -------------------------------------------------------- Summary: SELinux is preventing /usr/bin/chcon "mac_admin" access . Detailed Description: SELinux denied access requested by chcon. It is not expected that this access is required by chcon and this access may signal an intrusion attempt. It is also possible that the specific version or configuration of the application is causing it...

On May 4, 2018, at 3:03 PM, Akemi Yagi <amyagi at gmail.com> wrote: > > On Fri, May 4, 2018 at 12:03 PM, Warren Young <warren at etr-usa.com> wrote: >> >> $ sudo chcon -R -t samba_share_t /path/to/share > > Updated the page as suggested. Thanks. Thanks! I now see another instance of this in section 3. Instead of copying the text verbatim, it should probably be: chcon -R -t samba_share_t /mnt/data ?in order to match the text above it.

...ren at etr-usa.com> > wrote: > > On May 4, 2018, at 3:03 PM, Akemi Yagi <amyagi at gmail.com> wrote: > > > > > > On Fri, May 4, 2018 at 12:03 PM, Warren Young <warren at etr-usa.com > > > > wrote: > > > > > > > > $ sudo chcon -R -t samba_share_t /path/to/share > > > > > > Updated the page as suggested. Thanks. > > > > Thanks! > > > > I now see another instance of this in section 3. Instead of > > copying the text verbatim, it should probably be: > > > >...

Hi, I'm confused, why can root not change context of a directory ? I've moved a mysql dir from /var/lib to another drive. But running sudo chcon -R -t mysqld_t ./mysql Yields a screen full of messages such as chcon: failed to change context of ?schema_table_lock_waits.frm? to ?system_u:object_r:mysqld_t:s0?: Permission denied (and yes, mysql was shut down before the move and is till shut down).

...ntOS 7: $ sudo semanage fcontext ?at samba_share_t /path/to/share ?noise noise noise? semanage: error: unrecognized arguments: samba_share_t /path/to/share That and the following restorecon command can be replaced by a single shorter command, which also fixes the symptom: $ sudo chcon -R -t samba_share_t /path/to/share

On Fri, May 4, 2018 at 2:26 PM, Warren Young <warren at etr-usa.com> wrote: > On May 4, 2018, at 3:03 PM, Akemi Yagi <amyagi at gmail.com> wrote: >> >> On Fri, May 4, 2018 at 12:03 PM, Warren Young <warren at etr-usa.com> wrote: >>> >>> $ sudo chcon -R -t samba_share_t /path/to/share >> >> Updated the page as suggested. Thanks. > > Thanks! > > I now see another instance of this in section 3. Instead of copying the text verbatim, it should probably be: > > chcon -R -t samba_share_t /mnt/data > > ?in orde...

...#39;/usr/sbin/nrpe'': source => "puppet://$puppetserver/modules/nagios/nagios/libexec/nrpe", owner => ''root'', group => ''root'', notify => Service[''nagios''], } exec { ''chcon'': command => "/usr/bin/chcon -R -t bin_t /usr/sbin/nrpe", subscribe => File[''/usr/sbin/nrpe''], } What happens is that Puppet always updates the file because the seltype appears to be wrong. This means that the exec is always called and the servi...

On 05/04/2018 04:05 PM, Warren Young wrote: > On May 4, 2018, at 4:11 PM, Louis Lagendijk <louis at fazant.net> wrote: >> The comment is correct: chcon will not survive a relabel. You need to >> update the database first (semanage fcontext) and then let a relabel >> apply the new context. > Alright, then why do I get that error when I give the command from this morning?s wiki text, and how do I avoid it? # od -c sudo semanage fcont...

Am 10.02.2017 um 16:59 schrieb Tim Smith: > Hi, > > I'm confused, why can root not change context of a directory ? > > I've moved a mysql dir from /var/lib to another drive. > > But running sudo chcon -R -t mysqld_t ./mysql > > Yields a screen full of messages such as > > chcon: failed to change context of ?schema_table_lock_waits.frm? to > ?system_u:object_r:mysqld_t:s0?: Permission denied > > (and yes, mysql was shut down before the move and is till shut down). Because my...

On May 5, 2018, at 12:04 AM, Gordon Messmer <gordon.messmer at gmail.com> wrote: > > On 05/04/2018 04:05 PM, Warren Young wrote: >> On May 4, 2018, at 4:11 PM, Louis Lagendijk <louis at fazant.net> wrote: >>> The comment is correct: chcon will not survive a relabel. You need to >>> update the database first (semanage fcontext) and then let a relabel >>> apply the new context. >> Alright, then why do I get that error when I give the command from this morning?s wiki text, and how do I avoid it? > > # od...

...les in directories that SELinux policy can not predict. These directories have to be labeled with a file context which httpd can accesss. Allowing Access If you want to change the file context of trac-rewrite.log so that the httpd daemon can access it, you need to execute it using chcon -t httpd_sys_content_t.trac-rewrite.log. You can look at the httpd_selinux man page for additional information. Additional Information Source Context user_u:system_r:httpd_t Target Context system_u:object_r:etc_t Target Objects trac-rewrite.lo...

...e fcontext ?at samba_share_t /path/to/share > ?noise noise noise? > semanage: error: unrecognized arguments: samba_share_t /path/to/share > > That and the following restorecon command can be replaced by a single shorter command, which also fixes the symptom: > > $ sudo chcon -R -t samba_share_t /path/to/share Updated the page as suggested. Thanks. Akemi

...hare_t /path/to/share What is "noise" exactly?? I don't get errors from that command: # semanage fcontext -at samba_share_t /srv/samba # > That and the following restorecon command can be replaced by a single shorter command, which also fixes the symptom: As others pointed out, chcon is not a replacement for registering a persistent file context.

On May 4, 2018, at 5:13 PM, Gordon Messmer <gordon.messmer at gmail.com> wrote: > > On 05/04/2018 12:03 PM, Warren Young wrote: >> ?there is a command down in section 2 that gives an error here on CentOS 7: >> >> $ sudo semanage fcontext ?at samba_share_t /path/to/share >> ?noise noise noise? >> semanage: error: unrecognized arguments:

On May 4, 2018, at 4:11 PM, Louis Lagendijk <louis at fazant.net> wrote: > > The comment is correct: chcon will not survive a relabel. You need to > update the database first (semanage fcontext) and then let a relabel > apply the new context. Alright, then why do I get that error when I give the command from this morning?s wiki text, and how do I avoid it?

I tried to run chcon to set SELinux labels on a guestmounted dir and got: chcon: failed to change context of `authorized_keys' to `system_u:object_r:ssh_home_t:s0': Operation not supported I'm guessing that you need to pass 'seclabel' or 'user_xattr' or some such mount option to guestmount...

On 4 May 2018 at 19:49, Warren Young <warren at etr-usa.com> wrote: > On May 4, 2018, at 5:13 PM, Gordon Messmer <gordon.messmer at gmail.com> > wrote: > > > > On 05/04/2018 12:03 PM, Warren Young wrote: > >> ?there is a command down in section 2 that gives an error here on > CentOS 7: > >> > >> $ sudo semanage fcontext ?at

...pper/VolGroup01-* lrwxrwxrwx. root root system_u:object_r:quota_db_t:s0 /dev/mapper/VolGroup01-lv_staff -> ../dm-25 lrwxrwxrwx. root root system_u:object_r:device_t:s0 /dev/mapper/VolGroup01-lv_student -> ../dm-24 I have tried to correct this with the Logical Volume active and mounted using chcon -v --reference /dev/mapper/VolGroup01-lv_student /dev/mapper/VolGroup01-lv_staff and while this command completes the context is not changed. Can someone confirm or deny that making the Logical Volume inactive and then repeating the chcon should change the link to the correct context? Thanks for...

...t;negativebinomial at gmail.com>wrote: > I built a new VM under KVM today and I've been getting a slew of message > that selinux is blocking virtmanager from reading the new image. This > doesn't seem to be doing any harm, but I wanted to check whether I should > simply run chcon on the image (if I can). > > Virtmanager show up as usr_t, as do my other vm images, but the new one is > svirt_image_t. > > The selinux error says it denied a read access to virtmanager but that it > is not expected that the access is required. > > I tried running restoreco...