| /openbmc/openbmc/meta-ibm/recipes-extended/pam/libpam/pam.d/ |
| H A D | common-auth | 2 # /etc/pam.d/common-auth - authentication settings common to all services
5 # and should contain a list of the authentication modules that define
6 # the central authentication scheme for use on the system
8 # traditional Unix authentication mechanisms.
18 # Control gets here when no authentication module succeeds. Increment the
22 # Control gets here when authentication succeeds. Check if the user is locked
23 # out due to consecutive authentication failures and return status accordingly.
|
| /openbmc/openbmc/meta-phosphor/recipes-extended/pam/libpam/pam.d/ |
| H A D | common-auth | 2 # /etc/pam.d/common-auth - authentication settings common to all services
5 # and should contain a list of the authentication modules that define
6 # the central authentication scheme for use on the system
8 # traditional Unix authentication mechanisms.
14 # Control gets here when no authentication module succeeds. Increment the
17 # Control gets here when authentication succeeds. Check if the user is locked
18 # out due to consecutive authentication failures and return status accordingly.
|
| /openbmc/qemu/docs/system/ |
| H A D | vnc-security.rst | 16 authentication. For this setup it is recommended to restrict it to
33 The VNC protocol has limited support for password based authentication.
37 VNC server using password authentication should be restricted to only
39 authentication is not supported when operating in FIPS 140-2 compliance
40 mode as it requires the use of the DES cipher. Password authentication
59 authentication. The use of x509 certificates is strongly recommended,
62 authentication. This allows any client to connect, and provides an
101 authentication to provide two layers of authentication for clients.
114 With SASL authentication
117 The SASL authentication method is a VNC extension, that provides an
[all …]
|
| /openbmc/bmcweb/ |
| H A D | README.md | 28 Bmcweb supports multiple authentication protocols:
30 - Basic authentication per RFC7617
31 - Cookie based authentication for authenticating against webui-vue
32 - Mutual TLS authentication based on OpenSSL
33 - Session authentication through webui-vue
34 - XToken based authentication conformant to Redfish DSP0266
36 Each of these types of authentication is able to be enabled or disabled both via
38 options. All authentication mechanisms supporting username/password are routed
39 to libpam, to allow for customization in authentication implementations.
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-class-firmware-attributes | 149 What: /sys/class/firmware-attributes/*/authentication/
156 Devices support various authentication mechanisms which can be exposed
166 Change in any of these two authentication methods will also generate an
171 <attr> authentication is enabled.
175 The type of authentication used.
195 The means of authentication. This attribute is mandatory.
256 Available for HDD and NVMe authentication to set 'user' or 'master'
265 Used with HDD and NVME authentication to set the drive index
270 These attributes are used for certificate based authentication. This is
272 based authentication.
[all …]
|
| /openbmc/linux/drivers/platform/x86/hp/hp-bioscfg/ |
| H A D | spmobj-attributes.c | 42 size_t hp_calculate_security_buffer(const char *authentication) in hp_calculate_security_buffer() argument
46 if (!authentication) in hp_calculate_security_buffer()
49 authlen = strlen(authentication); in hp_calculate_security_buffer()
54 if (!strstarts(authentication, BEAM_PREFIX)) in hp_calculate_security_buffer()
69 int hp_populate_security_buffer(u16 *authbuf, const char *authentication) in hp_populate_security_buffer() argument
75 if (strstarts(authentication, BEAM_PREFIX)) { in hp_populate_security_buffer()
81 auth = hp_ascii_to_utf16_unicode(auth, authentication); in hp_populate_security_buffer()
93 authentication); in hp_populate_security_buffer()
|
| /openbmc/openbmc/poky/meta/recipes-extended/pam/libpam/pam.d/ |
| H A D | common-auth | 2 # /etc/pam.d/common-auth - authentication settings common to all services
5 # and should contain a list of the authentication modules that define
6 # the central authentication scheme for use on the system
8 # traditional Unix authentication mechanisms.
|
| /openbmc/linux/drivers/platform/x86/dell/dell-wmi-sysman/ |
| H A D | sysman.c | 76 size_t calculate_security_buffer(char *authentication) in calculate_security_buffer() argument
78 if (strlen(authentication) > 0) { in calculate_security_buffer()
79 return (sizeof(u32) * 2) + strlen(authentication) + in calculate_security_buffer()
80 strlen(authentication) % 2; in calculate_security_buffer()
92 void populate_security_buffer(char *buffer, char *authentication) in populate_security_buffer() argument
98 *sectype = strlen(authentication) > 0 ? 1 : 0; in populate_security_buffer()
99 *seclen = strlen(authentication); in populate_security_buffer()
102 if (strlen(authentication) > 0) in populate_security_buffer()
103 memcpy(auth, authentication, *seclen); in populate_security_buffer()
|
| /openbmc/openbmc/meta-arm/meta-arm-bsp/recipes-security/trusted-services/corstone1000/ |
| H A D | 0017-Implement-Private-Authenticated-Variable-verificatio.patch | 6 Refactor the implementation to only use the PK, KEK, DB authentication
7 chain for boot variables, and implement the self authentication for
64 - /* Save the timestamp into a buffer, which can be overwritten by the authentication function */
65 …imestamp and fingerprints into a buffer, which can be overwritten by the authentication function */
119 -/* Basic verification of the authentication header of the new variable.
146 + * Basic verification of the authentication header of the new variable.
147 * First finds the key variable responsible for the authentication of the new variable,
162 - /* Run Secure Boot related authentication steps */
165 + /* Run Private Authenticated Variable related authentication steps */
168 + /* Run Secure Boot related authentication steps */
[all …]
|
| H A D | 0016-Isolate-common-uefi-variable-authentication-steps.patch | 4 Subject: [PATCH 2/3] Isolate common uefi variable authentication steps
79 + * Time associated with the authentication descriptor. For the TimeStamp value,
115 + /* Run Secure Boot related authentication steps */
118 + /* Remove the authentication header from the variable if the authentication is successful */
154 * Platform Key is checked to enable or disable authentication.
168 /* If PK does not exist authentication is disabled */
192 - * Time associated with the authentication descriptor. For the TimeStamp value,
265 - /* Remove the authentication header from the variable if the authentication is successful */
|
| /openbmc/linux/Documentation/arch/arm64/ |
| H A D | pointer-authentication.rst | 2 Pointer authentication in AArch64 Linux
9 This document briefly describes the provision of pointer authentication
38 (APDAKey, APDBKey), and one for generic authentication (APGAKey).
49 Presence of address authentication functionality is advertised via
50 HWCAP_PACA, and generic authentication functionality via HWCAP_PACG.
57 with HINT space pointer authentication instructions protecting
59 with or without pointer authentication support.
72 authentication is present, the kernel will expose the position of TTBR0
91 Pointer authentication is enabled in KVM guest when each virtual cpu is
95 these userspace flags are checked before enabling pointer authentication.
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/pam/ |
| H A D | pam-radius_3.0.0.bb | 1 SUMMARY = "PAM module for RADIUS authentication"
3 authentication and accounting requests. You will need a RADIUS server to perform \
4 the actual authentication."
|
| /openbmc/openbmc/meta-arm/meta-arm-bsp/recipes-bsp/u-boot/u-boot/corstone1000/ |
| H A D | 0038-corstone1000-introduce-EFI-authenticated-capsule-upd.patch | 44 + log_err("Corstone1000: Capsule authentication flag check failed. Aborting update\n");
59 + log_err("Corstone1000: Capsule authentication check failed. Aborting update\n");
65 + log_debug("Corstone1000: Capsule authentication successful\n");
67 + log_debug("Corstone1000: Capsule authentication disabled. ");
|
| /openbmc/openbmc-test-automation/openpower/ |
| H A D | test_inband_bmc_auth_reset.robot | 2 Documentation OEM IPMI in-band BMC authentication reset.
4 # This resets the BMC authentication:
19 [Documentation] Trigger in-band BMC authentication reset and verify.
|
| /openbmc/openbmc-test-automation/docs/ |
| H A D | redfish_request_via_mTLS.md | 3 When the BMC only enables mTLS type for authentication. Redfish request in robot
14 - **VALID_CERT** indicates valid mTLS certificate for authentication. When a
56 ## Test Cases for mTLS authentication
58 mTLS authentication is only a means to connect to the BMC, not for testing
60 mTLS authentication. (Requires test certificate with different privileges or
|
| /openbmc/openbmc/poky/meta/recipes-connectivity/openssh/openssh/ |
| H A D | sshd_config | 62 # Change to yes to enable keyboard-interactive authentication (beware issues
76 # Set this to 'yes' to enable PAM authentication, account processing,
77 # and session processing. If this is enabled, PAM authentication will
80 # PAM authentication via KbdInteractiveAuthentication may bypass
83 # PAM authentication, then enable this but set PasswordAuthentication
|
| /openbmc/linux/drivers/target/iscsi/ |
| H A D | iscsi_target_tpg.c | 90 tpg->tpg_attrib.authentication = 0; in iscsit_load_discovery_tpg()
212 a->authentication = TA_AUTHENTICATION; in iscsit_set_default_tpg_attribs()
323 if (tpg->tpg_attrib.authentication) { in iscsit_tpg_enable_portal_group()
585 int iscsit_ta_authentication(struct iscsi_portal_group *tpg, u32 authentication) in iscsit_ta_authentication() argument
592 if ((authentication != 1) && (authentication != 0)) { in iscsit_ta_authentication()
594 " %u, ignoring request.\n", authentication); in iscsit_ta_authentication()
605 if (authentication) { in iscsit_ta_authentication()
638 a->authentication = authentication; in iscsit_ta_authentication()
640 a->authentication ? "Enforcing" : "Disabling", tpg->tpgt); in iscsit_ta_authentication()
|
| /openbmc/linux/Documentation/filesystems/ |
| H A D | ubifs-authentication.rst | 33 can be used to get full data authentication at the block layer.
37 authentication for UBIFS. Since UBIFS uses fscrypt for file contents and file
38 name encryption, the authentication system could be tied into fscrypt such that
40 be possible to use UBIFS authentication without using encryption.
209 This chapter introduces UBIFS authentication which enables UBIFS to verify
216 UBIFS authentication enables detection of offline data modification. While it
221 UBIFS authentication will not protect against rollback of full flash contents.
235 UBIFS authentication does not cover attacks where an attacker is able to
236 execute code on the device after the authentication key was provided.
327 it is necessary to also add authentication information frequently to the
[all …]
|
| /openbmc/u-boot/board/xilinx/zynqmp/ |
| H A D | Kconfig | 14 either authentication or encryption or both encryption
15 and authentication feature enabled while generating
|
| /openbmc/openbmc/meta-openembedded/meta-python/recipes-extended/python-pykickstart/files/ |
| H A D | 0001-support-authentication-for-kickstart.patch | 4 Subject: [PATCH] support authentication for kickstart
7 we support basic/digest authentication.
9 Add KickstartAuthError to report authentication failure,
29 + KickstartAuthError - An exception for errors relating to authentication
41 + """An exception for errors relating to authentication failed while
|
| /openbmc/qemu/docs/system/arm/ |
| H A D | emulation.rst | 56 - FEAT_EPAC (Enhanced pointer authentication)
67 - FEAT_FPACCOMBINE (Faulting on combined pointer authentication instructions)
68 - FEAT_FPACC_SPEC (Speculative behavior of combined pointer authentication instructions)
102 - FEAT_PACIMP (Pointer authentication - IMPLEMENTATION DEFINED algorithm)
103 - FEAT_PACQARMA3 (Pointer authentication - QARMA3 algorithm)
104 - FEAT_PACQARMA5 (Pointer authentication - QARMA5 algorithm)
108 - FEAT_PAuth (Pointer authentication)
109 - FEAT_PAuth2 (Enhancements to pointer authentication)
|
| /openbmc/qemu/qapi/ |
| H A D | ui.json | 230 # @auth: authentication method
302 # @auth: the current authentication type used by the server
304 # - 'none' if no authentication is being used
305 # - 'spice' uses SASL or direct TLS authentication, depending on
398 # Emitted after initial handshake and authentication takes place (if
496 # @auth: authentication method used for the plain (non-websocket) VNC
511 # @x509_dname: If x509 authentication is in use, the Distinguished
514 # @sasl_username: If SASL authentication is in use, the SASL username
515 # used for authentication.
544 # @auth: the current authentication type used by the server
[all …]
|
| /openbmc/qemu/ |
| H A D | qemu.sasl | 3 # as authentication.
6 # you like for authentication, because TLS provides the encryption
22 # 'scram-sha-256' plugin allows plain username/password authentication
|
| /openbmc/openbmc/meta-security/dynamic-layers/meta-python/recipes-security/mfa/ |
| H A D | python3-privacyidea_3.9.1.bb | 1 SUMMARY = "identity, multifactor authentication (OTP), authorization, audit"
2 …authentication like OTP tokens, SMS, smartphones or SSH keys. Using privacyIDEA you can enhance yo…
|
| /openbmc/u-boot/board/xilinx/zynq/ |
| H A D | Kconfig | 29 either authentication or encryption or both encryption
30 and authentication feature enabled while generating
|