| /openbmc/docs/security/ |
| H A D | how-to-report-a-security-vulnerability.md | 4 give the project time to address the problem before public disclosure.
8 - You have information about a security problem or vulnerability which is not
10 - You want the problem fixed before public disclosure and you are willing to
12 - You understand the problem will eventually be publicly disclosed.
20 not, the security response team will help route the problem.
21 - Include details about the security problem such as:
22 - The version and configuration of OpenBMC the problem appears in.
23 - How to reproduce the problem.
25 - As the problem reporter, you will be included in the problem response.
29 the security response team can help you route the problem.
[all …]
|
| H A D | obmc-security-response-team.md | 16 1. A community member reports a problem privately to the security response team
19 maintainers, and the problem submitter) work to understand the problem.
21 the problem, its severity, and how to protect your systems that were built on
37 communication vehicle between the person who reported the problem and the
44 working to fix the problem.
|
| H A D | obmc-security-response-team-guidelines.md | 19 1. Handle new problem reports.
23 problem is known.
25 2. Analyze the problem and engage collaborators as needed (upstream, downstream,
27 - Determine if the problem is new or known.
28 - Determine if the problem is in OpenBMC.
29 - If the problem is in a project that OpenBMC uses, re-route the problem to
31 - Note that the problem may be in a customized version of OpenBMC but not
33 - Determine which OpenBMC areas should address the problem.
37 - Please describe when the problem was introduced to help users learn if
40 problem in the original code through OpenBMC release 2.9, the affected
[all …]
|
| /openbmc/docs/ |
| H A D | SECURITY.md | 6 give the project time to address the problem before public disclosure.
10 - You have information about a security problem which is not yet publicly
12 - You want the problem fixed before public disclosure and you are willing to
14 - You understand the problem will eventually be publicly disclosed.
19 security problem such as:
20 - the version and configuration of OpenBMC the problem appears in
21 - how to reproduce the problem
23 - As the problem reporter, you will be included in the email thread for the
24 problem.
27 the problem. Activities may include:
[all …]
|
| /openbmc/bmcweb/redfish-core/include/registries/ |
| H A D | fabric_message_registry.hpp | 92 "Contact the network administrator for problem resolution.",
183 "Contact the network administrator for problem resolution.",
196 "Contact the network administrator for problem resolution.",
209 "Contact the network administrator for problem resolution.",
222 "Contact the network administrator for problem resolution.",
250 "Contact the network administrator for problem resolution.",
302 "Contact the network administrator for problem resolution.",
330 "Contact the network administrator for problem resolution.",
422 "Contact the network administrator for problem resolution.",
435 "Contact the network administrator for problem resolution.",
[all …]
|
| /openbmc/docs/designs/ |
| H A D | design-template.md | 11 - The focus of the document is to define the problem we need to solve and
59 ## Problem Description
61 (1 paragraph) What are we doing and why? What problem are you trying to solve?
79 (2-5 paragraphs) What are the constraints for the problem you are trying to
82 the details you know about the problem space, so they can help review your
90 have alternative solutions to a problem, list them concisely in a bullet list.
|
| H A D | unique-hostname.md | 9 ## Problem Description
13 getting the hostname conflict and the service name conflict. Hence, the problem
|
| /openbmc/qemu/.gitlab/issue_templates/ |
| H A D | bug.md | 5 to reproduce the problem with the latest qemu.git master built from
28 Give the smallest, complete command line that exhibits the problem.
43 ## Description of problem
44 <!-- Describe the problem, including any error/crash messages seen. -->
|
| /openbmc/openbmc/poky/bitbake/doc/bitbake-user-manual/ |
| H A D | bitbake-user-manual-library-functions.rst | 26 bb.warn("Houston, we have a %s", "bit of a problem")
30 bb.error("%s, we have a %s" % ("Houston", "big problem"))
35 bb.fatal(f"{h}, we have a critical problem")
|
| /openbmc/openbmc/meta-openembedded/meta-multimedia/recipes-multimedia/alsa-equal/alsa-equal/ |
| H A D | 0003-Fix-mixer.patch | 31 SNDERR("Problem with control file %s, %d.", controls, index);
41 SNDERR("Problem with control file %s.", controls);
48 SNDERR("Problem with control file %s.", controls);
81 SNDERR("Problem with control file %s.", controls);
88 SNDERR("Problem with control file %s.", controls);
|
| /openbmc/u-boot/board/renesas/rsk7203/ |
| H A D | rsk7203.c | 33 * This problem cannot evade by the swap function of CHIP, this can
35 * And this has problem by FIFO access only. pkt_data_pull/pkt_data_push
36 * functions necessary to solve this problem.
|
| /openbmc/u-boot/board/renesas/rsk7264/ |
| H A D | rsk7264.c | 34 * This problem cannot evade by the swap function of CHIP, this can
36 * And this has problem by FIFO access only. pkt_data_pull/pkt_data_push
37 * functions necessary to solve this problem.
|
| /openbmc/u-boot/board/renesas/rsk7269/ |
| H A D | rsk7269.c | 35 * This problem cannot evade by the swap function of CHIP, this can
37 * And this has problem by FIFO access only. pkt_data_pull/pkt_data_push
38 * functions necessary to solve this problem.
|
| /openbmc/u-boot/doc/driver-model/ |
| H A D | fdt-fixup.txt | 31 In the Linux kernel, one possible solution to this problem is to employ the
45 well, is being used in more and more drivers, the same problem of altering the
48 An additional problem with the device tree in U-Boot is that it is read-only,
52 this problem, it is a non-negligible task to implement it, an a interim
53 solution is needed to address the problem at least in the medium-term.
55 Hence, we propose a solution to this problem by offering a board-specific
|
| /openbmc/phosphor-logging/extensions/openpower-pels/ |
| H A D | user_header.hpp | 122 * @brief Returns the problem domain field.
124 * @return uint8_t - the problem domain
132 * @brief Returns the problem vector field.
134 * @return uint8_t - the problem vector
285 * @brief The problem domain field.
290 * @brief The problem vector field.
|
| /openbmc/webui-vue/.github/ISSUE_TEMPLATE/ |
| H A D | feature_request.md | 9 **Is your feature request related to a problem? Please describe.** A clear and
10 concise description of what the problem is. Ex. I'm always frustrated when [...]
|
| H A D | bug_report.md | 21 **Screenshots** If applicable, add screenshots to help explain your problem.
36 **Additional context** Add any other context about the problem here.
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-support/nis/ |
| H A D | nis.inc | 18 # a security problem (and this fix to the build problem is *much*
|
| /openbmc/phosphor-power/phosphor-power-sequencer/docs/ |
| H A D | pgood_faults.md | 14 one of the rails may fail to power on. This is often due to a hardware problem.
55 is a chassis-specific problem or a system-wide problem due to a
57 - If this is a chassis-specific problem, add the inventory path of the chassis
|
| H A D | power_loss.md | 30 specify the problem was the input voltage rather than the power supply hardware.
69 - `phosphor-chassis-state-manager` will determine if a power problem has
73 - If a power problem has occurred, `phosphor-chassis-state-manager` will do
|
| /openbmc/openbmc/.github/ISSUE_TEMPLATE/ |
| H A D | bug_report.md | 30 If applicable, add screenshots to help explain your problem.
38 Add any other context about the problem here.
|
| /openbmc/qemu/target/ppc/ |
| H A D | power8-pmu-regs.c.inc | 17 * PMCs) has problem state read access.
34 * PMCs) has problem state write access.
60 * MMCR2 problem state write functions.
149 * problem state programs read/write access to MMCR2,
151 * not changed when mtspr is executed in problem state, and
152 * all other bits return 0s when mfspr is executed in problem
|
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | security-subjects.rst | 131 notifies the project. Usually, the upstream project analyzes the problem again.
132 If they deem it a real security problem in their software, they develop and
135 handling patches, backporting patches etc, or just understanding the problem
147 problem. If they deem it a real security problem in their software, they
151 understanding the problem or what caused it.
164 If an upstream project does not fix the problem in a reasonable time,
|
| /openbmc/openbmc/meta-ibm/recipes-phosphor/power/power-sequencer/swift/ |
| H A D | ucd90160.yaml | 56 gpio_value: low # What GPIO value indicates a fault/problem?
76 gpio_value: low # What GPIO value indicates a fault/problem?
96 gpio_value: low # What GPIO value indicates a fault/problem?
140 gpio_value: low # What GPIO value indicates a fault/problem?
|
| /openbmc/openpower-hw-diags/attn/pel/ |
| H A D | user_header.hpp | 27 * | 4 | Problem Domain | Problem Vector | Event Action Flags |
135 * @brief The problem domain field.
140 * @brief The problem vector field.
|