similar to: System Recovery

First, has anyone successfully installed the HPLIP driver from HP in CentOS4? Second, does that driver really provide the toolbox which includes handy stuff like ink level monitoring? I got the source RPM (hplip-0.9.4-1.1.src.rpm) from an FC4 testing mirror, which rebuilt fine on this machine: . . . + umask 022 + cd /home/rj/rpmbuild/BUILD + cd

Has anyone had any success in rebuilding seamonkey 2.0.4 for CentOS 5 (32-bit)? I'm currently running seamonkey-2.0-1 which I rebuilt last November. Sadly, I have no idea where the SRPM originated. I found seamonkey-2.0.4-1.fc12.src.rpm and seamonkey-2.0.4-1.fc12.src.rpm, downloaded and got to 0th base: [rj at madeleine Downloads]$ rpmbuild --rebuild

libselinux defaults to "targeted" when no SELINUXTYPE is specified in /etc/config/selinux. Hence do the same here, instead of failing because of the missing key. Add a slow test for checking SELinux relabeling on a Fedora 27 guest, both with no changes, and with a modified configuration. --- customize/Makefile.am | 2 ++ customize/SELinux_relabel.ml | 14 ++++++++++--

I have some centos 4.4 server. i have disable selinux for some software problem: # cat /etc/selinux/config # This file controls the state of SELinux on the system. # SELINUX= can take one of these three values: # enforcing - SELinux security policy is enforced. # permissive - SELinux prints warnings instead of enforcing. # disabled - SELinux is fully disabled. SELINUX=disable #

Hey guys, For some reason I can't seem to enable SELinux on this one host. Here's my SELinux config file: [root at beta-new:~] #cat /etc/sysconfig/selinux # This file controls the state of SELinux on the system. # SELINUX= can take one of these three values: # enforcing - SELinux security policy is enforced. # permissive - SELinux prints warnings instead of enforcing. #

This shouldn't change the effect of this code. --- mlcustomize/SELinux_relabel.ml | 121 ++++++++++++++++++--------------- 1 file changed, 65 insertions(+), 56 deletions(-) diff --git a/mlcustomize/SELinux_relabel.ml b/mlcustomize/SELinux_relabel.ml index 44995df..5df1f08 100644 --- a/mlcustomize/SELinux_relabel.ml +++ b/mlcustomize/SELinux_relabel.ml @@ -28,65 +28,74 @@ module G = Guestfs

El 13 de abril de 2017 9:56:00 GMT-04:00, Rowland Penny via samba <samba at lists.samba.org> escribió: >On Thu, 13 Apr 2017 09:28:09 -0400 >Rommel Rodriguez Toirac via samba <samba at lists.samba.org> wrote: > >> >> I follow step by step Setting up a Share Using Windows ACLs from >> wiki, but still I have an Access denied when try to change the >>

By any change, is it a VPS? I know that my CloudAtCost (very cheap but extremely unreliable provider) prevents you from using SeLinux on their Centos image. On 12/29/2014 9:58 PM, Tim Dunphy wrote: > Hey guys, > > For some reason I can't seem to enable SELinux on this one host. > > Here's my SELinux config file: > > [root at beta-new:~] #cat

What possible reason could they have for that? On 30/12/14 02:17 AM, Laurent Dumont wrote: > By any change, is it a VPS? I know that my CloudAtCost (very cheap but > extremely unreliable provider) prevents you from using SeLinux on their > Centos image. > > On 12/29/2014 9:58 PM, Tim Dunphy wrote: >> Hey guys, >> >> For some reason I can't seem to enable

I saw the latest update announcements on the announce list, so I ran "yum check-update" and did not see seamonkey in the list. Which I guess makes sense, since it's a name change from mozilla. However, devhelp is in the list, and "yum update devhelp" pulls in seamonkey as a dependency. This seems like a sort of backdoor way to get seamonkey onto the system. Did these

Hello, When I use a standard Redhat kernel, it's ok. Everything's working right. That the Linux bridge configuration does not work afer I upgraded the kernel to 2.6.33.2. Why? [root at node78 ~]# cat /etc/issue Red Hat Enterprise Linux Server release 5.5 (Tikanga) Kernel \r on an \m [root at node78 ~]# uname -a Linux node78 2.6.33.2 #1 SMP Wed Apr 14 10:10:29 CST 2010 x86_64

On Mon, May 18, 2020 at 11:12:29AM +0200, Pino Toscano wrote: > On Tuesday, 5 May 2020 17:44:15 CEST Richard W.M. Jones wrote: > > https://bugzilla.redhat.com/show_bug.cgi?id=1828952#c2 > > I think we need to do a different approach than this patch. > > The biggest thing is that currently we check only SELINUXTYPE for the > actual policy, however we do not check SELINUX

On Tuesday, 5 May 2020 17:44:15 CEST Richard W.M. Jones wrote: > https://bugzilla.redhat.com/show_bug.cgi?id=1828952#c2 I think we need to do a different approach than this patch. The biggest thing is that currently we check only SELINUXTYPE for the actual policy, however we do not check SELINUX in case SELinux is in enforcing mode at all. IMHO we rather need to read

Rewrite the relabel API to read the policy configured in the guest, invoking setfiles (added as part of the appliance, as part of policycoreutils) to relabel the specified root. In case of failure at any point of the process, a touch of .autorelabel in the root is tried as last-attempt measure to do the relabel. Considering that running SELinux tools in the appliance might be affected by the

https://bugzilla.redhat.com/show_bug.cgi?id=1828952#c2 If SELINUXTYPE is set to some value other than targeted then we look for a directory /etc/selinux/<SELINUXTYPE> which does not exist. However this should not cause a fatal error. Using setfiles to do the relabelling immediately is a nice-to-have, but we can fallback to using autorelabel if we're unable to achieve it. ---

Do not attempt to relabel a guest in case its SELinux enforcing mode is not "enforcing", as it is either pointless, or it may fail because of an invalid policy configured. --- mlcustomize/SELinux_relabel.ml | 26 +++++++++++++++++++++++++- 1 file changed, 25 insertions(+), 1 deletion(-) diff --git a/mlcustomize/SELinux_relabel.ml b/mlcustomize/SELinux_relabel.ml index 647aeda..db00e59

Since it is available only in OCaml >= 4.03, which is higher than our requirement, add a simple reimplementation of it. Fixes commit 719d68fa247cc3885ecf7ec1c010faf83267d786. --- customize/SELinux_relabel.ml | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/customize/SELinux_relabel.ml b/customize/SELinux_relabel.ml index e7d440c29..7cc166edb 100644 ---

I'm probably dense - CentOS 4.1 # cat /etc/sysconfig/selinux ..snip... SELINUXTYPE=targeted # su - Alec # tail -n 3 /var/log/messages Aug 31 08:48:26 srv1 su(pam_unix)[31435]: session opened for user Alec by root(uid=0) Aug 31 08:48:26 srv1 su[31435]: Warning! Could not relabel /dev/pts/0 with user_u:object_r:devpts_t, not relabeling.Operation not permitted Aug 31 08:48:27 srv1

The raw socket option in the kernel only allows privileged processes to open them. Selinux controls which privileged processes have the right to. To allow an unprivileged process to access a raw socket you will need to write a proxy daemon that runs privileged and is allowed in selinux to create a raw socket. This daemon can then provide a unix socket to unprivileged processes whose access can

Dear R users, I'm pleased to announce that the first major update to the MAVIS package (Meta Analysis via Shiny) has been released to CRAN. MAVIS: Meta Analysis via Shiny v1.1 "Smiling Fox" has expanded greatly over the last couple of months to include the following. - User interface has been improved with the ?shinyBS? package and icons. - Support for single case design,