Go to file
Yann E. MORIN e4c284e6b9 package/pkg-utils: escape \ in generated legal-info
In the output of legal-info, which is JSON-formatted, we include the
CPI_ID (when it is valid).

For xerces, the CPE_ID contains two sequences of \+ (which is exactly
what is present in the NIST DB, [0]).

However, in JSON, like in C, \ escapes the following character; only a
very limited set of characters are valid to escape: " \ / b f n r t u.
Escaping any other character is invalid. Conformant JSON parser will
choke on invalid sequences, and so does not the json python module:

      File "/usr/lib/python2.7/json/decoder.py", line 380, in raw_decode
        obj, end = self.scan_once(s, idx)
    ValueError: Invalid \escape: line 1 column 608554 (char 608553)

We fix that be globally escaping \ in our json output, in the generic
sanitising macro.

[0] https://nvd.nist.gov/products/cpe/detail/645?namingFormat=2.3&orderBy=CPEURI&keyword=xerces&status=FINAL

Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2021-02-07 10:32:40 +01:00
arch
board configs/nexbox_a95x_defconfig: bump to kernel 5.10.12 2021-02-04 18:15:09 +01:00
boot
configs configs/nexbox_a95x_defconfig: bump to kernel 5.10.12 2021-02-04 18:15:09 +01:00
docs
fs
linux {linux, linux-headers}: bump 5.{4, 10}.x 4.{4, 9, 14, 19} series 2021-02-07 10:12:16 +01:00
package package/pkg-utils: escape \ in generated legal-info 2021-02-07 10:32:40 +01:00
support support/config-fragments/autobuild: use Bootlin toolchain for RISC-V 64 musl 2021-02-05 09:27:37 +01:00
system
toolchain toolchain/toolchain-external: update Arm AArch64 BE toolchain 10.2-2020.11 2021-02-03 22:52:57 +01:00
utils
.defconfig
.flake8
.gitignore
.gitlab-ci.yml
CHANGES
Config.in
Config.in.legacy
COPYING
DEVELOPERS package/tpm2-pkcs11: new package 2021-02-06 18:25:13 +01:00
Makefile
Makefile.legacy
README

Buildroot is a simple, efficient and easy-to-use tool to generate embedded
Linux systems through cross-compilation.

The documentation can be found in docs/manual. You can generate a text
document with 'make manual-text' and read output/docs/manual/manual.text.
Online documentation can be found at http://buildroot.org/docs.html

To build and use the buildroot stuff, do the following:

1) run 'make menuconfig'
2) select the target architecture and the packages you wish to compile
3) run 'make'
4) wait while it compiles
5) find the kernel, bootloader, root filesystem, etc. in output/images

You do not need to be root to build or run buildroot.  Have fun!

Buildroot comes with a basic configuration for a number of boards. Run
'make list-defconfigs' to view the list of provided configurations.

Please feed suggestions, bug reports, insults, and bribes back to the
buildroot mailing list: buildroot@buildroot.org
You can also find us on #buildroot on Freenode IRC.

If you would like to contribute patches, please read
https://buildroot.org/manual.html#submitting-patches