forked from richardcochran/linuxptp
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
port: add security processing to bc_event()
add sad_process_auth() to bc_event() to check for authentication tlvs on incoming messages. This processing happens after msg_post_recv(). However, if security is active, a duplicate message is allocated and kept in network byte order to be used for icv calculation. The standard proposes a security parameters database (SPD) to specify policy limiting attributes as to which messages should authenticated but this is a lot of overhead for a something that isn't too helpful. For this patch, the only policy limiting attribute is the port. That is to say, you can specify a spp (and corresponding Security Association) for each port. When spp is set to -1, no security processing is done. Signed-off-by: Clay Kaiser <Clay.Kaiser@ibm.com> Reviewed-by: Erez Geva <ErezGeva2@gmail.com> Reviewed-by: Miroslav Lichvar <mlichvar@redhat.com>
- Loading branch information
1 parent
d9511f7
commit 60980bb
Showing
9 changed files
with
182 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.