-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Open
Labels
A-registry-authenticationArea: registry authentication and authorization (authn authz)Area: registry authentication and authorization (authn authz)C-bugCategory: bugCategory: bugCommand-publishS-acceptedStatus: Issue or feature is accepted, and has a team member available to help mentor or reviewStatus: Issue or feature is accepted, and has a team member available to help mentor or review
Description
Problem
#15273 highlighted that cargo publish --token
exists. In #15057, we deprecated cargo login <token>
to avoid tokens being in shell history (see also #13623).
This is also incomplete: cargo publish
supports one-off token authentication but not other methods.
Proposed Solution
Deprecate it
Alternatively, add warnings as we may want to keep this for plumbing purposes.
Notes
No response
kornelski
Metadata
Metadata
Assignees
Labels
A-registry-authenticationArea: registry authentication and authorization (authn authz)Area: registry authentication and authorization (authn authz)C-bugCategory: bugCategory: bugCommand-publishS-acceptedStatus: Issue or feature is accepted, and has a team member available to help mentor or reviewStatus: Issue or feature is accepted, and has a team member available to help mentor or review
Type
Projects
Milestone
Relationships
Development
Select code repository
Activity
weihanglo commentedon Mar 6, 2025
Second. Should we do an FCP as a straw poll?
epage commentedon Mar 6, 2025
Eh, will happen now or in the PR. Either way.
tbu- commentedon Mar 24, 2025
I'm using this flag to support multiple different identities. I'm using
cargo publish --token=$(command)
. This is on a single-user machine.It'd be nice if there continues to be an alternative I can use.
weihanglo commentedon Mar 26, 2025
@tbu-
The situation is pretty much like this: #15057 (comment).