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: accept registry-scoped certfile and keyfile as credentials #5160

Merged
merged 1 commit into from
Jul 20, 2022

Commits on Jul 19, 2022

  1. feat: accept registry-scoped certfile and keyfile as credentials

    Closes npm#4765
    RFC: npm/rfcs#591
    
    While this doesn't directly allow top-level cert/key as credentials (per the
    original issue), it's a more targeted/secure approach that accomplishes the
    same end-result; the new options are scoped to a specific registry, and the
    actual cert/key contents are much less likely to be exposed. See the RFC for
    more context.
    
    Depends on:
    * npm/npm-registry-fetch#125
    * npm/config#69
    jenseng committed Jul 19, 2022
    Configuration menu
    Copy the full SHA
    9771bf6 View commit details
    Browse the repository at this point in the history