Kconfig 2.8 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283848586878889909192
  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. depends on SYSFS
  31. help
  32. This allows you to choose different security modules to be
  33. configured into your kernel.
  34. If this option is not selected, the default Linux security
  35. model will be used.
  36. If you are unsure how to answer this question, answer N.
  37. config SECURITY_NETWORK
  38. bool "Socket and Networking Security Hooks"
  39. depends on SECURITY
  40. help
  41. This enables the socket and networking security hooks.
  42. If enabled, a security module can use these hooks to
  43. implement socket and networking access controls.
  44. If you are unsure how to answer this question, answer N.
  45. config SECURITY_CAPABILITIES
  46. tristate "Default Linux Capabilities"
  47. depends on SECURITY
  48. help
  49. This enables the "default" Linux capabilities functionality.
  50. If you are unsure how to answer this question, answer Y.
  51. config SECURITY_ROOTPLUG
  52. tristate "Root Plug Support"
  53. depends on USB && SECURITY
  54. help
  55. This is a sample LSM module that should only be used as such.
  56. It prevents any programs running with egid == 0 if a specific
  57. USB device is not present in the system.
  58. See <http://www.linuxjournal.com/article.php?sid=6279> for
  59. more information about this module.
  60. If you are unsure how to answer this question, answer N.
  61. config SECURITY_SECLVL
  62. tristate "BSD Secure Levels"
  63. depends on SECURITY
  64. select CRYPTO
  65. select CRYPTO_SHA1
  66. help
  67. Implements BSD Secure Levels as an LSM. See
  68. <file:Documentation/seclvl.txt> for instructions on how to use this
  69. module.
  70. If you are unsure how to answer this question, answer N.
  71. source security/selinux/Kconfig
  72. endmenu