Jump to page: 1 25  
Page
Thread overview
https everywhere
Feb 21, 2014
Walter Bright
Feb 21, 2014
Dicebot
Feb 21, 2014
Adam Wilson
Feb 21, 2014
Dicebot
Feb 21, 2014
Adam Wilson
Feb 21, 2014
Jan Knepper
Feb 21, 2014
Walter Bright
Feb 21, 2014
Dicebot
Feb 21, 2014
Adam Wilson
Feb 21, 2014
Brad Anderson
Feb 21, 2014
Walter Bright
Feb 21, 2014
Brad Anderson
Feb 21, 2014
Nick Sabalausky
Feb 22, 2014
Leandro Lucarella
Feb 22, 2014
Nick Sabalausky
Feb 22, 2014
Nick Sabalausky
Feb 22, 2014
Leandro Lucarella
Feb 22, 2014
Leandro Lucarella
Feb 21, 2014
Dicebot
Feb 21, 2014
Brad Anderson
Feb 21, 2014
Dicebot
Feb 21, 2014
Brad Anderson
Feb 21, 2014
Dicebot
Feb 27, 2014
Kagamin
Feb 21, 2014
Nick Sabalausky
Feb 21, 2014
Brad Anderson
Feb 22, 2014
Nick Sabalausky
Feb 22, 2014
Rikki Cattermole
Feb 21, 2014
Jan Knepper
Feb 22, 2014
Ryan Chouinard
Feb 27, 2014
Kagamin
Feb 21, 2014
deadalnix
Feb 21, 2014
Dicebot
Feb 21, 2014
Nick Sabalausky
Feb 22, 2014
Dmitry Olshansky
Feb 22, 2014
Walter Bright
Feb 22, 2014
Dmitry Olshansky
Feb 21, 2014
Jan Knepper
Feb 21, 2014
Jan Knepper
Feb 21, 2014
Dmitry Olshansky
Feb 21, 2014
w0rp
Feb 21, 2014
Brad Roberts
Feb 22, 2014
Sönke Ludwig
Feb 26, 2014
deadalnix
Feb 27, 2014
Kagamin
February 21, 2014
dlang.org and dconf.org now support https,

https://dlang.org
https://dconf.org

Note that this is a self-signed certificate, and so when you first access it you'll get a dire warning from your browser.
February 21, 2014
On Friday, 21 February 2014 at 20:34:12 UTC, Walter Bright wrote:
> dlang.org and dconf.org now support https,
>
> https://dlang.org
> https://dconf.org
>
> Note that this is a self-signed certificate, and so when you first access it you'll get a dire warning from your browser.

Why can't free startssl certificate be used?
February 21, 2014
On Fri, 21 Feb 2014 12:35:10 -0800, Dicebot <public@dicebot.lv> wrote:

> On Friday, 21 February 2014 at 20:34:12 UTC, Walter Bright wrote:
>> dlang.org and dconf.org now support https,
>>
>> https://dlang.org
>> https://dconf.org
>>
>> Note that this is a self-signed certificate, and so when you first access it you'll get a dire warning from your browser.
>
> Why can't free startssl certificate be used?

It probably has to do with the fact that the NSA owns every Root Signing Key in the world.

-- 
Adam Wilson
GitHub/IRC: LightBender
Aurora Project Coordinator
February 21, 2014
On 2/21/2014 12:35 PM, Dicebot wrote:
> On Friday, 21 February 2014 at 20:34:12 UTC, Walter Bright wrote:
>> dlang.org and dconf.org now support https,
>>
>> https://dlang.org
>> https://dconf.org
>>
>> Note that this is a self-signed certificate, and so when you first access it
>> you'll get a dire warning from your browser.
>
> Why can't free startssl certificate be used?

I never heard of it.
February 21, 2014
22-Feb-2014 00:34, Walter Bright пишет:
> dlang.org and dconf.org now support https,
>
> https://dlang.org
> https://dconf.org
>
Good idea.

> Note that this is a self-signed certificate, and so when you first
> access it you'll get a dire warning from your browser.

That gets horribly wrong. With this kind of stuff we'd just scare away new users. Surely a CA signed SSL cert doesn't cost that much to ignore it.

-- 
Dmitry Olshansky
February 21, 2014
On Friday, 21 February 2014 at 20:39:28 UTC, Adam Wilson wrote:
> It probably has to do with the fact that the NSA owns every Root Signing Key in the world.

And how it is relevant? Not like we are speaking about security here - nothing sensitive is transferred from dlang.org; using self-signed certificates for public pages is just weird.
February 21, 2014
On Friday, 21 February 2014 at 20:40:24 UTC, Walter Bright wrote:
>> Why can't free startssl certificate be used?
>
> I never heard of it.

https://www.startssl.com/?app=1
February 21, 2014
On Fri, 21 Feb 2014 12:42:10 -0800, Dicebot <public@dicebot.lv> wrote:

> On Friday, 21 February 2014 at 20:39:28 UTC, Adam Wilson wrote:
>> It probably has to do with the fact that the NSA owns every Root Signing Key in the world.
>
> And how it is relevant? Not like we are speaking about security here - nothing sensitive is transferred from dlang.org; using self-signed certificates for public pages is just weird.

I agree, it's not exactly welcoming due to how browsers handle them.

-- 
Adam Wilson
GitHub/IRC: LightBender
Aurora Project Coordinator
February 21, 2014
On Fri, 21 Feb 2014 12:40:29 -0800, Walter Bright <newshound2@digitalmars.com> wrote:

> On 2/21/2014 12:35 PM, Dicebot wrote:
>> On Friday, 21 February 2014 at 20:34:12 UTC, Walter Bright wrote:
>>> dlang.org and dconf.org now support https,
>>>
>>> https://dlang.org
>>> https://dconf.org
>>>
>>> Note that this is a self-signed certificate, and so when you first access it
>>> you'll get a dire warning from your browser.
>>
>> Why can't free startssl certificate be used?
>
> I never heard of it.

I don't think they allow it for anything other than personal use though.

-- 
Adam Wilson
GitHub/IRC: LightBender
Aurora Project Coordinator
February 21, 2014
On Friday, 21 February 2014 at 20:34:12 UTC, Walter Bright wrote:
> dlang.org and dconf.org now support https,
>
> https://dlang.org
> https://dconf.org
>
> Note that this is a self-signed certificate, and so when you first access it you'll get a dire warning from your browser.

Cool, that's always welcome. I actually serve all of my website exclusively through HTTPS.

https://w0rp.com

I bought my certificate from Comodo. I think I only paid something like 10 dollars for a year or something, which I put down as being less than the cost of dinner if I eat out, so I just bought it.
« First   ‹ Prev
1 2 3 4 5