It doesnt matter where are/it using both of them just not worth the headache of using atm
important when there are matured tools, not now.
Never said oh we should use it , never said its any better. All what said is opinion from another project thus i already said to not take any of these projects and ideally stay on what was whonix using.
when used by default on debian thats the turn part im talking about, not who developed it.
same answer before.
not matured in the way that it should be matured like i described it
Sorry not productive one according to his shitty views on everything except almighty proprietary.
In the end this my views , im not the one who decide what to install and what not to install and do all the bugs solving and related work this is @Patrick job and decision. We are here to share our views, and my position is software tester if bubblewrap included or not i will test in both cases.
Being used by default on debian is also not a requirement for maturity.
Whonix used apparmor long before it was the default on debian yet I haven’t seen any criticisms from you about it.
The answer before is “it’s not worth it” with no other explanation.
It’s extremely important. Without, seccomp a huge amount of kernel attack surface is exposed. For example, unprivileged programs can even mess with kernel memory faults with syscalls such as userfaultfd or privileged programs can gain read-write access to memory with syscalls such as ioperm or iopl.
No, that’s complete misinformation. He only criticises things that deserve criticism including many proprietary things.
I don’t see why you keep going on about proprietary stuff when he’s a massive contributor to open source projects. Whonix is using a lot of his work already.