Update to 0.99.23.1.

Remove a patch which has been incorporated upstream, and one which has
been superceded.

Add a patch to use the system's RT_ROUNDUP macro if defined,
which fixes IPv6 routing on NetBSD 6 (where rtsock alignment has
changed).

Upstream NEWS:

* Changes in Quagga 0.99.23

Known issues:
- [bgpd] setting an extcommunity in a route map on a route that already has
  an extcommunity attribute will cause bgpd to crash.  This issue will be
  fixed in a followup minor release.

User-visible changes:
- [lib] Performance enhancements on hashes and timers.
- [bgpd] New feature: iBGP TTL security.
- [bgpd] New feature: relaxed bestpath criteria for multipath and improved
  display of multipath routes in "show ip bgp".  Scripts parsing this output
  may need to be updated.
- [bgpd] Multiprotocol peerings over IPv6 now try to find a more appropriate
  IPv4 nexthop by looking at the interface.
- [ospf6d] A large amount of changes has been merged for ospf6d.  Careful
  evaluation prior to deployment is recommended.
- [zebra] Recursive route support has been overhauled.  Scripts parsing
  "show ip route" output may need adaptation.
- [zebra] IPv6 address management has been improved regarding tentative
  addresses.  This is visible in that a freshly configured address will not
  immediately be marked as usable.
- [*] a lot of bugs have been fixed, please refer to the git log
Updated net/quagga to 0.99.23.1
Add two more NetBSD/evbearmv7hf-el patches.
Request from joerg to link with the correct lib paths
Update to 3.2.2:

This is a regularly-scheduled bugfix release.

    changegroup: fix file linkrevs during reorders (issue4462)
    hgweb: send proper HTTP response after uncaught exception
    largefiles: avoid exec-bit examination on the platforms unaware of it
    largefiles: don't show largefile/normal prompts if one side is unchanged
    manifest: fix a bug where working copy file 'add' mark was buggy
    merge: be precise about what merged into what in short desc
    merge: before cd/dc prompt, check that changed side really changed
    mq: fix update of headers that occur in the "wrong" order
    mq: introduce insertplainheader - same naive implementation as before
    mq: when adding headers in plain mode, separate them from message (issue4453)
    mq: when setting message in plain mode, separate it from header (issue4453)
    push: stop independent usage of bundle2 in syncphase (issue4454)
    pushkey: gracefully handle prepushkey hook failure (issue4455)
    rename: properly report removed and added file as modified (issue4458)
    revert: look for copy information for all local modifications
    revset: fix first and last for generatorset (issue4465)
    templates: fix broken "less" & "more" links in paper style (issue4460)
Updated devel/py-mercurial to 3.2.2
Add fix for CVE-2014-8123 from Fabian Keil.
Bump PKGREVISION.
Updated textproc/antiword to 0.37nb2
Set LICENSE.
Update to Asterisk 1.8.32.1: this is a security fix release.

The Asterisk Development Team has announced security releases for Certified
Asterisk 1.8.28 and 11.6 and Asterisk 1.8, 11, 12, and 13. The available
security releases are released as versions 1.8.28-cert3, 11.6-cert8, 1.8.32.1,
11.14.1, 12.7.1, and 13.0.1.

The release of these versions resolves the following security vulnerabilities:

* AST-2014-012: Unauthorized access in the presence of ACLs with mixed IP
  address families

  Many modules in Asterisk that service incoming IP traffic have ACL options
  ("permit" and "deny") that can be used to whitelist or blacklist address
  ranges. A bug has been discovered where the address family of incoming
  packets is only compared to the IP address family of the first entry in the
  list of access control rules. If the source IP address for an incoming
  packet is not of the same address as the first ACL entry, that packet
  bypasses all ACL rules.

* AST-2014-018: Permission Escalation through DB dialplan function

  The DB dialplan function when executed from an external protocol, such as AMI,
  could result in a privilege escalation. Users with a lower class authorization
  in AMI can access the internal Asterisk database without the required SYSTEM
  class authorization.

For more information about the details of these vulnerabilities, please read
security advisories AST-2014-012, AST-2014-013, AST-2014-014, AST-2014-015,
AST-2014-016, AST-2014-017, and AST-2014-018, which were released at the same
time as this announcement.

For a full list of changes in the current releases, please see the ChangeLogs:

http://downloads.asterisk.org/pub/telephony/asterisk/releases/ChangeLog-1.8.32.1

The security advisories are available at:

 * http://downloads.asterisk.org/pub/security/AST-2014-012.pdf
 * http://downloads.asterisk.org/pub/security/AST-2014-018.pdf

Thank you for your continued support of Asterisk!
Updated comms/asterisk18 to 1.8.32.1
Update to Asterisk 11.14.1:  this is a security fix release.

The Asterisk Development Team has announced security releases for Certified
Asterisk 1.8.28 and 11.6 and Asterisk 1.8, 11, 12, and 13. The available
security releases are released as versions 1.8.28-cert3, 11.6-cert8, 1.8.32.1,
11.14.1, 12.7.1, and 13.0.1.

The release of these versions resolves the following security vulnerabilities:

* AST-2014-012: Unauthorized access in the presence of ACLs with mixed IP
  address families

  Many modules in Asterisk that service incoming IP traffic have ACL options
  ("permit" and "deny") that can be used to whitelist or blacklist address
  ranges. A bug has been discovered where the address family of incoming
  packets is only compared to the IP address family of the first entry in the
  list of access control rules. If the source IP address for an incoming
  packet is not of the same address as the first ACL entry, that packet
  bypasses all ACL rules.

* AST-2014-018: Permission Escalation through DB dialplan function

  The DB dialplan function when executed from an external protocol, such as AMI,
  could result in a privilege escalation. Users with a lower class authorization
  in AMI can access the internal Asterisk database without the required SYSTEM
  class authorization.

In addition, the release of 11.6-cert8 and 11.14.1 resolves the following
security vulnerability:

* AST-2014-014: High call load with ConfBridge can result in resource exhaustion

  The ConfBridge application uses an internal bridging API to implement
  conference bridges. This internal API uses a state model for channels within
  the conference bridge and transitions between states as different things
  occur. Unload load it is possible for some state transitions to be delayed
  causing the channel to transition from being hung up to waiting for media. As
  the channel has been hung up remotely no further media will arrive and the
  channel will stay within ConfBridge indefinitely.

In addition, the release of 11.6-cert8, 11.14.1, 12.7.1, and 13.0.1 resolves
the following security vulnerability:

* AST-2014-017: Permission Escalation via ConfBridge dialplan function and
                AMI ConfbridgeStartRecord Action

  The CONFBRIDGE dialplan function when executed from an external protocol (such
  as AMI) can result in a privilege escalation as certain options within that
  function can affect the underlying system. Additionally, the AMI
  ConfbridgeStartRecord action has options that would allow modification of the
  underlying system, and does not require SYSTEM class authorization in AMI.

For a full list of changes in the current releases, please see the ChangeLogs:

http://downloads.asterisk.org/pub/telephony/asterisk/releases/ChangeLog-11.14.1

The security advisories are available at:

 * http://downloads.asterisk.org/pub/security/AST-2014-012.pdf
 * http://downloads.asterisk.org/pub/security/AST-2014-014.pdf
 * http://downloads.asterisk.org/pub/security/AST-2014-017.pdf
 * http://downloads.asterisk.org/pub/security/AST-2014-018.pdf

Thank you for your continued support of Asterisk!
Updated comms/asterisk to 11.14.1