Discussion:
dhcp security patch on 14.1
(too old to reply)
Wilson R
2021-08-12 03:33:40 UTC
Permalink
Hello,

after installing the security patch dhcp-4.4.2_P1-x86_64-1_slack14.1.txz on Slackware64 14.1 the dhcpd is not running and giving below error.

#dhcpd -t

Internet Systems Consortium DHCP Server 4.4.2-P1
Copyright 2004-2021 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
stats.c:386: REQUIRE((__builtin_expect(((stats) != ((void *)0)), 1) && __builtin_expect((((const isc__magic_t *)(stats))->magic == ((('S') << 24 | ('t') << 16 | ('a') << 8 | ('t')))), 1))) failed, back trace
#0 0x5fcb94 in ??
#1 0x5fcafa in ??
#2 0x61b2a2 in ??
#3 0x54cd35 in ??
#4 0x4f8862 in ??
#5 0x537b08 in ??
#6 0x48dbd0 in ??
#7 0x48de07 in ??
#8 0x40eb77 in ??
#9 0x40d1df in ??
#10 0x7f4c74bfad05 in ??
#11 0x40db71 in ??
Aborted

If the dhcp is reverted to dhcp-4.2.5_P1-x86_64-1.txz there is no issue.
Kindly let me know if there is an issue with the patch.

Thanks in advance.

WR
John McCue
2021-08-12 22:44:04 UTC
Permalink
Post by Wilson R
Hello,
after installing the security patch
dhcp-4.4.2_P1-x86_64-1_slack14.1.txz on Slackware64 14.1
the dhcpd is not running and giving below error.
<snip>

On Slackware 14.2 I needed to modify
/etc/NetworkManager/conf.d/00-dhcp-client.conf

and change it to use:
dhcp=dhclient

This was needed due to the modum provided to me by comcast.
Post by Wilson R
Thanks in advance.
WR
HTH
Wilson R
2021-08-13 13:09:27 UTC
Permalink
Post by John McCue
Post by Wilson R
Hello,
after installing the security patch
dhcp-4.4.2_P1-x86_64-1_slack14.1.txz on Slackware64 14.1
the dhcpd is not running and giving below error.
<snip>
On Slackware 14.2 I needed to modify
/etc/NetworkManager/conf.d/00-dhcp-client.conf
dhcp=dhclient
This was needed due to the modum provided to me by comcast.
Post by Wilson R
Thanks in advance.
WR
HTH
The issue is with the dhcp server and not with the dhcp-client. I have now created a slackware package from the source for dhcp-4.4.2_P1-x86_64-1_slack14.1.txz, which is working fine.

Thanks.
Mike Small
2021-08-13 15:31:15 UTC
Permalink
Post by Wilson R
The issue is with the dhcp server and not with the dhcp-client. I have
now created a slackware package from the source for
dhcp-4.4.2_P1-x86_64-1_slack14.1.txz, which is working fine.
Might you be out of date on a library dhcpd uses? The error before
looked like it was either not finding a struct it expected or else a
magic number within the data structure didn't match. This part...

stats.c:386: REQUIRE((__builtin_expect(((stats) != ((void *)0)), 1) &&
__builtin_expect((((const isc__magic_t *)(stats))->magic == ((('S') <<
24 | ('t') << 16 | ('a') << 8 | ('t')))), 1))) failed, back trace

Or maybe he built against 14.2 and assumed that nothing relevant
underneath had changed from 14.1.

- Mike Sm.
Henrik Carlqvist
2021-08-14 15:26:22 UTC
Permalink
Post by Wilson R
I have now created a slackware package from the source for
dhcp-4.4.2_P1-x86_64-1_slack14.1.txz, which is working fine.
Did you have to patch the source or change the way it builds compared to
the slackbuild script to make it work? Sorry I can't be to much help, I
only have a few 14.1 machines and none of them act as a dhcp server.

regards Henrik
Wilson R
2021-08-15 11:53:43 UTC
Permalink
Post by Henrik Carlqvist
Post by Wilson R
I have now created a slackware package from the source for
dhcp-4.4.2_P1-x86_64-1_slack14.1.txz, which is working fine.
Did you have to patch the source or change the way it builds compared to
the slackbuild script to make it work? Sorry I can't be to much help, I
only have a few 14.1 machines and none of them act as a dhcp server.
regards Henrik
I downloaded the source from isc.org (https://downloads.isc.org/isc/dhcp/4.4.2-P1/dhcp-4.4.2-P1.tar.gz)
I had to comment out line below line from the slackware original dhcp-4.2.5 slackbuild script.

#zcat $CWD/dhclient-script.PATH.diff.gz | patch -p1 || exit 1

After which the new package was created (dhcp-4.4.2_P1-x86_64-1.txz).
Wilson R
2021-08-15 11:53:45 UTC
Permalink
Post by Henrik Carlqvist
Post by Wilson R
I have now created a slackware package from the source for
dhcp-4.4.2_P1-x86_64-1_slack14.1.txz, which is working fine.
Did you have to patch the source or change the way it builds compared to
the slackbuild script to make it work? Sorry I can't be to much help, I
only have a few 14.1 machines and none of them act as a dhcp server.
regards Henrik
I downloaded the source from isc.org (https://downloads.isc.org/isc/dhcp/4.4.2-P1/dhcp-4.4.2-P1.tar.gz)
I had to comment out line below line from the slackware original dhcp-4.2.5 slackbuild script.

#zcat $CWD/dhclient-script.PATH.diff.gz | patch -p1 || exit 1

After which the new package was created (dhcp-4.4.2_P1-x86_64-1.txz).
Jimmy Johnson
2021-08-16 02:28:44 UTC
Permalink
Post by Wilson R
Hello,
after installing the security patch dhcp-4.4.2_P1-x86_64-1_slack14.1.txz on Slackware64 14.1 the dhcpd is not running and giving below error.
#dhcpd -t
Thanks in advance.
I'm going to give some information that may or may not help. On another
system I run I got a upgrade that messed up my internet connection,
deleting /etc/resolv.conf and rebooting solved the problem by
auto-installing a new config and it worked. I just changed to name to
resolv.conf.save until I know I had a working solution. Upgrading a
system can be a bitch sometimes.
--
Jimmy Johnson

Slackware 14.2 - AMD A8-7600 - EXT4 at sda12
Registered Linux User #380263
Sylvain Robitaille
2021-08-18 22:37:55 UTC
Permalink
Post by Wilson R
after installing the security patch
dhcp-4.4.2_P1-x86_64-1_slack14.1.txz on Slackware64 14.1 the dhcpd is
not running and giving below error.
Not helpful in this specific case, and more than a little late, but
hopefully helpful to someone out there at some point: in contrast to
the above report, my 32-bit Slackware-14.1 system running dhcpd indeed
had no trouble with the update to dhcp-4.4.2_P1-i486-1_slack14.1.
Certainly it suggests either that a) the OPs system may be missing
an additional update that the patched dhcp package needs, or b)
there is something not entirely ok with the patch package (I don't
recall ever encountering that myself in decades of using Slackware,
but I also wouldn't want to rule it out without trying to duplicate
the behaviour).

That building a custom package on the target system works fine also
reinforces that either of the above is a likely cause of the problem,
but I have to admit that I think it's as good a solution as any other,
so I have no further suggestions for the OP.
--
----------------------------------------------------------------------
Sylvain Robitaille ***@encs.concordia.ca

Systems analyst / AITS Concordia University
Faculty of Engineering and Computer Science Montreal, Quebec, Canada
----------------------------------------------------------------------
Loading...