Re: radiusd(8) bsdauth crashes if user authenticates with a mechanism ":style" and group checking on

Fri, 13 Dec 2019 22:37:31 +0200, Dennis Lindroos wrote: > > > If the user argument has the ":style" suffix attached to it then > > getpwnam(user) will return a NULL pointer. > > I tried just using strsep(3) to strip off the auth style and it works for > > me (this

radiusd(8) bsdauth crashes if user authenticates with a mechanism ":style" and group checking on

Hi guys, Discovered this SEGV when trying out radiusd with bsdauth and an alternative user auth mechanism, when group checking is enabled. If the user argument has the ":style" suffix attached to it then getpwnam(user) will return a NULL pointer. I tried just using strsep(3) to strip off the

vxlan(4) unaligned traps on alpha

>Synopsis: vxlan(4) unaligned traps crashes on alpha >Category: alpha >Environment: System : OpenBSD 6.0 Details : OpenBSD 6.0 (GENERIC) #469: Wed Jul 27 03:13:14 MDT 2016 dera...@alpha.openbsd.org:/usr/src/sys/arch/alpha/compile/G ENERIC

[no subject]

>Synopsis:reading from st(4) never stops (no eof?) >Category:kernel >Environment: System : OpenBSD 5.8 Details : OpenBSD 5.8 (GENERIC) #143: Sun Aug 16 06:15:00 MDT 2015 dera...@alpha.openbsd.org:/usr/src/sys/arch/alpha/compile/GENERIC Architecture:

rdistd fails: Could not find mount point

Synopsis: rdistd fails with Could not find mount point Category: system Environment: OpenBSD 5.6-stable Description: When using rdist, the server (rdistd) fails with setmntent failed: Undefined error: 0 which leads to Could not find mount point. How-To-Repeat: Fix: To me it looks like logical

OpenBSD 5.3 kernel build ulpt(4)

Hi I'm trying to compile a non-generic OPENBSD_5_3/i386 kernel and get this error: ld -Ttext 0xD0200120 -e start -N --warn-common -nopie -X -o bsd ${SYSTEM_HEAD} vers.o ${OBJS} ulpt.o(.text+0x8d): In function `ulpt_ucode_loader_hp': /mnt/src/sys/dev/usb/ulpt.c:685: undefined reference to