Blocking loading of modules via alias

General system Newbie
8

@cactux I was hoping that someone who has done this already or configured will be able to tell. That is why I had asked. Was banking on the knowledge of the crowd. :grinning_face:

Allright so this is what I found. Using the following in a conf file present in /etc/modprobe.d/ directory

install <<ModuleName>> /bin/false

blocks the module from being loaded via the command modprobe <<ModuleName>>. This also blocks the module from being loaded via aliases of the module, i.e. modprobe <<ModuleAlias>>. What this does not block are the following

  1. Any dependencies. If the <<ModuleName>> is dependent on some other module, that will get loaded.
  2. Loading of the module using insmod <<AbsolutePathToModuleFile>>

However if we use the following in a conf file present in /etc/modprobe.d/ directory

install <<ModuleName>> /bin/false
blacklist <<ModuleName>>

blocks the module from being loaded via the command modprobe as well as via insmod

So to answer the question, yeah blocking the module by using install <<ModuleName> /bin/false will also block the loading of the module using its alias. But it does not stop insmod.