Setting aside all security benefits (which the user can obviously choose to
implement or ignore), a major benefit here is being able to have multiple
wallets use the same blockchain process. I have 3 different bitcoind
processes running on the same server to utilize multiple wallets. Using
them
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.
On Fri, Feb 21, 2014 at 7:27 AM, Mike Hearn m...@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
Running the network part of the core as a system service might make sense for
server implementations, but it’s a pain in the rear for most users.
That said, I think segregating the two processes is a great idea. Let’s just
try to avoid some complicated scheme that involves necessarily running
On Fri, Feb 21, 2014 at 7:50 AM, William Yager will.ya...@gmail.com wrote:
Running the network part of the core as a system service might make sense
for server implementations, but it’s a pain in the rear for most users.
Come on, making it a possibility doesn't affect other kinds of use cases
5 matches
Mail list logo
