Should ProFTPD be removed from future Slackware releases?
SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
View Poll Results: Should ProFTPD be removed from future Slackware releases?
I've voted no.
Because I didn't found a solution to use vsftpd with a mysql database,
without using PAM. As far as I know, PAM is not used on Slackware.
So if anyone could give me a hint how to solve this, I could switch
from proftpd to vsftpd.
It would be helpful if those that voted "NO" would give some feedback as to why.
I don't think "It's what I've always used" is going to help sway any decisions though
Because it's known to work. It's feature-rich. And, if there are really security problems, use sftp or httpd or rsync or nfs.
The very simple ftpd or vsftpd may be needed by some people. So I have no objection to include it. If space is constrained, one can always remove some of the the numerous multimedia apps which are not much different from each other.
If the Slackware Team affords to keep track of the upstream updates, then Proftp is worth keeping as it may provide some features currently not covered by vsftp. Otherwise, the community can take over its maintenance on SBo, or elsewhere until the Team decides to take back on board.
It seems like ProFTPD has had a history of security flaws. As I recall, the reason that vsftpd became the default in Slackware (somewhere around Slack 9 maybe?) was because of a exploit that the ProFTPD team didn't react to quickly enough.
I suppose keeping it included as an option doesn't hurt anything, but since there are obviously some reliability concerns I don't know that enough people will run it to make it worth keeping around. Maybe it's time for a move to /pasture to maintain backwards compatibility with sites already running it, but focus new installations on vsftpd?