From ftpmaster at ftp-master.debian.org Sat Aug 1 10:00:14 2015 From: ftpmaster at ftp-master.debian.org (Debian FTP Masters) Date: Sat, 01 Aug 2015 10:00:14 +0000 Subject: [DSE-Dev] libsemanage_2.4-1_amd64.changes ACCEPTED into experimental, experimental Message-ID: Accepted: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Fri, 31 Jul 2015 16:21:13 +0200 Source: libsemanage Binary: libsemanage-common libsemanage1 libsemanage1-dev ruby-semanage python-semanage python3-semanage Architecture: source all amd64 Version: 2.4-1 Distribution: experimental Urgency: medium Maintainer: Debian SELinux maintainers Changed-By: Laurent Bigonville Description: libsemanage-common - Common files for SELinux policy management libraries libsemanage1 - SELinux policy management library libsemanage1-dev - Header files and libraries for SELinux policy manipulation python-semanage - Python bindings for SELinux policy management python3-semanage - Python3 bindings for SELinux policy management ruby-semanage - Ruby bindings to for SELinux policy management Changes: libsemanage (2.4-1) experimental; urgency=medium . * Team upload. * New upstream release - debian/patches/disable-expand-check.patch: Refreshed - debian/control: Bump {build-}dependencies to match new release - Adjust the debian/libsemanage1.symbols file * debian/watch: Update watch file URL * debian/control: Bump Standards-Version to 3.9.6 (no further changes) * Do not look for hll compiler in /usr/libexec * Start building python3 packages Checksums-Sha1: f9011c1256cb5489295a12da090c53abe46f9d8a 2226 libsemanage_2.4-1.dsc 7096d3999559c1a1a74330c0ef9778d8eea90057 151173 libsemanage_2.4.orig.tar.gz 3635c1adf389087f2dc4ea86c98a4fde61111d8d 15644 libsemanage_2.4-1.debian.tar.xz 4d70e12ddb632e95de18bd8bce09ea9b6e2899e1 25426 libsemanage-common_2.4-1_all.deb 724aa39fe53b1d40f4817f2d0c20d30aa8df1aef 129054 libsemanage1-dev_2.4-1_amd64.deb 37849b6def8d6cc711a984db1ffeb2f2585c3e6c 98042 libsemanage1_2.4-1_amd64.deb c0652c174986a412e09359e6b2e1a8e0a12b1b83 65440 python-semanage_2.4-1_amd64.deb 61c5d90f2bd044c97a36bc31a6fd36655cd8b101 65734 python3-semanage_2.4-1_amd64.deb 7f3faa888a55208815ae57a015cd7fb7352cb720 62774 ruby-semanage_2.4-1_amd64.deb Checksums-Sha256: 67d825830f180501388246750db2cf19f30d40b57ba01385407b8b577f31184b 2226 libsemanage_2.4-1.dsc 1a4cace4ef16786531ec075c0e7b2f961e2fee5dc86c5f983a689058899a6484 151173 libsemanage_2.4.orig.tar.gz db0d3c34320fff6d78a3b4dd258e7e948a43c6a9ab3e3658fb60129d12614272 15644 libsemanage_2.4-1.debian.tar.xz 5bfa3b6b008754cde042ba790b99ed63c456abee7de786821c64de9800975b7d 25426 libsemanage-common_2.4-1_all.deb 888a63bc1d8cbb21e53d7e516af4aa319f46ce9517dd6415fd7f04f43c7f1a7a 129054 libsemanage1-dev_2.4-1_amd64.deb dad266ff6feae0a30a1a34289eedf82af753a368a7774f303a4b1044a1144700 98042 libsemanage1_2.4-1_amd64.deb 6064e7f4d4c87969594117c4b3aa380a06c410c3adcadbe90d9e2ec5a76a0dde 65440 python-semanage_2.4-1_amd64.deb 3ebd4ff3f469d7f316f1a73de005eeeb24cda04078c64c5348e36e7103fbdf58 65734 python3-semanage_2.4-1_amd64.deb ce7570b8114a262e0c9a2f5989d65726dd42bc3fd991d60b429321e9b1f7c078 62774 ruby-semanage_2.4-1_amd64.deb Files: c07b050d75cf2ff22752bb249a24e706 2226 libdevel optional libsemanage_2.4-1.dsc cd551eb1cc5d20652660bda037972f0d 151173 libdevel optional libsemanage_2.4.orig.tar.gz 8b9b121f97c8c7ca624863acdebc408e 15644 libdevel optional libsemanage_2.4-1.debian.tar.xz 2b96810ca21f261e8a430be3660924f0 25426 libs optional libsemanage-common_2.4-1_all.deb b51d1525f80c0311de8f95c7779e9331 129054 libdevel optional libsemanage1-dev_2.4-1_amd64.deb 5412b37da331c8ebb0d68288313c752f 98042 libs optional libsemanage1_2.4-1_amd64.deb 1597d1ba6349352b1db6a4666413c9e3 65440 python optional python-semanage_2.4-1_amd64.deb 72cffda816dec7ae3dd4a7070ded0a3d 65734 python optional python3-semanage_2.4-1_amd64.deb 2733db6da17998290c9d8cf6e4a9b148 62774 ruby optional ruby-semanage_2.4-1_amd64.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBCAAGBQJVu4nnAAoJEB/FiR66sEPVdwEH/31BResY6e6REpfQLcbgIvcF zhf3ZGn8wRNGGW/p+quk5+Z0kKEvca7vJEE3ezj77nszXb4AAJYcsm51I1mLhoY0 G1QdVLznvkKld8iQqvrRmh0E2TTeAsw+HFyGJGyIALGZ/FpfkiG5Wjm+ZFY7uAtx uvHTPp1i885MQLDNRt8Xn3Q+OGzfp9nRJRbbt3EXccuVV+yV05i4569HQdh+C0ZR cBABdI7WCkLYTzZv7/jPK8/P9OqwXlw//yXxBwxupNh0ciuWvf3pC3Me6ze7z2s7 zpzZG0q40DAS3RD6VryNs0kesWl7j2Ha9fMuTJjEWIMaO3IxiRln3YFcv/hU4k8= =ygcT -----END PGP SIGNATURE----- Thank you for your contribution to Debian. From frazzledjazz at gmail.com Fri Aug 14 19:24:40 2015 From: frazzledjazz at gmail.com (Richard Jasmin) Date: Fri, 14 Aug 2015 14:24:40 -0500 Subject: [DSE-Dev] Bug#795505: selinux-basics: reccommends a non-existant package Message-ID: <20150814192440.7852.34836.reportbug@livingroom.c4home.net> Package: selinux-basics Version: 0.5.2 Severity: grave Tags: security Justification: renders package unusable Either instructions for setting up SELinux(enabled by default on Fedora) are wrong and need to be changed or selinux-policy-default package needs to be built for debian as a whole. Seems no distro has this package according to a web package search but setting up SELinux seems to depend on it. Did the policies get put into another package? They are pretty much required to setup SELinux. Tomoyo and apparmor may work as alternates but the reccommended course of action is SELinux.It is also more common method. There is also no reason to not have it installed and basic config setup by default(either on install media or live media). Ignore this hardening reccomendation at your own peril. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages selinux-basics depends on: ii checkpolicy 2.3-1 ii policycoreutils 2.3-1 pn python:any ii selinux-utils 2.3-2+b1 Versions of packages selinux-basics recommends: pn selinux-policy-default ii setools 3.3.8-3.2 Versions of packages selinux-basics suggests: pn logcheck pn syslog-summary -- no debconf information From frazzledjazz at gmail.com Fri Aug 14 20:47:36 2015 From: frazzledjazz at gmail.com (Richard Jasmin) Date: Fri, 14 Aug 2015 15:47:36 -0500 Subject: [DSE-Dev] Bug#795518: selinux-utils: neither labels set or SELinux enabled Message-ID: <20150814204736.22428.38281.reportbug@livingroom.c4home.net> Package: selinux-utils Version: 2.3-2+b1 Severity: grave Justification: renders package unusable when using "sudo selinux-activate" to enable SELinux and setting rcS properly, nothing actually happens once you reboot.The system respawns itself into a working state once more but SELinux remains disabled with no clue as to why.There is no other way to enable it and force a relabel of the system, which does not seem to happen when enabling SELinux. This seems to be a stretch problem as other version of debian seem to succeed at this point.Id use Jessie but xarchiver and ark have SEVERE data loss issues when making a backup set. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages selinux-utils depends on: ii libc6 2.19-19 ii libpcre3 2:8.35-7 ii libselinux1 2.3-2+b1 selinux-utils recommends no packages. selinux-utils suggests no packages. -- no debconf information From owner at bugs.debian.org Fri Aug 14 22:15:05 2015 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Fri, 14 Aug 2015 22:15:05 +0000 Subject: [DSE-Dev] Processed: severity of 795505 is normal, tagging 795505 References: <1439590306-4197-bts-jmw@debian.org> Message-ID: Processing commands for control at bugs.debian.org: > severity 795505 normal Bug #795505 [selinux-basics] selinux-basics: reccommends a non-existant package Severity set to 'normal' from 'grave' > tags 795505 - security Bug #795505 [selinux-basics] selinux-basics: reccommends a non-existant package Removed tag(s) security. > thanks Stopping processing here. Please contact me if you need assistance. -- 795505: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795505 Debian Bug Tracking System Contact owner at bugs.debian.org with problems From owner at bugs.debian.org Sat Aug 15 14:42:05 2015 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Sat, 15 Aug 2015 14:42:05 +0000 Subject: [DSE-Dev] Processed: reassign 795518 to selinux-basics References: <1439649517-3378-bts-bigon@debian.org> Message-ID: Processing commands for control at bugs.debian.org: > reassign 795518 selinux-basics Bug #795518 [selinux-utils] selinux-utils: neither labels set or SELinux enabled Bug reassigned from package 'selinux-utils' to 'selinux-basics'. No longer marked as found in versions libselinux/2.3-2. Ignoring request to alter fixed versions of bug #795518 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 795518: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795518 Debian Bug Tracking System Contact owner at bugs.debian.org with problems From noreply at release.debian.org Sat Aug 22 04:39:05 2015 From: noreply at release.debian.org (Debian testing autoremoval watch) Date: Sat, 22 Aug 2015 04:39:05 +0000 Subject: [DSE-Dev] selinux-basics is marked for autoremoval from testing Message-ID: selinux-basics 0.5.2 is marked for autoremoval from testing on 2015-09-12 It is affected by these RC bugs: 795518: selinux-basics: selinux-utils: neither labels set or SELinux enabled From pyotrc85 at autorambler.ru Sun Aug 23 01:02:58 2015 From: pyotrc85 at autorambler.ru (=?windows-1251?B?ze7t7eAg0PPn++Xi?=) Date: Sun, 23 Aug 2015 05:02:58 +0400 Subject: [DSE-Dev] =?cp1251?b?0PPn++XiIM3u7e3gIO7x8mHi6OvgIMLg7CDr6Pft7mUg?= =?cp1251?b?8e7u4fnl7ehl?= Message-ID: fac?book ????? ?????: ???? 20? ??????? ?? ????! ??????? ????????? ?? ??????? ?????! ? ??????? ???????? ????????. ?????? ???????????? ????????? ???? ?????????? ?? selinux-devel at lists.alioth.debian.org. ???? ?? ?? ?????? ???????? ??? ??. ?????? ?? Facebook, ???? ???? ?? ?? ??????, ????? ??? ????? ????????????? ??? ???????? ???????????? ??????, ??????????, ?????????? ?? ????????. Facebook, Inc., Attention: Department 6817, PO Box 886533, Palo Alto, CA 71447 -------------- next part -------------- An HTML attachment was scrubbed... URL: From fsateler at debian.org Sun Aug 23 14:22:27 2015 From: fsateler at debian.org (fsateler at debian.org) Date: Sun, 23 Aug 2015 11:22:27 -0300 Subject: [DSE-Dev] Bug#796693: selinux-basics: Has init script in runlevel S but no matching service file Message-ID: <20150823142227.6009028050F@felipepc.sateler> Package: selinux-basics Severity: important User: pkg-systemd-maintainers at lists.alioth.debian.org Usertags: init-rcs-service Hi, Your package selinux-basics has an initscript that is enabled in runlevel S, but it does not provide a corresponding systemd service unit. Systemd generates units for all sysv init scripts that do not have a corresponding systemd unit. By default, it sets DefaultDependencies=yes, which means they get ordered after early boot has finished. The problem is that to preserve the runlevel S semantics, systemd in debian is currently[1] ordering all S services Before=sysinit.target. This target is particularly early in the boot sequence, which means that it is most of the time too strict. In turn, this means it is fairly easy to end up with dependency cycles. For an example, see bug [763315]. Do note that the cycle still exists with sysvinit, it is just that systemd complains more loudly. Please add a systemd unit for the given service with the appropriate dependencies, which most of the time will be less strict than Before=sysinit.target. In other cases, the script is simply not applicable in systemd, in which case the package should ship a symlink to /dev/null as /lib/systemd/system/.service. We have prepared a transition wiki page[2] explaining the issue in more detail, and outlining some general guidance. Please refer to it as it will have useful information. If you have any other doubts, feel free to ask in pkg-systemd-maintainers at lists.alioth.debian.org -- [1] http://sources.debian.net/src/systemd/222-2/debian/patches/Add-support-for-rcS.d-init-scripts-to-the-sysv-gener.patch/ [763315] https://bugs.debian.org/763315 [2] https://wiki.debian.org/Teams/pkg-systemd/rcSMigration From tcanarias at allpromos.info Mon Aug 24 06:00:09 2015 From: tcanarias at allpromos.info (Turismo de Canarias) Date: Mon, 24 Aug 2015 06:00:09 +0000 Subject: [DSE-Dev] Regalamos 1.000 vuelos a Canarias Message-ID: <332331b6a2ece149cd247cc304333041@allpromos.info> An HTML attachment was scrubbed... URL: From tytso at mit.edu Sat Aug 29 16:31:06 2015 From: tytso at mit.edu (Theodore Ts'o) Date: Sat, 29 Aug 2015 12:31:06 -0400 Subject: [DSE-Dev] What's the current status of the refpolicy package? Message-ID: <20150829163106.GA27796@thunk.org> I see there have been a number of changes that there haven't been any updates in the debian package since February, and the git repo hasn't been updated since then either. What are the plans in terms of updates to the policy? Thanks, - Ted