Kconfig 2.2 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273
  1. #
  2. # XFRM configuration
  3. #
  4. config XFRM
  5. bool
  6. depends on NET
  7. config XFRM_USER
  8. tristate "Transformation user configuration interface"
  9. depends on INET && XFRM
  10. ---help---
  11. Support for Transformation(XFRM) user configuration interface
  12. like IPsec used by native Linux tools.
  13. If unsure, say Y.
  14. config XFRM_SUB_POLICY
  15. bool "Transformation sub policy support (EXPERIMENTAL)"
  16. depends on XFRM && EXPERIMENTAL
  17. ---help---
  18. Support sub policy for developers. By using sub policy with main
  19. one, two policies can be applied to the same packet at once.
  20. Policy which lives shorter time in kernel should be a sub.
  21. If unsure, say N.
  22. config XFRM_MIGRATE
  23. bool "Transformation migrate database (EXPERIMENTAL)"
  24. depends on XFRM && EXPERIMENTAL
  25. ---help---
  26. A feature to update locator(s) of a given IPsec security
  27. association dynamically. This feature is required, for
  28. instance, in a Mobile IPv6 environment with IPsec configuration
  29. where mobile nodes change their attachment point to the Internet.
  30. If unsure, say N.
  31. config XFRM_STATISTICS
  32. bool "Transformation statistics (EXPERIMENTAL)"
  33. depends on XFRM && PROC_FS && EXPERIMENTAL
  34. ---help---
  35. This statistics is not a SNMP/MIB specification but shows
  36. statistics about transformation error (or almost error) factor
  37. at packet processing for developer.
  38. If unsure, say N.
  39. config NET_KEY
  40. tristate "PF_KEY sockets"
  41. select XFRM
  42. ---help---
  43. PF_KEYv2 socket family, compatible to KAME ones.
  44. They are required if you are going to use IPsec tools ported
  45. from KAME.
  46. Say Y unless you know what you are doing.
  47. config NET_KEY_MIGRATE
  48. bool "PF_KEY MIGRATE (EXPERIMENTAL)"
  49. depends on NET_KEY && EXPERIMENTAL
  50. select XFRM_MIGRATE
  51. ---help---
  52. Add a PF_KEY MIGRATE message to PF_KEYv2 socket family.
  53. The PF_KEY MIGRATE message is used to dynamically update
  54. locator(s) of a given IPsec security association.
  55. This feature is required, for instance, in a Mobile IPv6
  56. environment with IPsec configuration where mobile nodes
  57. change their attachment point to the Internet. Detail
  58. information can be found in the internet-draft
  59. <draft-sugimoto-mip6-pfkey-migrate>.
  60. If unsure, say N.