BFD: SHA1 authentication
Add authentication support to BFD feature. Out of three existing authentication types, implement SHA1 (sole RFC requirement). Simple password is insecure and MD5 is discouraged by the RFC, so ignore those. Add/change APIs to allow configuring BFD authentication keys and their usage with BFD sessions. Change-Id: Ifb0fb5b19c2e72196d84c1cde919bd4c074ea415 Signed-off-by: Klement Sekera <ksekera@cisco.com>
This commit is contained in:

committed by
Damjan Marion

parent
402ed31285
commit
b17dd9607e
@ -89,8 +89,8 @@ class VppTestCase(unittest.TestCase):
|
||||
if dl == "core":
|
||||
if resource.getrlimit(resource.RLIMIT_CORE)[0] <= 0:
|
||||
# give a heads up if this is actually useless
|
||||
cls.logger.critical("WARNING: core size limit is set 0, core "
|
||||
"files will NOT be created")
|
||||
print(colorize("WARNING: core size limit is set 0, core files "
|
||||
"will NOT be created", RED))
|
||||
cls.debug_core = True
|
||||
elif dl == "gdb":
|
||||
cls.debug_gdb = True
|
||||
@ -533,12 +533,11 @@ class VppTestCase(unittest.TestCase):
|
||||
|
||||
self.assertEqual(real_value, expected_value, msg)
|
||||
|
||||
def assert_in_range(
|
||||
self,
|
||||
real_value,
|
||||
expected_min,
|
||||
expected_max,
|
||||
name=None):
|
||||
def assert_in_range(self,
|
||||
real_value,
|
||||
expected_min,
|
||||
expected_max,
|
||||
name=None):
|
||||
if name is None:
|
||||
msg = None
|
||||
else:
|
||||
|
Reference in New Issue
Block a user