Mozilla, Google and others have removed the ftp support from their web browsers, and the workarounds with their latest versions doesn't work anymore. This is a shame, it's very sad, but is the way things are going nowadays. In fact, I can't browse my own Node and download my own file base using web browsers. My public navigation is also affected by this lack of support.
In terms of feasibility, I can still access through FTP client to my Node, but it seems insecure from outer places/connections since the login negotiation is over plain-text. Let me know if I'm wrong.
Do you think it could be a good idea to ask Kim about some possible milestones in the roadmap of BBBS development?
In short/mid term:
- To implement more security in the current ftp protocol implementation (TLS)?
- To implement the file downloading through HTTP/S when the session
is web based.
In a long term:
- To implement SSH (including the sftp subservice support) daemon for incoming connections.
I have been seeing and thinking the same thing. It would be a good thing if th
files links were http/s instead of FTP today.
Secure protocols are a good thing.
All good. A CRAM-MD5 handshake in the binkp service would be welcome also.
It all sounds good to me. :)
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,038 |
Nodes: | 15 (0 / 15) |
Uptime: | 148:20:15 |
Calls: | 500,200 |
Calls today: | 1 |
Files: | 95,197 |
D/L today: |
418 files (84,668K bytes) |
Messages: | 465,993 |