Creating a Keychain
Context
A keychain must be created before applications are authenticated and encrypted. Deleting the keychain in use may interrupt communication. Exercise caution when you delete the keychain.
Transmission Control Protocol (TCP) applications are connected using TCP authentication. TCP uses enhanced TCP authentication options to send TCP authentication packets. Vendors use different kind-values to represent the enhanced TCP authentication option and different IDs to represent different algorithms. When a keychain is applied to a TCP application, you must configure the kind value and the mapping between the TCP algorithm and algorithm ID based on the peer configuration so that devices of different vendors can communicate.
Procedure
- Run system-view
The system view is displayed.
- Run keychain keychain-name mode { absolute | periodic { daily | weekly | monthly | yearly } }
A keychain is created and the keychain view is displayed.
- (Optional) Configure parameters in TCP authentication.
- Run tcp-algorithm-id { hmac-md5 | hmac-sha-256 | hmac-sha1-12 | hmac-sha1-20 | md5 | sha-1 | sha-256 | sm3 } algorithm-id
The mapping between the TCP algorithm and algorithm ID is configured.
HMAC-MD5, MD5, and SHA-1 have potential security risks. HMAC-SHA-256 or SHA-256 is recommended.
- Run tcp-algorithm-id { hmac-md5 | hmac-sha-256 | hmac-sha1-12 | hmac-sha1-20 | md5 | sha-1 | sha-256 | sm3 } algorithm-id
- (Optional) Run receive-tolerance { value | infinite }
The receive tolerance time is configured.
You are advised to set the receive tolerance time to advance the start receive time and delay the end receive time so that packets are not lost due to time asynchronization on the network.
- Run commit
The configuration is committed.
