Date: prev next · Thread: first prev next last
2015 Archives by date, by thread · List index


Hi there,

I've been working on making AppArmor profiles for LibreOffice and have been
wondering about the best way to integrate them upstream.  Originally I was
thinking about having them in AppArmor upstream but it makes more sense to
be in lock step with LibreOffice versions.  That way as bugs get fixed or
LibreOffice is made to require less permissions it shows up at the right
time.

You can see the latest public version here[1*] and that thread starts
here[2].

If they could be integrated somewhere with the build system it would help
solve the other big issue that I've ran into, the changing pathnames from
pre-built debs to different distros doing things differently.   In an ideal
world each different system then could just generate a libreoffice-apparmor
package that would enable the profiles.

If not (or if we want to decide all that later), I would just be happy
knowing where in the LibreOffice code base the profiles make sense to live.

Just to be clear, I don't believe you could turn these on by default right
now.   This just gives organizations who want LibreOffice confined that
option.

Kind regards,
Bryan

Canonical Backline Support Engineer

[1]  https://lists.ubuntu.com/archives/apparmor/2015-April/007713.html
[2]  https://lists.ubuntu.com/archives/apparmor/2015-April/007690.html
* This profile found a few bugs in AppArmor.  I had to do AppArmor restarts
to reload the profiles.

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.