Skip to content
Commits on Nov 4, 1999
  1. pchar: pathchar reimplementation.

    sumikawa committed
  2. pchar: pathchar reimplementation.

    sumikawa committed
  3. Initial revision

    sumikawa committed
  4. pchar: pathchar reimplementation.

    itojun committed
  5. fixed reqid infomation, s/16383/32767/.

    sakane committed
  6. added two sample configuraiton on loopback.

    sakane committed
  7. delete unused file.

    sakane committed
  8. * kame/sys/{netkey,netinet6}:

    sakane committed
    * kame/kame/{libipsec,setkey,racoon}:
    Implemented a policy level of `unique' for strict use of SA.
    The decimal number named `reqid' is used as the identifier in order to
    relate between a SA and SA requests in some policy.
    Manual keying may need explicitly to specify the identifier.  You can
    put the decimal number as the identifier after keyword `unique' of
    policy level followed by colon(:).  For example, "unique:1225".
    The value is:
    	0 are reserved.
    	1 - 16383 are reserved for manual keying.
    	Others are for kernel use.
    Note that this id doesn't identify a SA by only itself.
    XXX To be implemented the inbound policy check by level of `unique'
        after a implement of holding SA used to decode.
    XXX The field of reqid on PF_KEY message is in sadb_msg structure.
        It may not be adequated for portablity.
    XXX racoon has not been supported yet.
  9. Implemented a policy level of `unique' for strict use of SA.

    sakane committed
    The decimal number named `reqid' is used as the identifier in order to
    relate between a SA and SA requests in some policy.
    Manual keying may need explicitly to specify the identifier.  You can put
    the decimal number as the identifier after keyword `unique' of policy level
    followed by colon(:).  For example, "unique:1225".  The value is:
    	0 are reserved.
    	1 - 16383 are reserved for manual keying.
    	Others are for kernel use.
    Note that this id doesn't identify a SA by only itself.
    XXX To be implemented the inbound policy check by level of `unique'
        after a implement of holding SA used to decode.
    XXX The field of reqid on PF_KEY message is in sadb_msg structure.
        It may not be adequated for portablity.
  10. add ucd-snmp for openbsd.

    itojun committed
  11. Initial revision

    itojun committed
Commits on Nov 3, 1999
  1. typo

    itojun committed
  2. avoid duplicated def of endian-sensitive #define even if you do not

    itojun committed
    include machine/endian.h.
    #elif is not everywhere so use #else - #if.
  3. typo.

    itojun committed
  4. * openbsd/ports/zebra: upgrade to 0.81.

    itojun committed
  5. upgrade to 0.81.

    itojun committed
  6. * netbsd/pkgsrc/net/ucd-snmp, freebsd[23]/ucd-snmp:

    itojun committed
      use latest IPv6 patch.
  7. use latest IPv6 patch.

    itojun committed
  8. use latest IPv6 patch (not tested)

    itojun committed
  9. use latest IPv6 patch.

    itojun committed
  10. comment out last commit (extra sanity check).

    itojun committed
  11. add more tests for getnameinfo(3).

    itojun committed
  12. don't use u_long to hold IPv4 address.

    itojun committed
  13. forgot to raise failure count

    itojun committed
  14. add error mode test for getnameinfo(3).

    itojun committed
  15. *** empty log message ***

    itojun committed
  16. change unvisited case just for readability.

    itojun committed
    this may make some version of gcc angry (due to incorrect warning).
    
    From: Jaromir Dolecek <dolecek@ics.muni.cz>
  17. * kame/sys/netkey/key.c:

    sakane committed
    key_msg2sp() returns suitable error code.
    
    * kame/sys/netkey/key.c:
    Toss up a policy index as identity of SA user when kernel acquired SA.
    This is used extended identity type, that is SADB_X_IDENTTYPE_ADDR,
    included in the SADB_EXT_IDENTITY extension.
  18. comment about mode and level in policy.

    sakane committed
  19. toss up a policy index as identity of SA user.

    sakane committed
Something went wrong with that request. Please try again.