On Sat, 13 Nov 2021, Damien Miller wrote:
> On Thu, 11 Nov 2021, Damien Miller wrote:
>
> > Hi,
> >
> > Snaps is now carrying a change to ssh/sshd that converts their
> > mainloops from select(2) to poll/ppoll(2). This change should be
> > completely transparent, but please be on the lookout
On Mon, Nov 15, 2021 at 02:16:34PM +0300, Vitaliy Makkoveev wrote:
> ping...
OK bluhm@
> On Sat, Nov 13, 2021 at 07:20:23PM +0300, Vitaliy Makkoveev wrote:
> > On Fri, Nov 12, 2021 at 03:28:42AM +0300, Vitaliy Makkoveev wrote:
> > > The final step before rework UNIX sockets to fine grained
On Mon, Nov 15, 2021 at 04:25:54PM -0700, Theo de Raadt wrote:
> > + _cmds[${#_cmds[*]}]="ifconfig $_if $_ifup"
>
> I will be surprised if you can simply add "up" to potential
> ifconfig commandlines.
This does not amend "ifconfig foo0 bar ..." to ifconfig foo0 bar ... up"
if that's what
> + _cmds[${#_cmds[*]}]="ifconfig $_if $_ifup"
I will be surprised if you can simply add "up" to potential
ifconfig commandlines.
On Mon, Nov 15, 2021 at 02:31:42PM +, Klemens Nanni wrote:
> On Mon, Nov 15, 2021 at 01:37:49PM +, Stuart Henderson wrote:
> > On 2021/11/15 12:27, Klemens Nanni wrote:
> > > On Sun, Nov 14, 2021 at 07:04:42PM -0700, Theo de Raadt wrote:
> > > > I think physical interfaces should come up
On 15.11.2021. 17:23, Alexander Bluhm wrote:
> Hi,
>
> To debug IPsec and tdb refcounting it may be useful to have "show
> tdb" and "show all tdbs" in ddb.
Here's panic with this and mvs@ version of "IPsec tdb ref counting" diff
r620-1# > tdb_free() killing ourself
panic: kernel
On 15.11.2021. 16:44, Hrvoje Popovski wrote:
> On 15.11.2021. 15:04, Vitaliy Makkoveev wrote:
>> On Mon, Nov 15, 2021 at 02:51:16PM +0100, Hrvoje Popovski wrote:
>>
>> And you don'n see "> tdb_free() killing ourself" in dmesg
>> output?
>
>
> I couldn't find that message anywhere
>
On Mon, Nov 15, 2021 at 12:19:48PM +, Klemens Nanni wrote:
> On Mon, Nov 15, 2021 at 02:08:33PM +1000, David Gwynne wrote:
> > The subject line only tells half the story. The other half is that
> > instead of hoping it only identifies Ethernet interfaces it now actually
> > checks and
On Nov 15 17:58:38, schwa...@usta.de wrote:
> Hi Marc,
>
> Marc Espie wrote on Mon, Nov 15, 2021 at 05:06:23PM +0100:
> > On Mon, Nov 15, 2021 at 03:43:47PM +0100, Jan Stary wrote:
> >> On Nov 10 18:46:08, h...@stare.cz wrote:
> >>> On Nov 10 18:15:44, h...@stare.cz wrote:
>
> expr(1) says
On Mon, Nov 15, 2021 at 05:58:38PM +0100, Ingo Schwarze wrote:
> I don't know. A fairly reliable way to create security risks is
> complexity. Apart from the erratic run time behaviour that is likely to
> trip up sysadmins - LC_COLLATE can change the collation sequence even
> among ASCII
Hi Marc,
Marc Espie wrote on Mon, Nov 15, 2021 at 05:06:23PM +0100:
> On Mon, Nov 15, 2021 at 03:43:47PM +0100, Jan Stary wrote:
>> On Nov 10 18:46:08, h...@stare.cz wrote:
>>> On Nov 10 18:15:44, h...@stare.cz wrote:
expr(1) says
expr1 {=, >, >=, <, <=, !=} expr2
Eichert, Diana wrote:
> As a person who has spent a lot of time configuring network devices it
> seems normal to explicitly bring an interface UP, whatever type of
> interface.
Some commercial routers and switches have explicit up operations.
Others follow a change-and-commit model.
But
Hi,
To debug IPsec and tdb refcounting it may be useful to have "show
tdb" and "show all tdbs" in ddb.
ok?
bluhm
Index: share/man/man4/ddb.4
===
RCS file: /data/mirror/openbsd/cvs/src/share/man/man4/ddb.4,v
retrieving revision
On Mon, Nov 15, 2021 at 03:43:47PM +0100, Jan Stary wrote:
> Here's a try (see below);
> one sentence one line while here.
>
> I would also replace 'results' with 'result' everywhere,
> but I am not a native speaker.
>
> Jan
>
>
> On Nov 10 18:46:08, h...@stare.cz wrote:
> > On Nov 10
On 15.11.2021. 15:04, Vitaliy Makkoveev wrote:
> On Mon, Nov 15, 2021 at 02:51:16PM +0100, Hrvoje Popovski wrote:
>
> And you don'n see "> tdb_free() killing ourself" in dmesg
> output?
I couldn't find that message anywhere
On Sun, Nov 14, 2021 at 10:50:34PM +0100, Alexander Bluhm wrote:
> On Sat, Nov 13, 2021 at 06:04:07PM +0100, Alexander Bluhm wrote:
> > It passes regress but there are setups that are not covered. Bridge
> > and pfsync with IPsec and TCP signature need special care.
> >
> > When testing, please
Here's a try (see below);
one sentence one line while here.
I would also replace 'results' with 'result' everywhere,
but I am not a native speaker.
Jan
On Nov 10 18:46:08, h...@stare.cz wrote:
> On Nov 10 18:15:44, h...@stare.cz wrote:
> > expr(1) says
> >
> > expr1 {=, >, >=, <, <=,
(Does anyone want to commit this please?)
On Nov 10 09:31:57, mill...@openbsd.org wrote:
> On Wed, 10 Nov 2021 17:29:55 +0100, Jan Stary wrote:
>
> > With included, there is no need
> > to declare extern int optind and friends again.
>
> Right, most of this is old code that dates from before
On Mon, Nov 15, 2021 at 01:37:49PM +, Stuart Henderson wrote:
> On 2021/11/15 12:27, Klemens Nanni wrote:
> > On Sun, Nov 14, 2021 at 07:04:42PM -0700, Theo de Raadt wrote:
> > > I think physical interfaces should come up when something is configured
> > > on them, but virtual interfaces
On Mon, Nov 15, 2021 at 02:55:35PM +0100, Marcus MERIGHI wrote:
> Hello,
>
> [...]
> > +A more detailed cleanup can be done with the aid of the sysclean package.
>
> FWIW, sysclean(8) (that I just ran) did not remove
>
> /etc/fonts/conf.d/70-no-bitmaps.conf
>
it will, when snapshots
On Mon, Nov 15, 2021 at 02:51:16PM +0100, Hrvoje Popovski wrote:
And you don'n see "> tdb_free() killing ourself" in dmesg
output?
> On 15.11.2021. 13:11, Vitaliy Makkoveev wrote:
> > Hi,
> >
> > Could you try this diff? It should still panic, but I suspect to see
> > ">
On 15.11.2021. 13:11, Vitaliy Makkoveev wrote:
> Hi,
>
> Could you try this diff? It should still panic, but I suspect to see
> "> tdb_free() killing ourself" string.
panic with your diff
r620-1# panic: kernel diagnostic assertion "refcnt != ~0" failed: file
"/sys/kern/kern_synch.c",
On 2021/11/15 12:27, Klemens Nanni wrote:
> On Sun, Nov 14, 2021 at 07:04:42PM -0700, Theo de Raadt wrote:
> > I think physical interfaces should come up when something is configured
> > on them, but virtual interfaces shouldn't -- mostly because the order of
> > configuration is often muddled.
>
On 2021 Nov 15 (Mon) at 13:58:08 +0100 (+0100), Claudio Jeker wrote:
:On Mon, Nov 15, 2021 at 12:23:02PM +, Klemens Nanni wrote:
...
:Sure people got used to this mode. I agree with dlg@ that the way that
:this auto interface up happens is rather horrible from a network stack
:view. Also it
On Mon, Nov 15, 2021 at 12:23:02PM +, Klemens Nanni wrote:
> On Mon, Nov 15, 2021 at 12:00:18PM +1000, David Gwynne wrote:
> > On Sat, Nov 13, 2021 at 11:59:59PM +, Klemens Nanni wrote:
> > > Practically all interfaces pull itself up when IPs get assigned, but
> > > vport(4) does not.
> >
On 2021/11/15 12:16, Raf Czlonka wrote:
> On Mon, Nov 15, 2021 at 11:38:20AM GMT, Zé Loff wrote:
> >
> > On Mon, Nov 15, 2021 at 11:01:39AM +, Stuart Henderson wrote:
> > > Remove the symlink named something like 70-bitmap-only from
> > > /etc/fonts/conf.d
> >
> > Yes! Thank you!
> > For
On Sun, Nov 14, 2021 at 07:04:42PM -0700, Theo de Raadt wrote:
> I think physical interfaces should come up when something is configured
> on them, but virtual interfaces shouldn't -- mostly because the order of
> configuration is often muddled.
So "inet6 2001:db8::1" in hostname.em0 will do the
On Mon, Nov 15, 2021 at 12:00:18PM +1000, David Gwynne wrote:
> On Sat, Nov 13, 2021 at 11:59:59PM +, Klemens Nanni wrote:
> > Practically all interfaces pull itself up when IPs get assigned, but
> > vport(4) does not.
>
> Yes, I do (or don't do) this very deliberately when I get the chance.
On Mon, Nov 15, 2021 at 02:08:33PM +1000, David Gwynne wrote:
> The subject line only tells half the story. The other half is that
> instead of hoping it only identifies Ethernet interfaces it now actually
> checks and restricts itself to Ethernet interfaces. I couldn't help
> myself.
>
> If it
On Mon, Nov 15, 2021 at 12:35:13PM +0100, Hrvoje Popovski wrote:
> On 14.11.2021. 22:50, Alexander Bluhm wrote:
> > New diff with fix from mvs@. Please continue testing with this one.
>
> Hi,
>
> i've applied this diff on sasyncd setup with two ipsec sessions and i'm
> getting this panic. Box
On Mon, Nov 15, 2021 at 11:38:20AM GMT, Zé Loff wrote:
>
> On Mon, Nov 15, 2021 at 11:01:39AM +, Stuart Henderson wrote:
> > Remove the symlink named something like 70-bitmap-only from
> > /etc/fonts/conf.d
>
> Yes! Thank you!
> For the archives: it's /etc/fonts/conf.d/70-no-bitmaps.conf
On Mon, Nov 15, 2021 at 11:01:39AM +, Stuart Henderson wrote:
> Remove the symlink named something like 70-bitmap-only from /etc/fonts/conf.d
Yes! Thank you!
For the archives: it's /etc/fonts/conf.d/70-no-bitmaps.conf
> --
> Sent from a phone, apologies for poor formatting.
>
> On 15
On 14.11.2021. 22:50, Alexander Bluhm wrote:
> New diff with fix from mvs@. Please continue testing with this one.
Hi,
i've applied this diff on sasyncd setup with two ipsec sessions and i'm
getting this panic. Box didn't panic instantly but after some time. I
will leave ddb console active...
ping...
On Sat, Nov 13, 2021 at 07:20:23PM +0300, Vitaliy Makkoveev wrote:
> On Fri, Nov 12, 2021 at 03:28:42AM +0300, Vitaliy Makkoveev wrote:
> > The final step before rework UNIX sockets to fine grained locks. Except
> > `unp_ino' this leaves only per-socket data protected by `unp_lock'. The
>
Remove the symlink named something like 70-bitmap-only from /etc/fonts/conf.d
--
Sent from a phone, apologies for poor formatting.
On 15 November 2021 09:05:46 Zé Loff wrote:
On Fri, Nov 12, 2021 at 07:18:52PM +0100, Matthieu Herrb wrote:
Hi,
I've updated the X server in Xenocara to
On Fri, Nov 12, 2021 at 07:18:52PM +0100, Matthieu Herrb wrote:
> Hi,
>
> I've updated the X server in Xenocara to version 21.1.1, together with
> Freetype (2.11.0) and fontconfig 2.13.94.
>
> One of the visible change of this update is that some LCD panels now
> report their real physical
36 matches
Mail list logo
