Security API has been added for OMG DDS Security Specification compliance.

This API consists of only header files which are grabbed from spec IDL. The dynamically loaded plugins should implement API functions.

Built-in plugins will be added to the repository later. Third party plugins will also be able to be integrated.

Signed-off-by: Kurtulus Oksuztepe <kurtulus.oksuztepe@adlinktech.com>
This commit is contained in:
Kurtulus Oksuztepe 2019-05-23 16:57:55 +02:00 committed by eboasson
parent 68c21c06e3
commit 98cf8e2ae5
18 changed files with 1954 additions and 2 deletions

32
docs/dev/todo_list.md Normal file
View file

@ -0,0 +1,32 @@
# TODO LIST
## Security
* Reassess Jeroen's comment:
https://github.com/eclipse-cyclonedds/cyclonedds/pull/177#issuecomment-494040238
> 5. If the security_api just becomes part of ddsc, and it should in my opinion, then I'd prefer you propagate the naming scheme as introduced in ddsrt etc and name the header files e.g. dds/ddssec/auth.h or something instead of dds/security/dds_security_api_authentication.h.
* Reassess Jeroen's comment:
https://github.com/eclipse-cyclonedds/cyclonedds/pull/177#issuecomment-494040238
> I've spent a great deal of time stripping out all the various different error codes and make it so that we simply use DDS_RETCODE_ constants everywhere. This pull request reintroduces separate error codes and that's something I really don't approve of. The security error codes start at an offset of 100 and should nicely integrate with the other codes in dds/ddsrt/retcode.h. The messages should be retrievable using dds_strretcode if you ask me.
* reassess Erik's comment
https://github.com/eclipse-cyclonedds/cyclonedds/pull/177#issuecomment-490718462
> GuidPrefix & BuiltinTopicKey change
* reassess erik's comment
https://github.com/eclipse-cyclonedds/cyclonedds/pull/177#issuecomment-490718462
> ddsrt_strchrs
* Reassess Jeroen's comment:
https://github.com/eclipse-cyclonedds/cyclonedds/pull/177#issuecomment-494040238
> If the security_api just becomes part of ddsc, and it should in my opinion, then I'd prefer you propagate the naming scheme as introduced in ddsrt etc and name the header files e.g. dds/ddssec/auth.h or something instead of dds/security/dds_security_api_authentication.h.
* Reassess Jeroen's comment:
https://github.com/eclipse-cyclonedds/cyclonedds/pull/177#issuecomment-494040238
> If the security_api just becomes part of ddsc, and it should in my opinion, then I'd prefer you propagate the naming scheme as introduced in ddsrt etc and name the header files e.g. dds/ddssec/auth.h or something instead of dds/security/dds_security_api_authentication.h.