On Tue, Jul 04, 2017 at 09:32:37PM -0400, Ed Maste wrote:
> On 3 July 2017 at 12:29, Michelle Sullivan wrote:
> >
> > Been watching for it in 10-STABLE... didn't see it go in... did I miss it?
>
> It hasn't yet been merged -- there were a couple of issues with the
> initial commit which were fixe
On 3 July 2017 at 12:29, Michelle Sullivan wrote:
>
> Been watching for it in 10-STABLE... didn't see it go in... did I miss it?
It hasn't yet been merged -- there were a couple of issues with the
initial commit which were fixed shortly after in HEAD. We are now
waiting on the MFC timer for the f
Ed Maste wrote:
On 21 June 2017 at 20:22, Ed Maste wrote:
These changes are expected to be
committed to FreeBSD soon, and from there they will be merged to
stable branches and into updates for supported releases.
The changes have now been merged to HEAD in r320317.
https://svnweb.freebsd.org/c
On 21 June 2017 at 20:22, Ed Maste wrote:
> These changes are expected to be
> committed to FreeBSD soon, and from there they will be merged to
> stable branches and into updates for supported releases.
The changes have now been merged to HEAD in r320317.
https://svnweb.freebsd.org/changeset/base
> On 23 Jun 2017, at 01:19, Michelle Sullivan wrote:
>
> Peter,
>
> Peter Jeremy wrote:
>>
>> paying someone to provide whatever level of support you want. With
>> respect to your 9.x servers, no-one is saying you must replace the
>> hardware, just that the FreeBSD Project will not continue t
Peter,
Peter Jeremy wrote:
paying someone to provide whatever level of support you want. With
respect to your 9.x servers, no-one is saying you must replace the
hardware, just that the FreeBSD Project will not continue to provide
you with free support whilst you choose to run 9.x on them. Not
;ve seen
no indication that the Stack Clash vulnerability can be compared in
severity to WannaCry.
>hardware I have 9.x servers that 10.x/11.x and even 12.x are
>unbootable (and given the nature of the hardware I expect people to say
>'too old, you should replace the hardware' - no
On Thu, Jun 22, 2017 at 01:14:33PM +0200, Michelle Sullivan wrote:
> I know, but with potentially serious issues even M$ issue patches for
> older release...
Microsoft even has 114,000 employees [1]. There are billions of paying
customers, so Microsoft has staff and money to test and backport pat
ote:
Hi,
I assume FreeBSD security team is already aware about the Stack
Clash vulnerability, that is stated to affect FreeBSD amongst
other Unix-like OS.
Yes, the security team is aware of this. Improvements in stack
handling are in progress (currently in review).
I would like to provide so
> On 22 Jun 2017, at 03:10, Michelle Sullivan wrote:
>
> Ed Maste wrote:
>> On 20 June 2017 at 16:22, Ed Maste wrote:
>>> On 20 June 2017 at 04:13, Vladimir Terziev wrote:
>>>> Hi,
>>>>
>>>> I assume FreeBSD security team is alre
Ed Maste wrote:
On 20 June 2017 at 16:22, Ed Maste wrote:
On 20 June 2017 at 04:13, Vladimir Terziev wrote:
Hi,
I assume FreeBSD security team is already aware about the Stack Clash
vulnerability, that is stated to affect FreeBSD amongst other Unix-like OS.
Yes, the security team is aware
On 20 June 2017 at 16:22, Ed Maste wrote:
> On 20 June 2017 at 04:13, Vladimir Terziev wrote:
>> Hi,
>>
>> I assume FreeBSD security team is already aware about the Stack Clash
>> vulnerability, that is stated to affect FreeBSD amongst other Unix-like OS.
>
> Y
On 20 June 2017 at 04:13, Vladimir Terziev wrote:
> Hi,
>
> I assume FreeBSD security team is already aware about the Stack Clash
> vulnerability, that is stated to affect FreeBSD amongst other Unix-like OS.
Yes, the security team is aware of this. Improvements in stack
handling are
On Tue, Jun 20, 2017 at 08:13:46AM +, Vladimir Terziev wrote:
> Hi,
>
> I assume FreeBSD security team is already aware about the Stack Clash
> vulnerability, that is stated to affect FreeBSD amongst other Unix-like OS.
>
> Just in case here is the analyses document of
08:13:46AM +, Vladimir Terziev wrote:
> > > Hi,
> > >
> > > I assume FreeBSD security team is already aware about the Stack Clash
> > vulnerability, that is stated to affect FreeBSD amongst other Unix-like OS.
> > >
> > > Just in case here is the
t; >
> > I assume FreeBSD security team is already aware about the Stack Clash
> vulnerability, that is stated to affect FreeBSD amongst other Unix-like OS.
> >
> > Just in case here is the analyses document of Qualys:
> >
> > https://www.qualys.com/2017/06/19/stack
On Tue, Jun 20, 2017 at 08:13:46AM +, Vladimir Terziev wrote:
> Hi,
>
> I assume FreeBSD security team is already aware about the Stack Clash
> vulnerability, that is stated to affect FreeBSD amongst other Unix-like OS.
>
> Just in case here is the analyses document of
Funny enough, we had that covered for a short while, at least better than
it is now:
https://www.mail-archive.com/svn-src-all@freebsd.org/msg141063.html
On Tue, Jun 20, 2017 at 9:13 AM, Vladimir Terziev
wrote:
> Hi,
>
> I assume FreeBSD security team is already aware about the St
Hi,
I assume FreeBSD security team is already aware about the Stack Clash
vulnerability, that is stated to affect FreeBSD amongst other Unix-like OS.
Just in case here is the analyses document of Qualys:
https://www.qualys.com/2017/06/19/stack-clash/stack-clash.txt
Regards,
Vladimir
19 matches
Mail list logo
