Closed
Bug 130634
Opened 23 years ago
Closed 23 years ago
No support for SSL FTP (ftps://)
Categories
(Core Graveyard :: Networking: FTP, defect)
Tracking
(Not tracked)
People
(Reporter: ken2006, Assigned: asa)
Details
No support for SSL FTP (ftps://).
This may seem trivial (at least until/if ftp uploads are supported?), but
extending the internal ssl libraries to also support ftps:// would be extremely
cool and pair well with sites that offer it. (sites I run offer ftps:// -and use
the same username-password for both https and ftp (self-defeating). It would be
elegant stop running my tcp/21 service alltogether and instead require my users
to connect via tcp/990)
I realize there a few other variations on FTP encryption, but from what I can
tell tcp/990 seems to be pretty well accepted. I promise to worship anyone who
implements this!! :)
*** This bug has been marked as a duplicate of 85464 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
vrfy dupe. reporter if you could provide a test server please indicate username/password/server in that bug.
Status: RESOLVED → VERIFIED
Reporter | ||
Comment 3•23 years ago
|
||
Hmmmm. Seems that this type of functionality isnt endorsed by IANA... Enless it
should instead be implemented in DAV (which they do endorse). --I could live
with that... the server I use (sambar.com) supports some DAV protocols in
addition FTPS.
http://www.iana.org/assignments/uri-schemes
I'm gonna repost this as a request to implement DAV, because secure read-write
can only be a benifit, and some other browsers support DAV (IE).
PS:
ftps://sample:login@www.onnet.cc
Updated•10 months ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•