-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Tracking Issue for RFC 3231: Asymmetric Tokens #10519
Copy link
Copy link
Open
Labels
A-registriesArea: registriesArea: registriesA-registry-authenticationArea: registry authentication and authorization (authn authz)Area: registry authentication and authorization (authn authz)C-tracking-issueCategory: A tracking issue for something unstable.Category: A tracking issue for something unstable.S-waiting-on-feedbackStatus: An implemented feature is waiting on community feedback for bugs or design concerns.Status: An implemented feature is waiting on community feedback for bugs or design concerns.Z-asymmetric-tokenNightly: asymmetric-token authenticationNightly: asymmetric-token authentication
Description
Metadata
Metadata
Assignees
Labels
A-registriesArea: registriesArea: registriesA-registry-authenticationArea: registry authentication and authorization (authn authz)Area: registry authentication and authorization (authn authz)C-tracking-issueCategory: A tracking issue for something unstable.Category: A tracking issue for something unstable.S-waiting-on-feedbackStatus: An implemented feature is waiting on community feedback for bugs or design concerns.Status: An implemented feature is waiting on community feedback for bugs or design concerns.Z-asymmetric-tokenNightly: asymmetric-token authenticationNightly: asymmetric-token authentication
Type
Fields
Give feedbackNo fields configured for issues without a type.
Projects
Status
In Progress
Summary
RFC: #3231
Implementation:
Documentation: https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#asymmetric-tokenNightly: asymmetric-token authentication
Issue: Z-asymmetric-token
RFC 3231 adds support for Cargo to authenticate the user to registries without sending secrets over the network.
Unresolved Issues
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.