-
Notifications
You must be signed in to change notification settings - Fork 13
/
RELNOTES
1952 lines (1327 loc) · 73.3 KB
/
RELNOTES
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
Internet Systems Consortium DHCP Distribution
Version 3.0.7
May 14, 2008
Release Notes
IMPORTANT NEWS IN THIS RELEASE
FAILOVER: As of version 3.0.4, ISC has included a fix for an insidious
bug in the failover implementation which, if left unchecked, could result
in tying up all leases in transitional states (such as released, reset, or
expired). The crux of the problem is the lack of retransmission of leases
that rest in these states. The only way to solve this problem is to carry
additional state on the lease data structures to indicate acknowledgement
state.
To these ends, 'ATSFP', or Actual Time Sent From Peer, is now included
on lease state structures found in your dhcpd.leases file. This value
is identical to TSFP - the exception is that it is zeroed upon every
change to a lease that would necessitate a binding update, and it is
what is used to govern retransmission.
The presence of this new value on lease state structures presents an
operational dilemma. Since a zero value is normal, and there is no way
to version the dhcpd.leases file, if you simply start dhcpd 3.0.4 using
a dhcpd.leases file written by a pre-3.0.4 daemon, it will cause the
daemon to retransmit -all- leases upon connecting the failover channel
(the zero value is sensed to cause a retransmission).
This is harmless, or even beneficial if your lease databases are slightly
out of sync, but undesirable if you have a very large number of
failover-controlled leases.
As a workaround, simply synthesize an 'atsfp' dhcpd.leases entry for each
lease from the most recent 'tsfp' value. For example (all on one line):
awk '/^ tsfp / { printf("%s\n atsfp %s %s %s\n", $0, $2, $3, $4);
next; } // { print $0; }' /var/db/dhcpd.leases
Similarly, in the event it is necessary to downgrade from 3.0.4 to any
previous version, the atsfp values will need to be removed in order to
successfully start:
grep -v '^ atsfp ' /var/db/dhcpd.leases
NEW FEATURES
Version 3 of the ISC DHCP Distribution includes the following features
that are new since version 2.0:
- DHCP Failover Protocol support
- OMAPI, an API for accessing and modifying the DHCP server and
client state.
- Conditional behaviour
- Storing arbitrary information on leases
- Address pools with access control
- Client classing
- Address allocation restriction by class
- Relay agent information option support
- Dynamic DNS updates
- Many bug fixes, performance enhancements, and minor new DHCP
protocol features.
If you are running 3.0 beta 1 and are doing dynamic DNS updates, the
lease file is no longer forward-compatible to 3.0 final. A script
has been provided to convert 3.0b1 lease files. This is in
contrib/3.0b1-lease-convert.
For information on how to install, configure and run this software,
as well as how to find documentation and report bugs, please consult
the README file.
The Dynamic DNS Update support is a descendent of an implementation
done by Lans Carstensen and Brian Dols at Rose-Hulman Institute of
Technology, Jim Watt at Applied Biosystems, Irina Goble at Integrated
Measurement Systems, Igor Sharfmesser at Kazakh Telecom, and Brian
Murrell at BC Tel Advanced Communications. I'd like to express my
thanks to all of these good people here, both for working on the code
and for prodding me into improving it.
Changes since 3.0.7rc1
- None.
Changes since 3.0.7b1
- None.
Changes since 3.0.6
- Fixed "--version" flag in dhcrelay.
- Clarified error message when lease limit exceeded
- Fixed a buffer overflow error which could have allowed a denial
of service under unusual server configurations
- Bug in octal parsing fixed. Thanks to Bernd Fuhrmann for the report
and fix.
- The warning logged when an address range doesn't fit in the subnets
they were declared has been updated to be more helpful and identify the
typo in configuration that created the spanning addresses.
- The 'min-secs' configuration parameter's log message has been updated to
be more helpful.
- Fixed a bug in which write_lease() might report a failure incorrectly.
- Bug in server configuration parser caused server to get stuck on
startup for certain bad pool declarations. Thanks to Guillaume
Knispel for the bug report and fix.
- Fixed file descriptor leak on listen failure. Thanks to Tom Clark.
- Failover binding acks are now transmitted before new binding updates (which
may, very rarely, be related to a lease on the ack queue). This eliminates
a lease database inconsistency bug, as the remote system relies upon the
most recent message it received from its peer.
- POOLREQ messages received within 30 seconds of one another are ignored.
- 'lease imbalance' messages are not logged unless rebalance was actually
attempted ("ten percent" rule).
- A bug was fixed where the 'giaddr' may be used to find the client's subnet
rather than its own 'ciaddr'.
- A log message was introduced to clarify the situation where a failover
'address' parameter (the server's local address) did not resolve to an
IPv4 address.
- When server is configured with options that it overrides, a warning is
issued when the configuration file is read, rather than at the time the
option is overridden. This was important, because the warning was given
every time the option was overridden, which could create a lot of
unnecessary logging.
- When a failover server suspects it has encountered a peer running a
version 3.1.x failover server, a warning that the failover wire protocol
is incompatible is printed.
- The failover server no longer issues a floating point error if it encounters
a previously undefined option code.
- A memory leak when using omapi has been fixed.
Changes since 3.0.6rc1
- supersede_lease() now requeues leases in their respective hardware
address hash bucket. This mirrors client identifier behaviour.
Changes since 3.0.6b1
- None
Changes since 3.0.5
- Assorted fixes for broken network devices: Packet length is now
determined from the IP header length field to finally calculate the
UDP payload length, because some NIC drivers return more data than
they actually recived.
- UDP packets are now stored in aligned data structures.
- Allow trace output files (-tf option) to be overwritten, rather than
crashing dhcpd if the file already exists
- A bug was fixed that caused dhcpd to segfault if a pool was declared
outside the scope of a subnet in dhcpd.conf.
- A logic error in omapi interface code was repaired that might result in
incorrectly indicating 'up' state when any flags were set, rather than
specifically the INTERFACE_REQUESTED flag.Thanks to a patch from
Jochen Voss which got to us via Andrew Pollock at Debian.
- Spelling fixes.
- A reference leak on binding scopes set by ddns updates was repaired.
- A memory leak in the minires_nsendsigned() function call was repaired.
Effectively, this leaked ~176 bytes per DDNS update.
- In the case where an "L2" DHCP Relay Agent (one that does not set giaddr)
was directly attached to the same broadcast domain as the DHCP server,
the RFC3046 relay agent information option was not being returned to the
relay in the server's replies. This was fixed; the dhcp server no longer
requires the giaddr to reply with relay agent information. Note that
this also improves compatibility with L2 devices that "intercept" DHCP
packets and expect relay agent information even in unicast (renewal)
replies. Thanks to a patch from Pekka Silvonen.
- A bug was fixed where the BOOTP header 'sname' field had a value, the
copy written to persistent storage was actually the contents of the
'file' field.
- A bug was fixed where the nwip virtual option space was referencing
the fqdn option's virtual option space's option cache.
- Timestamp parsing errors that indicated missing "minutes" fields rather
than the actually missing "seconds" fields have been repaired thanks to
a patch from Kevin Steves.
- A grammar error in the dhclient.8 manpage was repaired thanks to a patch
from Chris Wagner.
- Several spelling typos were repaired, and some cross-references to other
relevant documents were included in the manpages, thanks to a patch
by Andrew Pollock which got to us via Tomas Pospisek.
- Some bugs were fixed in the 'emergency relay agent options hologram'
which is used to retain relay agent option contents from when the
client was in INIT or REBIND states. This should solve problems where
relay agent options were not echoed from the server, even when giaddr
was set.
- dhclient now closes its descriptor to dhclient.leases prior to executing
dhclient-script. Thanks to a patch from Tomas Pospisek.
- The server's "by client-id" and "by hardware address" hash table lists
are now sorted according to the preference to re-allocate that lease to
returning clients. This should eliminate pool starvation problems
arising when "INIT" clients were given new leases rather than presently
active ones.
- A bug that kept option overloading from working (on reception) has
been repaired.
Changes since 3.0.5rc2
- Failover servers try harder to retransmit binding updates upon entering
NORMAL state.
Changes since 3.0.5rc1
- A bug was repaired in fixes to the dhclient which sought to run the
dhclient-script with the 'EXPIRE' state should it receive a NAK in
response to a REQUEST. The client now iterates the PREINIT state
after the EXPIRE state, so that interfaces that might be configured
'down' can be brought back 'up' and initialized.
- DHCPINFORM handling for clients that properly set ciaddr and come to the
server via a relay agent has been repaired.
Changes since 3.0.4
- A warning that host statements declared within subnet or shared-network
scopes are actually global has been added.
- The default minimum lease time (if min-lease-time was not specified)
was raised from 0 to 300. 0 is not thought to be sensible, and is
known to be damaging.
- Added additional fatal error sanity checks surrounding lease binding
state count calculations (free/active counts used for failover pool
balancing).
- Some time value size fixes in 3.0.4 brought on from FreeBSD /usr/ports were
misapplied to server values rather than client values. The server no longer
advertises 8-byte lease-time options when on 64-bit platforms.
- A bug where leases not in ACTIVE state would get billed to billed classes
(classes with lease limitations) was fixed. Non-active leases OFFERed
to clients are no longer billed (but billing is checked before offering).
- The dhcpd.conf.5 manpage was updated in regard to the ddns-domainname
configuration option - the default configuration and results should be
more clear now.
- If the dhclient were to receive a DHCPNAK while it was in the RENEW
state (and consequently, had an active, 'bound' address and related
configuration options), it would fail to 'tear down' this information
before proceeding into INIT state. dhclient now iterates the dhclient-
script with the 'EXPIRE' action to cause these teardowns prior to entering
INIT state. Thanks to a patch from Chris Zimmerman.
- The omapi.1 manpage had some formatting errors repaired thanks to a patch
from Yoshihiko Sarumaru.
- A few lines of code that were failover-specific were moved within
#if defined() clauses so that compilation without failover could be
made possible.
- The log message emitted when the 'leased-address' value was not available
in dhcpd.conf "executable statements" has been updated to be more helpful.
Manpage information for this value has also been updated.
- Abandoned or dissociated (err condition) leases now remove any related
dynamic dns bindings. Thanks to a patch from Patrick Schoo.
- Attempting to write a new lease file to replace a corrupt (due to
encountering non-retryable errors during writing) lease file should
no longer result in an infinite recursion.
- Host declaration hardware addresses and client identifiers may only be
configured once. dhcpd will now fail to load config files that specify
multiple identifiers (previous versions would silently over-ride the
value with the later configured value).
Changes since 3.0.4rc1
- The dhcp-options.5 manpage was updated to correct indentation errors
thanks to a patch from Jean Delvare.
Changes since 3.0.4b3
- Some manual pages were clarified pursuant to discussion on the dhcp-server
mailing list.
Changes since 3.0.4b2
- Null-termination sensing for certain clients that unfortunatley require
it in DHCPINFORM processing was repaired.
- The host-name option and a few others were moved from "X" format to "t"
format to be compatible with new NULL handling functions.
- DHCPINFORM processing is a little more careful about return addressing
its responses, or if responding via a relay. The INFORM related
messages also log the 'effective client ip address' rather than the
client's supplied ciaddr (since some clients produce null ciaddrs).
- The server was inappropriately sending leases to the RESET state in the
event that multiple active leases were found to match a singly-identified
client. This was changed to RELEASED (by accepting a different, ACTIVE
binding, the client is implicitly releasing its lease). This repairs a
bug wherein secondary servers in failover pairs detecting this condition
move leases to RESET, and primaries refuse to accept that state
transition (properly).
- The memset-after-dmalloc() changes made in 3.0.4b1 have been backed out.
Changes since 3.0.4b1
- Command line parsing in omshell was repaired - it no longer closes
STDIN after reading one line.
- The resolver library no longer closes the /etc/resolv.conf file
descriptor it opened twice.
- Changes to trailing NULL removal in 't' option-atoms has been rethought,
it now includes 'd' (domain name) types, and tries hard not to rewind an
option beyond the start of the text field it is un-terminating.
Changes since 3.0.3
- A DDNS update handling function was misusing the DNS error codes, rather
than the internal generic result enumeration. The result is a confusing
syslog line, logging the wrong condition.
- The DHCP Server was not checking pool balance in the case where it brought
a non-ACTIVE lease out of storage for a client that was returning to use
a lease it once had long ago, and had since expired.
- Failover peers no longer bother to look for free leases to allocate when
they already found the client's ACTIVE lease. DISCOVERs are load balanced
wether freely-allocated or not, unless the server doubts the peer has
leases to allocate.
- Fixed a bug in dhcrelay agent addition code that suppressed trailing
PAD options - it was suppressing only one trailng PAD option, rather
than the entire block of them.
! Fixed some unlikely overlapping-region memcpy() bugs in dhcrelay agent
option addition and stripping code. Added a few sanity checks. Although
highly improbable, due to requiring the reception of a DHCP datagram well
in excess of all known to be used physical MTU limitations, it is possible
this may have been used in a stack overflow security vulnerability. Thanks
to a patch from infamous42md.
! Added some sanity checks to OMAPI connection/authentication code.
Although highly improbable, due to having to deliver in excess of 2^32
bytes of data via the OMAPI channel, not to mention requiring dhcpd to
be able to malloc() a memory region 2^32 bytes in size, it was possible
this might have resulted in a heap overflow security vulnerability.
Thanks to a patch from infamous42md.
- dmalloc() memset()'s the non-debug (data) portion of the allocated
memory to zero. Code that memset()'s the result returned by dmalloc() to
zero is redundant. These redundancies were removed.
- Some type declaration corrections to u_int16_t were made in common/tr.c
(Token Ring support) thanks to a patch from Jason Vas Dias at RedHat.
- A failover bug that was allowing leases that EXPIRED or were RELEASED
where tsfp and tstp are identical timestamps to languish in these
transitional states has been repaired. As a side effect, lease
databases should be kept more consistent overall, not just for these
transitional states.
- If the lease db is deleted out from under the daemon, and it moves to rewrite
the db, it will go ahead with the operation and move the new db into place
once it detects the old db does not exist.
- dhclient now ignores IRDA, SIT, and IEEE1394 network interfaces, as it
is either nonsensical or (in the case of IEEE1394) is not known to support
these interfaces. Thanks to Marius Gedminas and Andrew Pollock of Debian.
- Some previously undocumented reasons for dhclient-script invoking has
been doucmented in the dhclient-script.8 manpage.
- Failover potential expiry calculations (TSTP) have been corrected. Results
should be substantially more consistent, and proper given the constraints.
- Adjusted lease state validation checks in potential-conflict, to
account for possible clock skew similarly to normal state, and several
previously illegal transitions were made legal (ex: active->released).
- An impossible sanity check was removed from omapi/buffer.c, thanks to a
patch from 'infamous42md'.
- An OMAPI host/network byte order problem in lease time values has been
repaired.
- Several minor bugs, largely relating to treating 8-byte time values as
4-byte entities, have been repaired after careful review of the FreeBSD
ports collection's patch set. Thanks to the nameless entities who have
contributed to the FreeBSD ports.
- When writing a trace file, the file is now created with permissions 0600,
to help administrators avoid accidentally publicising sensitive config
data.
- The calculation of the maximum size of DHCP packets no longer includes
Ethernet framing overhead. The result is that the 'Maximum Message
Size' option advertised by clients, or the default value 576, is no
longer reduced by 14 bytes, and instead directly reflects the IP level
MTU (and the default, minimum allowed IP MTU of 576).
- The special status of RELEASED/EXPIRED/RESET leases when a server
is operating in partner-down was fixed. It no longer requires a
lease be twice the MCLT beyond STOS to 'reallocate', and the expiry
event to turn these into FREE leases without peer acknowledgement
(after STOS+MCLT) has been repaired.
- Compilation on older Solaris systems (lacking /usr/include/sys/int_types.h)
has been repaired.
- "append"ing a string onto the end of a "t" type option (such as the
domain-name field) that had been improperly NULL-terminated by the
DHCP server will no longer result in a truncated string containing
only the option from the server, and not the expected appended value.
Thanks to a patch from Jason Vas Dias at RedHat.
- File handlers on configuration state (config files and lease dbs) should
be treated consistently, regardless of wether TRACING is defined or not.
- The linux build environment has had some minor improvements - better
sensing of 64-bit pointer sizes (only used for establishing an icmp_id),
and corrections to #if operators regarding LINUX_MAJOR should it ever
move to 3.[01].x.
- The server now tries harder to survive the condition where it is unable
to open a new lease file to rewrite the lease state database.
Changes since 3.0.3b3
- dhclient.conf documentation for interface {} was updated to reflect recent
discussion on the dhcp-hackers mailing list.
- In response to reports that the software does not compile on GCC 4.0.0,
-Werror was removed from Makefile.conf for all platforms that used it.
We will address the true problem in a future release; this is a temporary
workaround.
Changes since 3.0.3b2
- An error in code changes introduced in 3.0.3b2 was corrected, which caused
static BOOTP clients to receive random addresses.
Changes since 3.0.3b1
- A bug was fixed in BOOTPREQUEST handling code wherein stale references to
host records would be left behind on leases that were not allocated to the
client currently booting (eg in the case where the host was denied booting).
- The dhcpd.conf.5 manpage was updated to be more clear in regards to
multiple host declarations (thanks to Vincent McIntyre). 'Interim' style
dynamic updates were also retouched.
Changes since 3.0.2
- A bug was fixed where a server might load balance a DHCP REQUEST to its
peer after already choosing not to load balance the preceeding DISCOVER.
The peer cannot allocate the originating server's lease.
- In the case where a secondary server lost its stable storage while the
primary was still in communications-interrupted, and came back online,
the lease databases would not be fully transferred to the secondary.
This was due to the secondary errantly sending an extra UPDREQ message
when the primary made its state transition to PARTNER-DOWN known.
- The package will now compile cleanly in gcc 3.3 and 3.4. As a side effect,
lease structures will be 9 bytes smaller on all platforms. Thanks to
Jason Vas Dias at Redhat.
- Interface discovery code in DISCOVER_UNCONFIGURED mode is now
properly restricted to only detecting broadcast interfaces. Thanks
to a patch from Jason Vas Dias at RedHat.
- decode_udp_ip_header was changed so that the IP address was copied out
to a variable, rather than referenced by a pointer. This enforces 4-byte
alignment of the 32-bit IP address value. Thanks to a patch from Dr.
Peter Poeml.
- An incorrect log message was corrected thanks to a patch from
Dr. Peter Poeml.
- A bug in DDNS was repaired, where if the server's first DDNS action was
a DDNS removal rather than a DDNS update, the resolver library's
retransmit timer and retry timer was set to the default, implying a
15 second timeout interval. Which is a little excessive in a synchronous,
single-threaded system. In all cases, ISC DHCP should now hold fast to
a 1-second timeout, trying only once.
- The siaddr field was being improperly set to the server-identifier when
responding to DHCP messages. RFC2131 clarified the siaddr field as
meaning the 'next server in the bootstrap process', eg a tftp server.
The siaddr field is now left zeroed unless next-server is configured.
- mockup_lease() could have returned in an error condition (or in the
condition where no fixed-address was found matching the shared
network) with stale references to a host record. This is probably not
a memory leak since host records generally never die anyway.
- A bug was repaired where failover servers would let stale client identifiers
persist on leases that were reallocated to new clients not sending an id.
- Binding scopes ("set var = value;") are now removed from leases allocated
by failover peers if the lease had expired. This should help reduce the
number of stale binding scopes on leases.
- A small memory leak was closed involving client identifiers larger than
7 bytes, and failover.
- Configuring a subnet in dhcpd.conf with a subnet mask of 32 bits might
cause an internal function to overflow heap. Thanks to Jason Vas Dias
at Redhat.
- Some inconsistencies in treating numbers that the lexer parsed as 'NUMBER'
or 'NUMBER_OR_NAME' was repaired. Hexadecimal parsing is affected, and
should work better.
- In several cases, parse warnings were being issued before the lexical
token had been advanced to the token whose value was causing an error...
causing parse warnings to claim the problem is on the wrong token.
- Host declarations matching on client identifier for dynamic leases will
no longer match fixed-address host declarations (this is now identical
to behaviour for host records matching on hardware address).
Changes since 3.0.2rc3
- A previously undocumented configuration directive, 'local-address',
was documented in the dhcpd.conf manpage.
Changes since 3.0.2rc2
- Two varaibles introduced in 3.0.2b1 were used without being initialized
in the case where neither the FILE nor SNAME fields were available for
overloading. This was repaired.
- A heretofore believed to be impossible corner case of the option
overloading implementation turned out to be possible ("Unable to sort
overloaded options after 10 tries."). The implementation was reworked
to consider the case of an option so large it would require more than
three chunks to fit.
- Many other instances of variables being used without being initialized
were repaired.
- An uninitialized variable in omapi_io_destroy() led to the discovery
that this function may result in orphaned pointers (and hence, a memory
leak).
Changes since 3.0.2rc1
- allocate_lease() was rewritten to repair a bug in which the server would
try to allocate an ABANDONED lease when FREE leases were available.
Changes since 3.0.2b1
- Some dhcp-eval.5 manpage formatting was repaired.
Changes since 3.0.1
- A bug was fixed in the server's 'option overloading' implementation,
where options loaded into the 'file' and 'sname' packet fields were
not aligned precisely as rfc2131 dictates.
- The FreeBSD client script was changed to support the case where a domain
name was not provided by the server.
- A memory leak in 'omshell' per each command line parsed was
repaired, thanks to a patch from Jarkko Torppa.
- Log functions writing to stderr were adjusted to use the STDERR_FILENO
system definition rather than '2'. This is a no-op for 90% of platforms.
- One call to trace_write_packet_iov() counted the number of io vectors
incorrectly, causing inconsistent tracefiles. This was fixed.
- Some expression parse failure memory leaks were closed.
- A host byte order problem in tracefiles was repaired.
- Pools configured in DHCPD for failover possessing permission lists that
previously were assumed to not include dyanmic bootp clients are now
a little more pessimistic. The result is, dhcpd will nag you about just
about most pools that possess a 'allow' statement with no 'deny' that
would definitely match a dynamic bootp client.
- The 'ddns-update-style' configuration warning bit now insists that
the configuration be globally scoped.
- Two memory leaks in dhclient were closed thanks to a patch from Felix
Farkas.
- Some minor but excellently pedantic documentation errors were fixed
thanks to a patch from Thomas Klausner.
- Bugs in operator precedence in executable statements have been repaired
once again. More legal syntaxes should be parsed legally.
- Failing to initialize a tracefile for any reason if a tracefile was
specified is now a fatal error. Thanks to a patch from Albert Herranz.
- Corrected a bug in which the number of leases transferred as calculated
by the failover primary and sent to peers in POOLRESP responses may be
incorrect. This value is not believed to be used by other failover
implementations, excepting perhaps as logged information.
- Corrected a bug in which 'dhcp_failover_send_poolresp()' was in fact
sending POOLREQ messages instead of POOLRESP mesasges. This message
was essentially ignored since failover secondaries effectively do not
respond to POOLREQ messages.
- Type definitions for various bitwidths of integers in the sunos5-5
build of ISC DHCP have been fixed. It should compile and run more
easily when built in 64-bit for this platform.
- "allow known-clients;" is now a legal syntax, to avoid confusion.
- If one dhcp server chooses to 'load balance' a request to its failover
peer, it first checks to see if it believes said peer has a free
lease to allocate before ignoring the DISCOVER.
- log() was logging a work buffer, rather than the value returned by
executing the statements configured by the user. In some cases,
the work buffer and the intended results were the same. In some other
cases, they were not. This was fixed thanks to a patch from Gunnar
Fjone and directconnect.no.
- Compiler warnings for some string type conversions was fixed, thanks
to Andreas Gustafsson.
- The netbsd build environments were simplified to one, in which
-Wconversion is not used, thanks to Andreas Gustafsson.
- How randomness in the backoff-cutoff dhclient configuration variable
is implemented was better documented in the manpage, and the behaviour
of dhclient in REQUEST timeout handling was changed to match that of
DISCOVER timeout handling.
- Omapi was hardened against clients that pass in null values, thanks
to a patch from Mark Jason Dominus.
- A bug was fixed in dhclient that kept it from doing client-side
ddns updates. Thanks to a patch from Andreas Gustafsson, which
underwent some modification after review by Jason Vas Dias.
- Failover implementations disconnected due to the network between
them (rather than one of the two shutting down) will now try to
re-establish the failover connection every 5 seconds, rather than
to simply try once and give up until one of them is restarted.
Thanks to a patch from Ulf Ekberg from Infoblox, and field testing
by Greger V. Teigre which led to an enhancement to it.
- A problem that kept DHCP Failover secondaries from tearing down
ddns records was repaired. Thanks to a patch from Ulf Ekberg from
Infoblox.
- 64bit pointer sizes are detected properly on FreeBSD now.
- A bug was repaired where the DHCP server would leave stale references
to host records on leases it once thought about offering to certain
clients. The result would be to apply host and 'known' scopes to the
wrong clients (possibly denying booting). NOTE: The 'mis-host' patch
that was being circulated as a workaround is not the way this bug was
fixed. If you were a victim of this bug in 3.0.1, you are cautioned
to proceed carefully and see if it fixes your problem.
- A bug was repaired in the server's DHCPINFORM handling, where it
tried to divine the client's address from the source packet and
would get it wrong. Thanks to Anshuman Singh Rawat.
- A log message was introduced to help illuminate the case where the
server was unable to find a lease to assign to any BOOTP client.
Thanks to Daniel Baker.
- A minor dhcpd.conf.5 manpage error was fixed.
Changes since 3.0.1rc14
- The global variable 'cur_time' was centralized and is now uniformly of a
type #defined in system-dependent headers. It had previously been defined
in one of many places as a 32-bit value, and this causes mayhem on 64-bit
big endian systems. It probably wasn't too healthy on little endian
systems either.
- A printf format string error introduced in rc14 was repaired.
- AIX system-dependent header file was altered to only define NO_SNPRINTF
if the condition used to #ifdef in vsnprintf in AIX' header files
is false.
- The Alpha/OSF system-dependent header file was altered to define
NO_SNPRINTF on OS revisions older than 4.0G.
- omapip/test.c had string.h added to its includes.
Changes since 3.0.1rc13
! CAN-2004-0460 - CERT VU#317350: Five stack overflow exploits were closed
in logging messages with excessively long hostnames provided by the
clients. It is highly probable that these could have been used by
attackers to gain arbitrary root access on systems using ISC DHCP 3.0.1
release candidates 12 or 13. Special thanks to Gregory Duchemin for
both finding and solving the problem.
! CAN-2004-0461 - CERT VU#654390: Once the above was closed, an opening
in log_*() functions was evidented, on some specific platforms where
vsnprintf() was not believed to be available and calls were wrapped to
sprintf() instead. Again, credit goes to Gregory Duchemin for finding
the problem. Calls to snprintf() are now linked to a distribution-local
snprintf implementation, only in those cases where the architecture is
not known to provide one (see includes/cf/[arch].h). If you experience
linking problems with snprintf/vsnprintf or 'isc_print_' functions, this
is where to look. This vulnerability did not exist in any previously
published version of ISC DHCP.
- Compilation on hpux 11.11 was repaired.
- 'The cross-compile bug fix' was backed out.
Changes since 3.0.1rc12
- Fixed a bug in omapi lease lookup function, to form the hardware
address for the hash lookup correctly, thanks to a patch from
Richard Hirst.
- Fixed a bug where dhcrelay was sending relayed responses back to the
broadcast address, but with the source's unicast mac address. Should
now conform to rfc2131 section 4.1.
- Cross-compile bug fix; use $(AR) instead of ar. Thanks to Morten Brorup.
- Fixed a crash bug in dhclient where dhcpd servers that do not provide
renewal times results in an FPE. As a side effect, dhclient can now
properly handle 0xFFFFFFFF (-1) expiry times supplied by servers. Thanks
to a patch from Burt Silverman.
- The 'ping timeout' debugs from rc12 were removed to -DDEBUG only,
and reformatted to correct a compilation error on solaris platforms.
- A patch was applied which fixes a case where leases read from the
leases database do not properly over-ride previously read leases.
- dhcpctl.3 manpage was tweaked.
Changes since 3.0.1rc11
- A patch from Steve Campbell was applied with minor modifications to
permit reverse dns PTR record updates with values containing spaces.
- A patch from Florian Lohoff was applied with some modifications to
dhcrelay. It now discards packets whose hop count exceeds 10 by default,
and a command-line option (-c) can be used to set this threshold.
- A failover bug relating to identifying peers by name length instead of
by name was fixed.
- Delcaring failover configs within shared-network statements should no
longer result in error.
- The -nw command line option to dhclient now works.
- Thanks to a patch from Michael Richardson:
- Some problems with long option processing have been fixed.
- Some fixes to minires so that updates of KEY records will work.
- contrib/ms2isc was updated by Shu-Min Chang of the Intel Corporation.
see contrib/ms2isc/readme.txt for revision notes.
- Dhclient no longer uses shell commands to kill another instance of
itself, it sends the signal directly. Thanks to a patch from Martin
Blapp.
- The FreeBSD dhclient-script was changed so that a failure to write to
/etc/resolv.conf does not prematurely end the script. This keeps dhclient
from looping infinitely when this is the case. Thanks to a patch from
Martin Blapp.
- A patch from Bill Stephens was applied which resolves a problem with lease
expiry times in failover configurations.
- A memory leak in configuration parsing was closed thanks to a patch from
Steve G.
- The function which discovers interfaces will now skip non-broadcast or
point-to-point interfaces, thanks to a patch from David Brownlee.
- Options not yet known by the dhcpd or dhclient have had their names
changed such that they do not contain # symbols, in case they should ever
appear in a lease file. An option that might have been named "#144" is
now "unknown-144".
- Another patch from Bill Stephens which allows the ping-check timeout to
be configured as 'ping-timeout'. Defaults to 1.
Changes since 3.0.1rc10
- Potential buffer overflows in minires repaired.
- A change to the linux client script to use /bin/bash, since /bin/sh may
not be bash.
- Some missing va_end cleanups thanks to a patch from Thomas Klausner.
- A correction of boolean parsing syntax validation - some illegal syntaxes
that worked before are now detected and produce errs, some legal syntaxes
that errored before will now work properly.
- Some search-and-replace errors that caused some options to change their
names was repaired.
- Shu-min Chang of the Intel corporation has contributed a perl script and
module that converts the MS NT4 DHCP configuration to a ISC DHCP3
configuration file.
- Applied the remainder of the dhcpctl memory leak patch provided by Bill
Squier at ReefEdge, Inc. (groo@reefedge.com).
- Missing non-optional failover peer configurations will now result in a soft
error rather than a null dereference.
Changes since 3.0.1rc9
- A format string was corrected to fix compiler warnings.
- A number of spelling corrections were made in the man pages.
- The dhclient.conf.5 man page was changed to refer to do-forward-updates
rather than a configuration option that doesn't exist.
- A FreeBSD-specific bug in the interface removal handling was fixed.
- A Linux-specific Token Ring detection problem was fixed.
- Hashes removed from as-yet-unknown agent options, having those options
appear in reality before we know about them will no longer produce
self-corrupting lease databases.
- dhclient will use the proper port numbers now when using the -g option.
- A order-of-operations bug with 2 match clauses in 1 class statement is
fixed thanks to a patch from Andrew Matheson.
- Compilation problems on Solaris were fixed.
- Compilation problems when built with DEBUG or DEBUG_PACKET were repaired.
- A fix to the dhcp ack process which makes certain group options will be
included in the first DHCPOFFER message was made thanks to a patch from
Ling Gou.
- A few memory leaks were repaired thanks to patches from Bill Squier at
ReefEdge, Inc. (groo@reefedge.com).
- A fix for shared-networks that sometimes give clients options for the
wrong subnets (in particular, 'option routers') was applied, thanks to
Ted Lemon for the patch.
- Omshell's handling of dotted octets as values was changed such that dots
one after the other produce zero values in the integer string.
Changes since 3.0.1rc8
- Fix a format string vulnerability in the server that could lead to a
remote root compromise (discovered by NGSEC Research Team, www.ngsec.com).
- Add additional support for NetBSD/sparc64.
- Fix a bug in the command-line parsing of the client. Also, resolve
a memory leak.
- Add better support for shells other than bash in the Linux client
script.
- Various build fixes for modern versions of FreeBSD and Linux.
- Fix a bad bounds check when printing binding state names.
- Clarify documentation about fixed-address and multiple addresses.
- Fix a typo in the authoritative error message.
- Make a log entry when we can't write a billing class.
- Use conversion targets that are the right size on all architectures.
- Increment the hop count when relaying.
- Log a message when lease state is changed through OMAPI.
- Don't rerun the shared_network when evaluating the pool.
- Fix a reversed test in the parser.
- Change the type of rbuf_max.
- Make FTS_LAST a manifest constant to quiet warnings.
Changes since 3.0.1rc7
- Fix two compiler warnings that are generated when compiling on Solaris
with gcc. These stop the build, even though they weren't actually
errors, because we prefer that our builds generate no warnings.
Changes since 3.0.1rc6
- Don't allow a lease that's in the EXPIRED, RELEASED or RESET state
to be renewed.
- Implement lease stealing for cases where the primary has fewer leases
than the secondary, as called for by the standard.
- Add a fudge factor to the lease expiry acceptance code, (suggested
by Kevin Miller of CMU).
- Fix a bug in permit_list_match that made it much too willing to say
that two permit lists matched.
- Unless DEBUG_DNS_UPDATES is defined, print more user-friendly (and
also more compact) messages about DNS updates.
- Fix a bug in generating wire-format domain names for the FQDN option.
- Fix a bug where the FQDN option would not be returned if the client
requested it, contrary to the standard.
- On Darwin, use the FreeBSD DHCP client script.
- On NetBSD/sparc, don't check for casting warnings.
- Add a flag in the DHCP client to disable updating the client's A
record when sending an FQDN option indicating that the client is
going to update its A record.
- In the client, don't attempt a DNS update until one second after
configuring the new IP address, and if the update times out, keep
trying until a response, positive or negative, is received from the
DNS server.
- Fix an uninitialized memory bug in the DHCP client.
- Apply some FreeBSD-specific bug fixes suggested by Murray Stokely.
- Fix a bug in ns_parserr(), where it was returning the wrong sort
of result code in some cases (suggested by Ben Harris of the
NetBSD project).
- Fix a bug in is_identifier(), where it was checking against EOF
instead of the END_OF_FILE token (also suggested by Ben Harris).
- Fix a bug where if an option universe contained no options, the
DHCP server could dump core (Walter Steiner).
- Fix a bug in the handling of encapsulated options.
- Fix a bug that prevented NWIP suboptions from being processed.
- Delete the FTS_BOOTP and FTS_RESERVED states and implement them
as modifier flags to the FTS_ACTIVE state, as called for in the
failover protocol standard.
- Fix bugs in the pool merging code that resulted in references and
dereferences of null pointers. This bug had no impact unless the
POINTER_DEBUG flag was defined.
- In the server, added a do-forward-updates flag that can be used to
disable forward updates in all cases, so that sites that want the
clients to take sole responsibility for updating their A record can
do so.
- Make it possible to disable optimization of PTR record updates.
Changes since 3.0.1rc5