rich1.0npub16lyqvgruy8k0mmn9f3gqr69w0xlahmzlc6x6lq95amk6uppffm3q69pqjmhttps://nostr.ae/npub16lyqvgruy8k0mmn9f3gqr69w0xlahmzlc6x6lq95amk6uppffm3q69pqjmnjumphttps://nostr.aeđź“… Original date posted:2013-12-08
đź“ť Original message:Forward secrecy:
I was definitively already interested in using this.
Binaries:
Sourceforge is not encrypted, actually. Although binaries hosting /
sharing could be a separate subject discussed later I think.
Revocation:
I guess we could just buy another SSL cert from another CA (I mean, if
that really happens). There's a few ones that are not US based.
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.
SaĂŻvann
Le 2013-12-07 22:38, Odinn Cyberguerrilla a Ă©crit :
> Hello, re. the dedicated server for bitcoin.org idea, I have a few thoughts
>
> 1) I have commented in a blogpost of August 2013 at
> https://odinn.cyberguerrilla.org/ with some thoughts relative to possible
> issues with CA related to bitcoin.org - where I mentioned something
> relative to the DigiCert certificate,
> "DigiCert “may revoke a Certificate, without notice, for the reasons
> stated in the CPS, including if DigiCert reasonably believes that” (…)
> “Applicant is added to a government list of prohibited persons or entities
> or is operating from a prohibited destination under the laws of the United
> States” (…) “the Private Key associated with a Certificate was disclosed
> or Compromised”"
> In the same post I mentioned
> "Bitcoin.org has no certificate, no encryption — a situation which has its
> own obvious problems. Bitcoin.org currently sends users to download the
> bitcoin-qt client from sourceforge. Sourceforge is encrypted and has a
> certificate based on GeoTrust:
> https://www.geotrust.com/resources/repository/legal/"
>
> (Currently (Dec. 7, 2013) bitcoin.org shows as 'not verified' and 'not
> encrypted' examining it in a cursory fashion w/ Chrome)
>
> Not sure how this would work, but it would be nice to see the content at
> bitcoin.org encrypted, of course, but also further decentralized? how many
> mirrors are there of bitcoin.org - not sure, but a few things that come to
> mind when thinking of this are Tahoe-LAFS and also .bit stuff (namecoin).
> There are many ways to decentralize something but that is just something
> that comes to mind.
>
> This has been discussed at https://bitcointalk.org/index.php?topic=16312.0
> ('Is Bitcoin.org a weakness of bitcoin?) in the past and see also this
> https://bitcointalk.org/index.php?topic=119652.0 which discusses mirroring
> of certain content
>
> Some things to think about.
>
>> I would like to know what are your thoughts on moving bitcoin.org on a
>> dedicated server with a SSL certificate?
>>
>> I am considering the idea more seriously, but I'd like some feedback
>> before taking steps.
>>
>> SaĂŻvann
>>
>> ------------------------------------------------------------------------------
>> Sponsored by Intel(R) XDK
>> Develop, test and display web and hybrid apps with a single code base.
>> Download it for free now!
>> http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Bitcoin-development mailing list
>> Bitcoin-development at lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>>
>
>
>
> ------------------------------------------------------------------------------
> Sponsored by Intel(R) XDK
> Develop, test and display web and hybrid apps with a single code base.
> Download it for free now!
> http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>