commons/memona-plugin-ftp
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Explain connection permissions and supported transports
CI / checks (pull_request) Successful in 1m6s
Details

Browse Source
This commit is contained in:
Danny Kim
2026-09-30 15:46:45 +09:00
parent 7f9fd13a02
commit 55a4f458b6
1 changed files with 11 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+11 -1
View File
@@ -14,6 +14,16 @@ One provider, `ftp`, for the `ftp` and `ftps` schemes. A connection is
configured with a server name, an optional port, a TLS toggle for FTPS, and an configured with a server name, an optional port, a TLS toggle for FTPS, and an
optional username and password. An empty username signs in anonymously. optional username and password. An empty username signs in anonymously.
In Memona's connection permissions, enter the server's hostname or IP in
**Allowed hosts**, without a scheme, port or path. An empty list blocks the
connection. Turn on **Private network** as well for localhost or a private
network; this switch does not grant a host by itself. Save and reconnect after
changing permissions.
The TLS toggle currently starts TLS on the control connection only. Protected
data connections and explicit `AUTH TLS` negotiation are not implemented, so
the plugin does not yet provide a complete FTPS connection.
Listing and stat need a server that answers `MLSD` and `MLST`, the Listing and stat need a server that answers `MLSD` and `MLST`, the
machine-readable listing commands. A server without them reports the folder as machine-readable listing commands. A server without them reports the folder as
unsupported rather than guessing at the older, human-formatted listing or unsupported rather than guessing at the older, human-formatted listing or
@@ -23,7 +33,7 @@ so a conditional write is reported as unsupported rather than simulated.
## Passive mode and the port range ## Passive mode and the port range
Transfers are passive: the plugin asks the server for a data port with `EPSV` Transfers are passive: the plugin asks the server for a data port with `EPSV`
or `PASV` and connects out to it. The server picks a fresh port for every and connects out to it; `PASV` fallback is not implemented. The server picks a fresh port for every
transfer and announces it only as the transfer begins, so the range that has to transfer and announces it only as the transfer begins, so the range that has to
be reachable is wide. be reachable is wide.