5 ms·
At least it's secure and usually FTPS...hopefully using TLS 1.2+ cryptographic protocol. Previous discussion: https://news.ycombinator.com/item?id=7636066 htt
by iokevins 9y ago
At least it's secure and usually FTPS...hopefully using TLS 1.2+ cryptographic protocol.
Previous discussion:
https://news.ycombinator.com/item?id=7636066 https://news.ycombinator.com/item?id=7636066
- peterwwillis 9y agoWhich is a bit like saying, at least the 70mph mountain pass road has a guard rail.
- microcolonel 9y agoWell, if not TLS, then what would you use? Noise? TLS is the only widely deployed standard cryptographic protocol which has ever protected any internet communication to any degree. For its many flaws and patchwork, there is nothing even competing in the category.
- AnthonyMouse 9y agoThere is ssh. Actually sftp (ssh) tends to be a lot more popular than FTPS (TLS) because of the whole FTPS NAT catastrophe that sftp doesn't have.
- mjcl 9y agoYes. In my experience FTPS is a whole bucket of nope. I've never encountered a situation where we couldn't use SFTP. The only time I've had FTPS work 'well' is when the client & server were both written by the same company (Tumbleweed) and they don't follow the RFC exactly.
- peterwwillis 9y agoIt doesn't matter if the connection is secured if the data itself is not secured. Transport security is a red herring in a complex system. If you are driving a car at 70mph around a mountain pass, even a really strong guard rail leaves the possibility that you could plummet ten thousand feet to your death. If, on the other hand, you were driving on the Bonneville salt flats at 45mph, there is much, much less danger. Secure your data. Then paint the bike shed.
- momzer 9y agoJust a clarification, NACHA uses SFTP rather than FTPS.