[sword-devel] Firefox to remove support for the FTP protocol | ZDNet

[Troy A. Griffitts]

I disagree.

I never use my browser for FTP and I don't want security for the files I
transfer over FTP.  It's a waste of bandwidth and cycles.

HTTPS doesn't provide a common means to discover and traverse file
systems like FTP.  WebDAV over HTTPS would be the alternative.

SFTP would be our preference if necessary.

We use FTP because we don't care about "securely transferring the data
of Bibles".  Be sure, we care about security in persecuted countries,
but that security is to protect the identity of the client and host and
no "protocol" will do that.  If a government wants to monitor their
people who hit "crosswire.org" then the client needs to use a VPN or
something similar to avoid detection.  A secure "protocol" won't hide
the origin and destination.

We use FTP because it is a means to take a working SWORD library and
make it available with NO ADDITIONAL META INFORMATION to clients.  Point
your FTP server to the root of your working SWORD library and you are done.

It is the easiest to setup for 3rd party publishers.

I'm curious to hear real world benefits of changing to another
solution.  Please share if you have any,

Troy



On 3/20/20 9:28 AM, David Haslam wrote:
> Thank you Caleb for so succinctly expressing the point that I vaguely
> hinted at. 
>
> This is something that needs our urgent attention. 
>
> David
>
> Sent from ProtonMail Mobile
>
>
> On Fri, Mar 20, 2020 at 16:23, Caleb Maclennan <caleb at alerque.com
> <mailto:caleb at alerque.com>> wrote:
>> I don't think code sharing code with browsers is even the issue here,
>> the issue is the FTP ecosystem is going away — and surprising quickly
>> for something that used to be so ubiquitous. I've already bumped into
>> several ISP's just flat out blocking all FTP traffic, probably
>> because they didn't know of or care about any ongoing uses for it.
>> With browsers dropping support, it's validity as a protocol is going
>> to quickly go by the wayside. All existing FTP based systems should
>> be ported to HTTPS (and only 'S') at the earliest convenience.
>>
>> On Fri, Mar 20, 2020 at 5:22 PM Greg Hellings
>> <greg.hellings at gmail.com <mailto:greg.hellings at gmail.com>> wrote:
>>
>>
>>
>>     On Fri, Mar 20, 2020 at 2:20 AM David Haslam
>>     <dfhdfh at protonmail.com <mailto:dfhdfh at protonmail.com>> wrote:
>>
>>         The writing is on the wall for FTP.
>>
>>         Firefox to remove support for the FTP protocol | ZDNet
>>         https://flip.it/AY-TTt
>>
>>         How will this trend affect how we design and communicate?
>>
>>
>>     Since we don't use or rely on Mozilla or Chrome code, I imagine
>>     it won't affect much of anything.
>>
>>     --Greg
>>
>>
>>         Best regards,
>>
>>         David
>>
>>         Sent from ProtonMail Mobile
>>         _______________________________________________
>>         sword-devel mailing list: sword-devel at crosswire.org
>>         <mailto:sword-devel at crosswire.org>
>>         http://www.crosswire.org/mailman/listinfo/sword-devel
>>         Instructions to unsubscribe/change your settings at above page
>>
>>     _______________________________________________
>>     sword-devel mailing list: sword-devel at crosswire.org
>>     <mailto:sword-devel at crosswire.org>
>>     http://www.crosswire.org/mailman/listinfo/sword-devel
>>     Instructions to unsubscribe/change your settings at above page
>>
>
>
>
> _______________________________________________
> sword-devel mailing list: sword-devel at crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.crosswire.org/pipermail/sword-devel/attachments/20200320/22de8029/attachment-0001.html>