ISC-HMAC-FIXUP(1) BIND9 ISC-HMAC-FIXUP(1)NAME
isc-hmac-fixup - fixes HMAC keys generated by older versions of BIND
SYNOPSIS
isc-hmac-fixup {algorithm} {secret}
DESCRIPTION
Versions of BIND 9 up to and including BIND 9.6 had a bug causing HMAC-SHA* TSIG keys which were longer than the digest length of the hash
algorithm (i.e., SHA1 keys longer than 160 bits, SHA256 keys longer than 256 bits, etc) to be used incorrectly, generating a message
authentication code that was incompatible with other DNS implementations.
This bug has been fixed in BIND 9.7. However, the fix may cause incompatibility between older and newer versions of BIND, when using long
keys. isc-hmac-fixup modifies those keys to restore compatibility.
To modify a key, run isc-hmac-fixup and specify the key's algorithm and secret on the command line. If the secret is longer than the digest
length of the algorithm (64 bytes for SHA1 through SHA256, or 128 bytes for SHA384 and SHA512), then a new secret will be generated
consisting of a hash digest of the old secret. (If the secret did not require conversion, then it will be printed without modification.)
SECURITY CONSIDERATIONS
Secrets that have been converted by isc-hmac-fixup are shortened, but as this is how the HMAC protocol works in operation anyway, it does
not affect security. RFC 2104 notes, "Keys longer than [the digest length] are acceptable but the extra length would not significantly
increase the function strength."
SEE ALSO
BIND 9 Administrator Reference Manual, RFC 2104.
AUTHOR
Internet Systems Consortium
COPYRIGHT
Copyright (C) 2010 Internet Systems Consortium, Inc. ("ISC")
BIND9 January 5, 2010 ISC-HMAC-FIXUP(1)
Check Out this Related Man Page
ISC-HMAC-FIXUP(8) BIND9 ISC-HMAC-FIXUP(8)NAME
isc-hmac-fixup - fixes HMAC keys generated by older versions of BIND
SYNOPSIS
isc-hmac-fixup {algorithm} {secret}
DESCRIPTION
Versions of BIND 9 up to and including BIND 9.6 had a bug causing HMAC-SHA* TSIG keys which were longer than the digest length of the hash
algorithm (i.e., SHA1 keys longer than 160 bits, SHA256 keys longer than 256 bits, etc) to be used incorrectly, generating a message
authentication code that was incompatible with other DNS implementations.
This bug has been fixed in BIND 9.7. However, the fix may cause incompatibility between older and newer versions of BIND, when using long
keys. isc-hmac-fixup modifies those keys to restore compatibility.
To modify a key, run isc-hmac-fixup and specify the key's algorithm and secret on the command line. If the secret is longer than the digest
length of the algorithm (64 bytes for SHA1 through SHA256, or 128 bytes for SHA384 and SHA512), then a new secret will be generated
consisting of a hash digest of the old secret. (If the secret did not require conversion, then it will be printed without modification.)
SECURITY CONSIDERATIONS
Secrets that have been converted by isc-hmac-fixup are shortened, but as this is how the HMAC protocol works in operation anyway, it does
not affect security. RFC 2104 notes, "Keys longer than [the digest length] are acceptable but the extra length would not significantly
increase the function strength."
SEE ALSO
BIND 9 Administrator Reference Manual, RFC 2104.
AUTHOR
Internet Systems Consortium
COPYRIGHT
Copyright (C) 2010, 2013 Internet Systems Consortium, Inc. ("ISC")
BIND9 January 5, 2010 ISC-HMAC-FIXUP(8)
First some back ground info:
I am working on a computer running SuSE 7.3
I am still trying to set up a DNS
I downloaded BIND 9.2.1 and was following a tutorial about BIND. It said at virtually the start of the tutorial that I should find a file called named.conf in my /etc directory. Yes, I... (1 Reply)
Dear All
I have a group of patterns which look like this :
2 20080223_15:12:15.259 ISC-Libya BritishTelecom2 104 IAM 20104016641 218925164479 b 3330 ACM b 3337 ANM f 78309 REL b 78520 RLC :COMMA: NCI=10,FCI=2001,CPC=0A,TMR=00,USI: :COMMB: BCI=0434,OBI=01: :RELCAUSE:10:
I want a script that... (4 Replies)
Dear All
I have a file which contains lines looks like this:
ISC Egypt-Alex2 126 104541338 218926893238 f 1B
ISC BT-Colindale 26 249126190534 218913486850 b 29
ISC Egypt-Cairo2 199 129026052 218927661509 b 26
As you see in each line $4 and $5 are phone numbers , i want a script which... (19 Replies)
Dear All
How are you
I have files which look like this :
20080406_12:43:55.779 ISC Sprint- 39 21624032999 218925866728
20080406_12:44:07.811 ISC Sprint- 20 21620241815 218927736810
20080406_12:44:00.485 ISC Sprint- 50 21621910404 218913568053... (0 Replies)
I have tried thought of using instfix -ivqc | grep BIND , but this did not return the result I was looking for; it seem to list out the the different patches that had been applied to BIND. I'm actually looking for overall version, like you'd get when checking the OS level for instance. (1 Reply)
Hi all,
I need to calculate MAC value using HMAC-SHA256 algorithm with a message and a key.
Is there any Linux APIs/utilities already exist for HMAC-SHA256?
Thanks,
Amio (3 Replies)
Hi all,
I have some sort of problem with BIND DNS server my environment as follows.
bash-3.00# cat /etc/release
Solaris 10 6/06 s10s_u2wos_09a SPARC
Copyright 2006 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to... (3 Replies)
Hello,
I have a RedHat machine (version 5.11) and i need to install BIND version version 9.9.7-P2 in order to fix a known BIND vulnerability CVE-2015-5477.
I downloaded the tar file from isc website but i am having trouble to install the file.
Does anybody knows a link for the rpm package of... (0 Replies)