[Pkg-privacy-maintainers] Bug#884043: obfsproxy: Ship an AppArmor profile again

intrigeri intrigeri at debian.org
Mon Dec 11 06:21:50 UTC 2017


I suggest first checking why we're still including obfsproxy:
I suspect most of the reverse-dependency relationships might be
obsolete nowadays (the last upstream version was released 3 years ago,
and AFAIK obfs4proxy is the future).

If obfsproxy is still useful in contexts where AppArmor confining
matters, I'm fine with us including a profile again *if* someone
commits to maintaining it, which apparently is hard to do properly
without routinely using it on testing/sid.



More information about the Pkg-privacy-maintainers mailing list