From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WGjw2-0003wE-Nu for bitcoin-development@lists.sourceforge.net; Fri, 21 Feb 2014 06:50:10 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.219.53 as permitted sender) client-ip=209.85.219.53; envelope-from=will.yager@gmail.com; helo=mail-oa0-f53.google.com; Received: from mail-oa0-f53.google.com ([209.85.219.53]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WGjw1-0001SB-Ns for bitcoin-development@lists.sourceforge.net; Fri, 21 Feb 2014 06:50:10 +0000 Received: by mail-oa0-f53.google.com with SMTP id m1so3499902oag.26 for ; Thu, 20 Feb 2014 22:50:04 -0800 (PST) X-Received: by 10.60.115.68 with SMTP id jm4mr1443759oeb.45.1392965404380; Thu, 20 Feb 2014 22:50:04 -0800 (PST) Received: from wireless-10-148-122-32.public.utexas.edu (nat-128-62-71-162.public.utexas.edu. [128.62.71.162]) by mx.google.com with ESMTPSA id g4sm7334210obe.5.2014.02.20.22.50.02 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 20 Feb 2014 22:50:02 -0800 (PST) Content-Type: multipart/signed; boundary="Apple-Mail=_816E40A8-9273-4901-A584-B01E3D86A574"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) From: William Yager In-Reply-To: Date: Fri, 21 Feb 2014 00:50:01 -0600 Message-Id: References: To: Wladimir X-Mailer: Apple Mail (2.1827) X-Spam-Score: -0.6 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (will.yager[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1WGjw1-0001SB-Ns Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Fwd: Bitcoin Core trial balloon: splitting blockchain engine and wallet X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Feb 2014 06:50:10 -0000 --Apple-Mail=_816E40A8-9273-4901-A584-B01E3D86A574 Content-Type: multipart/alternative; boundary="Apple-Mail=_F8441105-F86E-4B3E-A604-4751744C4D2C" --Apple-Mail=_F8441105-F86E-4B3E-A604-4751744C4D2C Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 Running the network part of the core as a system service might make = sense for server implementations, but it=92s a pain in the rear for most = users.=20 That said, I think segregating the two processes is a great idea. Let=92s = just try to avoid some complicated scheme that involves necessarily = running things under multiple users. Will On Feb 21, 2014, at 0:43, Wladimir wrote: > The most straightforward way would be to run the blockchain daemon as = a system service (with its own uid/gid and set of Apparmor/SELinux = restrictions) and the wallet daemon as the user. --Apple-Mail=_F8441105-F86E-4B3E-A604-4751744C4D2C Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252 Running the network part of the core as a system = service might make sense for server implementations, but it=92s a pain = in the rear for most users. 

That said, I think = segregating the two processes is a great idea. Let=92s just try to avoid = some complicated scheme that involves necessarily running things under = multiple users.

Will

On = Feb 21, 2014, at 0:43, Wladimir <laanwj@gmail.com> = wrote:

The most straightforward way would be = to run the blockchain daemon as a system service (with its own uid/gid = and set of Apparmor/SELinux restrictions) and the wallet daemon as the = user.

= --Apple-Mail=_F8441105-F86E-4B3E-A604-4751744C4D2C-- --Apple-Mail=_816E40A8-9273-4901-A584-B01E3D86A574 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org iQEcBAEBAgAGBQJTBvcZAAoJEP6RFSSE221wdXIH/0xBay/rS9lAUSS616fRGY+G PQnlJyNcXKdBFUytqFWjTUTE6Rg0TV3boR1NhPgIs7KmSdgTahUABEJlkbdwTZsB Mw6KE+tGBn0of5qvZajBcRB8LUExuJlthRDu8Dqobs0veAzAcZkzlWJb+x+TQcW4 fEMTPSzdJYgGHZFd25zfJxbZXdDv/YdH5g+3pP+sc/O1wxL79IZ2V5qbN1Fom+Gl QZGO65W2EY2L0ycmB6aiG02cLa0rdtz86xXaRYJrbDMs/6DQz917DmKD0WomXbg7 yaeKofSx8lnFufySKd0G9bPb+5hGlfeyJuvsSVa9HtH10/yVMCsFCEGaTps3mTg= =h4z6 -----END PGP SIGNATURE----- --Apple-Mail=_816E40A8-9273-4901-A584-B01E3D86A574--