Mirror of git.yoctoproject.org/poky https://git.enea.com/cgit/linux/poky.git/atom?h=walnascar 2020-01-27T16:48:08+00:00 2020-01-27T16:48:08+00:00 Wang Mingyu wangmy@cn.fujitsu.com 2020-01-20T12:26:45+00:00 urn:sha1:6f902721c4e8d5e15dff9d8221f4d8db62425423 (From OE-Core rev: 287de363f80a2f9919b942a1349f58575e8b91d8) Signed-off-by: Wang Mingyu <wangmy@cn.fujitsu.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2019-11-10T14:06:10+00:00 Haris Okanovic haris.okanovic@ni.com 2019-11-07T22:06:51+00:00 urn:sha1:ad34c73cbf2099ee1e70e99ea63f6cec930c597c Enable nativesdk builds of gnupg and it's dependencies (libksba, npth, and pinentry) to fix builds of nativesdk-opkg. This is necessary on distribution which enable gpg signature verification in opkg and also build SDK images that include opkg. (From OE-Core rev: e935cba0122a93df611c9a846c16b7841b715fd8) Signed-off-by: Haris Okanovic <haris.okanovic@ni.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2019-11-10T14:06:10+00:00 Haris Okanovic haris.okanovic@ni.com 2019-11-07T22:04:19+00:00 urn:sha1:1792105f9e9298aeec4562f20313f8e05b7226a6 Add minimal "gnupg-gpg" package containing just enough binaries to run gpg and gpg-agent. Add dependency in normal "gnupg" package to preserve old behavior. Some applications like opkg don't need all functionality provided by normal gnupg installations. This minimal package provides just enough functionality to verify and manage keys in opkg, in order to minimize disk overhead. (From OE-Core rev: 6686c64ad30481d4d67af6a7b9bec7e7ae1a83fe) Signed-off-by: Haris Okanovic <haris.okanovic@ni.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2019-09-16T22:02:44+00:00 Jason Wessel jason.wessel@windriver.com 2019-09-11T18:32:04+00:00 urn:sha1:7ae68c580cc9ff1e2ba3c65b84cf3a02ebaaaac1 The gpg commit signing in ostree-native doesn't work properly when running from sstate. The ostree-native is linked with gpgme-native's libraries, which have calls into gpg. Ultimately it turned out the problem was that gpgme calls gpgconf and some of the other gnupg-native binaries directly. Not all the binaries have a wrapper which sets the environment variable GNUPG_BIN. Without this wrapper these binaries it gets the path assignment from the original compilation which causes a fault when running from sstate in a new tmp directory because these paths will not exist. (From OE-Core rev: f93bf3bd051923618ce3949d5686fdb8cf998645) Signed-off-by: Jason Wessel <jason.wessel@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2019-07-11T08:32:50+00:00 Anuj Mittal anuj.mittal@intel.com 2019-07-10T02:37:23+00:00 urn:sha1:3c5f407923ff288a93a349074bfbf3f764d3e264 Also fixes CVE-2019-13050. Announcement: https://lists.gnupg.org/pipermail/gnupg-announce/2019q3/000439.html (From OE-Core rev: c6e46323f0d62daf8bd424e642581fdcba920ef7) Signed-off-by: Anuj Mittal <anuj.mittal@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>