| /openbmc/openbmc/meta-security/recipes-core/packagegroup/ |
| H A D | packagegroup-core-security.bb | 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 = "\
20 packagegroup-security-utils \
[all …]
|
| /openbmc/docs/security/ |
| 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 | obmc-security-response-team-guidelines.md | 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
70 - Publish a security advisory to the affected OpenBMC repository.
[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 | obmc-github-security-advisory-template.md | 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/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/ |
| 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/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.
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
43 pull upstream components, incorporating their respective security fixes
[all …]
|
| /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/openbmc/meta-security/classes/ |
| H A D | sanity-meta-security.bbclass | 5 if 'security' not in e.data.getVar('DISTRO_FEATURES').split() and not skip_check:
6 bb.warn("You have included the meta-security layer, but \
7 'security' has not been enabled in your DISTRO_FEATURES. Some bbappend files \
8 and preferred version setting may not take effect. See the meta-security README \
9 for details on enabling security support.")
|
| /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,
15 related code. It is written to be useful for both security researchers and
18 How to report a potential security vulnerability?
26 a message to security AT yoctoproject DOT org, including as many details as
32 reporting potential security issues in the specific ``SECURITY.md`` file at the
39 Branches maintained with security fixes
49 maintained with security patches, but well-tested patches may still be accepted
55 We have set up two security-related mailing lists:
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/ssiapi/ssiapi/ |
| H A D | 0004-Do-not-override-flags-coming-from-build-environment.patch | 6 e.g. we need some optimization level turned on when security flags are enabled
24 …ty=hidden -D_GNU_SOURCE -O3 -fstack-protector -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -fPIC"
25 -CFLAGS="-std=gnu99 -fstack-protector -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -fPIC"
26 …sibility-inlines-hidden -O3 -fstack-protector -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -fPIC"
27 …ty=hidden -D_GNU_SOURCE -O3 -fstack-protector -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -fPIC"
28 +#CFLAGS="-std=gnu99 -fstack-protector -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -fPIC"
29 …sibility-inlines-hidden -O3 -fstack-protector -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -fPIC"
|
| /openbmc/openbmc/meta-security/meta-tpm/recipes-core/packagegroup/ |
| H A D | packagegroup-security-tpm-i2c.bb | 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)} \
|
| H A D | packagegroup-security-vtpm.bb | 8 PACKAGES = "packagegroup-security-vtpm"
10 SUMMARY:packagegroup-security-vtpm = "Security Software vTPM support"
11 RDEPENDS:packagegroup-security-vtpm = " \
|
| /openbmc/docs/ |
| H A D | SECURITY.md | 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/recipes-core/images/ |
| H A D | security-test-image.bb | 1 DESCRIPTION = "A small image for testing meta-security packages"
3 require security-build-image.bb
9 ${@bb.utils.contains("BBFILE_COLLECTIONS", "tpm-layer", "packagegroup-security-tpm","", d)} \
10 ${@bb.utils.contains("BBFILE_COLLECTIONS", "tpm-layer", "packagegroup-security-tpm2","", d)} \
11 …${@bb.utils.contains("BBFILE_COLLECTIONS", "parsec-layer", "packagegroup-security-parsec","", d)} \
|
| H A D | security-build-image.bb | 1 DESCRIPTION = "A small image for building meta-security packages"
9 packagegroup-core-security \
18 export IMAGE_BASENAME = "security-build-image"
22 …END = " ${@bb.utils.contains('DISTRO_FEATURES', 'apparmor', 'apparmor=1 security=apparmor', '', d)…
|
| /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/openbmc/meta-openembedded/meta-oe/recipes-extended/libpwquality/ |
| H A D | libpwquality_1.4.5.bb | 32 --with-securedir=${base_libdir}/security \
38 FILES:${PN} += "${base_libdir}/security/pam_pwquality.so"
39 FILES:${PN}-dbg += "${base_libdir}/security/.debug"
40 FILES:${PN}-staticdev += "${base_libdir}/security/pam_pwquality.a"
41 FILES:${PN}-dev += "${base_libdir}/security/pam_pwquality.la"
|
| /openbmc/openbmc/meta-security/meta-parsec/recipes-core/packagegroups/ |
| H A D | packagegroup-security-parsec.bb | 9 packagegroup-security-parsec \
12 SUMMARY:packagegroup-security-parsec = "Security Parsec"
13 RDEPENDS:packagegroup-security-parsec = "\
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/pam/ |
| H A D | pam-radius_3.0.0.bb | 25 install -d ${D}${base_libdir}/security
26 install -m 644 ${S}/pam_radius_auth.so ${D}${base_libdir}/security
29 FILES:${PN} += "${base_libdir}/security/*.so"
30 FILES:${PN}-dbg += "${base_libdir}/security/.debug"
|
| /openbmc/openbmc/meta-security/meta-parsec/recipes-core/images/ |
| H A D | security-parsec-image.bb | 10 packagegroup-security-tpm2 \
11 packagegroup-security-parsec \
16 export IMAGE_BASENAME = "security-parsec-image"
|
| /openbmc/obmc-console/ |
| H A D | .clang-tidy | 112 clang-analyzer-security.FloatLoopCounter,
113 clang-analyzer-security.insecureAPI.SecuritySyntaxChecker,
114 clang-analyzer-security.insecureAPI.UncheckedReturn,
115 clang-analyzer-security.insecureAPI.bcmp,
116 clang-analyzer-security.insecureAPI.bcopy,
117 clang-analyzer-security.insecureAPI.bzero,
118 clang-analyzer-security.insecureAPI.decodeValueOfObjCType,
119 clang-analyzer-security.insecureAPI.getpw,
120 clang-analyzer-security.insecureAPI.gets,
121 clang-analyzer-security.insecureAPI.mkstemp,
[all …]
|
| /openbmc/libpldm/ |
| H A D | .clang-tidy | 112 clang-analyzer-security.FloatLoopCounter,
113 clang-analyzer-security.insecureAPI.SecuritySyntaxChecker,
114 clang-analyzer-security.insecureAPI.UncheckedReturn,
115 clang-analyzer-security.insecureAPI.bcmp,
116 clang-analyzer-security.insecureAPI.bcopy,
117 clang-analyzer-security.insecureAPI.bzero,
118 clang-analyzer-security.insecureAPI.decodeValueOfObjCType,
119 clang-analyzer-security.insecureAPI.getpw,
120 clang-analyzer-security.insecureAPI.gets,
121 clang-analyzer-security.insecureAPI.mkstemp,
[all …]
|
| /openbmc/libcper/ |
| H A D | .clang-tidy | 105 clang-analyzer-security.FloatLoopCounter,
106 clang-analyzer-security.insecureAPI.SecuritySyntaxChecker,
107 clang-analyzer-security.insecureAPI.UncheckedReturn,
108 clang-analyzer-security.insecureAPI.bcmp,
109 clang-analyzer-security.insecureAPI.bcopy,
110 clang-analyzer-security.insecureAPI.bzero,
111 clang-analyzer-security.insecureAPI.decodeValueOfObjCType,
112 clang-analyzer-security.insecureAPI.getpw,
113 clang-analyzer-security.insecureAPI.gets,
114 clang-analyzer-security.insecureAPI.mkstemp,
[all …]
|