From: Wladimir <laanwj@gmail•com>
To: "Dustin D. Trammell" <dtrammell@dustintrammell•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Fwd: Bitcoin Core trial balloon: splitting blockchain engine and wallet
Date: Sat, 22 Feb 2014 07:53:33 +0100 [thread overview]
Message-ID: <CA+s+GJD=-Y5e7jfBt8Ced-2wXkjYcODBKrre2jqT-k-tQO8fCQ@mail.gmail.com> (raw)
In-Reply-To: <1393031340.6897.90.camel@staypuft>
[-- Attachment #1: Type: text/plain, Size: 1414 bytes --]
On Sat, Feb 22, 2014 at 2:09 AM, Dustin D. Trammell <
dtrammell@dustintrammell•com> wrote:
> On Fri, 2014-02-21 at 07:43 +0100, 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.
>
> This assumes you as a user have the rights to do so. This would be
> preferred, but in some cases may not be possible. Perhaps it should be
> optional?
>
No! I'm proposing that we force everyone to do it. Using all means
necessary. There should be regular audits that everyone is running the
software exactly in my configuration, and if not, a special task force will
take care that spankings are carried out on the spot.
Repeated offenders will lose their BitLicense.
</s>
Please stop kicking this dead horse. It was just a random idea. Maybe a way
how Linux distributions could structure it, but it may or may not apply in
your case. And that's fine, this is free software development, you can do
whatever you want!
Let's try to bring this discussion back to its original intention: for
anyone that wants to concretely help this along, please help reviewing and
testing the pull requests that jgarzik mentions.
Wladimir
BTW: All of those patches are helpful for monolithic-bitcoind as well as
they (lay the groundwork for) speeding up block synchronization.
[-- Attachment #2: Type: text/html, Size: 2031 bytes --]
next prev parent reply other threads:[~2014-02-22 6:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-21 6:09 [Bitcoin-development] " 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 ` [Bitcoin-development] Fwd: " Wladimir
2014-02-21 6:50 ` William Yager
2014-02-21 6:54 ` Wladimir
2014-02-22 1:09 ` Dustin D. Trammell
2014-02-22 6:53 ` Wladimir [this message]
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+GJD=-Y5e7jfBt8Ced-2wXkjYcODBKrre2jqT-k-tQO8fCQ@mail.gmail.com' \
--to=laanwj@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=dtrammell@dustintrammell$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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