> I used openssl-1.1.0g and didn't have any problems building vsftpd. > -- > Hazel
Then apparently they put SSL_library_init back in. > For me, the second result (first is their wiki) is > https://www.archlinux.org/packages/community/x86_64/vsftpd/ > > In Source Files, the PKGBUILD Ah, there it is. Yes, I did the same thing (see below). > > Agree it doesn't explain the failure, but probably only one person > built it, and perhaps with different dependencies. Hazel + Paul is at least two. And how is it you know what others did? Ken, I know you're too experienced to make the assumption that everybody builds their systems as you do! But that seems to be what you're suggesting. Fundamentally, it goes against the whole ethos of the "*NIX Bazaar"! > Doh! It's in LFS these days. 1.0.2 is only retained for its libs, > for those packages which cannot use 1.1.0. And 1.0.2 is versioned by BLFS, so vsftpd would need instructions for finding it. Include files too. > > And to finally confirm, make-ca-0.8 does indeed work fine without > that workaround. > > ĸen I'll have to look at that later, I can see "Iron Horse" coming!! > > Colour me very impressed ;-) "Even a blind dog finds a bone once in a while." Besides, I began programming on a CADET machine. and still have my handbuilt IMSAI. Musta learned something? > > All I've ever managed to find at any flavour of SuSe was srpms, and > most of the links to those seemed broken. Any pointers ? > > ĸen Sorry, can't remember just how. Once I got it I refocused on building. Short term memory's shot. Birthday's on Monday--easy to remember--two days before D-Day, the REAL D-Day. As I say it, to people's blank stares, "When I was born, Hitler owned Europe." Would've been eve of, but as you know, channel weather was bad, Ike could wait a day. Mom couldn't! > Paul, > Your problem was not clear to me. I think what you are doing is: > > 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. > > 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. > Uploads would generally be via scp and downloads either scp or http(s). I typically use FTP at OSUOSL(.org). > 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. I'm stepping down from my soapbox now, not for want of arguments to make. All I'll do is leave a parting shot that the great thing about (B)LFS, IMO, has always been it's openness to help users make the systems they want to make--unlike at least two major vendors that make users take their systems their way! -- Paul Rogers [email protected] Rogers' Second Law: "Everything you do communicates." (I do not personally endorse any additions after this line. TANSTAAFL :-) -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
