| /openbmc/openbmc/poky/scripts/ |
| H A D | cve-json-to-text.py | 97 keys_in_package = {"name", "layer", "version", "issue"}
109 for issue in package["issue"]:
111 if keys_in_issue - issue.keys():
112 print("Warning: Missing keys %s in 'issue' for the package '%s'"
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"]
[all …]
|
| /openbmc/openbmc/poky/bitbake/lib/bb/tests/fetch-testdata/apple/cups/ |
| H A D | releases | 532 …<div class="d-inline"><svg class="octicon octicon-issue-opened" viewBox="0 0 14 16" version="1.1" …
731 …Issue <a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="50…
734 …terface (Issue <a class="issue-link js-issue-link" data-error-text="Failed to load issue title" da…
736 …Issue <a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="47…
737 …Issue <a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="48…
738 …Issue <a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="48…
740 (Issue <a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="48…
742 …Issue <a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="48…
743 …Issue <a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="49…
745 …Issue <a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="50…
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-graphics/directfb/directfb/ |
| H A D | configurefix.patch | 4 …Issue: directfb: /work/i586-poky-linux/directfb-1.4.15-r1/packages-split/directfb/usr/bin/dfblayer…
5 WARNING: QA Issue: directfb: /work/i586-poky-linux/directfb-1.4.15-r1/packages-split/directfb/usr/b…
6 WARNING: QA Issue: directfb: /work/i586-poky-linux/directfb-1.4.15-r1/packages-split/directfb/usr/b…
7 WARNING: QA Issue: directfb: /work/i586-poky-linux/directfb-1.4.15-r1/packages-split/directfb/usr/b…
8 WARNING: QA Issue: directfb: /work/i586-poky-linux/directfb-1.4.15-r1/packages-split/directfb/usr/b…
9 WARNING: QA Issue: directfb: /work/i586-poky-linux/directfb-1.4.15-r1/packages-split/directfb/usr/l…
10 WARNING: QA Issue: directfb: /work/i586-poky-linux/directfb-1.4.15-r1/packages-split/directfb/usr/l…
11 WARNING: QA Issue: directfb: /work/i586-poky-linux/directfb-1.4.15-r1/packages-split/directfb/usr/l…
12 WARNING: QA Issue: directfb: /work/i586-poky-linux/directfb-1.4.15-r1/packages-split/directfb/usr/l…
13 WARNING: QA Issue: directfb: /work/i586-poky-linux/directfb-1.4.15-r1/packages-split/directfb/usr/l…
[all …]
|
| /openbmc/openbmc/.github/ |
| H A D | stale.yml | 3 # Number of days of inactivity before an issue becomes stale (6 months)
6 # Number of days of inactivity before a stale issue is closed
9 # Label to use when marking an issue as stale
12 # Comment to post when marking an issue as stale. Set to `false` to disable
14 This issue has been automatically marked as stale because no activity has
16 next 30 days. If this issue should not be closed please add a comment.
19 # Comment to post when closing a stale issue. Set to `false` to disable
21 This issue has been closed because no activity has occurred in the last 7
22 months. Please reopen if this issue should not have been closed. Thank you
|
| /openbmc/openbmc-test-automation/tools/ |
| H A D | github_issues_to_csv | 25 for issue in response.json():
26 if "pull_request" not in issue:
27 labels = ", ".join([label["name"] for label in issue["labels"]])
32 close_date = issue.get("closed_at")
34 close_date = issue.get("closed_at").split("T")[0]
36 assignee_resp = issue.get("assignees", "Not Assigned")
47 milestone_resp = issue.get("milestone", "Not Assigned")
55 issue.get("title").encode("utf-8"),
56 issue.get("state").encode("utf-8"),
57 issue.get("created_at").split("T")[0],
[all …]
|
| /openbmc/openbmc/meta-raspberrypi/.github/ |
| H A D | ISSUE_TEMPLATE.md | 2 If you are reporting a new issue, make sure that we do not have any duplicates
3 already open. You can ensure this by searching the issue list for this
4 repository. If there is a duplicate, please close your issue and add a comment
5 to the existing issue instead.
14 **Steps to reproduce the issue:**
25 **Additional information you deem important (e.g. issue happens only occasionally):**
|
| /openbmc/qemu/docs/specs/ |
| H A D | vmw_pvscsi-spec.rst | 18 The registers area is used to raise hypervisor interrupts and issue device
29 are registers to issue device commands (with optional short data),
30 issue device interrupts, and control interrupt masking.
81 a. Issue ``PVSCSI_CMD_ADAPTER_RESET`` command
83 c. Issue ``PVSCSI_CMD_SETUP_MSG_RING`` command with no additional data,
86 d. Issue ``PVSCSI_CMD_SETUP_RINGS`` command, provide rings configuration
88 e. Issue ``PVSCSI_CMD_SETUP_MSG_RING`` command again, provide
97 c. Issue ``PVSCSI_CMD_ADAPTER_RESET`` command
103 b. Issue ``PVSCSI_REG_OFFSET_KICK_RW_IO`` for R/W operations
109 a. Issue ``PVSCSI_CMD_ABORT_CMD`` command
|
| /openbmc/u-boot/include/ |
| H A D | tpm_api.h | 15 * Issue a TPM_Startup command.
24 * Issue a TPM_SelfTestFull command.
32 * Issue a TPM_ContinueSelfTest command.
40 * Issue a TPM_NV_DefineSpace command. The implementation is limited
53 * Issue a TPM_NV_ReadValue command. This implementation is limited
66 * Issue a TPM_NV_WriteValue command. This implementation is limited
80 * Issue a TPM_Extend command.
96 * Issue a TPM_PCRRead command.
107 * Issue a TSC_PhysicalPresence command. TPM physical presence flag
117 * Issue a TPM_ReadPubek command.
[all …]
|
| H A D | tpm-v1.h | 286 * Issue a TPM_Startup command.
295 * Issue a TPM_SelfTestFull command.
303 * Issue a TPM_ContinueSelfTest command.
311 * Issue a TPM_NV_DefineSpace command. The implementation is limited
324 * Issue a TPM_NV_ReadValue command. This implementation is limited
337 * Issue a TPM_NV_WriteValue command. This implementation is limited
351 * Issue a TPM_Extend command.
365 * Issue a TPM_PCRRead command.
376 * Issue a TSC_PhysicalPresence command. TPM physical presence flag
386 * Issue a TPM_ReadPubek command.
[all …]
|
| /openbmc/openbmc/meta-arm/meta-arm/recipes-security/trusted-services/files/ |
| H A D | 0002-Fix-MbedTLS-3.6-and-GCC-14-compatibility.patch | 12 ...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 D | base-files_3.0.14.bb | 21 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/documentation/contributor-guide/ |
| H A D | identify-component.rst | 7 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/meta-yadro/recipes-core/os-release/ |
| H A D | os-release.bbappend | 119 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/meta/conf/distro/include/ |
| H A D | cve-extra-exclusions.inc | 2 # 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. \
32 Issue is memory exhaustion via glob() calls, e.g. from within an ftp server \
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/qemu/include/hw/i3c/ |
| H A D | mock-i3c-target.h | 11 * To write to the buffer, issue a private write and send data.
12 * To read from the buffer, issue a private read.
15 * To issue an IBI, set the 'ibi-magic-num' property to a non-zero number, and
16 * send that number in a private transaction. The mock target will issue an IBI
|
| H A D | mock-target.h | |
| /openbmc/openbmc/poky/meta/lib/patchtest/tests/ |
| H A D | test_python_pylint.py | 62 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/poky/documentation/migration-guides/ |
| H A D | release-notes-4.0.3.rst | 100 - linux-yocto/5.10: fix buildpaths issue with gen-mach-types
101 - linux-yocto/5.10: fix buildpaths issue with pnmtologo
105 - linux-yocto/5.15: fix buildpaths issue with gen-mach-types
106 - linux-yocto/5.15: fix buildpaths issue with pnmtologo
135 - python3: Backport patch to fix an issue in subinterpreters
139 - qemu: Fix slirp determinism issue
145 - rust: fix issue building cross-canadian tools for aarch64 on x86_64
159 - udev-extraconf:mount.sh: fix a umount issue
161 - vala: Fix on target wrapper buildpaths issue
177 - yocto-bsps/5.10: fix buildpaths issue with gen-mach-types
[all …]
|
| /openbmc/u-boot/arch/arm/mach-at91/ |
| H A D | mpddrc.c | 63 /* Issue a NOP command */ in ddr2_init()
69 /* Issue a NOP command */ in ddr2_init()
72 /* Issue an all banks precharge command */ in ddr2_init()
75 /* Issue an extended mode register set(EMRS2) to choose operation */ in ddr2_init()
79 /* Issue an extended mode register set(EMRS3) to set EMSR to 0 */ in ddr2_init()
84 * Issue an extended mode register set(EMRS1) to enable DLL and in ddr2_init()
97 /* Issue an all banks precharge command */ in ddr2_init()
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-multimedia/cdrkit/files/ |
| H A D | 0001-define-__THROW-to-avoid-build-issue-with-musl.patch | 4 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/meta-openembedded/meta-networking/recipes-protocols/radiusclient-ng/radiusclient-ng/ |
| H A D | Modify-configure.in-and-etc-Makefile.am.patch | 50 -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/docs/designs/ |
| H A D | thermal-control-modes.md | 11 An issue was discovered where the exhaust heat from the system GPUs causes
12 overtemp warnings on optical cables on certain system configurations. The issue
15 is needed to do so. Since the issue revolves around the optical cables
30 exhaust temp and include that within the fan control algorithm. A similar issue
|
| /openbmc/openbmc/poky/meta/recipes-devtools/rust/ |
| H A D | rust-source.inc | 6 file://repro-issue-fix-with-cc-crate-hashmap.patch;patchdir=${RUSTSRC} \
21 CVE_STATUS[CVE-2024-24576] = "not-applicable-platform: Issue only applies on Windows"
22 CVE_STATUS[CVE-2024-43402] = "not-applicable-platform: Issue only applies on Windows"
|
| /openbmc/openbmc/poky/meta/recipes-sato/puzzles/ |
| H A D | puzzles_git.bb | 50 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/docs/tof/ |
| H A D | contract.md | 74 the TOF. When an issue is opened the TOF will respond to a proposal or a
77 Once an issue has a proposal, TOF members have 8 days to vote on the proposal in
82 in the issue being put on the next TOF meeting agenda. To ensure proposals do
87 Issue vote indicators by reacting to the top post:
96 submitted via a GitHub issue using the process documented earlier in this
|