From: Wladimir <laanwj@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: [Bitcoin-development] Fwd: Bitcoin Core trial balloon: splitting blockchain engine and wallet
Date: Fri, 21 Feb 2014 07:43:36 +0100 [thread overview]
Message-ID: <CA+s+GJAgs7otQB_tQNCntZ5gR+gp3+PfA+iiKPsjLu2oenaSUA@mail.gmail.com> (raw)
In-Reply-To: <CA+s+GJCRqqmoHkmsq+6x9Wm6btKzdXoPjw5Af8zRDEkDE+6+zw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 636 bytes --]
On Fri, Feb 21, 2014 at 7:27 AM, Mike Hearn <mike@plan99.net> wrote:
> Bear in mind a separate process doesn't buy you anything without a
> sandbox, and those are expensive (in terms of complexity).
>
Sandboxing in user space is complex, agreed,
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.
This would also allow sharing one blockchain daemon between multiple users
and wallet processes (not necessarily on the same machine), something I've
wanted to be able to do for a long time.
Wladimir
[-- Attachment #2: Type: text/html, Size: 1190 bytes --]
next prev parent reply other threads:[~2014-02-21 6:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-21 6:09 [Bitcoin-development] Bitcoin Core trial balloon: splitting blockchain engine and wallet Jeff Garzik
2014-02-21 6:27 ` Mike Hearn
[not found] ` <CA+s+GJCRqqmoHkmsq+6x9Wm6btKzdXoPjw5Af8zRDEkDE+6+zw@mail.gmail.com>
2014-02-21 6:43 ` Wladimir [this message]
2014-02-21 6:50 ` [Bitcoin-development] Fwd: " William Yager
2014-02-21 6:54 ` Wladimir
2014-02-22 1:09 ` Dustin D. Trammell
2014-02-22 6:53 ` Wladimir
2014-02-24 22:16 ` James Hartig
2014-02-21 6:50 ` [Bitcoin-development] " Jeff Garzik
2014-02-21 10:41 ` Mike Hearn
2014-02-21 11:06 ` Peter Todd
2014-02-22 1:04 ` Dustin D. Trammell
2014-02-22 2:08 ` Jeff Garzik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CA+s+GJAgs7otQB_tQNCntZ5gR+gp3+PfA+iiKPsjLu2oenaSUA@mail.gmail.com \
--to=laanwj@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox