reassign 851647 suricata
thanks
Hi all,
[...]
>> You could add:
>>
>> Tested-by: Arturo Borrero Gonzalez
>
> Done... and force-pushed the --amended commit to my branch.
>
> I'll open a ticket in the Suricata Redmine then to check with upstream.
> They'll be able to comment further, let's see
Hi all,
I've prepared some first code [1] and will be testing it today in a QEMU
VM with SSSE3 disabled. If that works I'll ping upstream, OK?
>>>
>>> Ok, the patch looks good. Ping me if you need additional testing.
>>
>> Yes, please! I would be grateful for another pair of eyes. So far
On 23 January 2017 at 14:31, Sascha Steinbiss wrote:
> Hi Arturo,
>
>>> I've prepared some first code [1] and will be testing it today in a QEMU
>>> VM with SSSE3 disabled. If that works I'll ping upstream, OK?
>>
>> Ok, the patch looks good. Ping me if you need additional testing.
>
> Yes, please
Hi Arturo,
>> I've prepared some first code [1] and will be testing it today in a QEMU
>> VM with SSSE3 disabled. If that works I'll ping upstream, OK?
>
> Ok, the patch looks good. Ping me if you need additional testing.
Yes, please! I would be grateful for another pair of eyes. So far I've
bee
On 23 January 2017 at 12:01, Sascha Steinbiss wrote:
>
> I've prepared some first code [1] and will be testing it today in a QEMU
> VM with SSSE3 disabled. If that works I'll ping upstream, OK?
>
Ok, the patch looks good. Ping me if you need additional testing.
best regards.
Hi Arturo,
>> BTW, It hasn't escaped our notice that there is a new
>> 'hs_valid_platform()' function in Hyperscan 4.4 which checks at runtime
>> whether the executing CPU has SSSE3 support. This may help to no longer
>> require a Hyperscan-specific Debian package for Suricata: if Suricata
>> coul
On 20 January 2017 at 15:33, Sascha Steinbiss wrote:
>
> BTW, It hasn't escaped our notice that there is a new
> 'hs_valid_platform()' function in Hyperscan 4.4 which checks at runtime
> whether the executing CPU has SSSE3 support. This may help to no longer
> require a Hyperscan-specific Debian p
Hi Arturo and Robert,
>> FYI, I have tried building the hyperscan package with a current git
>> snapshot from upstream's 'develop' branch [1]. After adding some new
>> build-deps (mostly libsqlite3) and patching out a duplicated Boost
>> header, the package builds fine for 4.4. I have also checked
On 18 January 2017 at 16:09, Sascha Steinbiss wrote:
>
> FYI, I have tried building the hyperscan package with a current git
> snapshot from upstream's 'develop' branch [1]. After adding some new
> build-deps (mostly libsqlite3) and patching out a duplicated Boost
> header, the package builds fine
Hi Arturo,
just a quick update from me, after doing some test builds earlier today.
>> From the suricata package point of view we rely on some details of
>> the current hyperscan debian implementation:
>>
>> * the hyperscan install-time warning, which will perhaps no longer
>>be relevant.
Hi Aturo,
let me answer your questions inline:
On Tue, 17 Jan 2017 09:48:27 +0100 Arturo Borrero Gonzalez wrote:
> Package: hypersan
> Severity: wishlist
>
> Dear hyperscan maintainers,
>
> thanks for your work with the hyperscan package in debian, it's really
> appreciated.
>
> I just knew that
Package: hypersan
Severity: wishlist
Dear hyperscan maintainers,
thanks for your work with the hyperscan package in debian, it's really
appreciated.
I just knew that hyperscan v4.4 (which is about to be released by upstream)
will include the so-called 'fat runtime' which enables hyperscan to cho
12 matches
Mail list logo
