Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: HSM auth - c8y connection init & built in bridge #3366

Draft
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

Bravo555
Copy link
Contributor

Proposed changes

Types of changes

  • Bugfix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Improvement (general improvements like code refactoring that doesn't explicitly fix a bug or add any new functionality)
  • Documentation Update (if none of the other choices apply)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Paste Link to the issue


Checklist

  • I have read the CONTRIBUTING doc
  • I have signed the CLA (in all commits with git commit -s)
  • I ran cargo fmt as mentioned in CODING_GUIDELINES
  • I used cargo clippy as mentioned in CODING_GUIDELINES
  • I have added tests that prove my fix is effective or that my feature works
  • I have added necessary documentation (if appropriate)

Further comments

@Bravo555 Bravo555 changed the title feat: HSM auth - c8y direct connection feat: HSM auth - c8y connection init & built in bridge Jan 29, 2025
As a preparation for the HSM support, we upgrade to the latest version
of rustls that supports FIPS mode using aws-lc-rs that is compatible
with rumqttc, i.e. rustls-0.22 from 0.21.

Because of breaking changes in rustls (Certificate and PrivateKey types
were replaced with CertificateDer and PrivateKeyDer types) relatively
big changes in certificate crate were required: the crate was split to
expose rustls-0.21 and rustls-0.22 variants of its public items. The
reason for this was that there were some crates (axum-server) that
bumped rustls 0.21->0.23(not yet supported by rumqttc) and had no
rustls-0.22 support, so they had to keep using rustls-0.21 compatible
structs, while our callsites to rumqttc were updated to use rustls-0.22
compatible structs.

This split was made to get on with rustls-0.22 as fast as possible and
an effort should be made in the future to reduce it as much as possible
by refactoring dependencies, erasing relevant types, and so on.

Signed-off-by: Marcel Guzik <marcel.guzik@cumulocity.com>
Signed-off-by: Marcel Guzik <marcel.guzik@cumulocity.com>
Signed-off-by: Marcel Guzik <marcel.guzik@cumulocity.com>
Signed-off-by: Marcel Guzik <marcel.guzik@cumulocity.com>
Copy link
Contributor

Robot Results

✅ Passed ❌ Failed ⏭️ Skipped Total Pass % ⏱️ Duration
560 0 3 560 100 1h31m56.432405999s

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant