Discussion:
Bug#805493: release-notes: Document how to migrate SELinux policies from the old store to the new one
(too old to reply)
Laurent Bigonville
2015-11-18 18:40:02 UTC
Permalink
Package: release-notes
Severity: normal
User: selinux-***@lists.alioth.debian.org
Usertags: selinux

Hi,

With the new SELinux userspace 2.4, the policy store has moved from
/etc/selinux/<policy_name> to /var/lib/selinux/<policy_name> (the format
of the store has also changed).

The packages from the refpolicy (selinux-policy-default and
selinux-policy-mls) should be fixed to automatically migrate the the new
store (ATM this still need to be done, see #805492)

We should probably document how to do the migration for the policies
maintained directly by the users and quickly explain the differences.

Cheers,

Laurent Bigonville

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.2.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_BE.utf8, LC_CTYPE=fr_BE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Debian Bug Tracking System
2017-04-29 09:00:01 UTC
Permalink
tags -1 moreinfo
Bug #805493 [release-notes] release-notes: Document how to migrate SELinux policies from the old store to the new one
Added tag(s) moreinfo.
--
805493: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805493
Debian Bug Tracking System
Contact ***@bugs.debian.org with problems
Niels Thykier
2017-04-29 09:00:01 UTC
Permalink
Control: tags -1 moreinfo
Post by Laurent Bigonville
Package: release-notes
Severity: normal
Usertags: selinux
Hi,
With the new SELinux userspace 2.4, the policy store has moved from
/etc/selinux/<policy_name> to /var/lib/selinux/<policy_name> (the format
of the store has also changed).
The packages from the refpolicy (selinux-policy-default and
selinux-policy-mls) should be fixed to automatically migrate the the new
store (ATM this still need to be done, see #805492)
We should probably document how to do the migration for the policies
maintained directly by the users and quickly explain the differences.
Cheers,
Laurent Bigonville
[...]
Hi,

This seems like a good idea. Unfortunately, I know next to nothing
about this, so I will need some help with writing this.

Some bits that would be helpful to me:

* What do the admin need to do to perform them migration?

* Do we have a reference (to upstream) about why this is happening?

* I assume this is only relevant for people who have installed,
enabled SELinux AND written their own SELinux policies?
- Given most probably doesn't, I will add a note so people know that
they can most likely skip the section.
- Is the "set sebool" policies also auto-migrated?

* Can the admin easily check if they need to do something?
- E.g. do we have a one line shell snippet that can reliably say
"manual migration needed" ? (It is fine if we can't, it just
intended as extra service to the admins)

* Anything else worth mentioning?
- Can it be done prior to the upgrade?
- Must it be performed after upgrade but before reboot?

Thanks,
~Niels
Debian Bug Tracking System
2017-06-09 23:00:01 UTC
Permalink
Your message dated Fri, 09 Jun 2017 22:52:00 +0000
with message-id <dee2fe05-028e-027c-40db-***@thykier.net>
and subject line Re: release-notes: Document how to migrate SELinux policies from the old store to the new one
has caused the Debian Bug report #805493,
regarding release-notes: Document how to migrate SELinux policies from the old store to the new one
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ***@bugs.debian.org
immediately.)
--
805493: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805493
Debian Bug Tracking System
Contact ***@bugs.debian.org with problems
Loading...