[Pkg-privacy-maintainers] Bug#817267: Bug#817267: torbrowser-launcher: AppArmor profile still blocks browser self-upgrade

Holger Levsen holger at layer-acht.org
Wed Mar 9 15:53:23 UTC 2016

control: forwarded -1 https://github.com/micahflee/torbrowser-launcher/issues/227

Hi intrigeri,

On Mittwoch, 9. März 2016, intrigeri at debian.org wrote:
> apparently I still need this rule to allow the browser to complete its
> upgrade process and restart after an update has been applied:
>   owner
> @{HOME}/.local/share/torbrowser/tbb/{i686,x86_64}/tor-browser_*/Browser.ba
> k/ rwk,
> It was part of those I provided on #808140, but apparently it
> disappeared when the suggested fixes were applied upstream as
> commit:3f536f5.


Could you please be so kind and provide a git commit fixing this upstream
in the file apparmor/torbrowser.Browser.firefox directly? I could guess at
which line to add the missing line, but I think you have a stronger opinion.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 828 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.alioth.debian.org/pipermail/pkg-privacy-maintainers/attachments/20160309/76b0b341/attachment.sig>

More information about the Pkg-privacy-maintainers mailing list