dependencies: update Rust crates to use ring 0.17.x #6
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed changes
Update Rust crates to versions which use the newer ring 0.17.x release. ring 0.17.x makes it possible to compile thin-edge.io for different target triples (though it is still not possible via cargo-zigbuild).
Whilst the build tooling has not been updated to support building for the additional targets, it at least opens the possibility for users to build the project on the native architectures, or use their own setup which uses clang (an example can be seen from the ring workflow which shows how to build for multiple targest on a linux x86_64 host).
Note
A fork of the x509-parser crate was created due to a delay in a PR being merged due to the MSRV being changed for an optional feature (there is an ongoing discussion in the PR how this could be resolved, but it will take time)
Types of changes
Paste Link to the issue
Checklist
cargo fmt
as mentioned in CODING_GUIDELINEScargo clippy
as mentioned in CODING_GUIDELINESFurther comments