Home
last modified time | relevance | path

Searched refs:issue (Results 1 – 25 of 607) sorted by relevance

12345678910>>...25

/openbmc/openbmc/poky/scripts/
H A Dcve-json-to-text.py109 for issue in package["issue"]:
111 if keys_in_issue - issue.keys():
113 % (keys_in_issue - issue.keys(), package["name"]))
116 lines += "CVE: %s\n" % issue["id"]
117 lines += "CVE STATUS: %s\n" % issue["status"]
118 lines += "CVE DETAIL: %s\n" % issue["detail"]
119 if "description" in issue:
120 lines += "CVE DESCRIPTION: %s\n" % issue["description"]
121 if "summary" in issue:
122 lines += "CVE SUMMARY: %s\n" % issue["summary"]
[all …]
/openbmc/openbmc-test-automation/tools/
H A Dgithub_issues_to_csv26 for issue in response.json():
27 if "pull_request" not in issue:
28 labels = ", ".join([label["name"] for label in issue["labels"]])
33 close_date = issue.get("closed_at")
35 close_date = issue.get("closed_at").split("T")[0]
37 assignee_resp = issue.get("assignees", "Not Assigned")
48 milestone_resp = issue.get("milestone", "Not Assigned")
56 issue.get("title").encode("utf-8"),
57 issue.get("state").encode("utf-8"),
58 issue
[all...]
/openbmc/openbmc/meta-arm/meta-arm/recipes-security/trusted-services/files/
H A D0002-Fix-MbedTLS-3.6-and-GCC-14-compatibility.patch12 ...or-triggered-build-issue-with-gcc-14.patch | 33 +++++++++++++++++++
14 create mode 100644 external/MbedTLS/0002-Fix-Werror-triggered-build-issue-with-gcc-14.patch
16 …TLS/0002-Fix-Werror-triggered-build-issue-with-gcc-14.patch b/external/MbedTLS/0002-Fix-Werror-tri…
20 +++ b/external/MbedTLS/0002-Fix-Werror-triggered-build-issue-with-gcc-14.patch
25 +Subject: [PATCH 1/1] Fix -Werror triggered build issue with gcc 14
28 +a known issue (see [1]) and I am taking the proposed fix.
/openbmc/openbmc/poky/meta/recipes-core/base-files/
H A Dbase-files_3.0.14.bb21 file://issue.net \
22 file://issue \
61 ${sysconfdir}/issue /${sysconfdir}/issue.net \
132 install -m 644 ${S}/issue* ${D}${sysconfdir}
134 printf "${DISTRO_NAME} " >> ${D}${sysconfdir}/issue
135 printf "${DISTRO_NAME} " >> ${D}${sysconfdir}/issue.net
138 printf "%s " $distro_version_nodate >> ${D}${sysconfdir}/issue
139 printf "%s " $distro_version_nodate >> ${D}${sysconfdir}/issue.net
141 printf "\\\n \\\l\n" >> ${D}${sysconfdir}/issue
142 echo >> ${D}${sysconfdir}/issue
[all …]
/openbmc/openbmc/poky/meta/lib/patchtest/tests/
H A Dtest_python_pylint.py62 for issue in self.pylint_test:
63 if self.pylint_test[issue] not in self.pylint_pretest.values():
65 … data=[('Output', 'Please, fix the listed issues:'), ('', issue + ' ' + self.pylint_test[issue])])
/openbmc/openbmc/meta-yadro/recipes-core/os-release/
H A Dos-release.bbappend119 with open(d.expand('${B}/issue'), 'w') as f:
124 install -m 0644 issue ${D}${sysconfdir}/issue
125 install -m 0644 issue ${D}${sysconfdir}/issue.net
128 CONFFILES:${PN} += " ${sysconfdir}/issue ${sysconfdir}/issue.net"
129 FILES:${PN} += " ${sysconfdir}/issue ${sysconfdir}/issue.net"
/openbmc/openbmc/poky/documentation/contributor-guide/
H A Didentify-component.rst7 so the first step is to identify the component where the issue likely lies.
8 For example, if you have a hardware issue, it is likely related to the BSP
10 or :term:`layer`. If the issue is a build/configuration one and a distro is in
11 use, they would likely be the first place to ask questions. If the issue is a
19 If the issue is in the core metadata layer (OpenEmbedded-Core) or in BitBake,
/openbmc/openbmc/poky/meta/lib/oeqa/selftest/cases/
H A Dcve_check.py355 found_cves = { issue["id"]: issue["status"] for issue in package["issue"]}
464 for issue in package["issue"]:
465 found_cves[issue["id"]] = {
466 "status" : issue["status"],
467 "detail" : issue["detail"] if "detail" in issue else "",
468 "description" : issue["description"] if "description" in issue else ""
/openbmc/u-boot/board/esd/vme8349/
H A Dcaddy.h33 uint32_t issue; member
40 uint32_t issue; member
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-multimedia/cdrkit/files/
H A D0001-define-__THROW-to-avoid-build-issue-with-musl.patch4 Subject: [PATCH 1/2] define __THROW to avoid build issue with musl
25 +/* define __THROW to avoid build issue when it's not available from the libc */
40 +/* define __THROW to avoid build issue when it's not available from the libc */
/openbmc/openbmc/poky/meta/conf/distro/include/
H A Dcve-extra-exclusions.inc2 # or there is no reasonable action the Yocto Project can take to resolve the issue.
3 # It contains all the information we are aware of about an issue and analysis about
24 The issue here is spoofing of domain names using characters from other character sets. \
34 Upstream don't see it as a security issue, ftp servers shouldn't be passing \
43 CVE applies to a netapp product as well as flagging a general issue. We don't ship anything \
61 # ensure the bulk of the major kernel CVEs are fixed and we don't dive into each individual issue
63 CVE_STATUS[CVE-1999-0524] = "ignored: cpe:*:linux_kernel:issue is that ICMP exists, can be filewall…
72 The issue is of low impact, at worst sitting in an infinite loop rather than exploitable."
76 There was a proposed patch but rejected by upstream qemu. It is unclear if the issue can \
/openbmc/openbmc/meta-openembedded/meta-networking/recipes-protocols/radiusclient-ng/radiusclient-ng/
H A DModify-configure.in-and-etc-Makefile.am.patch50 -pkgsysconf_DATA = issue port-id-map radiusclient.conf \
53 +pkgsysconf_DATA = issue port-id-map radiusclient.conf
59 EXTRA_DIST = issue port-id-map dictionary dictionary.ascend \
61 @@ -25,6 +27,7 @@ EXTRA_DIST = issue port-id-map dictionary dictionary.ascend \
/openbmc/qemu/hw/intc/
H A Drx_icu.c94 int issue; in rxicu_set_irq() local
107 issue = level; in rxicu_set_irq()
111 issue = (level == 0 && src->level == 1); in rxicu_set_irq()
115 issue = (level == 1 && src->level == 0); in rxicu_set_irq()
119 issue = ((level ^ src->level) & 1); in rxicu_set_irq()
125 if (issue == 0 && src->sense == TRG_LEVEL) { in rxicu_set_irq()
134 if (issue) { in rxicu_set_irq()
/openbmc/openbmc/poky/meta/recipes-sato/puzzles/
H A Dpuzzles_git.bb50 CVE_STATUS[CVE-2024-13769] = "cpe-incorrect: issue in ThemeREX's Wordpress theme Puzzles"
51 CVE_STATUS[CVE-2024-13770] = "cpe-incorrect: issue in ThemeREX's Wordpress theme Puzzles"
52 CVE_STATUS[CVE-2025-0837] = "cpe-incorrect: issue in ThemeREX's Wordpress theme Puzzles"
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/beep/
H A Dbeep_1.4.12.bb1 SUMMARY = "beep allows you to have the PC speaker issue beeps and beep patterns"
2 DESCRIPTION = "beep allows you to have the PC speaker issue beeps and beep \
/openbmc/openbmc/meta-openembedded/meta-filesystems/
H A DSECURITY.md4 If you would like to report a public issue (for example, one with a released
9 If you are dealing with a not-yet released or urgent issue, please send a
/openbmc/openbmc/meta-openembedded/meta-webserver/
H A DSECURITY.md4 If you would like to report a public issue (for example, one with a released
9 If you are dealing with a not-yet released or urgent issue, please send a
/openbmc/openbmc/meta-openembedded/meta-multimedia/
H A DSECURITY.md4 If you would like to report a public issue (for example, one with a released
9 If you are dealing with a not-yet released or urgent issue, please send a
/openbmc/openbmc/meta-openembedded/meta-python/
H A DSECURITY.md4 If you would like to report a public issue (for example, one with a released
9 If you are dealing with a not-yet released or urgent issue, please send a
/openbmc/openbmc/meta-openembedded/meta-oe/
H A DSECURITY.md4 If you would like to report a public issue (for example, one with a released
9 If you are dealing with a not-yet released or urgent issue, please send a
/openbmc/openbmc/meta-openembedded/meta-initramfs/
H A DSECURITY.md4 If you would like to report a public issue (for example, one with a released
9 If you are dealing with a not-yet released or urgent issue, please send a
/openbmc/openbmc/meta-openembedded/meta-perl/
H A DSECURITY.md4 If you would like to report a public issue (for example, one with a released
9 If you are dealing with a not-yet released or urgent issue, please send a
/openbmc/openbmc/meta-openembedded/meta-networking/
H A DSECURITY.md4 If you would like to report a public issue (for example, one with a released
9 If you are dealing with a not-yet released or urgent issue, please send a
/openbmc/openbmc/meta-openembedded/meta-xfce/
H A DSECURITY.md4 If you would like to report a public issue (for example, one with a released
9 If you are dealing with a not-yet released or urgent issue, please send a
/openbmc/openbmc/poky/meta/recipes-connectivity/neard/neard/
H A DMakefile.am-fix-parallel-issue.patch4 Subject: [PATCH] Makefile.am: fix parallel issue
7 fix the race issue:

12345678910>>...25