On Wed, Sep 20, 2017 at 05:54:19PM +0800, Ed Greshko wrote:
> On 09/20/17 17:33, Frédéric Bron wrote:
> >> ls -Zd /etc
> > system_u:object_r:etc_t:s0 /etc/
> >
> > looks fine?
> >
>
> Yes, perfectly fine...
>
> How the output of this?
>
> restorecon -F -v /etc/passwd
>
> FWIW, looking in /etc/s
On 09/20/17 18:13, Frédéric Bron wrote:
>> How the output of this?
>>
>> restorecon -F -v /etc/passwd
> Relabeled /etc/passwd from unconfined_u:object_r:passwd_file_t:s0 to
> system_u:object_r:passwd_file_t:s0
>
> So the force option was necessary?
Yes But I don't think unconfined_u:object_r:
> How the output of this?
>
> restorecon -F -v /etc/passwd
Relabeled /etc/passwd from unconfined_u:object_r:passwd_file_t:s0 to
system_u:object_r:passwd_file_t:s0
So the force option was necessary?
___
users mailing list -- users@lists.fedoraproject.org
On 09/20/17 17:33, Frédéric Bron wrote:
>> ls -Zd /etc
> system_u:object_r:etc_t:s0 /etc/
>
> looks fine?
>
Yes, perfectly fine...
How the output of this?
restorecon -F -v /etc/passwd
FWIW, looking in /etc/selinux/targeted/contexts/files/file_contexts I see
/etc/passwd[-\+]? --
> ls -Zd /etc
system_u:object_r:etc_t:s0 /etc/
looks fine?
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
On 09/20/17 16:22, Frédéric Bron wrote:
>> A few questions
>>
>> 1. Is the file /.autorelabel gone? It should be, after a relabel.
> yes and I saw the relabeling operation. After that, the computer rebooted.
>
>> 2. Do you happen to know what the labels were previously?
> Halas, I do not kno
> A few questions
>
> 1. Is the file /.autorelabel gone? It should be, after a relabel.
yes and I saw the relabeling operation. After that, the computer rebooted.
> 2. Do you happen to know what the labels were previously?
Halas, I do not know.
> 3. If you do a "restorecon /etc/passwd"
On 09/19/2017 07:14 PM, Rick Stevens wrote:
On 09/18/2017 11:24 AM, Frédéric Bron wrote:
Hi,
I created a new user using kuser.
I wanted to change his password with passwd user :
$ su
$ passwd user
I got the following error:
passwd: Erreur de manipulation du jeton d'authentification
Then I did
On 09/20/17 14:14, Frédéric Bron wrote:
>> What is the label for /etc/passwd and /etc/shadow, this may be unrelated but
>> I have experienced a similar issue and the /etc/shadow was not labelled
>> correctly by SELinux.
> after relabeling I have:
> # ls -Z /etc/{passwd,shadow}
> unconfined_u:object
> What is the label for /etc/passwd and /etc/shadow, this may be unrelated but
> I have experienced a similar issue and the /etc/shadow was not labelled
> correctly by SELinux.
after relabeling I have:
# ls -Z /etc/{passwd,shadow}
unconfined_u:object_r:passwd_file_t:s0 /etc/passwd
unconfined_
On 09/18/2017 11:24 AM, Frédéric Bron wrote:
> Hi,
>
> I created a new user using kuser.
> I wanted to change his password with passwd user :
> $ su
> $ passwd user
>
> I got the following error:
> passwd: Erreur de manipulation du jeton d'authentification
>
> Then I did:
> $ setenforce 0
> and
On 18 September 2017 at 14:24, Frédéric Bron wrote:
> Hi,
>
> I created a new user using kuser.
> I wanted to change his password with passwd user :
> $ su
> $ passwd user
>
> I got the following error:
> passwd: Erreur de manipulation du jeton d'authentification
>
> Then I did:
> $ setenforce 0
Hi,
I created a new user using kuser.
I wanted to change his password with passwd user :
$ su
$ passwd user
I got the following error:
passwd: Erreur de manipulation du jeton d'authentification
Then I did:
$ setenforce 0
and it worked.
Later, I reenabled selinux:
$ setenfoce 1
and the user tri
On 05/27/2014 01:35 PM, arag...@dcsnow.com wrote:
> > Looks like the milter-greylist.sock is mislabeled. What directory is it
> > in? Why isn't it in /run?
>
> Well, see, I was following a guide (probably old) that pointed
> Sendmail to /var/milter-greylist so I just changed the greylist.conf
> fi
> Looks like the milter-greylist.sock is mislabeled. What directory is
it
> in? Why isn't it in /run?
Well, see, I was
following a guide (probably old) that pointed Sendmail to
/var/milter-greylist so I just changed the greylist.conf file instead of
changing the semdial.mc file.
Now that you
On 05/27/2014 12:55 PM, arag...@dcsnow.com wrote:
>
> Hi,
>
> So I'm trying to get milter-greylist working with
> selinux
> and I seem to have a problem. It doesn't seem to know
> what
> milter-greylist is trying to access so I can't add a rule to fix
> it.Â
> Here is what I see in /var/log/mes
Hi,
So I'm trying to get milter-greylist working with
selinux
and I seem to have a problem. It doesn't seem to know
what
milter-greylist is trying to access so I can't add a rule to fix
it.Â
Here is what I see in /var/log/message when I try to run
systemctl start
milter-greylist
May 27 12:47
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/22/2011 09:04 AM, François Patte wrote:
> Bonjour,
>
> I tried to run the selinux system manager from the menu administration
> and it failed
>
> So I tried to run it from a terminal:
>
> /usr/share/system-config-selinux/system-config-seli
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bonjour,
I tried to run the selinux system manager from the menu administration
and it failed
So I tried to run it from a terminal:
/usr/share/system-config-selinux/system-config-selinux.py
answer:
Traceback (most recent call last):
File "/u
On Tue, Nov 23, 2010 at 2:30 PM, Daniel J Walsh wrote:
>> Thanks, Daniel. Let me add some more information:
>>
>> /home/psmith/programs/myprogram: error while loading shared libraries:
>> /home/psmith/gurobi400/linux64/lib/libgurobi.so.4.0.0: cannot enable
>> executable stack as shared object requ
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/23/2010 09:28 AM, Paul Smith wrote:
> On Tue, Nov 23, 2010 at 2:22 PM, Daniel J Walsh wrote:
>>>> I am experiencing the following problem with SELinux on F14:
>>>>
>>>> Nov 23 12:49:33 localhost kern
On Tue, Nov 23, 2010 at 2:22 PM, Daniel J Walsh wrote:
>>> I am experiencing the following problem with SELinux on F14:
>>>
>>> Nov 23 12:49:33 localhost kernel: [ 4881.260409] type=1400
>>> audit(1290516573.348:31748): avc: denied { execstack } for
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/23/2010 07:56 AM, Alan Cox wrote:
> On Tue, 23 Nov 2010 12:52:41 +
> Paul Smith wrote:
>
>> Dear All,
>>
>> I am experiencing the following problem with SELinux on F14:
>>
>> Nov 23 12:49:33 loc
On Tue, 23 Nov 2010 12:52:41 +
Paul Smith wrote:
> Dear All,
>
> I am experiencing the following problem with SELinux on F14:
>
> Nov 23 12:49:33 localhost kernel: [ 4881.260409] type=1400
> audit(1290516573.348:31748): avc: denied { execstack } for
> pid=
Dear All,
I am experiencing the following problem with SELinux on F14:
Nov 23 12:49:33 localhost kernel: [ 4881.260409] type=1400
audit(1290516573.348:31748): avc: denied { execstack } for
pid=14597 comm="myprogram"
scontext=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c102
25 matches
Mail list logo
