Niels Thykier <ni...@thykier.net> writes: > Chris Lamb: >> Hi Andreas, >> >>> [...] >> ... which does seem to cover the ftp:// case. Perhaps you were >> thinking of something like: >> >> The watch file uses an unencrypted transport protocol for the >> URI such as http:// or ftp://. It is recommended to use a secure >> transport such as HTTPS for anonymous read-only access.
> Perhaps "... such as HTTPS or FTPS (FTP + TLS) for anonymous read-only > access." would help cover the FTP-case? I suspect the number of free software distribution sites that currently use FTP but would support FTP + TLS is at most a rounding error away from zero. -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
