user.d 1.7 KB

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