permission denied errors upgrading kernel
by Matthew Miller
So, I'm trying to back myself out of having the non-working 2.6.19 kernel
packages installed in rawhide. What's up with these errors?
$ ls kernel-*.rpm
kernel-2.6.18-1.2849.fc6.x86_64.rpm
kernel-devel-2.6.18-1.2849.fc6.x86_64.rpm
kernel-headers-2.6.18-1.2849.fc6.x86_64.rpm
$ sudo rpm -ivh kernel-*
Preparing... ########################################### [100%]
1:kernel-headers ########################################### [33%]
2:kernel ########################################### [67%]
cp: cannot set setfscreatecon `system_u:object_r:sbin_t:s0': Permission denied
cp: cannot set setfscreatecon `system_u:object_r:insmod_exec_t:s0': Permission denied
cp: cannot set setfscreatecon `system_u:object_r:lvm_exec_t:s0': Permission denied
3:kernel-devel ########################################### [100%]
This is accompanied by a bunch of this in the log:
audit(1165588655.467:18): avc: denied { setfscreate } for pid=3096
comm="cp" scontext=user_u:system_r:bootloader_t:s0
tcontext=user_u:system_r:bootloader_t:s0 tclass=process
audit(1165588655.563:19): avc: denied { execute_no_trans } for pid=3097
comm="mkinitrd" name="ld-2.5.90.so" dev=dm-0 ino=950275
scontext=user_u:system_r:bootloader_t:s0
tcontext=system_u:object_r:ld_so_t:s0 tclass=file
audit(1165588655.563:20): avc: denied { execute_no_trans } for pid=3098
comm="mkinitrd" name="ld-2.5.90.so" dev=dm-0 ino=950275
scontext=user_u:system_r:bootloader_t:s0
tcontext=system_u:object_r:ld_so_t:s0 tclass=file
audit(1165588655.599:21): avc: denied { execute_no_trans } for pid=3099
comm="mkinitrd" name="ld-2.5.90.so" dev=dm-0 ino=950275
scontext=user_u:system_r:bootloader_t:s0
tcontext=system_u:object_r:ld_so_t:s0 tclass=file
audit(1165588655.615:22): avc: denied { execute_no_trans } for pid=3100
comm="mkinitrd" name="ld-2.5.90.so" dev=dm-0 ino=950275
scontext=user_u:system_r:bootloader_t:s0
tcontext=system_u:object_r:ld_so_t:s0 tclass=file
audit(1165588655.639:23): avc: denied { execute_no_trans } for pid=3101
comm="mkinitrd" name="ld-2.5.90.so" dev=dm-0 ino=3112970
scontext=user_u:system_r:bootloader_t:s0
tcontext=system_u:object_r:ld_so_t:s0 tclass=file
audit(1165588655.663:24): avc: denied { execute_no_trans } for pid=3102
comm="mkinitrd" name="ld-2.5.90.so" dev=dm-0 ino=3112970
scontext=user_u:system_r:bootloader_t:s0
tcontext=system_u:object_r:ld_so_t:s0 tclass=file
audit(1165588655.691:25): avc: denied { setfscreate } for pid=3108
comm="cp" scontext=user_u:system_r:bootloader_t:s0
tcontext=user_u:system_r:bootloader_t:s0 tclass=process
audit(1165588655.695:26): avc: denied { execute_no_trans } for pid=3109
comm="mkinitrd" name="ld-2.5.90.so" dev=dm-0 ino=950275
scontext=user_u:system_r:bootloader_t:s0
tcontext=system_u:object_r:ld_so_t:s0 tclass=file
audit(1165588655.699:27): avc: denied { execute_no_trans } for pid=3110
comm="mkinitrd" name="ld-2.5.90.so" dev=dm-0 ino=950275
scontext=user_u:system_r:bootloader_t:s0
tcontext=system_u:object_r:ld_so_t:s0 tclass=file
audit(1165588655.699:28): avc: denied { execute_no_trans } for pid=3111
comm="mkinitrd" name="ld-2.5.90.so" dev=dm-0 ino=950275
scontext=user_u:system_r:bootloader_t:s0
tcontext=system_u:object_r:ld_so_t:s0 tclass=file
audit(1165588655.699:29): avc: denied { execute_no_trans } for pid=3112
comm="mkinitrd" name="ld-2.5.90.so" dev=dm-0 ino=950275
scontext=user_u:system_r:bootloader_t:s0
tcontext=system_u:object_r:ld_so_t:s0 tclass=file
audit(1165588655.699:30): avc: denied { execute_no_trans } for pid=3113
comm="mkinitrd" name="ld-2.5.90.so" dev=dm-0 ino=3112970
scontext=user_u:system_r:bootloader_t:s0
tcontext=system_u:object_r:ld_so_t:s0 tclass=file
audit(1165588655.703:31): avc: denied { execute_no_trans } for pid=3114
comm="mkinitrd" name="ld-2.5.90.so" dev=dm-0 ino=3112970
scontext=user_u:system_r:bootloader_t:s0
tcontext=system_u:object_r:ld_so_t:s0 tclass=file
audit(1165588656.087:32): avc: denied { setfscreate } for pid=3184
comm="cp" scontext=user_u:system_r:bootloader_t:s0
tcontext=user_u:system_r:bootloader_t:s0 tclass=process
audit(1165588656.091:33): avc: denied { execute_no_trans } for pid=3185
comm="mkinitrd" name="ld-2.5.90.so" dev=dm-0 ino=950275
scontext=user_u:system_r:bootloader_t:s0
tcontext=system_u:object_r:ld_so_t:s0 tclass=file
audit(1165588656.095:34): avc: denied { execute_no_trans } for pid=3186
comm="mkinitrd" name="ld-2.5.90.so" dev=dm-0 ino=950275
scontext=user_u:system_r:bootloader_t:s0
tcontext=system_u:object_r:ld_so_t:s0 tclass=file
audit(1165588656.095:35): avc: denied { execute_no_trans } for pid=3187
comm="mkinitrd" name="ld-2.5.90.so" dev=dm-0 ino=950275
scontext=user_u:system_r:bootloader_t:s0
tcontext=system_u:object_r:ld_so_t:s0 tclass=file
audit(1165588656.095:36): avc: denied { execute_no_trans } for pid=3188
comm="mkinitrd" name="ld-2.5.90.so" dev=dm-0 ino=950275
scontext=user_u:system_r:bootloader_t:s0
tcontext=system_u:object_r:ld_so_t:s0 tclass=file
audit(1165588656.099:37): avc: denied { execute_no_trans } for pid=3189
comm="mkinitrd" name="ld-2.5.90.so" dev=dm-0 ino=3112970
scontext=user_u:system_r:bootloader_t:s0
tcontext=system_u:object_r:ld_so_t:s0 tclass=file
audit(1165588656.099:38): avc: denied { execute_no_trans } for pid=3190
comm="mkinitrd" name="ld-2.5.90.so" dev=dm-0 ino=3112970
scontext=user_u:system_r:bootloader_t:s0
tcontext=system_u:object_r:ld_so_t:s0 tclass=file
Thank you, SE Linux!
I haven't rebooted yet, but presumably it isn't gonna be happy.
How do I fix this? How do I make this not ever happen? How can I tell that
it was going to happen BEFORE it happens?
--
Matthew Miller mattdm(a)mattdm.org <http://mattdm.org/>
Boston University Linux ------> <http://linux.bu.edu/>
17 years, 4 months
Re: fedora-selinux-list Digest, Vol 34, Issue 13
by stefano＠proinco.net
esto es un mensaje automatico.
al momento estare ausente en las proximas semanas. por qualquiera comunicacion de trabajo comuniquense a la oficina. saludos
stefano bagnasco
17 years, 4 months
Re: fedora-selinux-list Digest, Vol 34, Issue 12
by stefano＠proinco.net
esto es un mensaje automatico.
al momento estare ausente en las proximas semanas. por qualquiera comunicacion de trabajo comuniquense a la oficina. saludos
stefano bagnasco
17 years, 4 months
Re: fedora-selinux-list Digest, Vol 34, Issue 11
by stefano＠proinco.net
esto es un mensaje automatico.
al momento estare ausente en las proximas semanas. por qualquiera comunicacion de trabajo comuniquense a la oficina. saludos
stefano bagnasco
17 years, 4 months
Speakers for 3rd SELinux Symposium (Registration opens)
by Frank Mayer
All, we have announced the speakers for the 3rd SELinux Symposium, which will be held in Baltimore, Maryland on 12-16 March 2007. You can see the agenda, paper and tutorial abstracts, and registration information at the web site: www.selinux-symposium.org. Below is the text from the press release. Hope you can join us again at this conference. Thanks to all the authors who submitted papers. You can still participate by submitting case study and works-in-progress proposals (see web site). Frank
===============================================================
Speakers Confirmed for the
Third Annual Security Enhanced Linux Symposium and Developer Summit
Event Slated for March 12-16, 2007 in Baltimore, Maryland, USA
Baltimore, Maryland-December 11, 2006 - The Security Enhanced Linux (SELinux) Symposium announces papers and speakers for its third annual symposium. Experts from business, government, and academia will share and discuss the latest SELinux application experience, research and development results, and product plans. The event explores the popular SELinux technology and the power of flexible mandatory access control in Linux. Registration for the SELinux Symposium, scheduled for March 12-16, 2007 in Baltimore, Maryland, is now open at www.selinux-symposium.org.
The Third SELinux Symposium features two full days of SELinux-related tutorials followed by a two-day technical agenda that includes papers, presentations, and case studies by experts and practitioners with SELinux. Topics for the symposium include changes and extensions to the core SELinux technology, advances in SELinux policy management and development, and the use of SELinux to build secure system solutions. The symposium also includes an invitation-only SELinux developer summit, where the core developers and contributors of SELinux discuss upcoming technology changes, requirements, and plans.
Papers for the symposium were selected via a community review process and include authors from several organizations, including atsec, Hewlett-Packard, IBM, Pennsylvania State University, Red Hat, SPARTA, Tresys Technology, University of Maryland-Baltimore County, U.S. Joint Forces Command, and the U.S. National Security Agency. The full agenda for the symposium is available at www.selinux-symposium.org.
About the SELinux Symposium
The Security Enhanced Linux (SELinux) Symposium is an annual exchange of ideas, technology, and research involving SELinux. SELinux is emerging technology that adds flexible, strong mandatory access control security to Linux. The third annual symposium is scheduled for March 12-16, 2007 in Baltimore, Maryland, USA. This year's symposium is sponsored by Hewlett-Packard, IBM, Red Hat, and Tresys Technology. The event brings together experts from business, government, and academia to share research, development, and application experiences using SELinux. For information on registration and sponsorship opportunities, see www.selinux-symposium.org.
17 years, 4 months
Re: fedora-selinux-list Digest, Vol 34, Issue 10
by stefano＠proinco.net
esto es un mensaje automatico.
al momento estare ausente en las proximas semanas. por qualquiera comunicacion de trabajo comuniquense a la oficina. saludos
stefano bagnasco
17 years, 5 months
Re: fedora-selinux-list Digest, Vol 34, Issue 9
by stefano＠proinco.net
esto es un mensaje automatico.
al momento estare ausente en las proximas semanas. por qualquiera comunicacion de trabajo comuniquense a la oficina. saludos
stefano bagnasco
17 years, 5 months
Re: fedora-selinux-list Digest, Vol 34, Issue 8
by stefano＠proinco.net
esto es un mensaje automatico.
al momento estare ausente en las proximas semanas. por qualquiera comunicacion de trabajo comuniquense a la oficina. saludos
stefano bagnasco
17 years, 5 months
Re: fedora-selinux-list Digest, Vol 34, Issue 7
by stefano＠proinco.net
esto es un mensaje automatico.
al momento estare ausente en las proximas semanas. por qualquiera comunicacion de trabajo comuniquense a la oficina. saludos
stefano bagnasco
17 years, 5 months
Re: fedora-selinux-list Digest, Vol 34, Issue 6
by stefano＠proinco.net
esto es un mensaje automatico.
al momento estare ausente en las proximas semanas. por qualquiera comunicacion de trabajo comuniquense a la oficina. saludos
stefano bagnasco
17 years, 5 months
