From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 91433139083 for ; Tue, 12 Dec 2017 19:03:03 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 1A203E0F40; Tue, 12 Dec 2017 19:02:57 +0000 (UTC) Received: from mail.muc.de (colin.muc.de [193.149.48.1]) by pigeon.gentoo.org (Postfix) with SMTP id 69606E0F34 for ; Tue, 12 Dec 2017 19:02:55 +0000 (UTC) Received: (qmail 77444 invoked by uid 3782); 12 Dec 2017 19:02:54 -0000 Received: from acm.muc.de (p548C6C38.dip0.t-ipconnect.de [84.140.108.56]) by colin.muc.de (tmda-ofmipd) with ESMTP; Tue, 12 Dec 2017 20:02:54 +0100 Received: (qmail 5653 invoked by uid 1000); 12 Dec 2017 18:55:15 -0000 Date: Tue, 12 Dec 2017 18:55:15 +0000 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: Is gnome becoming obligatory? Message-ID: <20171212185515.GA5274@ACM> References: <6582741.F9gJHCEsXr@dell_xps> <2343494.DDJaQvByiF@dell_xps> <6cb25230-9803-2bd4-ee69-66504d0d1822@gmx.com> <5A2D04A1.6090101@youngman.org.uk> <20171210101330.GA5671@ACM> <20171211185602.7a1853c9@digimed.co.uk> <20171211210321.GA12473@ACM> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.7.2 (2016-11-26) X-Delivery-Agent: TMDA/1.1.12 (Macallan) From: Alan Mackenzie X-Primary-Address: acm@muc.de X-Archives-Salt: caca3bd1-b0d6-4147-8b00-80679493f6ac X-Archives-Hash: 2e766370dbb41d78369f9ed8495adfc0 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 : > > 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).