3 ms·
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. I certainly did
by SwellJoe 18y ago
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. I certainly didn't think I was arguing that people ought to use it to mean anything else.
Many users (and a few clients and servers) do use the term incorrectly. I don't like it, and clearly you don't either...I don't see what you're disagreeing with.
And, of course FTP over SSL is not extremely rare...not even close to rare. All of the major FTP servers, and many FTP clients, support it quite easily, and many, many end users insist on it. ProFTPd, possibly the most popular FTP server, can be configured to use it with just a few configuration directives.
I'm not encouraging anyone to use the terms incorrectly or to use the FTPS protocol instead of SFTP. 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 guess I've not been very clear. I apologize for misleading anyone into thinking I intended to praise the misuse of terms. 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.
- nailer 18y agoYou asked what I specifically disagreed with. Your original post: > the most common meaning of SFTP has come to be "FTP encrypted with SSL" I disagree with that. We both think people should use 'SFTP' to correctly mean as implemented by an SSH server, but you think the term has lost meaning. I am disagreeing with that.
- SwellJoe 18y agoOK. I'll buy that, and based on a search of the various terms, things seem to be improving. My personal experience is clouded by supporting our own products, which is possibly not an entirely representative sample. But, for what it's worth, we have about 1000 paying customers who are web developers...and we're still hearing misuse of the terms on a very regular basis. I'd like to think things are getting better.
- nailer 18y agoJoe, while I've got your attention, somewhat off-topic, does webmin use an intermediary language that spans all config files, or does it directly parse for each format? What do you use to make the parsers?
- SwellJoe 18y agoIndependent parser for every config file. 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. and have it respect those changes, along with comments and file order. 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. I can see a few places where it makes sense...for example, I see a place in the world for tools like puppet. But I've never been in a situation where I was willing to accept a GUI or management automation tool as the only way to ever edit a configuration file (though, with Webmin, I almost never need to hit the command line, I always can). Webmin is written in Perl, and it uses a few relatively simple libraries that Jamie has built over the years (Webmin is 11 years old this October) for slurping files into arrays, breaking them into key=values, etc. Thus each module has a lot of code devoted to parsing...some more than others. We've begun working on making this functionality accessible to other Perl code (and eventually other code in general) via APIs, but that's still coming along slowly...and some of it is unfortunately not abstract enough to be as useful as we'd like. For example, using the Postfix module and the Sendmail module doesn't necessarily have the same semantics--starting and stopping the service are almost always the same between services, but anything config file related is very specific and you have to have knowledge of the directives to do anything with them. Sometimes the parsers use regexes, sometimes array munging with splice/unsplice/push/pop/etc. grep and map play a big role in Webmin code as well, as they make a lot of kinds of parsing a lot more concise. The code can be intimidating at first, as it's really big (~400kLOC), and because Webmin has never (intentionally) broken backward compatibility for module authors (in eleven years!) has a lot of pretty hairy legacy code. Newer modules and those that are more aggressively maintained (Dovecot, Virtualmin and its related modules, Sendmail, Postfix, Apache, etc.) are nicer to read than older ones. Anyway, I don't think there is any one silver bullet to deal with configuration files on Linux. They're all pretty wildly different, and some have very bizarre quirks and complexity. Apache, for example, can have arbitrary directives and syntax added by modules, and anything that parses the configuration has to be able to at least understand it well enough to skip over those sections and directives.