Luke-Jr [ARCHIVE] on Nostr: 📅 Original date posted:2013-12-08 📝 Original message:On Sunday, December 08, ...
📅 Original date posted:2013-12-08
📝 Original message:On Sunday, December 08, 2013 9:03:38 AM Saïvann Carignan wrote:
> Binaries:
> Sourceforge is not encrypted, actually. Although binaries hosting /
> sharing could be a separate subject discussed later I think.
Encryption is useless here. We want everyone to be able to download Bitcoin
clients. Binaries on sourceforge are signed by multiple parties using gitian.
> Decentralization:
> So long as we actually use DNS, the website is centralized :( However,
> its content isn't (can be forked on GitHub), but regarding the domain
> name, there is not much we can do against this AFAIK.
So long as someone has root (or a user that can modify it), the website is
centralised. To really solve this, we would need a dedicated server that
accepts commands only when signed by N-of-M parties, inside a cage locked by
padlocks with keys held by independent parties, with a SSL certificate issued
by an authority that has multiple parties watch it every step of the way into
that server.
Luke
Published at
2023-06-07 15:10:25Event JSON
{
"id": "53a3b91b8533e42b947e21112bd772511ac62eddaef79e75b4bbd4bbd4448b06",
"pubkey": "6ac6a519b554d8ff726a301e3daec0b489f443793778feccc6ea7a536f7354f1",
"created_at": 1686150625,
"kind": 1,
"tags": [
[
"e",
"d517aa463a22abef5f03468f652eeefb44676da99926537d88111078c3e0468b",
"",
"root"
],
[
"e",
"622c0d40a610b6af5dc98180adcbdb9040738307187b408d9f607aa7dd4cb62e",
"",
"reply"
],
[
"p",
"d7c806207c21ecfdee654c5001e8ae79bfdbec5fc68daf80b4eeedae04294ee2"
]
],
"content": "📅 Original date posted:2013-12-08\n📝 Original message:On Sunday, December 08, 2013 9:03:38 AM Saïvann Carignan wrote:\n\u003e Binaries:\n\u003e Sourceforge is not encrypted, actually. Although binaries hosting /\n\u003e sharing could be a separate subject discussed later I think.\n\nEncryption is useless here. We want everyone to be able to download Bitcoin \nclients. Binaries on sourceforge are signed by multiple parties using gitian.\n\n\u003e Decentralization:\n\u003e So long as we actually use DNS, the website is centralized :( However,\n\u003e its content isn't (can be forked on GitHub), but regarding the domain\n\u003e name, there is not much we can do against this AFAIK.\n\nSo long as someone has root (or a user that can modify it), the website is \ncentralised. To really solve this, we would need a dedicated server that \naccepts commands only when signed by N-of-M parties, inside a cage locked by \npadlocks with keys held by independent parties, with a SSL certificate issued \nby an authority that has multiple parties watch it every step of the way into \nthat server.\n\nLuke",
"sig": "ee501b8713b7e974c5c235d5ad2140f0c1ecd11b3c93c1e2e09c960c9156c29ba5d024e72b60cb1a2cbc252c42c349407c7767870327de3cdf21b76ade46b346"
}