Re: FreeBSD Security Advisory FreeBSD-SA-15:13.tcp

2015-07-23 Thread Slawa Olhovchenkov
On Thu, Jul 23, 2015 at 02:33:31PM -0700, Xin Li wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > (Bcc'ed some unnamed patch authors so they can correct me if I was wrong > ). > > On 07/23/15 13:48, Slawa Olhovchenkov wrote: > > On Thu, Jul 23, 2015 at 12:29:57PM -0700, Xin Li wrot

Re: FreeBSD Security Advisory FreeBSD-SA-15:13.tcp

2015-07-23 Thread Xin Li
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 (Bcc'ed some unnamed patch authors so they can correct me if I was wrong ). On 07/23/15 13:48, Slawa Olhovchenkov wrote: > On Thu, Jul 23, 2015 at 12:29:57PM -0700, Xin Li wrote: > >> -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 >> >> On 07/22/

Re: FreeBSD Security Advisory FreeBSD-SA-15:13.tcp

2015-07-23 Thread Slawa Olhovchenkov
On Thu, Jul 23, 2015 at 12:29:57PM -0700, Xin Li wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > On 07/22/15 06:18, Slawa Olhovchenkov wrote: > > On Wed, Jul 22, 2015 at 02:57:46AM +, FreeBSD Security > > Advisories wrote: > > > > This is correspondent to kern/25986? Or kern/2

Re: FreeBSD Security Advisory FreeBSD-SA-15:13.tcp

2015-07-23 Thread Xin Li
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 07/21/15 23:52, ga...@zahemszky.hu wrote: >> IV. Workaround >> >> No workaround is available, but systems that do not provide TCP >> based service to untrusted networks are not vulnerable. >> >> Note that the tcpdrop(8) utility can be used to p

Re: FreeBSD Security Advisory FreeBSD-SA-15:13.tcp

2015-07-23 Thread Xin Li
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 07/22/15 06:18, Slawa Olhovchenkov wrote: > On Wed, Jul 22, 2015 at 02:57:46AM +, FreeBSD Security > Advisories wrote: > > This is correspondent to kern/25986? Or kern/25986 is different > bug? I think it's the same bug. Cheers, - -- Xin L

Re: FreeBSD Security Advisory FreeBSD-SA-15:13.tcp

2015-07-22 Thread Slawa Olhovchenkov
On Wed, Jul 22, 2015 at 02:57:46AM +, FreeBSD Security Advisories wrote: This is correspondent to kern/25986? Or kern/25986 is different bug? > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > = > FreeBSD-SA-15

Re: FreeBSD Security Advisory FreeBSD-SA-15:13.tcp

2015-07-22 Thread Gareth de Vaux
On Wed 2015-07-22 (10:31), Pietro Cerutti wrote: > Hi, I just updated my system as usual using freebsd-update. I was > expecting it to require a reboot, since it's touching kernel code, but > it hasn't. freebsd-version shows 10.1-RELEASE-p15 for both kernel and > userland. Am I missing something

Re: FreeBSD Security Advisory FreeBSD-SA-15:13.tcp

2015-07-22 Thread Pietro Cerutti
On 2015-07-22 04:57, FreeBSD Security Advisories wrote: 2) To update your vulnerable system via a binary patch: Systems running a RELEASE version of FreeBSD on the i386 or amd64 platforms can be updated via the freebsd-update(8) utility: # freebsd-update fetch # freebsd-update install Hi, I

Re: FreeBSD Security Advisory FreeBSD-SA-15:13.tcp

2015-07-21 Thread gabor
IV. Workaround No workaround is available, but systems that do not provide TCP based service to untrusted networks are not vulnerable. Note that the tcpdrop(8) utility can be used to purge connections which have become wedged. For example, the following command can be used to generate comman

Re: FreeBSD Security Advisory FreeBSD-SA-15:13.tcp

2015-07-21 Thread Peter Rosa
Hi, V. Solution Perform one of the following: 3) To update your vulnerable system via a source code patch: The following patches have been verified to apply to the applicable FreeBSD release branches. c) Recompile your kernel as described in https://www.FreeBSD.org/handbook/kernelconfig.ht

FreeBSD Security Advisory FreeBSD-SA-15:13.tcp

2015-07-21 Thread FreeBSD Security Advisories
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 = FreeBSD-SA-15:13.tcpSecurity Advisory The FreeBSD Project Topic: