I've used dozens of management products over the years that start from a database and push out the config files via templates, and other such 'One True Vision' kind of thing, and it's just not worth it. and have it respect those changes, along with comments and file order.

It's the only way to do it such that it allows you to edit config files outside of Webmin, using the command line, using other tools, etc. Independent parser for every config file. I just wanted to point out that people use the terms incorrectly extremely often, and it's wise to be explicit about the protocol you mean. I apologize for misleading anyone into thinking I intended to praise the misuse of terms. In fact, I've been recommending SSH FTP for years (one could probably dig up mailing lists posts that include me scolding people for using FTP from ten years ago). I'm not encouraging anyone to use the terms incorrectly or to use the FTPS protocol instead of SFTP. ProFTPd, possibly the most popular FTP server, can be configured to use it with just a few configuration directives. All of the major FTP servers, and many FTP clients, support it quite easily, and many, many end users insist on it. I don't like it, and clearly you don't either.I don't see what you're disagreeing with.Īnd, of course FTP over SSL is not extremely rare.not even close to rare. Many users (and a few clients and servers) do use the term incorrectly.

I certainly didn't think I was arguing that people ought to use it to mean anything else. You disagree with what? I thought I was quite clear that the appropriate meaning of SFTP is SSH File Transfer Protocol and has been for years. And, of course, there is no RFC defining secure FTP, so it's a de facto 'standard' which can lead to buggy implementations and a lot of finger pointing-server says client is wrong, client says server is wrong, user says 'I give up' and uses FTP, instead. It's stabilized somewhat in recent years, and usually clients will do the right thing-and the most common meaning of SFTP has come to be 'FTP encrypted with SSL' (which is actually one of the weaker forms of security for FTP-but it's got some semblance of 'standardization', and works in lots of clients and servers, so that makes it superior). Unfortunate, since SFTP means too many incompatible things. Historically, people tried to convince folks to call it FTPS (for FTP over SSL, which is the most popular form of secured FTP), but that seems to have never taken off. Depending on the client, it may mean 'FTP encrypted with SSL' or 'FTP with encryption extensions of one of a couple of types invented independently by FTP server authors over the years' or 'SSH File Transfer Protocol' (which is actually the real meaning of the abbreviation, and was in use for several years before secure FTP began to be common).

Cyberduck sftp nested server