openembedded-core.git/meta/recipes-devtools/file, branch thud

file: alternatify file

2018-10-18T15:47:59+00:00

file is also provided by toybox.

Signed-off-by: Dan McGregor 
Signed-off-by: Richard Purdie

file: Update to 5.34

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

Distros which have glibc 2.28 on them otherwsise fail
to build due to some syscall mismatches

Signed-off-by: Khem Raj 
Signed-off-by: Richard Purdie

file: fix regression for determining DB file type

2018-07-18T09:09:29+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)

Signed-off-by: Yi Zhao 
Signed-off-by: Ross Burton

file: Security fix CVE-2018-10360

2018-07-13T15:32:38+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

Signed-off-by: Yi Zhao 
Signed-off-by: Ross Burton

file: update to 5.33

2018-06-28T11:26:56+00:00

Drop 0001-Add-P-prompt-into-Usage-info.patch since it is already fixed
upstream.

Signed-off-by: Yi Zhao 
Signed-off-by: Richard Purdie

file: 5.31 -> 5.32

2017-11-21T13:02:53+00:00

Rebase debian-742262.patch for new source.

Signed-off-by: Robert Yang 
Signed-off-by: Ross Burton

file: 5.30 -> 5.31

2017-06-28T14:51:59+00:00

1. Upgrade file from 5.30 to 5.31

2. Rebase the following patch file.
   debian-742262.patch

Signed-off-by: Fan Xin 
Signed-off-by: Ross Burton

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

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

This reverts commit adb71e06768adadda7b69c3b5e81ca3ad67237f4.

Upstream restored the original hashes.

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

2017-03-17T15:37: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 
Signed-off-by: Paul Gortmaker 
Signed-off-by: Richard Purdie

file: 5.29 -> 5.30

2017-03-01T12:54:17+00:00

Signed-off-by: Robert Yang 
Signed-off-by: Ross Burton