user.d 1.7 KB

1234567891011121314151617181920212223242526272829303132333435363738394041
  1. Long: user
  2. Short: u
  3. Arg: <user:password>
  4. Help: Server user and password
  5. Category: important auth
  6. Example: -u user:secret $URL
  7. ---
  8. Specify the user name and password to use for server authentication. Overrides
  9. --netrc and --netrc-optional.
  10. If you simply specify the user name, curl will prompt for a password.
  11. The user name and passwords are split up on the first colon, which makes it
  12. impossible to use a colon in the user name with this option. The password can,
  13. still.
  14. On systems where it works, curl will hide the given option argument from
  15. process listings. This is not enough to protect credentials from possibly
  16. getting seen by other users on the same system as they will still be visible
  17. for a brief moment before cleared. Such sensitive data should be retrieved
  18. from a file instead or similar and never used in clear text in a command line.
  19. When using Kerberos V5 with a Windows based server you should include the
  20. Windows domain name in the user name, in order for the server to successfully
  21. obtain a Kerberos Ticket. If you don't then the initial authentication
  22. handshake may fail.
  23. When using NTLM, the user name can be specified simply as the user name,
  24. without the domain, if there is a single domain and forest in your setup
  25. for example.
  26. To specify the domain name use either Down-Level Logon Name or UPN (User
  27. Principal Name) formats. For example, EXAMPLE\\user and user@example.com
  28. respectively.
  29. If you use a Windows SSPI-enabled curl binary and perform Kerberos V5,
  30. Negotiate, NTLM or Digest authentication then you can tell curl to select
  31. the user name and password from your environment by specifying a single colon
  32. with this option: "-u :".
  33. If this option is used several times, the last one will be used.