Question about unconfined App Armor profiles & processes & complain mode

[Patrick]

Thank you!

@Tenforthat

I understand the concept that complain mode is there so that profiles and processes can tell you they have violations without that necessarily killing them, and you can adjust and test from there, but is this expected?

Expected.

Actually difficult to know for users. Either it’s in complain mode because the profile is considered unfinished or some other reason. Whonix firewall apparmor profiles makes little sense outside of completion of development of apparmor-profile-everything. In theory, a profile might be good enough and it’s an Kicksecure, Whonix or upstream bug that it’s not in enforce mode by default. Hard to tell without being a developer and researching these things in-depth.

@Tenforthat

To my nonspecific question:

Seems unrelated to AppArmor.
1 question = 1 forum topic please.

@Tenforthat

and when I ran ‘top’ I saw systemd-socket-. Does this strike you as just standard random bugs?

systemd-socket-proxyd is expected (in Whonix source code and Whonix wiki).

@Tenforthat

I also had an occurance where in a DISPVM downloads were going to a mozilla folder, not .tb/tor-browser/…

Using Firefox or Tor Browser?
Separate forum topic if you like to discuss this further please.

@Tenforthat

I’ve had sys-whonix crash randomly

Separate forum discussion or topic required here too.
Depends on how you noticed the crash.
Random crashes would belong to Qubes (as per What to post in this Qubes-Whonix forum and what not.).

@Tenforthat

and when it loads back up it no longer shows keepassxc in the list when I click on the whonix lock icon (offline vault, should it even be in there?). Sometimes a dispvm that is currently running will no longer appear despite it still running and saying it is on tor.

Related to sdwdate-gui. This would require a separate forum topic and detailed instructions how to reproduce this issue so I can potentially reproduce and fix it.