73115d2807
Prepare to switch security/suricata to the version of libhtp recommended by upstream. This also frees devel/libhtp up for an update, which can be used for the Suricata 2.x branch and onward. www/libhtp-suricata: - Update (downgrade) to 0.2.14 - Use the correct and supported libhtp repo from Suricata - Enable STAGE support - Update pkg-plist - Take maintainership - Remove unnecessary patch (htp_util.c) - qa: Add CONFLICTS - qa: Use our AUTOTOOLS framework completely to prepare the build - qa: Patch htp.pc.in file for proper pkg-config versioning devel/libhtp: - Take maintainership - qa: Add CONFLICTS Reviewed by: wxs, mva, Johannes Meixner Approved by: wxs (maintainer)
23 lines
1 KiB
Text
23 lines
1 KiB
Text
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: https://github.com/ironbee/libhtp
|