In message <516c58ed.40...@freebsd.org>, Jung-uk Kim writes:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 2013-04-15 15:27:55 -0400, Cy Schubert wrote:
> > In message , Scott
> > Long writes:
> >>
> >> On Apr 15, 2013, at 11:48 AM,
everyone busy. My main goal is to make sure IPF doesn't disappear nor go
into disrepair and to make sure it's well maintained. Let's work together.
--
Cheers,
Cy Schubert
FreeBSD UNIX: Web: http://www.FreeBSD.org
___
freebsd-cur
I've been poking at this off and on last night. Any ideas?
--
Cheers,
Cy Schubert
FreeBSD UNIX: Web: http://www.FreeBSD.org
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscr
In message <1257671366135...@web6f.yandex.ru>, "Ilya A. Arkhipov" writes:
> 16.04.2013, 21:56, "Cy Schubert" :
> > Has anyone see this before? Just updated my CURRENT partitions on my
> > testbed and laptop. The laptop just boots but I've managed to
In message
, Ivan Voras writes:
> On 17 April 2013 00:44, Cy Schubert wrote:
>
> > You were correct. Backing out r249508 in my tree resolves the panic on both
> > hosts.
>
> Hi,
>
> Sorry about that - should be fixed by
> http://svnweb.freebsd.org/base?view=r
In message
, Ed Maste writes:
> On 15 April 2013 16:12, Cy Schubert wrote:
> > The existing license isn't that BSD-friendly either, which is why it lives
> > in contrib/. I think the 5.1.X GPLv2 is about the same friendliness as
> > Darren's IPF 4.1.X license.
branches (which I managed to get to under svn 1.7.2).
To answer the obvious question, I've done svn upgrade and when that didn't
help I subsequently used a fresh checkout from my local test SVN repo, so
this is not an issue.
Any and all help would be appreciated. Thanks for your hel
In message <20130705084649.gc67...@freebsd.org>, Gleb Smirnoff writes:
> Cy,
>
> On Thu, Jul 04, 2013 at 03:10:14PM -0700, Cy Schubert wrote:
> C> Unfortunately it doesn't work any more. Here is what svn spit out at me.
> C>
> C> slippy$ cd $MY_WORK_DI
In message <51da85cf.3000...@freebsd.org>, Andre Oppermann writes:
> On 05.07.2013 20:38, Cy Schubert wrote:
> > In message <20130705084649.gc67...@freebsd.org>, Gleb Smirnoff writes:
> >> What I'd prefer to see is the following:
> >>
> >> -
In message <20130708134400.gh67...@glebius.int.ru>, Gleb Smirnoff writes:
> Cy,
>
> On Fri, Jul 05, 2013 at 11:38:21AM -0700, Cy Schubert wrote:
> C> > What I'd prefer to see is the following:
> C> >
> C> > - commit new ipfilter untouched t
is in fact meta mode rebuilding because of some makefile change.
Without meta mode I've experienced odd weirdnesses that are fixed through a
subsequent clean build.
I just started using meta mode again this week after a few years hiatus to
see if it addresses the occasional weird behaviour due to something not
being rebuilt when it should have been.
--
Cheers,
Cy Schubert
FreeBSD UNIX: Web: http://www.FreeBSD.org
NTP: Web: https://nwtime.org
e^(i*pi)+1=0
here and would be a perfect candidate for migration to ports.
--
Cheers,
Cy Schubert
FreeBSD UNIX: Web: https://FreeBSD.org
NTP: Web: https://nwtime.org
e^(i*pi)+1=0
t would be a good project to have a still in school upcoming developer to
work on.
--
Cheers,
Cy Schubert
FreeBSD UNIX: Web: https://FreeBSD.org
NTP: Web: https://nwtime.org
e^(i*pi)+1=0
some serious ZFS
> > > problems - I didn't find it right now.
> > >
> > > Thanks in advance,
> > >
> >
> > That's fallout from the new block cloning feature, adding the author
> >
>
> Thanks.
>
> As of this moment, all systems with the newest kernel and the new ZFS option
> enabled, crash -
> the reason is mostly in different ZFS datasets. I guess there is no way back
> once this faulty
> option is enabled?
I've run a test on a scratch pool here, first without block_cloning
enabled, then with. There was no corruption when block_cloning was
disabled. There was corruption when block_cloning was enabled.
I don't know of any way to revert back nor is there any way to fix or
recover the corrupted blocks.
--
Cheers,
Cy Schubert
FreeBSD UNIX: Web: https://FreeBSD.org
NTP: Web: https://nwtime.org
e^(i*pi)+1=0
In message <434b83db-f6bb-436f-8aa5-385730d20...@dawidek.net>,
=?utf-8?Q?Pawe=C
5=82_Jakub_Dawidek?= writes:
>
>
> > On Apr 11, 2023, at 11:31, Cy Schubert wrote:
> >=20
> > =EF=BB=BFIn message <20230409161436.5412fa6e@thor.intern.walstatt.dynvpn.d=
>
In message <20230411142831.db824...@slippy.cwsent.com>, Cy Schubert writes:
> In message <434b83db-f6bb-436f-8aa5-385730d20...@dawidek.net>,
> =?utf-8?Q?Pawe=C
> 5=82_Jakub_Dawidek?= writes:
> >
> >
> > > On Apr 11, 2023, at 11:31, Cy Schubert
ng to
conclusions. I've taken an extremely cautious approach, rolling back
snapshots (as much as possible, i.e. poudriere datasets) when EXDEV
corruption was encountered.
I did not rollback any snapshots in my MH mail directory. Rolling back
snapshots of my MH maildir would result in
In message , Mark Millard
write
s:
> [This just puts my prior reply's material into Cy's
> adjusted resend of the original. The To/Cc should
> be coomplete this time.]
>
> On Apr 12, 2023, at 22:52, Cy Schubert =
> wrote:
>
> > In message , Mark =
> Millar
In message <20230413064252.1e5c1...@slippy.cwsent.com>, Cy Schubert writes:
> In message , Mark Millard
> write
> s:
> > [This just puts my prior reply's material into Cy's
> > adjusted resend of the original. The To/Cc should
> > be coomplete this t
In message <20230413070426.8a54f...@slippy.cwsent.com>, Cy Schubert writes:
> In message <20230413064252.1e5c1...@slippy.cwsent.com>, Cy Schubert writes:
> > In message , Mark Millard
> > write
> > s:
> > > [This just puts my prior reply's material
On Thu, 13 Apr 2023 19:54:42 +0900
Paweł Jakub Dawidek wrote:
> On Apr 13, 2023, at 16:10, Cy Schubert wrote:
> >
> > In message <20230413070426.8a54f...@slippy.cwsent.com>, Cy Schubert writes:
> > In message <20230413064252.1e5c1...@slippy.cwsent.com>, Cy
In message
, Mateusz Guzik writes:
> On 4/13/23, Cy Schubert wrote:
> > On Thu, 13 Apr 2023 19:54:42 +0900
> > Pawe=C5=82 Jakub Dawidek wrote:
> >
> >> On Apr 13, 2023, at 16:10, Cy Schubert wrote=
> :
> >> >
> >> > =EF=BB=BFIn m
. IMO one is generally safe to run poudriere on the
latest ZFS with the additional patch.
My tests of the additional patch concluded that it resolved my last
problems, except for the sent email problem I'm still investigating. I'm
sure there's a simple explanation for it, i.e. the email thread was
corrupted by the EXDEV regression which cannot be fixed by anything, even
reverting to the previous ZFS -- the data in those files will remain
damaged regardless.
I cannot speak to the others who have had poudriere and other issues. I
never had any problems with poudriere on top of the new ZFS.
WRT reverting block_cloning pools to without, your only option is to backup
your pool and recreate it without block_cloning. Then restore your data.
--
Cheers,
Cy Schubert
FreeBSD UNIX: Web: https://FreeBSD.org
NTP: Web: https://nwtime.org
e^(i*pi)+1=0
In message <20230415175218.777d0...@thor.intern.walstatt.dynvpn.de>,
FreeBSD Us
er writes:
> Am Sat, 15 Apr 2023 07:36:25 -0700
> Cy Schubert schrieb:
>
> > In message <20230415115452.08911...@thor.intern.walstatt.dynvpn.de>,
> > FreeBSD Us
> > er wri
On Sat, 15 Apr 2023 18:07:34 +0200
Florian Smeets wrote:
> On 15.04.23 17:51, FreeBSD User wrote:
> > Am Sat, 15 Apr 2023 07:36:25 -0700
> > Cy Schubert schrieb:
> >>
> >> With an up-to-date tree + pjd@'s "Fix data corruption when cloning embedded
&
In message <5a47f62d-0e78-4c3e-84c0-45eeb03c7...@yahoo.com>, Mark Millard
write
s:
> On Apr 15, 2023, at 07:36, Cy Schubert =
> wrote:
>
> > In message <20230415115452.08911...@thor.intern.walstatt.dynvpn.de>,=20=
>
> > FreeBSD Us
> > er writes:
> &g
imental sysctl. Maybe even have it print "(experimental)" to warn
users that it will hurt.
3. Update the man pages to caution that block_cloning is experimental and
unstable.
It's not enough to have a sysctl without hiding block_cloning completely
from view. Only expose it in zpo
een detected in the following files:
>
>
>Can it be that the error was in file which is deleted now? Or was in snapshot
>which was already destroyed by some automatic script?
>
>Kind regards
>Miroslav Lachman
>
>
Zpool export/import or reboot may fix this.
--
Cheers
Can you try wpa_supplicant-devel? It was updated last week. The -devel port
tracks the latest WPA development.
--
Cheers,
Cy Schubert
FreeBSD UNIX:Web: https://FreeBSD.org
NTP: Web: https://nwtime.org
e^(i*pi
On Fri, 30 Jun 2023 10:56:54 -0700
Cy Schubert wrote:
> Can you try wpa_supplicant-devel? It was updated last week. The -devel port
> tracks the latest WPA development.
>
>
Now that I'm back at home, looking at hostap (our upstream w1.fi) commit
logs, there have been
Pull request #787. I can look at it.
--
Cheers,
Cy Schubert
FreeBSD UNIX: Web: https://FreeBSD.org
NTP: Web: https://nwtime.org
e^(i*pi)+1=0
In message , "Naman
Sood
" writes:
> Hi,
>
> wpa_supplicant-devel unfortunately did
xfe0=
> 422ef8560) at /usr/src/sys/sys/file.h:367
> > #17 kern_ioctl (td=3Dtd@entry=3D0xfe0422ef8560, fd=3D4, com=3Dcom=
> @entry=3D3222821401, data=3D, data@entry=3D0xfffffe02fb827d50 =
> "\017") at /usr/src/sys/kern/sys_generic.c:807
> > #18 0x
I haven't experienced any problems (yet) either.
--
Cheers,
Cy Schubert
FreeBSD UNIX: Web: https://FreeBSD.org
NTP: Web: https://nwtime.org
e^(i*pi)+1=0
In message
, Kevin Bowling writes:
> The two MFVs on head have improved/fixed stabil
s consistent with PR/271945. Reducing -J to 1 or 5:1 circumvents this
panic.
This is certainly a different panic from the one experienced on the
poudriere builder building i386 packages. Both machines run in amd64 mode.
--
Cheers,
Cy Schubert
FreeBSD UNIX: Web: https://FreeBSD.org
NTP
t /usr/src/sys/fs/devfs/devfs_vnops.c:866
>#15 0x80bca1ce in fo_ioctl (fp=0xf81e9207f0a0, com=3222821401,
> data=, active_cred=, td=) at
> /usr/src/sys/sys/file.h:367
>#16 kern_ioctl (td=td@entry=0xfe0314249020, fd=,
> com=com@entry=3222821401, data=, data@e
Cheers,
Cy Schubert
FreeBSD UNIX: Web: https://FreeBSD.org
NTP: Web: https://nwtime.org
e^(i*pi)+1=0
message dated "Tue, 15 Aug 2023 17:18:37 -0400."
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
In message
memory is laid out on your
system you may get a hang instead.
You need to install thew new kernel and world first. Disable xdm, gdm, any
other *dm, or simply not use startx. From a text console session rebuild
the drm port and reinstall it.
I use poudriere here. My procedure is to updat
ils" are used a
>lot, probably with userlands from distributions actually using xattr.
>
>Cheers, Felix
>
If we are to break it to fix a problem, maybe a sysctl to enable/disable then?
--
Cheers,
Cy Schubert
FreeBSD UNIX:Web: https://FreeBSD.org
NTP: Web: https://nwtime.org
e^(i*pi)+1=0
Pardon the typos. Small keyboard in use.
000191264a4fbca in ?? ()
Backtrace stopped: Cannot access memory at address 0x19125ca905c8
(kgdb)
*vp looks good.
Dump is available if needed.
--
Cheers,
Cy Schubert
FreeBSD UNIX: Web: https://FreeBSD.org
NTP: Web: https://nwtime.org
e^(i*pi)+1=0
ÀÀÀÀÀÀÀÀ
In message , Mark Johnston writes:
> On Tue, Aug 29, 2023 at 07:08:35PM -0700, Cy Schubert wrote:
> > Hi
> >
> > Just got the following panic on an and64 machine running poudriere building
>
> > i386 packages.
> >
> > panic: vm_page_dequeue_deferr
6508
9-b22aae410bc7: Wed Aug 30 04:38:24 PDT 2023 root@cwsys:/export/obj/opt/
src/
git-src/amd64.amd64/sys/BREAK2 amd64
Almost the same configuration as the other machine.
--
Cheers,
Cy Schubert
FreeBSD UNIX: Web: https://FreeBSD.org
NTP: Web: https://nwtime.org
rt two days ago. The problems have been documented on the
-current list.
--
Cheers,
Cy Schubert
FreeBSD UNIX: Web: https://FreeBSD.org
NTP: Web: https://nwtime.org
e^(i*pi)+1=0
ÀÀÀÀÀÀÀÀ
In message , Mark Millard
write
s:
> On Sep 5, 2023, at 08:58, Cy Schubert wrote:
>
> > In message <20230830204406.24fd...@slippy.cwsent.com>, Cy Schubert =
> writes:
> >> In message <20230830184426.gm1...@freebsd.org>, Glen Barber writes:
> >>>
k = {lock_object = {
lo_name = 0x80b6167f "explock", lo_flags = 108199936,
lo_data = 0, lo_witness = 0xf8021fd82880}, lk_lock = 1,
lk_exslpfail
ÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀ
On Tue, 12 Sep 2023 05:29:41 +0100
Graham Perrin wrote:
> On 12/09/2023 00:17, Cy Schubert wrote:
>
> > … poudriere …
>
> > panic: vm_page_dequeue_deferred: page 0xfe000b7e9748 has unexpected
> > queue state
> > …
> <https://bugs.freebsd.org/
obal --add safe.directory /usr/src
>
>
This could be due to e6dc6a27230, which was committed this morning. There
is discussion on the src commits ML (dev-commits-src-all,
dev-commits-src-main) about reverting the change.
--
Cheers,
Cy Schubert
FreeBSD UNIX: Web: https://FreeBSD.org
NTP: Web: https://nwtime.org
e^(i*pi)+1=0
ÀÀÀÀÀÀÀÀÀ
9934592: Invalid argument
Try reducing your arc.max by an order of 10. This suggests that it's
probably failing in param_set_arc_max() in the val >= arc_all_memory()
comparison..
--
Cheers,
Cy Schubert
FreeBSD UNIX: Web: https://FreeBSD.org
NTP: Web: https://nwtime.or
gt; at /usr/src/sys/kern/kern_intr.c:1218
> #33 ithread_loop (arg=arg@entry=0xf80001c5aea0)
> at /usr/src/sys/kern/kern_intr.c:1306
> #34 0x804adae2 in fork_exit (
> callout=0x804b1120 , arg=0xf80001c5aea0,
> frame=0xfe00ce259f
On Wed, 8 Nov 2023 15:14:34 +0100
Marek Zarychta wrote:
> W dniu 8.11.2023 o 14:10, Marek Zarychta pisze:
> >
> > W dniu 27.09.2023 o 01:07, Tomoaki AOKI pisze:
> >> On Tue, 26 Sep 2023 15:19:46 -0700
> >> Cy Schubert wrote:
> >>
> >>
should someone else have noticed this.
I'll play around with this a little over the weekend.
--
Cheers,
Cy Schubert
FreeBSD UNIX: Web: https://FreeBSD.org
NTP: Web: https://nwtime.org
e^(i*pi)+1=0
ÀÀÀÀÀÀÀÀ
#x27;s IP to /etc/hosts or if using dhcp, prefix your hostname
to the localhost entry in /etc/hosts like this,
127.0.0.1 my_hostname_whatever_it_is localhost localhost.my.domain
Also make sure rpcbind is running.
--
Cheers,
Cy Schubert
FreeBSD UNIX: Web: https://FreeBSD.org
NTP: Web: https://nwtime.org
e^(i*pi)+1=0
ÀÀÀÀÀÀÀÀÀ
kernel config, both should have
> been rebuilt as a part of
> the kernel build.)
>
Is anyone by chance seeing autofs in the backtrace too?
--
Cheers,
Cy Schubert
FreeBSD UNIX: Web: https://FreeBSD.org
NTP: Web: https://nwtime.org
e^(i*pi)+1=0
the kern.geom.debugflags sysctl foot shooting option so that
it works. (Not that bsdlabel or fdisk worked around the issue). Otherwise
one is left with boot to single user or from alternate media if that
doesn't work.
I do have a patch that circumvents the problem. I haven't looked it i
>
> > > fdisk was good, but somewhere around the CHS -> LBA transition things
> > > got weird with it, and for really big disks there were reports of issues
> that
> > > I could never encounter when I set out to fix them... Most likely due to
> a
>
of a commit that broke loader (or was it a
boot blocks -- I can't remember the exact details anymore) in 12 or
13-CURRENT. The extra tools came in handy as I worked through the mess.
>
> gpart is not the "GPT partition tool". It's the universal swiss army =
> knife
> "GEOM partition tool" for all disk partitioning in any format supported.
>
> Kind regards,
> Patrick=
>
--
Cheers,
Cy Schubert
FreeBSD UNIX: Web: https://FreeBSD.org
NTP: Web: https://nwtime.org
e^(i*pi)+1=0
In message
, Warner Losh writes:
> --b0adc9060fbe7411
> Content-Type: text/plain; charset="UTF-8"
> Content-Transfer-Encoding: quoted-printable
>
> On Wed, Jan 24, 2024, 10:07=E2=80=AFPM Cy Schubert om>
> wrote:
>
> > In message <20
In message <2369865.bDOn7JOVgO@ravel>, Olivier Certner writes:
> --nextPart5823302.8T7jmnknE8
> Content-Transfer-Encoding: 7Bit
> Content-Type: text/plain; charset="UTF-8"; protected-headers="v1"
> From: Olivier Certner
> To: Cy Schubert
> Subj
In message <84c6f3b1-58b3-44f8-aeaf-35f78e059...@quip.cz>, Miroslav Lachman
wri
tes:
> On 25/01/2024 06:50, Cy Schubert wrote:
> > In message c
>
>
> >>
> >> What can they do that gpart can't do?
> >
> > This was quite a while ago, boote
In message <20240125101308.92e93...@slippy.cwsent.com>, Cy Schubert writes:
> In message <84c6f3b1-58b3-44f8-aeaf-35f78e059...@quip.cz>, Miroslav Lachman
> wri
> tes:
> > On 25/01/2024 06:50, Cy Schubert wrote:
> > > In message
> > > l.
> >
ving home, other will have other distractions)
>
>As Rod suggested I'll have the tools emit a warning when they are run,
>so that those users will become aware.
>https://reviews.freebsd.org/D43585
>https://reviews.freebsd.org/D43586
>
We can also point people to the two new ports.
nel the answer. btw,
> > see mntopts(3) for where this code would go.
> These days most mount options are parsed in the kernel via vfs_getopts(),
> but not "atime". It appears that "(no)atime" sets/clears MNT_NOATIME in
> userspace via the getmntopts() function tha
In message <3f6cf45c-3d34-4da6-9b81-337eb70bb...@karels.net>, Mike Karels
write
s:
> On 30 Jan 2024, at 15:48, Cy Schubert wrote:
>
> > In message c
> > om>
> > , Rick Macklem writes:
> >> On Tue, Jan 30, 2024 at 10:49=E2=80=AFAM Mike Karels wro
> t
sival_ptr =3D 0xfe08a079ee80, sigval_int =3D =
> -1602621824,
> > sigval_ptr =3D 0xfe08a079ee80}, _reason =3D {_fault =3D=
> {
> >_trapno =3D 1489045984}, _timer =3D {_timerid =3D =
> 1489045984,
> >_overrun =3D 17
In message <20240212193044.e089d...@slippy.cwsent.com>, Cy Schubert writes:
> In message <625e0ea4-9413-45ad-b05c-500833a1d...@freebsd.org>,
> tuexen@freebsd.o
> rg writes:
> > > On Feb 12, 2024, at 10:36, Alexander Leidinger =
> > wrote:
> > >=20
&
Cy Schubert writes:
> In message , Gleb Smirnoff writes:
> > On Tue, Apr 09, 2024 at 07:02:11PM +0200, FreeBSD User wrote:
> > F> The crash is still present on the most recent checked out sources as of
> mi
> > nutes ago.
> > F> I just checked out on HEAD the
.c.o -MF
>> src/intel/common/libintel_common.a.p/xe_intel_gem.c.o.d -o
>> src/intel/common/libintel_common.a.p/xe_intel_gem.c.o -c
>> ../src/intel/common/xe/intel_gem.c
>> ../src/intel/common/xe/intel_gem.c:72:9: error: duplicate case value '4'
>>72 |case CLOCK_BOOTTIME:
>
I pushed commits to fix this, the wpa_supplicant*, and hostapd* ports last
night.
--
Cheers,
Cy Schubert
FreeBSD UNIX: Web: https://FreeBSD.org
NTP: Web: https://nwtime.org
e^(i*pi)+1=0
In message
, Nuno Teixeira writes:
>
> (...)
>
week.
It's currently in use here. I've experienced no problems so far.
--
Cheers,
Cy Schubert
FreeBSD UNIX: Web: https://FreeBSD.org
NTP: Web: https://nwtime.org
e^(i*pi)+1=0
revision.
slippy$ git log ce220b82ad546d3518a805750e5ee6add73f1fbf
fatal: bad object ce220b82ad546d3518a805750e5ee6add73f1fbf
slippy$
To verify that my repo wasn't damaged in any way I cloned a fresh new repo
from git.freebsd.org. I still can't list that revision.
>
> --
> Gleb Smirnoff
>
--
Cheers,
Cy Schubert
FreeBSD UNIX: Web: https://FreeBSD.org
NTP: Web: https://nwtime.org
e^(i*pi)+1=0
not logging =
> anymore
>
> =E2=80=A2 [2:13 PM]Flox:
> FreeBSD fbsd15.localdomain 15.0-CURRENT FreeBSD 15.0-CURRENT #0 =
> main-aea9dba46b: Sat Aug 10 16:48:02 EDT 2024 =
> mike@fbsd15.localdomain:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG =
> amd64
Yeah. I'm get
In message <54076f5e-cd6d-40d6-b4b7-495cf8e67...@blastwave.org>, Dennis
Clarke
writes:
> On 8/10/24 22:15, Cy Schubert wrote:
> > In message , Mark Millard
> > write
> > s:
>
> >> =E2=80=A2 [2:12 PM]Flox: getting this error in ZFS since recent =
> &
On Sun, 11 Aug 2024 12:29:18 -0400
Dennis Clarke wrote:
> On 8/11/24 09:41, Cy Schubert wrote:
> > In message <54076f5e-cd6d-40d6-b4b7-495cf8e67...@blastwave.org>, Dennis
> > Clarke
> > writes:
> >> On 8/10/24 22:15, Cy Schubert wrote:
> >>&g
using grep in scripts
and at times I need simply grep.
---
Sent using a tiny phone keyboard. Apologies for any typos and autocorrect.
Cy Schubert
or
-Original Message-
From: Kevin Oberman
Sent: 28/09/2017 10:13
To: Warner Losh
Cc: Nick Hibma; FreeBSD Current Mailing List
Subject: Re: H
hostapd is also affected. Simple for us, not so simple if you've
purchased a commodity wirless router. I doubt most of the vendors will do
anything.
There are over a dozen (excluding tests and debugging outputs, 16 by my count)
commits our upstream have applied to hostapd and wpa_supplicant.
17-13080, CVE-2017-13081, CVE-2017-13082, CVE-2017-13084,
> CVE-2017-13086,CVE-2017-13087, CVE-2017-13088.
The gory details are here:
https://w1.fi/security/2017-1/wpa-packet-number-reuse-with-replayed-messages.txt
The announcement is here:
https://www.krackattacks.com/
--
Cheers,
Cy Schube
Eight patches have been posted so, it should be easy to patch 2.5, MFC, and
bring head up to 2.6 later. This should avoid the risk of possible regressions.
I haven't looked at the ports.
---
Sent using a tiny phone keyboard. Apologies for any typos and autocorrect.
Cy Schuber
Looking at the wpa_supplicant port, it may be a quicker win than base at
the moment.
I don't have much of my lunch hour left to complete anything.
--
Cheers,
Cy Schubert
FreeBSD UNIX: Web: http://www.FreeBSD.org
The need of the many outweighs the greed of the few.
In me
I'll commit the wpa_supplicant port now but I don't have enough time this
lunch hour to create a vuxml entry or to update the hostapd port.
It may be simpler to update base to 2.6 to facilitate patching. What do
people think?
--
Cheers,
Cy Schubert
FreeBSD UNIX:
It doesn't, which is why I patched the port at lunch today. It's a quick win
with the time I had.
I think we should update base to 2.6 and apply the patches.
---
Sent using a tiny phone keyboard. Apologies for any typos and autocorrect.
Cy Schubert
or
-Original Message-
Fr
I'll test it when I get home tonight. The WiFi here at the tech park is open
so, I couldn't test here.
---
Sent using a tiny phone keyboard. Apologies for any typos and autocorrect.
Cy Schubert
or
-Original Message-
From: Franco Fichtner
Sent: 16/10/2017 13:34
To: Cy S
In message , Franco
Fichtne
r writes:
>
>
> > On 17. Oct 2017, at 12:32 AM, Cy Schubert wrote:
> >
> > I'll test it when I get home tonight. The WiFi here at the tech park is ope
> n so, I couldn't test here.
>
> Tested:
>
> hostapd
In message <20171017125829.ga35...@albert.catwhisker.org>, David Wolfskill
writ
es:
>
>
> --azLHFNyN32YCQGCU
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
> Content-Transfer-Encoding: quoted-printable
>
> On Mon, Oct 16, 2017 at 11:27
I had no problems last night. It associated with one of my netgear APs. I used
/etc/wpa_supplicant.conf.
I am running head and all my ports are built on head (most poudeiere and a few
by hand).
---
Sent using a tiny phone keyboard. Apologies for any typos and autocorrect.
Cy Schubert
or
Adrian,
??? Are you replying to me?
--
Cheers,
Cy Schubert
FreeBSD UNIX: Web: http://www.FreeBSD.org
The need of the many outweighs the greed of the few.
In message
, Adrian Chadd writes:
> [snip]
>
> yes you need to rebuild; the ioctl layout changed between -1
ly either. Our friends at pfsense document it be disabled.
It can cause issues with our ipfilter firewall on some interfaces (e.g.
fxp). I also recall reading a Juniper KB about path MTU discovery and TSO
not playing well together.
Not that TSO is bad but disabling it is something to try whe
iews.freebsd.org
Yes, and that's the first step to becoming a committer. I recall sending
multiple patches because I didn't want to patch brand new FreeBSD systems
after installing the ISO (they were plastic discs then). (We used FreeBSD
for infrastructure servers at $JOB at the
osed changes
> as plain text would also be an option? Â I suspect there are more people
> with good ideas on improving manpages than there are people who've
> decided they really want to learn the arcane skill of manpage markup
> language.
That's a useful skill too. Not jus
test most build cases for things like bmake upgrades
> > or other high risk changes like META_MODE.
> >
> >
> > I'll think about this and add to my list of things to implement.
>
> I would even go so far as to say this may be what we should be
> running in (a)
.
Cy Schubert
or
---
-Original Message-
From: Thomas Laus
Sent: 22/11/2017 04:50
To: FreeBSD Current
Subject: Mergemaster won't run on NFS mount
I have been updating FreeBSD for years on my fastest computer and then
NFS mounting /usr/src and /usr/obj to share with other PC'
In message <20171122201845.ga57...@mail.laus.org>, Thomas Laus writes:
> Cy Schubert [cy.schub...@komquats.com] wrote:
> > I used to buildworld/installeworld using NFS shares at one time. Testing it
> again this morning revealed still no issues. I used a ro src and rw obj
What about those of us who want multiple accounts?
Just kidding but you get my point.
What's to stop someone from having more than one vote?
---
Sent using a tiny phone keyboard.
Apologies for any typos and autocorrect.
Also, this old phone only supports top post. Apologies.
Cy Schuber
old phone only supports top post. Apologies.
Cy Schubert
or
The need of the many outweighs the greed of the few.
---
-Original Message-
From: O. Hartmann
Sent: 12/12/2017 14:19
To: Rodney W. Grimes
Cc: O. Hartmann; FreeBSD CURRENT; Freddie Cash; Alan Somers
Subject: Re: SMART: disk pro
IIRC, as I scripted this and haven't looked at it for a long time: LESS=-MMs
---
Sent using a tiny phone keyboard.
Apologies for any typos and autocorrect.
Also, this old phone only supports top post. Apologies.
Cy Schubert
or
The need of the many outweighs the greed of th
This Linux commit gives us a hint.
https://lkml.org/lkml/2017/12//27/2
---
Sent using a tiny phone keyboard.
Apologies for any typos and autocorrect.
Also, this old phone only supports top post. Apologies.
Cy Schubert
or
The need of the many outweighs the greed of the few.
---
-Original
https://mobile.twitter.com/grsecurity/status/948170302286172160?p=v
---
Sent using a tiny phone keyboard.
Apologies for any typos and autocorrect.
Also, this old phone only supports top post. Apologies.
Cy Schubert
or
The need of the many outweighs the greed of the few.
---
-Original
---
Sent using a tiny phone keyboard.
Apologies for any typos and autocorrect.
Also, this old phone only supports top post. Apologies.
Cy Schubert
or
The need of the many outweighs the greed of the few.
---
-Original Message-
From: Zaphod Beeblebrox
Sent: 02/01/2018 15:50
To: Michael
On January 2, 2018 4:24:55 PM PST, Cy Schubert wrote:
>https://mobile.twitter.com/grsecurity/status/948170302286172160?p=v
>
>---
>Sent using a tiny phone keyboard.
>Apologies for any typos and autocorrect.
>Also, this old phone only supports top post. Apologies.
>
>Cy Sch
On January 2, 2018 4:56:48 PM PST, Michael Butler
wrote:
>On 01/02/18 19:20, Cy Schubert wrote:
>> This Linux commit gives us a hint.
>>
>> https://lkml.org/lkml/2017/12//27/2
>
>Sadly, the articles I've read to date make no mention of which Intel
>silicon re
Sorry, cpuid.
---
Sent using a tiny phone keyboard.
Apologies for any typos and autocorrect.
Also, this old phone only supports top post. Apologies.
Cy Schubert
or
The need of the many outweighs the greed of the few.
---
-Original Message-
From: Kurt Jaeger
Sent: 02/01/2018 21:41
To
More food for thought.
https://mobile.twitter.com/pwnallthethings/status/947978927284383744
---
Sent using a tiny phone keyboard.
Apologies for any typos and autocorrect.
Also, this old phone only supports top post. Apologies.
Cy Schubert
or
The need of the many outweighs the greed of the few
201 - 300 of 452 matches
Mail list logo
