ftp: update wording for flags
Minor wording change to help for explicit and implicit FTPS flags. More consistent between flags. Add 's' to request because only one 'client' mentioned.
This commit is contained in:
parent
3f3afe489f
commit
87e54f2dde
1 changed files with 5 additions and 5 deletions
|
@ -57,16 +57,16 @@ func init() {
|
||||||
Required: true,
|
Required: true,
|
||||||
}, {
|
}, {
|
||||||
Name: "tls",
|
Name: "tls",
|
||||||
Help: `Use FTPS over TLS (Implicit)
|
Help: `Use Implicit FTPS (FTP over TLS)
|
||||||
When using implicit FTP over TLS the client will connect using TLS
|
When using implicit FTP over TLS the client connects using TLS
|
||||||
right from the start, which in turn breaks the compatibility with
|
right from the start which breaks compatibility with
|
||||||
non-TLS-aware servers. This is usually served over port 990 rather
|
non-TLS-aware servers. This is usually served over port 990 rather
|
||||||
than port 21. Cannot be used in combination with explicit FTP.`,
|
than port 21. Cannot be used in combination with explicit FTP.`,
|
||||||
Default: false,
|
Default: false,
|
||||||
}, {
|
}, {
|
||||||
Name: "explicit_tls",
|
Name: "explicit_tls",
|
||||||
Help: `Use FTP over TLS (Explicit)
|
Help: `Use Explicit FTPS (FTP over TLS)
|
||||||
When using explicit FTP over TLS the client explicitly request
|
When using explicit FTP over TLS the client explicitly requests
|
||||||
security from the server in order to upgrade a plain text connection
|
security from the server in order to upgrade a plain text connection
|
||||||
to an encrypted one. Cannot be used in combination with implicit FTP.`,
|
to an encrypted one. Cannot be used in combination with implicit FTP.`,
|
||||||
Default: false,
|
Default: false,
|
||||||
|
|
Loading…
Add table
Reference in a new issue