On Fri, Dec 21, 2018 at 8:05 PM Yousong Zhou wrote:
>
> On Sat, 22 Dec 2018 at 01:21, Kevin 'ldir' Darbyshire-Bryant
> wrote:
> >
> > Backport
> > https://git.kernel.org/pub/scm/linux/kernel/git/mips/linux.git/commit/?id=adcc81f148d733b7e8e641300c5590a2cdc13bf3
> >
> > "Mapping the delay slot em
On Sat, 22 Dec 2018 at 01:21, Kevin 'ldir' Darbyshire-Bryant
wrote:
>
> Backport
> https://git.kernel.org/pub/scm/linux/kernel/git/mips/linux.git/commit/?id=adcc81f148d733b7e8e641300c5590a2cdc13bf3
>
> "Mapping the delay slot emulation page as both writeable & executable
> presents a security ris
On Fri, Dec 21, 2018 at 9:21 AM Kevin 'ldir' Darbyshire-Bryant
wrote:
>
> Backport
> https://git.kernel.org/pub/scm/linux/kernel/git/mips/linux.git/commit/?id=adcc81f148d733b7e8e641300c5590a2cdc13bf3
>
> "Mapping the delay slot emulation page as both writeable & executable
> presents a security r
Backport
https://git.kernel.org/pub/scm/linux/kernel/git/mips/linux.git/commit/?id=adcc81f148d733b7e8e641300c5590a2cdc13bf3
"Mapping the delay slot emulation page as both writeable & executable
presents a security risk, in that if an exploit can write to & jump into
the page then it can be used a
With kernel 4.19 new configuration options for the compiler were added.
These are automatically selected and set, instead of having them in each
target configuration, put them into the generic configuration.
Signed-off-by: Hauke Mehrtens
---
target/linux/generic/config-4.19 | 6 ++
1 file ch
The configuration option was renamed with kernel 4.19 from
CONFIG_CC_STACKPROTECTOR to CONFIG_STACKPROTECTOR adapt the code to set
both options.
CONFIG_STACKPROTECTOR now sets the regular stack protector and
CONFIG_STACKPROTECTOR_STRONG activates the additional protection of more
functions.
Signe
> -Ursprüngliche Nachricht-
> Von: openwrt-devel Im Auftrag
> von James Feeney
> Gesendet: Donnerstag, 20. Dezember 2018 20:46
[...]
> There also seems to be a presumption that a "newbie" is, or should be,
> running luci. I believe that that is also an inappropriate assumption.
>
> U
Hi,
> Why did you remove this dir?
To save space on the download servers.
> If we want to build custom binaries using SDK, should we use something else?
Use the feeds mechanism within the SDK to build your required libaries
first, e.g.:
./scripts/feeds update
./scripts/feeds install libpcap
m
Hi,
in the commit 7dfbac8073e1f5fd47f85743b9ebead842ed3c70, signed of by
Felix Fietkau, you removed staging_dir/target_ directory from SDK
build.
In this folder all the libraries and header files need for compiling
custom binaries reside.
Why did you remove this dir?
If we want to build cust
