MSGID: 1:153/757.0 69964470
REPLY: 2:343/107.0 81298e2b
TZUTC: -0800
CHARSET: LATIN-1
> 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.

I have been seeing and thinking the same thing. It would be a good thing if
the files links were http/s instead of FTP today.

> 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.

Secure protocols are a good thing.

> Do you think it could be a good idea to ask Kim about some possible
> milestones in the roadmap of BBBS development?

It wouldn't hurt.

> 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.

All good. A CRAM-MD5 handshake in the binkp service would be welcome also.

> In a long term:

> - To implement SSH (including the sftp subservice support) daemon for
> incoming connections.

It all sounds good to me. :)

--- BBBS/Li6 v4.10 Toy-5
 * Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)
SEEN-BY: 1/120 123 14/0 15/0 18/0 90/1 105/81 106/201 120/340 123/0
SEEN-BY: 123/25 40 131 180 190 200 755 129/305 330 134/100 135/300
SEEN-BY: 138/146 153/105 135 757 7715 154/10 221/6 222/2 226/30 227/114
SEEN-BY: 229/110 317 424 426 452 550 664 700 240/1120 5832 249/206
SEEN-BY: 250/1 266/512 275/100 1000 280/464 282/1038 292/854 299/6
SEEN-BY: 300/4 301/1 317/3 320/219 322/757 342/11 200 396/45 633/280
SEEN-BY: 640/1321 712/848 3634/0 12 15 27 50 119
PATH: 153/757 3634/12 153/7715 229/426