Paul,
echo "#define VSF_BUILD_SSL" >> builddefs.h
make
Correct. Following the book. It says to add that for SSL support. SSL support seemed like a good thing.
echo "#define VSF_BUILD_TCPWRAPPERS" >>builddefs.h &&
echo "#define VSF_BUILD_SSL" >>builddefs.h &&
echo "#undef VSF_BUILD_PAM" >>builddefs.h &&
#sed -e 's|#define VSF_SYSDEP_HAVE_LIBCAP|//&|' -i sysdeputil.c && #obsolete, soft delete
sed 's/SSL_library_init/SSL_CTX_new/' -i vsf_findlibs.sh
We don't normally test with the define as that is not in the mainline
instructions, but only in Command Explanations as an optional thing to do.
I don't know why one wouldn't want SSL support in a network server.
Can you share the patch for vsftpd that you found?
See last line above.
OK. Thanks. That indeed works.
OTOH, perhaps we should just remove vsftpd from the book. I can't get
to the url in the book right now and the last update to the package is
dated July 2015. It does not appear to be maintained.
"Ain't broke, don't fix it!"
First question is: does it need updating? CVE-2015-1419 was reported 2/1/15 against 3.0.2. 3.0.3 was released 7/25/15. I can't find any vulnerabilities reported against 3.0.3. I don't know what you expect.
In addition ftp seems to have become be a relatively unused protocol.
I don't know why you claim that. You don't use it, I do.
Of course I use it. There are several upstream sites that are ftp only,
but those are slowly going away. My comment referred to uploading via
ftp.
Uploads would generally be via scp and downloads either scp or http(s).
I typically use FTP at OSUOSL(.org).
You know that the base LFS system provides an FTP client?
You also know that vsftpd is a server, not a client?
Why do you need vsftpd? I'm not saying you don't, but I'm curious what
your use case is.
About the only thing I can see using ftp server for is for anonymous
uploads and that would be unusual/dangerous. In addition that could be
done via http if really needed.
What happened to "Your system, your rules"? I think we have a
significant difference of opinion here. For example, I have used
telnet more than a few times when ssh got bolixed. Dangerous? Not
inherently, the sysadmin (me) took steps to preserve security,
pulling plugs. Presume sysadmins know their job, have judged their
risks.
Of course it is your system to do as you please. But sometimes newer
things are better than the old ways. Of course, some newer things are
worse (*cough* systemd *cough*).
One of the things I like to teach at school are what applications or
programs are still around, but of questionable value. Most books I see
want to teach every program in coreutils. Some have been around since
RAM was measured in K and floppies or punch cards were the main mass
storage devices. (e.g. When is the last time you used the unlink command?)
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above