Remove duplicate network allowlists from FTP setup

README.md

@@ -8,17 +8,16 @@ The plugin is a WebAssembly component built against the Memona filesystem
 contract, `memona:filesystem@0.1.0`. It uses only the host's sockets; it has no
 ambient filesystem, environment or network access of its own.
 
+This package requires a Memona version that supports plugin manifest schema 2.
+
 ## What it registers
 
 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
 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.
+For localhost or a server on a private network, turn on **Private network** in
+the connection settings. Save and reconnect after changing these settings.
 
 The TLS toggle currently starts TLS on the control connection only. Protected
 data connections and explicit `AUTH TLS` negotiation are not implemented, so
@@ -37,11 +36,9 @@ and connects out to it; `PASV` fallback is not implemented. The server picks a f
 transfer and announces it only as the transfer begins, so the range that has to
 be reachable is wide.
 
-`manifest.json` declares `networkPorts` as 21 and 1024-65535, and `networkHosts`
-as `*` because a server can be anywhere. Declaring is not granting: a
-connection reaches only the host and ports the person grants it, and a grant
-never accepts a wildcard host. Grant the control port and the span the server
-uses for its data channel, usually `21` and `1024-65535`.
+The package declares socket ports 21 and 1024-65535, which Memona applies
+automatically to each connection. The control port and passive data ports
+must be within these ranges.
 
 ## Build