4 Commits (c587e90ebccfe8883ea951e723be461dc58dcc06)

Author	SHA1	Message	Date
Philippe Antoine	26da953f6d	util/hash: use randomized hash algorithm ... For datasets and http ranges Ticket: 7209 Prevents abusive hash collisions from known djb2 algorithm	10 months ago
Shivani Bhardwaj	cbb571a61c	rust/base64: add decoder ... Add a pure rust base64 decoder. This supports 3 modes of operation just like the C decoder as follows. 1. RFC 2045 2. RFC 4648 3. Strict One notable change is that "strict" mode is carried out by the rust base64 crate instead of native Rust. This crate was already used for encoding in a few places like datasets of string type. As a part of this mode, now, only the strings that can be reliably converted back are decoded. The decoder fn is available to C via FFI. Bug 6280 Ticket 7065 Ticket 7058	10 months ago
Jason Ish	6392216f6b	base64: use the Rust base64 encode implementation ... Replace our internal base64 implementation with a ffi wrapper around the Rust implementation provided by an external crate.	4 years ago
Victor Julien	317376f59d	datasets: match on lists of data ... Datasets are sets/lists of data that can be accessed or added from the rule language. This patch implements 3 data types: 1. string (or buffer) 2. md5 3. sha256 The patch also implements 2 new rule keywords: 1. dataset 2. datarep The dataset keyword allows matching against a list of values to see if it exists or not. It can also add the value to the set. The set can optionally be stored to disk on exit. The datarep support matching/lookups only. With each item in the set a reputation value is stored and this value can be matched against. The reputation value is unsigned 16 bit, so values can be between 0 and 65535. Datasets can be registered in 2 ways: 1. through the yaml 2. through the rules The goal of this rules based approach is that rule writers can start using this without the need for config changes. A dataset is implemented using a thash hash table. Each dataset is its own separate thash.	6 years ago