[ubuntu/saucy-proposed] dbus 1.6.12-0ubuntu5 (Accepted)

Tyler Hicks tyhicks at canonical.com
Wed Aug 28 22:36:13 UTC 2013


dbus (1.6.12-0ubuntu5) saucy; urgency=low

  * Add support for mediation of D-Bus messages and services. AppArmor D-Bus
    rules are described in the apparmor.d(5) man page. dbus-daemon will use
    libapparmor to perform queries against the AppArmor policies to determine
    if a connection should be able to send messages to another connection, if
    a connection should be able to receive messages from another connection,
    and if a connection should be able to bind to a well-known name.
    - debian/patches/aa-build-tools.patch: Update build files to detect and
      build against libapparmor
    - debian/patches/aa-mediation.patch: Support AppArmor mediation of D-Bus
      messages and services. By default, AppArmor mediation is enabled if
      AppArmor is available. To disable AppArmor mediation, place
      '<apparmor mode="disabled"/>' in each bus configuration file. See the
      dbus-daemon(1) man page for more details.
    - debian/patches/aa-get-connection-apparmor-security-context.patch: Add an
      org.freedesktop.DBus.GetConnectionAppArmorSecurityContext method that
      takes the unique name of a connection as input and returns the AppArmor
      label attached to the connection
    - debian/patches/aa-kernel-compat-check.patch: Perform a compatibility
      check of dbus, libapparmor, and the AppArmor kernel code during
      initialization to determine if everything is in place to perform
      AppArmor mediation. This is a temporary patch to overcome some potential
      incompatabilities during the Saucy development release and should be
      dropped prior to Saucy's release.
    - debian/control: Add libapparmor-dev as a Build-Depends
    - debian/rules: Specify that D-Bus should be built against libapparmor
      during the configure stage of the build
  * debian/patches/aa-mediation.patch: Clean up the AppArmor initialization
    - Don't treat any errors from aa_is_enabled() as fatal unless the AppArmor
      D-Bus mode is set to "required". This should fix errors when various
      test cases need to start dbus-daemon on buildds. (LP: #1217598)
    - Don't print to stderr during initialization unless an error has
      occurred (LP: #1217710)
    - Don't redefine _dbus_warn() to syslog(). A previous comment left in the
      code suggested that _dbus_warn() caused segfaults. Testing proves that
      is not the case.
  * debian/patches/aa-get-connection-apparmor-security-context.patch: Refresh
    patch to fix offset warnings after modifying aa-mediation.patch

Date: Wed, 28 Aug 2013 13:26:13 -0700
Changed-By: Tyler Hicks <tyhicks at canonical.com>
Maintainer: Ubuntu Developers <ubuntu-devel-discuss at lists.ubuntu.com>
Signed-By: Jamie Strandboge <jamie at ubuntu.com>
https://launchpad.net/ubuntu/saucy/+source/dbus/1.6.12-0ubuntu5
-------------- next part --------------
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Wed, 28 Aug 2013 13:26:13 -0700
Source: dbus
Binary: dbus dbus-x11 libdbus-1-3 dbus-1-doc libdbus-1-dev dbus-1-dbg
Architecture: source
Version: 1.6.12-0ubuntu5
Distribution: saucy
Urgency: low
Maintainer: Ubuntu Developers <ubuntu-devel-discuss at lists.ubuntu.com>
Changed-By: Tyler Hicks <tyhicks at canonical.com>
Description: 
 dbus       - simple interprocess messaging system (daemon and utilities)
 dbus-1-dbg - simple interprocess messaging system (debug symbols)
 dbus-1-doc - simple interprocess messaging system (documentation)
 dbus-x11   - simple interprocess messaging system (X11 deps)
 libdbus-1-3 - simple interprocess messaging system (library)
 libdbus-1-dev - simple interprocess messaging system (development headers)
Launchpad-Bugs-Fixed: 1217598 1217710
Changes: 
 dbus (1.6.12-0ubuntu5) saucy; urgency=low
 .
   * Add support for mediation of D-Bus messages and services. AppArmor D-Bus
     rules are described in the apparmor.d(5) man page. dbus-daemon will use
     libapparmor to perform queries against the AppArmor policies to determine
     if a connection should be able to send messages to another connection, if
     a connection should be able to receive messages from another connection,
     and if a connection should be able to bind to a well-known name.
     - debian/patches/aa-build-tools.patch: Update build files to detect and
       build against libapparmor
     - debian/patches/aa-mediation.patch: Support AppArmor mediation of D-Bus
       messages and services. By default, AppArmor mediation is enabled if
       AppArmor is available. To disable AppArmor mediation, place
       '<apparmor mode="disabled"/>' in each bus configuration file. See the
       dbus-daemon(1) man page for more details.
     - debian/patches/aa-get-connection-apparmor-security-context.patch: Add an
       org.freedesktop.DBus.GetConnectionAppArmorSecurityContext method that
       takes the unique name of a connection as input and returns the AppArmor
       label attached to the connection
     - debian/patches/aa-kernel-compat-check.patch: Perform a compatibility
       check of dbus, libapparmor, and the AppArmor kernel code during
       initialization to determine if everything is in place to perform
       AppArmor mediation. This is a temporary patch to overcome some potential
       incompatabilities during the Saucy development release and should be
       dropped prior to Saucy's release.
     - debian/control: Add libapparmor-dev as a Build-Depends
     - debian/rules: Specify that D-Bus should be built against libapparmor
       during the configure stage of the build
   * debian/patches/aa-mediation.patch: Clean up the AppArmor initialization
     - Don't treat any errors from aa_is_enabled() as fatal unless the AppArmor
       D-Bus mode is set to "required". This should fix errors when various
       test cases need to start dbus-daemon on buildds. (LP: #1217598)
     - Don't print to stderr during initialization unless an error has
       occurred (LP: #1217710)
     - Don't redefine _dbus_warn() to syslog(). A previous comment left in the
       code suggested that _dbus_warn() caused segfaults. Testing proves that
       is not the case.
   * debian/patches/aa-get-connection-apparmor-security-context.patch: Refresh
     patch to fix offset warnings after modifying aa-mediation.patch
Checksums-Sha1: 
 c892c034d024e9eebbdd547c20615637298dc6bd 2680 dbus_1.6.12-0ubuntu5.dsc
 aafa28651a824d0c7933e68899cb1e421d4992eb 61118 dbus_1.6.12-0ubuntu5.debian.tar.gz
Checksums-Sha256: 
 0d1dad776214be2360dbb3b58968daed8aa792eaf891ffd749b3a7cc586fcfbb 2680 dbus_1.6.12-0ubuntu5.dsc
 f25f3a250cfa1964630ae461163eb3b3b88a84b626378f6b360191833031accc 61118 dbus_1.6.12-0ubuntu5.debian.tar.gz
Files: 
 e1d026b3d492cc12d30d25891ea55d52 2680 admin optional dbus_1.6.12-0ubuntu5.dsc
 44a6ef3dbfebdc53c5d3d85255df006d 61118 admin optional dbus_1.6.12-0ubuntu5.debian.tar.gz
Original-Maintainer: Utopia Maintenance Team <pkg-utopia-maintainers at lists.alioth.debian.org>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)

iQIcBAEBCgAGBQJSHmX6AAoJEFHb3FjMVZVzPB4P/3Pcn+brlnafpAF+SGzWMkBF
JfcMYNKn3Bqby2hHCjpcigZpeCKRF/tBUPLijOc4qqkKTS5IxNulWThAtnfn+6zM
IsUIxSoggYGiA5OL7sb+XAUf+cr2yZjC/NaBzt5+xV5c1Ru7JH5eMCicV0TTnFqe
488OxoATxDkofaOoEHclnzAQ88XzVC9olMWVwffhIax+84p5gmMJE7rKApBeQrGP
LrlzdRvmwVd4D01tZHSMuJiPT++9bqMqd3L3+RkuihDch0CNQ6Mysv3+lfBw+aTL
FpsBkLE+TknycclHWGUvEN1ZmCtAhyHMr9MDi2dZiUkpzrTlCTcC88Cy9jmAvgYD
nTUNVRcukFvwZEnAShxR3jzr/VZCy1CZWgUk3m001YjCcoRLICTA1ZoByFW0bgK9
5pt2IbpTQ06I1a2dkReqfxWDwIoP19RsOvDDTg1f5Li86p3vlLvZEX/qKUTw1C2S
iy/n4s2T+Y1JyE/U/JerAnhnar92oohpxSq2RvkuJTef/hFa14MT0obTbvVOhxpX
r4HD+gJNP4OFbRBcZOJ/ms/VblL7AcWTukt+PQIL2ogOglH4dyLANTyFWZp0Zi0H
NehhkG7YT+EPRi4AlqMskNPWkTEzevTov6JKNXlu6WwJzzsl5j8frR5gsEeJ020w
ZgzMtTOYDKUyklqBaXxD
=06Vi
-----END PGP SIGNATURE-----


More information about the Saucy-changes mailing list