Salut,
j’essai d’utiliser apparmor pour la securité en suivant le wiki
https://wiki.debian.org/AppArmor/HowToUse
Dès l’installation ça ne va pas:
update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
Job for apparmor.service failed. See 'systemctl status apparmor.service' and 'journalctl -xn' for details.
invoke-rc.d: initscript apparmor, action "start" failed.
je vérifie le statut par rapport à systemd
[code]root@desktop:/etc/apt# systemctl status apparmor
● apparmor.service - LSB: AppArmor initialization
Loaded: loaded (/etc/init.d/apparmor)
Active: failed (Result: exit-code) since lun. 2016-01-04 16:35:10 CET; 57s ago
janv. 04 16:35:10 desktop apparmor[5831]: Starting AppArmor profiles:AppArmor not available…M…
janv. 04 16:35:10 desktop apparmor[5831]: failed!
janv. 04 16:35:10 desktop systemd[1]: apparmor.service: control process exited, code=exited…s=1
janv. 04 16:35:10 desktop systemd[1]: Failed to start LSB: AppArmor initialization.
janv. 04 16:35:10 desktop systemd[1]: Unit apparmor.service entered failed state.
Hint: Some lines were ellipsized, use -l to show in full.[/code]
Un peu de recherche et je trouve cette commande
root@desktop:/etc/apt# systemctl enable apparmor
Synchronizing state for apparmor.service with sysvinit using update-rc.d...
Executing /usr/sbin/update-rc.d apparmor defaults
Executing /usr/sbin/update-rc.d apparmor enable
Mais ça ne suffit pas
[code]root@desktop:/etc/apt# systemctl stop apparmor
root@desktop:/etc/apt# systemctl start apparmor
Job for apparmor.service failed. See ‘systemctl status apparmor.service’ and ‘journalctl -xn’ for details.
root@desktop:/etc/apt# systemctl status apparmor.service
● apparmor.service - LSB: AppArmor initialization
Loaded: loaded (/etc/init.d/apparmor)
Active: failed (Result: exit-code) since lun. 2016-01-04 16:42:35 CET; 26s ago
Process: 6205 ExecStart=/etc/init.d/apparmor start (code=exited, status=1/FAILURE)
root@desktop:/etc/apt# journalctl -xn
– Logs begin at lun. 2016-01-04 12:26:04 CET, end at lun. 2016-01-04 16:42:35 CET. –
janv. 04 16:35:10 desktop systemd[1]: Failed to start LSB: AppArmor initialization.
– Subject: L’unité (unit) apparmor.service a échoué
– Defined-By: systemd
– Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
– L’unité (unit) apparmor.service a échoué, avec le résultat failed.
janv. 04 16:35:10 desktop systemd[1]: Unit apparmor.service entered failed state.
janv. 04 16:35:15 desktop systemd-sysv-generator[6101]: Overwriting existing symlink /run/systemd
janv. 04 16:37:46 desktop systemd-sysv-generator[6161]: Overwriting existing symlink /run/systemd
janv. 04 16:37:46 desktop systemd-sysv-generator[6175]: Overwriting existing symlink /run/systemd
janv. 04 16:42:34 desktop apparmor[6205]: Starting AppArmor profiles:AppArmor not available as ke
janv. 04 16:42:34 desktop apparmor[6205]: failed!
janv. 04 16:42:35 desktop systemd[1]: apparmor.service: control process exited, code=exited statu
janv. 04 16:42:35 desktop systemd[1]: Failed to start LSB: AppArmor initialization.
– Subject: L’unité (unit) apparmor.service a échoué
– Defined-By: systemd
– Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
– L’unité (unit) apparmor.service a échoué, avec le résultat failed.
janv. 04 16:42:35 desktop systemd[1]: Unit apparmor.service entered failed state.[/code]
root@desktop:/etc/apt# cat /sys/module/apparmor/parameters/enabled
N
Que faire?