| /openbmc/openbmc/meta-security/recipes-core/packagegroup/ |
| H A D | packagegroup-core-security.bb | 1 DESCRIPTION = "Security packagegroup for Poky"
9 packagegroup-core-security \
10 packagegroup-security-utils \
11 packagegroup-security-scanners \
12 packagegroup-security-audit \
13 packagegroup-security-ids \
14 packagegroup-security-mac \
15 packagegroup-security-compliance \
16 …${@bb.utils.contains("DISTRO_FEATURES", "ptest", "packagegroup-meta-security-ptest-packages", "", …
19 RDEPENDS:packagegroup-core-security = "\
[all …]
|
| /openbmc/linux/Documentation/security/ |
| D | lsm.rst | |
| /openbmc/docs/security/ |
| H A D | obmc-security-response-team-guidelines.md | 1 # Security response team guidelines
3 These are the guidelines for OpenBMC security responders, including the security
5 problems reported by the [security vulnerability reporting process][].
7 Each project within OpenBMC works independently to resolve security
8 vulnerabilities. The security response team helps the maintainers, provides
22 - Communicate by opening the GitHub draft security advistory as soon as the
34 - [Create the draft security advisory][] and populate its fields.
42 - Use private channels, for example, email, GitHub draft security advistory,
44 - Inform contacts this is private work as part of the OpenBMC security
52 - Submit the problem to another security response team, for example, the
[all …]
|
| H A D | obmc-security-response-team.md | 1 # The OpenBMC security vulnerability reporting process
3 This describes the OpenBMC security vulnerability reporting process which is
4 intended to give the project time to address security problems before public
9 - a procedure to privately report security vulnerabilities
10 - a security response team to address reported vulnerabilities
11 - the openbmc-security email address for the response team
12 - guidelines for security response team members
16 1. A community member reports a problem privately to the security response team
18 2. The responders (including the security response team, the repository
20 3. The repository maintainer creates an OpenBMC security advisory which explains
[all …]
|
| H A D | how-to-report-a-security-vulnerability.md | 1 # How to report a security vulnerability
3 This describes how you can report an OpenBMC security vulnerability privately to
8 - You have information about a security problem or vulnerability which is not
14 To begin the process: Privately contact the OpenBMC security response team and
17 - Suggest sending an email. Use `openbmc-security at lists.ozlabs.org`.
20 not, the security response team will help route the problem.
21 - Include details about the security problem such as:
29 the security response team can help you route the problem.
31 When the project owners get a new security problem, they will create a [GitHub
32 security advisory][] in their repository and begin work. The advisory has draft
[all …]
|
| H A D | network-security-considerations.md | 1 # Network Security Considerations
7 This is only intended to be a guide; security is ultimately the responsibility
9 a security vulnerability, please consider [how to report a security
12 [how to report a security vulnerability]:
13 https://github.com/openbmc/docs/blob/master/security/how-to-report-a-security-vulnerability.md
32 - The BMC is presumed to have a network adapter. The security considerations of
33 the NIC are important to the BMC security, but are outside the scope of this
48 driver have security considerations which are important to BMC security, but are
83 Transport layer security (TLS) protocols are configured for each service at
125 Laws may require products built on OpenBMC to have reasonable security built
[all …]
|
| H A D | obmc-github-security-advisory-template.md | 1 # OpenBMC Security Advisory Template
4 new draft GitHub security advisories as part of the [Security response team
8 security advisory "Description" field
10 [security response team guidelines]: ./obmc-security-response-team-guidelines.md
29 Please coordinate with the security response team
72 - Email openbmc-security at lists.ozlabs.org
|
| /openbmc/linux/drivers/memory/tegra/ |
| D | tegra194.c | |
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | security-subjects.rst | 8 and need to handle security issues and practices both internal (in the code
12 This manual assembles security-related information concerning the whole
13 ecosystem. It includes information on reporting a potential security issue,
14 the operation of the YP Security team and how to contribute in the
15 related code. It is written to be useful for both security researchers and
18 How to report a potential security vulnerability?
23 :yocto_bugs:`Security Bugzilla </enter_bug.cgi?product=Security>`.
26 a message to security AT yoctoproject DOT org, including as many details as
29 Yocto Project Security team.
32 reporting potential security issues in the specific ``SECURITY.md`` file at the
[all …]
|
| H A D | securing-images.rst | 6 Security is of increasing concern for embedded devices. Consider the
10 - *"*\ `Security Risks of Embedded
18 - *"*\ `Security Issues for Embedded
19 Devices <https://elinux.org/images/6/6f/Security-issues.pdf>`__\ *"*
23 variables that you can consider to help you reach the security goals you
31 Because the security requirements and risks are different for every
35 hardening and on security.
46 other potential security problems.
48 - Pay particular attention to the security for any web-based
53 resulting from the interface's security becoming compromised can be
[all …]
|
| /openbmc/openbmc/meta-arm/ |
| H A D | SECURITY.md | 3 Arm takes security issues seriously and welcomes feedback from researchers and
4 the security community in order to improve the security of its products and
6 vulnerabilities and other security issues.
8 Security issues can be complex and one single timescale doesn't fit all
10 security notifications and fixes to be available and facilitate coordinated
18 meta-arm@lists.yoctoproject.org and arm-security@arm.com.
21 to the maintainers \(see [README.md](/README.md)\) and arm-security@arm.com, including as much
24 …rmation, please visit https://developer.arm.com/support/arm-security-updates/report-security-vulne…
27 ## Branches maintained with security fixes
36 security patches, but well-tested patches may still be accepted for them for
[all …]
|
| /openbmc/openbmc/meta-security/ |
| H A D | .gitlab-ci.yml | 54 - kas shell kas/$CI_JOB_NAME.yml -c "bitbake -k security-build-image integrity-image-minimal"
61 - kas build --target security-build-image kas/$CI_JOB_NAME.yml
67 - kas build --target security-parsec-image kas/$CI_JOB_NAME.yml
74 - kas build --target security-test-image kas/$CI_JOB_NAME.yml
75 - kas build -c testimage --target security-test-image kas/$CI_JOB_NAME.yml
80 …$CI_JOB_NAME.yml -c "bitbake -k core-image-minimal security-build-image security-tpm-image securi…
82 - kas build --target security-build-image kas/$CI_JOB_NAME-alt.yml
88 - kas build --target security-parsec-image kas/$CI_JOB_NAME.yml
93 - kas build --target security-build-image kas/$CI_JOB_NAME.yml
99 - kas build --target security-parsec-image kas/$CI_JOB_NAME.yml
[all …]
|
| H A D | README.md | 2 …s](https://gitlab.com/akuster/meta-security/badges/master-next/pipeline.svg)](https://gitlab.com/a…
4 …tus](https://gitlab.com/akuster/meta-security/badges/master/pipeline.svg)](https://gitlab.com/akus…
6 Meta-security
10 to have 'security' in DISTRO_FEATURES to have effect.
13 DISTRO_FEATURES:append = " security"
15 If meta-security is included, but security is not enabled as a
18 You have included the meta-security layer, but
19 'security' has not been enabled in your DISTRO_FEATURES. Some bbappend files
27 This layer provides security tools, hardening tools for Linux kernels
28 and libraries for implementing security mechanisms.
[all …]
|
| /openbmc/linux/Documentation/driver-api/nvdimm/ |
| D | security.rst | |
| /openbmc/linux/Documentation/netlabel/ |
| D | lsm_interface.rst | |
| D | introduction.rst | |
| /openbmc/openbmc/meta-security/dynamic-layers/meta-perl/recipes-core/packagegroup/ |
| H A D | packagegroup-core-security.bbappend | 4 packagegroup-security-hardening \
6 RDEPENDS:packagegroup-core-security += "\
7 packagegroup-security-hardening \
10 SUMMARY:packagegroup-security-hardening = "Security Hardening tools"
11 RDEPENDS:packagegroup-security-hardening = " \
15 RDEPENDS:packagegroup-security-scanners += "\
|
| /openbmc/openbmc/meta-security/recipes-scanners/buck-security/ |
| H A D | buck-security_0.7.bb | 1 SUMMARY = "Linux security scanner"
2 DESCRIPTION = "Buck-Security is a security scanner for Debian and Ubuntu Linux. It runs a couple of…
3 system. This enables you to quickly overview the security status of your Linux system."
4 SECTION = "security"
8 SRC_URI = "http://sourceforge.net/projects/buck-security/files/buck-security/buck-security_${PV}/${…
21 cp -r ${S}/buck-security ${D}${bindir}
22 …:Spec->catfile(dirname(File::Spec->rel2abs(__FILE__)), "buck/checks")!' ${D}${bindir}/buck-security
23 …c->catfile(dirname(File::Spec->rel2abs(__FILE__)), "buck/checks/lib")!' ${D}${bindir}/buck-security
24 …le::Spec->catfile(dirname(File::Spec->rel2abs(__FILE__)), "buck/lib")!' ${D}${bindir}/buck-security
25 …= File::Spec->catfile(dirname(File::Spec->rel2abs(__FILE__)), "buck")!' ${D}${bindir}/buck-security
|
| /openbmc/docs/ |
| H A D | SECURITY.md | 1 # Security Policy
3 ## How to report a security vulnerability
5 This describes how you can report an OpenBMC security vulnerability privately to
10 - You have information about a security problem which is not yet publicly
18 - Send an email to `openbmc-security at lists.ozlabs.org` with details about the
19 security problem such as:
26 The OpenBMC security response team (SRT) will respond to you and work to address
30 Anyone brought onboard should be given a link to the OpenBMC [security
38 - Create an OpenBMC security advisory.
55 [security response team guidelines]: ./obmc-security-response-team-guidelines.md
|
| /openbmc/openbmc/meta-security/meta-tpm/recipes-core/packagegroup/ |
| H A D | packagegroup-security-tpm-i2c.bb | 1 DESCRIPTION = "Security packagegroup for TPM i2c support"
8 PACKAGES = "packagegroup-security-tpm-i2c"
10 SUMMARY:packagegroup-security-tpm-i2c = "Security TPM i2c support"
11 RDEPENDS:packagegroup-security-tpm-i2c = " \
12 ${@bb.utils.contains('MACHINE_FEATURES', 'tpm', 'packagegroup-security-tpm', '', d)} \
13 ${@bb.utils.contains('MACHINE_FEATURES', 'tpm2', 'packagegroup-security-tpm2', '', d)} \
|
| /openbmc/linux/fs/cachefiles/ |
| D | security.c | |
| /openbmc/linux/fs/ceph/ |
| D | Kconfig | |
| /openbmc/qemu/docs/system/ |
| H A D | security.rst | 1 Security title
7 This chapter explains the security requirements that QEMU is designed to meet
10 Security Requirements
13 QEMU supports many different use cases, some of which have stricter security
14 requirements than others. The community has agreed on the overall security
16 considered supported from a security perspective.
36 real-world use cases and treated as security bugs if this is the case.
43 the non-virtualization use case should meet the same security requirements as
45 non-virtualization use case code was not written with these security
48 Bugs affecting the non-virtualization use case are not considered security
[all …]
|
| /openbmc/pldm/ |
| H A D | .clang-tidy | 114 clang-analyzer-security.FloatLoopCounter,
115 clang-analyzer-security.insecureAPI.DeprecatedOrUnsafeBufferHandling,
116 clang-analyzer-security.insecureAPI.SecuritySyntaxChecker,
117 clang-analyzer-security.insecureAPI.UncheckedReturn,
118 clang-analyzer-security.insecureAPI.bcmp,
119 clang-analyzer-security.insecureAPI.bcopy,
120 clang-analyzer-security.insecureAPI.bzero,
121 clang-analyzer-security.insecureAPI.decodeValueOfObjCType,
122 clang-analyzer-security.insecureAPI.getpw,
123 clang-analyzer-security.insecureAPI.gets,
[all …]
|
| /openbmc/linux/include/uapi/linux/ |
| D | rxrpc.h | |