fix certificate start date to work regardless of the timezone

[mikaelarguedas]

Currently if the machine generating the certificate has a local time ahead of UTC, the nodes fail to be created.

This PR switches to uses UTC time for the certificate start and end of validity times.

Error messages

Fast-RTPS:

2019-08-01 02:19:18.354 [SECURITY Error] Error validating the local participant identity. () -> Function init
2019-08-01 02:19:18.355 [RTPS_PARTICIPANT Error] Cannot create participant due to security initialization error -> Function createParticipant

Connext:

[CREATE Participant]RTI_Security_CertHelper_verifyCert:X509_verify_cert returned 0 with error 9: certificate is not yet valid
[CREATE Participant]RTI_Security_Authentication_get_certificate:failed to verify certificate
[CREATE Participant]RTI_Security_Authentication_validate_local_identity:failed to get certificate
[CREATE Participant]DDS_DomainParticipantTrustPlugins_getLocalParticipantSecurityState:!certificate verify fail
[CREATE Participant]DDS_DomainParticipant_createI:!get local participant security state
[CREATE Participant]DDS_DomainParticipantFactory_create_participant_disabledI:!create participant
DDSDomainParticipant_impl::create_disabledI:!create participant
DDSDomainParticipant_impl::createI:!create participant
DomainParticipantFactory_impl::create_participant():!create failure creating participant

Signed-off-by: Mikael Arguedas mikael.arguedas@gmail.com

[kyrofa]

Yeah seems sensible, thanks @mikaelarguedas!

[mikaelarguedas]

@jacobperron or @mjcarroll gentle 🛎️
Can this be merged as is or should it get another 👀 and/or CI to go in ?

[jacobperron]

LGTM!

• Linux
• Linux-aarch64
• macOS
• Windows