[BGPCEP-77] Improve the TCP-MD5 framework to expose run-time availability Created: 01/Apr/14 Updated: 03/Mar/19 Due: 30/Apr/14 Resolved: 29/Apr/14 |
|
| Status: | Resolved |
| Project: | bgpcep |
| Component/s: | General |
| Affects Version/s: | Bugzilla Migration |
| Fix Version/s: | Bugzilla Migration |
| Type: | Improvement | ||
| Reporter: | Robert Varga | Assignee: | Dana Kutenicsova |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Issue Links: |
|
||||||||||||||||
| Description |
|
In order to cleanly integrate the MD5 option, the upstream users (BGP and PCEP) need to detect whether the feature is supported at runtime – e.g. whether we are running on a system which supports the underlying interfaces. Some of this information is already available, but it needs to be exposed from MD5NioServerSocketChannel and MD5NioSocketChannel as static methods. It is okay to check only once when the class is loaded – we will not deal with things like kernel module getting unloaded. |
| Comments |
| Comment by Robert Varga [ 29/Apr/14 ] |