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