03:15 koobs 

devel/libhtp: Update to 0.5.33

 - Sort pkg-plist (ports compliance)

Changelog:

  https://github.com/OISF/libhtp/blob/0.5.33/ChangeLog

PR:	248483
MFH:	2020Q3 (blanket: bugfix release)

 

05:52 koobs 

devel/libhtp: Update to 0.5.25

 * Remove CONFLICTS_INSTALL (libhtp-suricata port deleted)
 * Remove unecessary PLIST_SUB
 * Update and sort pkg-plist
 * Bump security/suricata PORTREVISION, library name/version change

Changelog:

  https://github.com/OISF/libhtp/blob/0.5.25/ChangeLog

PR:		220757
Submitted by:	Franco Fichtner (franco opnsense org)

 

10:40 bapt 

Cleanup plist

 

09:59 koobs 

devel/libhtp: Update to 0.5.15, correctly link to libiconv

- Update to 0.5.15
- Wrangle autoconf/make on linking libiconv with a workaround [1]
- pkg-descr: Remove Author:

[1] https://github.com/ironbee/libhtp/issues/76

 

07:56 koobs 

devel/libhtp: Update to 0.5.12, Update LICENSE

- Update to 0.5.12
- Update pkg-plist
- Update LICENSE (BSD3CLAUSE)
- Deprecate USES_AUTOTOOLS=libtool
- Refactor AUTOTOOLS and AUTO* bits
- Replace manual autogen.sh with AUTOTOOLS bits
- Replace REINPLACE_CMD with pathfix and PATHFIX_MAKEFILEIN
- Remove unecessary CFLAGS
- Strip libraries using install-strip target

 

10:51 koobs 

devel/libhtp: Update to 0.5.9

- Update to 0.5.9
- Update pkg-plist
- Remove unnecessary patch
- QA: Enable STAGE support
- QA: Add LICENSE (BSD)
- QA: Add regression-test target
- QA: Remove commented-out MASTER_SITES
- QA: Re-order USE_* section

Changes:

https://github.com/ironbee/libhtp/blob/0.5.9/ChangeLog

PR:		ports/183785
Submitted by:	wxs

 

09:21 wxs 

Update to 0.3.0

02:41 wxs 

LibHTP is a security-aware parser for the HTTP protocol and the related bits
and pieces. The goals of the project, in the order of importance, are as
follows:

 1. Completeness of coverage; LibHTP must be able to parse virtually all
    traffic that is found in practice.

 2. Permissive parsing; LibHTP must never fail to parse a stream that would
    be parsed by some other web server.

 3. Awareness of evasion techniques; LibHTP must be able to detect and
    effectively deal with various evasion techniques, producing, where
    practical, identical or practically identical results as the web
    server processing the same traffic stream.

 4. Performance; The performance must be adequate for the desired tasks.
    Completeness and security are often detremental to performance. Our
    idea of handling the conflicting requirements is to put the library
    user in control, allowing him to choose the most desired library
    characteristic.

Author: Ivan Ristic <ivanr@webkreator.com>
WWW: http://www.libhtp.org