| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
| |
instead of hand-defining the YY_NO_INPUT macro.
MFC after: 1 week
|
|
|
|
|
|
| |
function does not get defined needlessly.
MFC after: 1 week
|
|
|
|
|
|
|
|
| |
This commit includes all remaining changes for the time being including
user space updates.
Submitted by: bz
Approved by: re
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is the second of two commits; bring in the userland support to finish.
Teach libipsec and setkey about the tcp-md5 class of security associations,
thus allowing administrators to add per-host keys to the SADB for use by
the tcpsignature_compute() function.
Document that a single SPI must be used until such time as the code which
adds support to the SPD to specify flows for tcp-md5 treatment is suitable
for production.
Sponsored by: sentex.net
|
|
|
|
|
|
|
|
|
|
| |
- fixed a length of the sadb extension in the case of pfkey_send_x5().
- used getprotobynumber() for printing a upper layer protocol name.
- modified the output format against the change of the setkey syntax
about a icmp6 type/code.
- don't enumerate reserved fields. use memset.
Obtained from: KAME
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This work was based on kame-20010528-freebsd43-snap.tgz and some
critical problem after the snap was out were fixed.
There are many many changes since last KAME merge.
TODO:
- The definitions of SADB_* in sys/net/pfkeyv2.h are still different
from RFC2407/IANA assignment because of binary compatibility
issue. It should be fixed under 5-CURRENT.
- ip6po_m member of struct ip6_pktopts is no longer used. But, it
is still there because of binary compatibility issue. It should
be removed under 5-CURRENT.
Reviewed by: itojun
Obtained from: KAME
MFC after: 3 weeks
|
|
|
|
|
| |
behavior change: policy syntax was changed. you may need to update your
setkey(8) configuration files.
|
|
|
|
| |
(Sorry, this should be committed with previous commit to Makefile.)
|
|
|
|
|
|
|
|
|
| |
Sorry for the flapping, but no change will be done for 4.0 anymore.
Official standard will be published around April or later.
If different format would be adopted at that time, then support for
the new format will be added to the succeeding FreeBSD 4.x.
Approved by: jkh
|
|
Reviewed by: freebsd-arch, cvs-committers
Obtained from: KAME project
|