<div dir="ltr">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 serially isn't an option in my case. Also, peers can run the cheaper process instead of having the wallet functionality which isn't even used.<div>
<br></div><div>On the security front, this doesn't seem to be any less secure and it gives the user the flexibility to make it as secure as they feel comfortable. If they want to run them both as the same user with no SELinux or file protections (this isn't stopping or encouraging that) they're already doing that now with bitcoind, albeit with possibly a larger attack surface.</div>
</div><div class="gmail_extra"><br clear="all"><div><div dir="ltr">Thanks,<br>--<br>James Hartig<br>Software Engineer @ Grooveshark.com<br><a href="http://twitter.com/jameshartig" target="_blank">http://twitter.com/jameshartig</a><div style="width:16px;height:16px;display:inline-block">
</div><div style="width:16px;height:16px;display:inline-block"> </div><br></div></div>
<br><br><div class="gmail_quote">On Sat, Feb 22, 2014 at 1:53 AM, Wladimir <span dir="ltr"><<a href="mailto:laanwj@gmail.com" target="_blank">laanwj@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote"><div class="">On Sat, Feb 22, 2014 at 2:09 AM, Dustin D. Trammell <span dir="ltr"><<a href="mailto:dtrammell@dustintrammell.com" target="_blank">dtrammell@dustintrammell.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div>On Fri, 2014-02-21 at 07:43 +0100, Wladimir wrote:<br>
> The most straightforward way would be to run the blockchain daemon as<br>
> a system service (with its own uid/gid and set of Apparmor/SELinux<br>
> restrictions) and the wallet daemon as the user.<br>
<br>
</div>This assumes you as a user have the rights to do so. This would be<br>
preferred, but in some cases may not be possible. Perhaps it should be<br>
optional?<br></blockquote><div><br></div></div><div>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.</div>
<div><br></div><div>Repeated offenders will lose their BitLicense.</div><div></s><br></div><div><br></div><div>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!</div>
<div><br></div><div>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.</div>
<span class="HOEnZb"><font color="#888888">
<div><br></div><div>Wladimir<br></div><div><div>BTW: All of those patches are helpful for monolithic-bitcoind as well as they (lay the groundwork for) speeding up block synchronization.</div></div><div><br></div></font></span></div>
</div>
</div>
<br>------------------------------------------------------------------------------<br>
Managing the Performance of Cloud-Based Applications<br>
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.<br>
Read the Whitepaper.<br>
<a href="http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk" target="_blank">http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk</a><br>_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href="mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-development@lists.sourceforge.net</a><br>
<a href="https://lists.sourceforge.net/lists/listinfo/bitcoin-development" target="_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-development</a><br>
<br></blockquote></div><br></div>