On 9/19/2010 6:57 AM, kalpesh varyani wrote:
I would just like to know, how BIND takes care of the 2038 problem.
Since now DNSSEC has a lot to do with timings, there could be issues if
someone would set the signature expiry time to a large value (possibly
after Y2K38). This can create problems, if care is not taken in BIND
code. Or does BIND code is designed so that it relies on the OS to deal
with this problem?
Note that signature expiration times are used to protect from replay
attacks. If you are signing zones with expiration dates 28 years in the
future, you may want to consider if this is a good idea or not.
All signature expire times are in MMDDHHMMSS format in the zone data
and are handled correctly as far as BIND deals with it.
If your OS deals with the 2038 issue correctly, then BIND will as well.
I do also assume that there will be a few BIND releases between now and
then and that you will be upgrading accordingly.
Description: OpenPGP digital signature
bind-users mailing list