Kconfig 3.2 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899
  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 keys may be viewed"
  20. depends on KEYS
  21. help
  22. This option turns on support for the /proc/keys file - through which
  23. can be listed all the keys on the system that are viewable by the
  24. reading process.
  25. The only keys included in the list are those that grant View
  26. permission to the reading process whether or not it possesses them.
  27. Note that LSM security checks are still performed, and may further
  28. filter out keys that the current process is not authorised to view.
  29. Only key attributes are listed here; key payloads are not included in
  30. the resulting table.
  31. If you are unsure as to whether this is required, answer N.
  32. config SECURITY
  33. bool "Enable different security models"
  34. depends on SYSFS
  35. help
  36. This allows you to choose different security modules to be
  37. configured into your kernel.
  38. If this option is not selected, the default Linux security
  39. model will be used.
  40. If you are unsure how to answer this question, answer N.
  41. config SECURITY_NETWORK
  42. bool "Socket and Networking Security Hooks"
  43. depends on SECURITY
  44. help
  45. This enables the socket and networking security hooks.
  46. If enabled, a security module can use these hooks to
  47. implement socket and networking access controls.
  48. If you are unsure how to answer this question, answer N.
  49. config SECURITY_NETWORK_XFRM
  50. bool "XFRM (IPSec) Networking Security Hooks"
  51. depends on XFRM && SECURITY_NETWORK
  52. help
  53. This enables the XFRM (IPSec) networking security hooks.
  54. If enabled, a security module can use these hooks to
  55. implement per-packet access controls based on labels
  56. derived from IPSec policy. Non-IPSec communications are
  57. designated as unlabelled, and only sockets authorized
  58. to communicate unlabelled data can send without using
  59. IPSec.
  60. If you are unsure how to answer this question, answer N.
  61. config SECURITY_CAPABILITIES
  62. tristate "Default Linux Capabilities"
  63. depends on SECURITY
  64. help
  65. This enables the "default" Linux capabilities functionality.
  66. If you are unsure how to answer this question, answer Y.
  67. config SECURITY_ROOTPLUG
  68. tristate "Root Plug Support"
  69. depends on USB && SECURITY
  70. help
  71. This is a sample LSM module that should only be used as such.
  72. It prevents any programs running with egid == 0 if a specific
  73. USB device is not present in the system.
  74. See <http://www.linuxjournal.com/article.php?sid=6279> for
  75. more information about this module.
  76. If you are unsure how to answer this question, answer N.
  77. source security/selinux/Kconfig
  78. endmenu