On Mon, Apr 27, 2015 at 03:12:43PM -0700, Ronald F. Guilmette wrote:
>
> In message ,
> Charles Swiger wrote:
>
> >On Apr 27, 2015, at 11:37 AM, Ronald F. Guilmette
> >wrot
> >e:
> ...
> >> and/or whether FreeBSD provides any options which,
> >> for example, might automagically trigger a clo
On Tue, April 28, 2015 01:12, Ronald F. Guilmette wrote:
>
> In message ,
> Charles Swiger wrote:
>
>>On Apr 27, 2015, at 11:37 AM, Ronald F. Guilmette
>>wrot
>>e:
> ...
>>> and/or whether FreeBSD provides any options which,
>>> for example, might automagically trigger a close of the relevant T
Snort (and brethren) at the perimeter seem like a reasonable approach.
http://seclists.org/snort/2015/q2/114
But, more likely to succeed will be SSL everywhere, and certificate
pinning, since this is primarily a web-based attack:
http://www.wired.com/2015/04/researchers-uncover-method-detect-nsa-q
"Ronald F. Guilmette" writes:
> In message <44a8xte4i0@lowell-desk.lan>,
> Lowell Gilbert wrote:
>
>>"Ronald F. Guilmette" writes:
>>
>>> I am prompted to ask here whether or not FreeBSD performs any sort of
>>> logging of instances when "duplicate TCP packets but with different
>>> payloa
On Mon, Apr 27, 2015, at 03:34, Piotr Kubaj wrote:
> Hi,
>
> I wrote about this vulnerability in January:
> https://lists.freebsd.org/pipermail/freebsd-security/2015-January/008115.html
>
> There were only patches for stable.
>
There is an open PR as well
https://bugs.freebsd.org/bugzilla/sh
