Paul Spooren <m...@aparcar.org> wrote:
> The current list of release goals for 20.xx states[0] that LuCI should
> use HTTPS per default. This works by creating on-device a self-signed
> certificate. Self-signed certificates result in warnings and may cause
> more harm than good, multiple discussion are found in the mail archive.
> As no clean solution seems in reach while 20.xx seems close, I'd like to
> suggest to postponse HTTPS LuCI (`luci-ssl` vs `luci`) per default.
> This isn't a vote but a request for developer/user opinions.
I agree with postponing this.
I think that we need to do some work on this problem.
This is a subset (an easier subset actually) of a general IoT onboarding
problem.
I would like to form a design-team to figure out what we can do in practice,
and I would be happy to lead/act-as-convenor it via a series online working
meetings if the group wants.
The need for a PPPoE username/password is one of the challenges.
-- ] Never tell me the odds! | ipv6 mesh networks [ ] Michael Richardson, Sandelman Software Works | IoT architect [ ] m...@sandelman.ca http://www.sandelman.ca/ | ruby on rails [
signature.asc
Description: PGP signature
_______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
