Fixes broken cryptographic authentication in OSPF

Cryptographic authentication in OSPF is defective by
design - there might be several packets independently
sent to the network (for example HELLO, LSUPD and LSACK)
where they might be reordered and that causes crypt.
sequence number error.

That can be workarounded by not incresing sequence number
too often. Now we update it only when last packet was sent
before at least one second. This can constitute a risk of
replay attacks, but RFC supposes something similar (like time
in seconds used as CSN).

1 files changed, 7 insertions, 1 deletions

diff --git a/nest/config.Y b/nest/config.Y
index 48940ff..e843777 100644
--- a/nest/config.Y
+++ b/nest/config.Y
@@ -22,7 +22,13 @@ static list *this_p_list;
 static struct password_item *this_p_item;
 static int password_id;
 
-static list *
+static inline void
+reset_passwords(void)
+{
+ this_p_list = NULL;
+}
+
+static inline list *
 get_passwords(void)
 {
   list *rv = this_p_list;