Kconfig 2.7 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485868788899091
  1. #
  2. # Security configuration
  3. #
  4. menu "Security options"
  5. config KEYS
  6. bool "Enable access key retention support"
  7. help
  8. This option provides support for retaining authentication tokens and
  9. access keys in the kernel.
  10. It also includes provision of methods by which such keys might be
  11. associated with a process so that network filesystems, encryption
  12. support and the like can find them.
  13. Furthermore, a special type of key is available that acts as keyring:
  14. a searchable sequence of keys. Each process is equipped with access
  15. to five standard keyrings: UID-specific, GID-specific, session,
  16. process and thread.
  17. If you are unsure as to whether this is required, answer N.
  18. config KEYS_DEBUG_PROC_KEYS
  19. bool "Enable the /proc/keys file by which all keys may be viewed"
  20. depends on KEYS
  21. help
  22. This option turns on support for the /proc/keys file through which
  23. all the keys on the system can be listed.
  24. This option is a slight security risk in that it makes it possible
  25. for anyone to see all the keys on the system. Normally the manager
  26. pretends keys that are inaccessible to a process don't exist as far
  27. as that process is concerned.
  28. config SECURITY
  29. bool "Enable different security models"
  30. help
  31. This allows you to choose different security modules to be
  32. configured into your kernel.
  33. If this option is not selected, the default Linux security
  34. model will be used.
  35. If you are unsure how to answer this question, answer N.
  36. config SECURITY_NETWORK
  37. bool "Socket and Networking Security Hooks"
  38. depends on SECURITY
  39. help
  40. This enables the socket and networking security hooks.
  41. If enabled, a security module can use these hooks to
  42. implement socket and networking access controls.
  43. If you are unsure how to answer this question, answer N.
  44. config SECURITY_CAPABILITIES
  45. tristate "Default Linux Capabilities"
  46. depends on SECURITY
  47. help
  48. This enables the "default" Linux capabilities functionality.
  49. If you are unsure how to answer this question, answer Y.
  50. config SECURITY_ROOTPLUG
  51. tristate "Root Plug Support"
  52. depends on USB && SECURITY
  53. help
  54. This is a sample LSM module that should only be used as such.
  55. It prevents any programs running with egid == 0 if a specific
  56. USB device is not present in the system.
  57. See <http://www.linuxjournal.com/article.php?sid=6279> for
  58. more information about this module.
  59. If you are unsure how to answer this question, answer N.
  60. config SECURITY_SECLVL
  61. tristate "BSD Secure Levels"
  62. depends on SECURITY
  63. select CRYPTO
  64. select CRYPTO_SHA1
  65. help
  66. Implements BSD Secure Levels as an LSM. See
  67. <file:Documentation/seclvl.txt> for instructions on how to use this
  68. module.
  69. If you are unsure how to answer this question, answer N.
  70. source security/selinux/Kconfig
  71. endmenu