IP-SR(8) Linux IP-SR(8)NAME
ip-sr - IPv6 Segment Routing management
SYNOPSIS
ip sr { COMMAND | help }
ip sr hmac show
ip sr hmac set KEYID ALGO
ip sr tunsrc show
ip sr tunsrc set ADDRESS
DESCRIPTION
The ip sr command is used to configure IPv6 Segment Routing (SRv6) internal parameters.
Those parameters include the mapping between an HMAC key ID and its associated hashing algorithm and secret, and the IPv6 address to use as
source for encapsulated packets.
The ip sr hmac set command prompts for a passphrase that will be used as the HMAC secret for the corresponding key ID. A blank passphrase
removes the mapping. The currently supported algorithms for ALGO are sha1 and sha256.
If the tunnel source is set to the address :: (which is the default), then an address of the egress interface will be selected. As this
operation may hinder performances, it is recommended to set a non-default address.
EXAMPLES
Configure an HMAC mapping for key ID 42 and hashing algorithm SHA-256
# ip sr hmac set 42 sha256
Set the tunnel source address to 2001:db8::1
# ip sr tunsrc set 2001:db8::1
SEE ALSO ip-route(8)AUTHOR
David Lebrun <david.lebrun@uclouvain.be>
iproute2 14 Apr 2017 IP-SR(8)
Check Out this Related Man Page
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)