Tracking Issue for RFC 3231: Asymmetric Tokens

[ehuss]

Summary

RFC: #3231
Implementation:

• Asymmetric tokens #10771
• Wrapper type for data that should never be logged #11545

Documentation: https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#asymmetric-token
Issue: Z-asymmetric-token Nightly: asymmetric-token authentication

RFC 3231 adds support for Cargo to authenticate the user to registries without sending secrets over the network.

Unresolved Issues

• Get a Asymmetric Public key from credentials/config #11518
• A new type for data that should never be logged. #11519
• Asymmetric Tokens from credential processes #11520
• Asymmetric Tokens and server issuing challenges #11521
• Better user-facing documentations

No response

Future Extensions

No response

About tracking issues

Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.

[Eh2406]

Needs to be coordinated with #10474