Personally, I've had enough problems with apparmor doing this exact
sort of thing that I just remove/purge it and mark it as on hold so
that it doesn't reinstall.
Since apparmor is 'security' software, that may not be the best advice,
but at the same time, I have a hard time trusting security
Thank you for this. Is there any way around this? This didn't used to be
problem.
Sent with Proton Mail secure email.
--- Original Message ---
On Thursday, December 22nd, 2022 at 7:15 AM, trinity pointard
wrote:
> Hi,
>
> These lines Toralf references come from the logs you
Hi,
These lines Toralf references come from the logs you sent. It looks
like apparmor didn't want obfs4proxy to open some file.
I'm not sure why obfs4proxy would care about this file, maybe it's
something the go runtime likes to look at. It does not look fatal
though.
Logs also says
> Dec 20
I'm not sure I understand. Are you showing me more lines of code to add?
Sent from Proton Mail mobile
Original Message
On Dec 21, 2022, 5:18 AM, Toralf Förster wrote:
> On 12/20/22 15:27, Anonforpeace via tor-relays wrote: > Dec 20 08:55:16
> mxh-HP-Compaq-Pro-6300-SFF
On 12/20/22 15:27, Anonforpeace via tor-relays wrote:
Dec 20 08:55:16 mxh-HP-Compaq-Pro-6300-SFF kernel: [137278.310446]
audit: type=1400 audit(1671544516.974:36): apparmor="DENIED"
operation="open" profile="system_tor"
name="/sys/kernel/mm/transparent_hugepage/hpage_pmd_size" pid=17728
Hello:
I hope you can help me. I'm having trouble keeping my bridge up. Ports are
forwarded. Running latest version of Tor. I had it running for at least roughly
7 to 10 days and then it went down and keeping it up is trouble. I even setup
dynamic dns on my router using no-ip.com to see if
