{"id":4999,"date":"2014-05-08T23:58:31","date_gmt":"2014-05-08T15:58:31","guid":{"rendered":"https:\/\/webhostinggeeks.com\/howto\/?p=4999"},"modified":"2023-09-18T15:43:25","modified_gmt":"2023-09-18T15:43:25","slug":"how-to-disable-and-remove-apparmor-on-ubuntu-14-04","status":"publish","type":"post","link":"https:\/\/webhostinggeeks.com\/howto\/how-to-disable-and-remove-apparmor-on-ubuntu-14-04\/","title":{"rendered":"How to Disable and Remove AppArmor on Ubuntu 14.04"},"content":{"rendered":"

AppArmor, an acronym for Application Armor, is a Linux kernel security module that provides a Mandatory Access Control (MAC) system. It is a powerful tool that helps mitigate the risk of security breaches by restricting programs’ capabilities with per-program profiles. While it is a valuable asset for enhancing security, it can sometimes cause unexpected issues with certain services on your Ubuntu<\/a> system.<\/p>\n

This guide will walk you through the process of disabling and removing AppArmor on Ubuntu 14.04, which can be particularly useful if you find that it’s causing more problems than it’s solving.<\/p>\n

Before we proceed, it’s important to note that this guide is intended for Ubuntu 14.04 minimal installations without a graphical user interface (GUI). If you’re using a different version of Ubuntu or a different Linux distribution, the steps may vary.<\/p>\n

Disabling and Removing AppArmor on Ubuntu 14.04<\/h2>\n

Step 1: Checking the Status of AppArmor<\/h3>\n

Before you disable or remove AppArmor, it’s a good idea to check its current status. This can be done by entering the following command into your terminal:<\/p>\n

\r\nsudo apparmor_status\r\n<\/pre>\n
This command will display information about the AppArmor module, including whether it’s loaded and how many profiles are in enforce mode, complain mode, or unconfined.<\/p>\n
Example:<\/p>\n
\r\ndimitri@ubuntu14:~$ sudo apparmor_status\r\napparmor module is loaded.\r\n4 profiles are loaded.\r\n4 profiles are in enforce mode.\r\n   \/sbin\/dhclient\r\n   \/usr\/lib\/NetworkManager\/nm-dhcp-client.action\r\n   \/usr\/lib\/connman\/scripts\/dhclient-script\r\n   \/usr\/sbin\/tcpdump\r\n0 profiles are in complain mode.\r\n1 processes have profiles defined.\r\n1 processes are in enforce mode.\r\n   \/sbin\/dhclient (669)\r\n0 processes are in complain mode.\r\n0 processes are unconfined but have a profile defined.\r\n<\/pre>\n
Step 2: Disabling AppArmor<\/h3>\n
To disable AppArmor, you will need to stop the service and unload the kernel module. This can be done with the following commands:<\/p>\n
\r\nsudo \/etc\/init.d\/apparmor stop\r\n<\/pre>\n
\r\nsudo update-rc.d -f apparmor remove\r\n<\/pre>\n
Alternatively, you can use the service command to stop AppArmor:<\/p>\n
sudo service apparmor stop<\/pre>\n
sudo update-rc.d -f apparmor remove<\/pre>\n
Step 3: Removing AppArmor Software<\/h3>\n
After disabling AppArmor, you can remove the software from your system with the following command:<\/p>\n
sudo apt-get remove apparmor apparmor-utils -y<\/pre>\n
This command will remove both the apparmor and apparmor-utils packages from your system. After running this command, you should see a message indicating that the packages have been removed and how much disk space has been freed.<\/p>\n
Example:<\/p>\n
dimitri@ubuntu14:~$ sudo apt-get remove apparmor apparmor-utils -y\r\nReading package lists... Done\r\nBuilding dependency tree\r\nReading state information... Done\r\nThe following packages will be REMOVED:\r\n  apparmor apparmor-utils\r\n0 upgraded, 0 newly installed, 2 to remove and 119 not upgraded.\r\nAfter this operation, 1,467 kB disk space will be freed.\r\n(Reading database ... 93228 files and directories currently installed.)\r\nRemoving apparmor-utils (2.8.95~2430-0ubuntu5) ...\r\nRemoving apparmor (2.8.95~2430-0ubuntu5) ...\r\n * Clearing AppArmor profiles cache                                                          [ OK ]\r\nAll profile caches have been cleared, but no profiles have been unloaded.\r\nUnloading profiles will leave already running processes permanently\r\nunconfined, which can lead to unexpected situations.\r\n\r\nTo set a process to complain mode, use the command line tool\r\n'aa-complain'. To really tear down all profiles, run the init script\r\nwith the 'teardown' option.\"\r\nProcessing triggers for man-db (2.6.7.1-1) ...\r\n<\/pre>\n
Commands Mentioned<\/h2>\n