-
Notifications
You must be signed in to change notification settings - Fork 657
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding support for OSPF authentication modes and encryption types #1127
base: master
Are you sure you want to change the base?
Conversation
"Authentication mode to be used for OSPF interface links."; | ||
} | ||
|
||
leaf simple-password { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
when
conditionals could probably be explored to match the branching based on the AUTH_MODE
chosen
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We would want to be able to configure message digest keys, simple password irrespective of mode selected.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's fair. Note in JUNOS there is mutual exclusivity between modes in which password/keys are children of the mode vs. independent objects/toggles
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Have you considered coverage for keychains which is supported across various implementations?
|
||
leaf key-id { | ||
type uint8 { | ||
range "1..255"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This range looks to be EOS specific. The entire 8-bit range is usable including 0 for the Key ID
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, I have removed the restriction.
"Authentication mode to be used for OSPF interface links."; | ||
} | ||
|
||
leaf simple-password { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's fair. Note in JUNOS there is mutual exclusivity between modes in which password/keys are children of the mode vs. independent objects/toggles
} | ||
|
||
leaf auth-key { | ||
type string; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For this and simple-password
, we'll want to consider what these values mean for storage. Much like in ISIS, we likely at least want to leverage oc-types:routing-password
to put some rules around a specific typedef when it comes to reads and writes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have changed the simple-password and auth-key type to oc-types:routing-password
isn't a security threat if we share OSPF configured password via streaming ? |
Thanks, |
Not as of now. |
auth-mode is same as 'Autype' but we have defined it as identity AUTH_MODE. It is added under "authentication" which is under "interface" right? md-encryption is now changed to "auth-algo" which defines the hash algorithm to be used to generate message digest. |
"We would want to be able to configure message digest keys, simple password irrespective of mode selected." ==> Saw this comment from you. If this is the case, mode configuration should be outside of key values right? Means, Autype should reflect what is the actual Autype on the configured on the interface; not the Autype associated with the key. |
So, we can configure mode here without configuring keys right and vice-versa, all existing under "authentication" container. |
Why is Autype is associated with "simple-password"? MD5 also should have an Autype of 2. |
If possible, please make the design common to all Cryptographic Authentications. Keyed-MD5 is just one among them. |
/gcbrun |
No major YANG version changes in commit 589800b |
Change Scope
Currently, OSPF authentication is not well-defined with only the authentication-type parameter being available and also with no defined values specified. Added a backward compatible new authentication node under OSPF interface where we can define authentication modes, simple password, and also a message-digest container to configure key, password, encryption type.
Platform Implementations