linux/poky.git/meta/recipes-devtools/file, branch 2.6_M3

file: Update to 5.34

2018-08-08T09:51:59+00:00

Distros which have glibc 2.28 on them otherwsise fail to build due to some syscall mismatches (From OE-Core rev: 990a9c944375146bb3f0208b30e8b7f50239cef5) Signed-off-by: Khem Raj Signed-off-by: Richard Purdie

file: fix regression for determining DB file type

2018-07-18T09:18:42+00:00

The version 5.33 introduced a regression bug for determining the DB file type. Backport a patch from upstream to fix it. Before apply the patch: $ file aliases.db aliases.db: created: Thu Jan 1 00:38:24 1970, modified: Thu Jan 1 00:00:00 1970 After apply the patch: $ file aliases.db aliases.db: Berkeley DB (Btree, version 9, native byte-order) (From OE-Core rev: 99e50d9e53ab23fc643c46378fa8c36190995335) Signed-off-by: Yi Zhao Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

file: Security fix CVE-2018-10360

2018-07-15T15:16:16+00:00

CVE-2018-10360: The do_core_note function in readelf.c in libmagic.a in file 5.33 allows remote attackers to cause a denial of service (out-of-bounds read and application crash) via a crafted ELF file. References: https://nvd.nist.gov/vuln/detail/CVE-2018-10360 Patch from: https://github.com/file/file/commit/a642587a9c9e2dd7feacdf513c3643ce26ad3c22 (From OE-Core rev: 22886cf6f37d9a5c6ff90e10e0c17ed7f6321305) Signed-off-by: Yi Zhao Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

file: update to 5.33

2018-06-29T10:07:44+00:00

Drop 0001-Add-P-prompt-into-Usage-info.patch since it is already fixed upstream. (From OE-Core rev: 02f8aff020762e77bf49587115f6b8fbc96296c9) Signed-off-by: Yi Zhao Signed-off-by: Richard Purdie

file: 5.31 -> 5.32

2017-11-21T13:06:12+00:00

Rebase debian-742262.patch for new source. (From OE-Core rev: 4231e238d9fe6b2178b900cde49ca17ce5aa1f47) Signed-off-by: Robert Yang Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

file: 5.30 -> 5.31

2017-06-28T14:52:18+00:00

1. Upgrade file from 5.30 to 5.31 2. Rebase the following patch file. debian-742262.patch (From OE-Core rev: f38290ec2a727427a6481e4dafb02ecd8a60fad1) Signed-off-by: Fan Xin Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

Revert "file: update SRCREV for 5.30 to fix fetch fail on missing commit"

2017-03-21T22:39:17+00:00

This reverts commit adb71e06768adadda7b69c3b5e81ca3ad67237f4. Upstream restored the original hashes. Signed-off-by: Richard Purdie

file: update SRCREV for 5.30 to fix fetch fail on missing commit

2017-03-17T16:53:05+00:00

Machines that cloned a while ago will have the commit, but new deployments won't because it seems the upstream changed/rebased and the old commit ID has been garbage-collected away. Hence the fetch fails to check out the named commit ID. Both the old (gone) commit, and the "new" commit show the same dates and commit log and point at 5.30, so hopefully this is the right thing to do. A git diff of the two seems to only show a blanket uprev of CVS tags and deletion of a couple autogen'd files, and no real source changes. Cc: Christos Zoulas (From OE-Core rev: adb71e06768adadda7b69c3b5e81ca3ad67237f4) Signed-off-by: Paul Gortmaker Signed-off-by: Richard Purdie

file: 5.29 -> 5.30

2017-03-01T23:27:06+00:00

(From OE-Core rev: 83a822e7b7810a9a59f0ad0efe6c827b89878b61) Signed-off-by: Robert Yang Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

file: 5.28 -> 5.29

2017-01-05T13:54:06+00:00

Upgrade file from 5.28 to 5.29. (From OE-Core rev: 056b31649141f8160ce05d72b9e53e39ac97c718) Signed-off-by: Huang Qiyu Signed-off-by: Ross Burton Signed-off-by: Richard Purdie