On Tue, 24 Aug 2021 22:44:39 -0400
tempforever wrote:
> Neat. Thanks for the info. I was actually wondering about just that
> very thing (how to block a program's network access) when the audacity
> topic restarted.
Hi,
with this methods it will be a never ending cat and mouse game
and you gi
Neat. Thanks for the info. I was actually wondering about just that
very thing (how to block a program's network access) when the audacity
topic restarted.
Mason Loring Bliss wrote:
> On Tue, Aug 24, 2021 at 06:41:59PM -0400, Mason Loring Bliss wrote:
>
>> So, whether you set it persistently or
On Tue, Aug 24, 2021 at 06:41:59PM -0400, Mason Loring Bliss wrote:
> So, whether you set it persistently or not, you start with:
>
> sudo sysctl -w kernel.unprivileged_userns_clone=1
>
> ...and then you can run something that has no configured network:
>
> $ unshare -n ping 4.2.2.1
>
When I first heard about Audacity's plans to start shooting data back to
the mother ship, I was dismayed. But then I thought, "boy, we have some
technical tools to address this" and I started digging. The obvious answer,
since AppArmor made it into Devuan Beowulf, was to use that to block
Audacity
Dr. Nikolaus Klepp wrote:
> This is a strict no-go. Any software even with the "option" to get you
> prosecuted by any countries laws will get you in trouble. Any sane person
> should stay away from that crap as far as possible.
Unfortunately you’ll struggle to stay away. There is a lot of fre
Dear Erik,
dva...@internode.on.net - 24.08.21, 07:25:07 CEST:
>I hope that interests someone. It's not often that an
> opportunity to espouse the original text Swiss army knife presents
> itself.
Thanks!
Nice one.
Best,
--
Martin
___
Dng maili
