📄 pluto.8
字号:
.TH IPSEC_PLUTO 8 "28 March 1999".SH NAMEipsec pluto \- IPsec IKE keying daemon.bripsec whack \- control interface for IPSEC keying daemon.SH SYNOPSIS.na.nh.HP.ft Bipsec pluto[\-\-help][\-\-version][\-\-optionsfrom\ \c\fIfilename\fP][\-\-nofork][\-\-stderrlog][\-\-noklips][\-\-uniqueids][\fB\-\-interface\fP \fIinterfacename\fP][\-\-ikeport\ \c\fIportnumber\fP][\-\-ctlbase\ \c\fIpath\fP][\-\-secretsfile\ \c\fIsecrets\(hyfile\fP][\-\-adns \fIpathname\fP][\-\-lwdnsq \fIpathname\fP][\-\-perpeerlog][\-\-perpeerlogbase\ \c\fIdirname\fP][\-\-ipsecdir\ \c\fIdirname\fP][\-\-coredir\ \c\fIdirname\fP][\-\-noretransmits][\-\-debug\(hynone][\-\-debug\(hyall][\-\-debug\(hyraw][\-\-debug\(hycrypt][\-\-debug\(hyparsing][\-\-debug\(hyemitting][\-\-debug\(hycontrol][\-\-debug\(hylifecycle][\-\-debug\(hyklips][\-\-debug\(hydns][\-\-debug\(hyoppo][\-\-debug\(hyprivate].HP.ft Bipsec whack[\-\-help][\-\-version].HP.ft Bipsec whack\-\-name\ \c\fIconnection-name\fP.br[\-\-id\ \c\fIid\fP] \c[\-\-host\ \c\fIip\(hyaddress\fP][\-\-ikeport\ \c\fIport\(hynumber\fP][\-\-nexthop\ \c\fIip\(hyaddress\fP][\-\-client\ \c\fIsubnet\fP][\-\-dnskeyondemand][\-\-updown\ \c\fIupdown\fP].br\-\-to.br[\-\-id\ \c\fIid\fP][\-\-host\ \c\fIip\(hyaddress\fP][\-\-ikeport\ \c\fIport\(hynumber\fP][\-\-nexthop\ \c\fIip\(hyaddress\fP][\-\-client\ \c\fIsubnet\fP][\-\-dnskeyondemand][\-\-updown\ \c\fIupdown\fP].br[\-\-aggrmode][\-\-psk][\-\-rsasig][\-\-encrypt][\-\-authenticate][\-\-compress][\-\-tunnel][\-\-pfs][\-\-disablearrivalcheck][\-\-ipv4][\-\-ipv6][\-\-tunnelipv4][\-\-tunnelipv6][\-\-ikelifetime\ \c\fIseconds\fP][\-\-ipseclifetime\ \c\fIseconds\fP][\-\-rekeymargin\ \c\fIseconds\fP][\-\-rekeyfuzz\ \c\fIpercentage\fP][\-\-keyingtries\ \c\fIcount\fP][\-\-dontrekey][\-\-delete][\-\-ctlbase\ \c\fIpath\fP][\-\-optionsfrom\ \c\fIfilename\fP][\-\-label\ \c\fIstring\fP].HP.ft Bipsec whack\-\-keyid\ \c\fIid\fP[\-\-addkey][\-\-pubkeyrsa\ \c\fIkey\fP][\-\-ctlbase\ \c\fIpath\fP][\-\-optionsfrom\ \c\fIfilename\fP][\-\-label\ \c\fIstring\fP].HP.ft Bipsec whack\-\-myid\ \c\fIid\fP.HP.ft Bipsec whack\-\-listen|\-\-unlisten[\-\-ctlbase\ \c\fIpath\fP][\-\-optionsfrom\ \c\fIfilename\fP][\-\-label\ \c\fIstring\fP].HP.ft Bipsec whack\-\-route|\-\-unroute\-\-name\ \c\fIconnection-name\fP[\-\-ctlbase\ \c\fIpath\fP][\-\-optionsfrom\ \c\fIfilename\fP][\-\-label\ \c\fIstring\fP].HP.ft Bipsec whack\-\-initiate|\-\-terminate\-\-name\ \c\fIconnection-name\fP[\-\-xauthuser user][\-\-xauthpass pass][\-\-asynchronous][\-\-ctlbase\ \c\fIpath\fP][\-\-optionsfrom\ \c\fIfilename\fP][\-\-label\ \c\fIstring\fP].HP.ft Bipsec whack[\-\-tunnelipv4][\-\-tunnelipv6]\-\-oppohere \fIip\(hyaddress\fP\-\-oppothere \fIip\(hyaddress\fP.HP.ft Bipsec whack\-\-delete\-\-name\ \c\fIconnection-name\fP[\-\-ctlbase\ \c\fIpath\fP][\-\-optionsfrom\ \c\fIfilename\fP][\-\-label\ \c\fIstring\fP].HP.ft Bipsec whack\-\-deletestate\ \c\fIstate-number\fP[\-\-ctlbase\ \c\fIpath\fP][\-\-optionsfrom\ \c\fIfilename\fP][\-\-label\ \c\fIstring\fP].HP.ft Bipsec whack[\-\-name\ \c\fIconnection-name\fP][\-\-debug\(hynone][\-\-debug\(hyall][\-\-debug\(hyraw][\-\-debug\(hycrypt][\-\-debug\(hyparsing][\-\-debug\(hyemitting][\-\-debug\(hycontrol][\-\-debug\(hylifecycle][\-\-debug\(hyklips][\-\-debug\(hydns][\-\-debug\(hyoppo][\-\-debug\(hyprivate][\-\-ctlbase\ \c\fIpath\fP][\-\-optionsfrom\ \c\fIfilename\fP][\-\-label\ \c\fIstring\fP].HP.ft Bipsec whack\-\-status[\-\-ctlbase\ \c\fIpath\fP][\-\-optionsfrom\ \c\fIfilename\fP][\-\-label\ \c\fIstring\fP].HP.ft Bipsec whack\-\-shutdown[\-\-ctlbase\ \c\fIpath\fP][\-\-optionsfrom\ \c\fIfilename\fP][\-\-label\ \c\fIstring\fP].ft R.hy.ad.SH DESCRIPTION.BR plutois an IKE (``IPsec Key Exchange'') daemon..BR whackis an auxiliary program to allow requests to be made to a running.BR pluto ..LP.BR plutois used to automatically build shared ``security associations'' on asystem that has IPsec, the secure IP protocol.In other words,.BR plutocan eliminate much of the work of manual keying.The actualsecure transmission of packets is the responsibility of other parts ofthe system (see.BR KLIPS ,the companion implementation of IPsec).\fIipsec_auto\fP(8) provides a more convenient interface to\fBpluto\fP and \fBwhack\fP..SS IKE's Job.LPA \fISecurity Association\fP (\fISA\fP) is an agreement between two network nodes onhow to process certain traffic between them. This processing involvesencapsulation, authentication, encryption, or compression..LPIKE can be deployed on a network node to negotiate SecurityAssociations for that node. These IKE implementations can onlynegotiate with other IKE implementations, so IKE must be on each nodethat is to be an endpoint of an IKE-negotiated Security Association.No other nodes need to be running IKE..LPAn IKE instance (i.e. an IKE implementation on a particular networknode) communicates with another IKE instance using UDP IP packets, sothere must be a route between the nodes in each direction..LPThe negotiation of Security Associations requires a number of choicesthat involve tradeoffs between security, convenience, trust, andefficiency. These are policy issues and are normally specified to theIKE instance by the system administrator..LPIKE deals with two kinds of Security Associations. The first part ofa negotiation between IKE instances is to build an ISAKMP SA. AnISAKMP SA is used to protect communication between the two IKEs.IPsec SAs can then be built by the IKEs \- these are used to carryprotected IP traffic between the systems..LPThe negotiation of the ISAKMP SA is known as Phase 1. In theory,Phase 1 can be accomplished by a couple of different exchange types,but we only implement one called Main Mode (we don't implementAggressive Mode)..LPAny negotiation under the protection of an ISAKMP SA, including thenegotiation of IPsec SAs, is part of Phase 2. The exchange typethat we use to negotiate an IPsec SA is called Quick Mode..LPIKE instances must be able to authenticate each other as part of theirnegotiation of an ISAKMP SA. This can be done by several mechanismsdescribed in the draft standards..LPIKE negotiation can be initiated by any instance with any other. Ifboth can find an agreeable set of characteristics for a SecurityAssociation, and both recognize each others authenticity, they can setup a Security Association. The standards do not specify what causesan IKE instance to initiate a negotiation..LPIn summary, an IKE instance is prepared to automate the management ofSecurity Associations in an IPsec environment, but a number of issuesare considered policy and are left in the system administrator's hands..SS Pluto.LP\fBpluto\fP is an implementation of IKE. It runs as a daemon on a networknode. Currently, this network node must be a LINUX system running the\fBKLIPS\fP implementation of IPsec..LP\fBpluto\fP only implements a subset of IKE. This is enough for it tointeroperate with other instances of \fBpluto\fP, and many other IKEimplementations. We are working on implementing more of IKE..LPThe policy for acceptable characteristics for Security Associations ismostly hardwired into the code of \fBpluto\fP (spdb.c). Eventuallythis will be moved into a security policy database with reasonableexpressive power and more convenience..LP
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -