Hello. On Tue, Dec 12, 2017 at 01:01:29 -0600, J García wrote: > 2017-12-11 15:03 GMT-06:00 Alan Mackenzie <a...@muc.de>: > > OK. But it's still there taking up RAM, and (more importantly) makes a > > systemd system a broader target for attacks. Whether a system has an > > http server (or, for that matter, an SSH server), for whatever purpose, > > should be for the system administrator to decide. I suspect this isn't > > the case for systemd's http server.
> Too much suspicion, too much assumtions, One doesn't get by in contemporary life without them. My suspicion, founded on the content of a normally reliable mailing list (this one) is that systemd would (i) build into my system much that I don't want to use; (ii) would force me into using some of that stuff. openrc doesn't have these attributes. > $ equery -N u systemd | grep http > - - http : Enable embedded HTTP server in journald > $ grep -C 2 http $PORTDIR/sys-apps/systemd/systemd-235-r1.ebuild > 42: http? ( > 43: >=net-libs/libmicrohttpd-0.9.33:0= > 44- ssl? ( >=net-libs/gnutls-3.1.4:0= ) > 45- ) > 42: http? ( > 43: >=net-libs/libmicrohttpd-0.9.33:0= > 44- ssl? ( >=net-libs/gnutls-3.1.4:0= ) > 45- ) > I prefer certainty, don't you? If certainty were free of costs, or even cheap, then yes. > It is actually more useful to check the software, than lose your time > with so many words on this list. No, it would take far too much time and effort to check out the software, particularly for something I have no use for. You seem to know systemd reasonably well - maybe you've got it installed and you're using it. Please tell me whether my suspicion above (that systemd builds stuff into the system that is likely to be superfluous to a user, and possibly forces its use on its users) is well founded. Thanks! -- Alan Mackenzie (Nuremberg, Germany).
