📅 Original date posted:2014-02-22
📝 Original message:On Sat, Feb 22, 2014 at 2:09 AM, Dustin D. Trammell <
dtrammell at 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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140222/b0c5a3ef/attachment.html>;
Wladimir [ARCHIVE] /
npub1xq…ymc2p
2023-06-07 15:13:53
in reply to nevent1q…28tw
Author Public Key
npub1xqshkqv2g7uea4xzqwvmgjcz7u8vfavw6aazs999v0azsv3w7u3qpymc2pPublished at
2023-06-07 15:13:53Event JSON
{
"id": "96b32a5502fa7aa0fde3afcfd4a87e511e956f2120a0e95485fa82ad26eb3cf8",
"pubkey": "30217b018a47b99ed4c20399b44b02f70ec4f58ed77a2814a563fa28322ef722",
"created_at": 1686150833,
"kind": 1,
"tags": [
[
"e",
"9aebc30798366b34740fac6d16d40f9f47d2e3c9df627d88700dd2937bdb6892",
"",
"root"
],
[
"e",
"df73f6da92f7d4b6e0189b9e63a4eecaefa94460ede260eebbee8fdff4b12a9e",
"",
"reply"
],
[
"p",
"87d7580842e7548da90dfb907f32eff172e21a9efab372cd7e24110e82e2f0d5"
]
],
"content": "📅 Original date posted:2014-02-22\n📝 Original message:On Sat, Feb 22, 2014 at 2:09 AM, Dustin D. Trammell \u003c\ndtrammell at dustintrammell.com\u003e wrote:\n\n\u003e On Fri, 2014-02-21 at 07:43 +0100, Wladimir wrote:\n\u003e \u003e The most straightforward way would be to run the blockchain daemon as\n\u003e \u003e a system service (with its own uid/gid and set of Apparmor/SELinux\n\u003e \u003e restrictions) and the wallet daemon as the user.\n\u003e\n\u003e This assumes you as a user have the rights to do so. This would be\n\u003e preferred, but in some cases may not be possible. Perhaps it should be\n\u003e optional?\n\u003e\n\nNo! I'm proposing that we force everyone to do it. Using all means\nnecessary. There should be regular audits that everyone is running the\nsoftware exactly in my configuration, and if not, a special task force will\ntake care that spankings are carried out on the spot.\n\nRepeated offenders will lose their BitLicense.\n\u003c/s\u003e\n\nPlease stop kicking this dead horse. It was just a random idea. Maybe a way\nhow Linux distributions could structure it, but it may or may not apply in\nyour case. And that's fine, this is free software development, you can do\nwhatever you want!\n\nLet's try to bring this discussion back to its original intention: for\nanyone that wants to concretely help this along, please help reviewing and\ntesting the pull requests that jgarzik mentions.\n\nWladimir\nBTW: All of those patches are helpful for monolithic-bitcoind as well as\nthey (lay the groundwork for) speeding up block synchronization.\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140222/b0c5a3ef/attachment.html\u003e",
"sig": "a71575927150de3b642ed4f28c86160e9f011e3ad84102e4e286dcbd5764e315f19d6ada4bb2ec24bee8e3a608b03e2aa2722fca7a83e1a2fee32696381327d8"
}