On Tue, Jul 19, 2022 at 07:18:54PM +0200, Moritz Buhl wrote:
> A solution would be to move the allocation of the pf_anchor struct
> into a pool. One final question would be regarding the size of the
> hiwat or hardlimit. Any suggestions?
10 seems way to low. We want to limit resource abuse.
Dear tech@,
I am investigating a syzkaller reproducer found in the
"no output from test machine (7)" crashes:
https://syzkaller.appspot.com/bug?id=d93e92fde3857c69df2cf46b4244d9814c4318a7
https://syzkaller.appspot.com/text?tag=ReproC=116ee2e008
The code calls DIOCXBEGIN, with different
On Tue, Jul 19, 2022 at 12:31:47PM +0200, Theo Buehler wrote:
> On Tue, Jul 19, 2022 at 11:43:25AM +0200, Claudio Jeker wrote:
> > aspath_extract() should do at least a minimal overflow check and not
> > access memory after the segment. Can't use fatalx here because bgpctl
> > also uses this
On Tue, Jul 19, 2022 at 11:43:25AM +0200, Claudio Jeker wrote:
> aspath_extract() should do at least a minimal overflow check and not
> access memory after the segment. Can't use fatalx here because bgpctl
> also uses this function. Instead return 0, that is an invalid ASN.
> No code will check
On Tue, Jul 19, 2022 at 12:08:40PM +0200, Claudio Jeker wrote:
> Use kf for all struct kroute_full variables in bgpd. This makes the code
> more consistent.
ok
Use kf for all struct kroute_full variables in bgpd. This makes the code
more consistent.
--
:wq Claudio
Index: kroute.c
===
RCS file: /cvs/src/usr.sbin/bgpd/kroute.c,v
retrieving revision 1.273
diff -u -p -r1.273 kroute.c
---
aspath_extract() should do at least a minimal overflow check and not
access memory after the segment. Can't use fatalx here because bgpctl
also uses this function. Instead return 0, that is an invalid ASN.
No code will check the return value but that is fine since all callers
ensure that pos does
On Sun, Jul 17, 2022 at 10:38:53AM +0200, Matthieu Herrb wrote:
> Hi,
>
> twm(1) is the original X11R5 window manager. It has not been update to
> support any of the extended window manager hints and still only knows
> how to handle the legacy bitmapped fonts rendered by the X server.
>
> In
