Paul Spooren 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
On Thu, Nov 19, 2020 at 8:37 PM Rosen Penev wrote:
>
> On Thu, Nov 19, 2020 at 4:40 PM Paul Spooren wrote:
> >
> > Hi all,
> >
> > DSA (Distributed Switch Architecture)[0] is a main feature of 20.xx and
> > one of the last blockers for a branch. The goal states[1] support where
> > possible, not
On Thu, Nov 19, 2020 at 4:40 PM Paul Spooren wrote:
>
> Hi all,
>
> DSA (Distributed Switch Architecture)[0] is a main feature of 20.xx and
> one of the last blockers for a branch. The goal states[1] support where
> possible, not necessarily every target.
>
> This mail thread should be used to
Hi
On 2020-11-19, Paul Spooren wrote:
[...]
> The following targets seem use `swconfig`, should/can they be ported?
> Please post states and links to work in progress migrations:
[...]
> * ath79
[...]
> * ipq40xx
> * ipq806x
[...]
> * lantiq/xrx200
[...]
[ ipq807x is questionable at the moment,
> Given that the first login via LuCI, on a fresh install, is not with a
> password anyway. What if setting the initial password sets up
> letsencrypt also. Then when letsencrypt's first successful cert install,
> https gets enabled as the default and then requests the user reboot to
> complete
Hi
On 2020-11-19, TheWerthFam wrote:
> Given that the first login via LuCI, on a fresh install, is not with a
> password anyway. What if setting the initial password sets up
> letsencrypt also. Then when letsencrypt's first successful cert install,
> https gets enabled as the default and then
Given that the first login via LuCI, on a fresh install, is not with a
password anyway. What if setting the initial password sets up
letsencrypt also. Then when letsencrypt's first successful cert install,
https gets enabled as the default and then requests the user reboot to
complete the
Hi all,
DSA (Distributed Switch Architecture)[0] is a main feature of 20.xx and
one of the last blockers for a branch. The goal states[1] support where
possible, not necessarily every target.
This mail thread should be used to get an overview of the missing bits.
The following targets seem use
Hi,
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
Currently it's assumed, that already downloaded tarballs are always
fine, so no checksum checking is performed and the tarball is used even
if it might be corrupted.
From now on, we're going to always check the downloaded tarballs before
considering them valid.
Steps to reproduce:
1. remove
Hi Sebastian,
thanks for following up with a v4. I merged this change in
https://git.openwrt.org/2127accd441b1c979c8f3f56f3ad5264542e185a now.
~ Jo
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
Sebastian Kemper kirjoitti 18.11.2020 klo 23.58:
Commit 5d76065 moved the creation of the symvers directory to
include/kernel-build.mk. This is fine when building from scratch. But
when unpacking an SDK the directory doesn't exist and because the kernel
won't be built (again) this directory will
12 matches
Mail list logo
