On 9/2/20 12:05 PM, Yousong Zhou wrote:
> On Wed, 2 Sep 2020 at 01:32, Hauke Mehrtens wrote:
>>
>> On 9/1/20 12:45 AM, Yousong Zhou wrote:
>>> It's worth mentioning that recent versions of macos since 10.15 have a
>>> restriction on certificate validity period, self-signed or not. It's
>>> a stro
On Wed, 2 Sep 2020 at 01:32, Hauke Mehrtens wrote:
>
> On 9/1/20 12:45 AM, Yousong Zhou wrote:
> > It's worth mentioning that recent versions of macos since 10.15 have a
> > restriction on certificate validity period, self-signed or not. It's
> > a strong restriction that the browser ui will have
Hauke Mehrtens wrote:
>
> We will still over normal http, using https is only an
> addition.
So you will change <> back to 0 by
default then? So it's actually optional? It's currently hardset
to 1 here:
https://git.openwrt.org/?p=openwrt/openwrt.git;a=blob;f=package/network/services/uhttpd/fil
On 9/1/20 12:45 AM, Yousong Zhou wrote:
> It's worth mentioning that recent versions of macos since 10.15 have a
> restriction on certificate validity period, self-signed or not. It's
> a strong restriction that the browser ui will have no buttons or knobs
> to bypass the certificate validation, r
Forgive me for chiming in now, for I have not been following the discussion
closely.
Is this change (specifically, using these certs for "ordinary operation" of
OpenWrt) being considered for the 20.0x release? Would it delay the RC1 release
in any way?
If so, I believe we should move it off th
Yousong Zhou wrote:
> It's worth mentioning that recent versions of macos since 10.15
> have a restriction on certificate validity period, self-signed
> or not. It's a strong restriction that the browser ui will have
> no buttons or knobs to bypass the certificate validation,
> rendering such sit
> Op 1 sep. 2020, om 01:21 heeft Daniel Golle het
> volgende geschreven:
>
> On Tue, Sep 01, 2020 at 06:45:02AM +0800, Yousong Zhou wrote:
>> It's worth mentioning that recent versions of macos since 10.15 have a
>> restriction on certificate validity period, self-signed or not. It's
>> a st
On Tue, 1 Sep 2020 at 06:45, Yousong Zhou wrote:
>
> It's worth mentioning that recent versions of macos since 10.15 have a
> restriction on certificate validity period, self-signed or not. It's
> a strong restriction that the browser ui will have no buttons or knobs
> to bypass the certificate v
On Tue, Sep 01, 2020 at 06:45:02AM +0800, Yousong Zhou wrote:
> It's worth mentioning that recent versions of macos since 10.15 have a
> restriction on certificate validity period, self-signed or not. It's
> a strong restriction that the browser ui will have no buttons or knobs
> to bypass the cer
It's worth mentioning that recent versions of macos since 10.15 have a
restriction on certificate validity period, self-signed or not. It's
a strong restriction that the browser ui will have no buttons or knobs
to bypass the certificate validation, rendering such sites
inaccessible. I remembered
ts.openwrt.org
>> Cc: Hauke Mehrtens
>> Subject: [PATCH] uhttpd: Increase default certificate validate from 2 to 10
>> years
>>
>> The user has to accept this specific certificate manually in his browser, the
>> browser does not trust it automatically, in this proc
e default certificate validate from 2 to 10
> years
>
> The user has to accept this specific certificate manually in his browser, the
> browser does not trust it automatically, in this process the user gets a scary
> message to approve. I am not aware of a way to improve this initial
The user has to accept this specific certificate manually in his
browser, the browser does not trust it automatically, in this process
the user gets a scary message to approve. I am not aware of a way to
improve this initial certificate approval.
After the certificate expired the user gets a scary
13 matches
Mail list logo
