| /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 | 29 Bmcweb supports multiple authentication protocols:
31 - Basic authentication per RFC7617
32 - Cookie based authentication for authenticating against webui-vue
33 - Mutual TLS authentication based on OpenSSL
34 - Session authentication through webui-vue
35 - XToken based authentication conformant to Redfish DSP0266
37 Each of these types of authentication is able to be enabled or disabled both via
39 options. All authentication mechanisms supporting username/password are routed
40 to libpam, to allow for customization in authentication implementations.
|
| /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/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-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:
21 [Documentation] Trigger in-band BMC authentication reset and verify.
|
| /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/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/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/u-boot/board/xilinx/zynq/ |
| H A D | Kconfig | 29 either authentication or encryption or both encryption
30 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,
32 + KickstartAuthError - An exception for errors relating to authentication
44 + """An exception for errors relating to authentication failed while
|
| /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-openembedded/meta-gnome/recipes-extended/polkit-gnome/ |
| H A D | polkit-gnome_0.105.bb | 19 file://polkit-gnome-authentication-agent-1.desktop \
27 install -m644 ${UNPACKDIR}/polkit-gnome-authentication-agent-1.desktop \
|
| /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/openbmc-test-automation/lib/ |
| H A D | dmtf_redfishtool_utils.robot | 23 # authentication error, etc. ).
42 # authentication error, etc. ).
62 # authentication error, etc. ).
80 # authentication error, etc. ).
|
| /openbmc/qemu/docs/system/arm/ |
| H A D | emulation.rst | 57 - FEAT_EPAC (Enhanced pointer authentication)
68 - FEAT_FPACCOMBINE (Faulting on combined pointer authentication instructions)
69 - FEAT_FPACC_SPEC (Speculative behavior of combined pointer authentication instructions)
103 - FEAT_PACIMP (Pointer authentication - IMPLEMENTATION DEFINED algorithm)
104 - FEAT_PACQARMA3 (Pointer authentication - QARMA3 algorithm)
105 - FEAT_PACQARMA5 (Pointer authentication - QARMA5 algorithm)
109 - FEAT_PAuth (Pointer authentication)
110 - FEAT_PAuth2 (Enhancements to pointer authentication)
|
| /openbmc/qemu/qapi/ |
| H A D | ui.json | 233 # @auth: authentication method
305 # @auth: the current authentication type used by the server
307 # - 'none' if no authentication is being used
308 # - 'spice' uses SASL or direct TLS authentication, depending on
399 # Emitted after initial handshake and authentication takes place (if
498 # @auth: authentication method used for the plain (non-websocket) VNC
513 # @x509_dname: If x509 authentication is in use, the Distinguished
516 # @sasl_username: If SASL authentication is in use, the SASL username
517 # used for authentication.
546 # @auth: the current authentication type used by the server
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/vlock/vlock-2.2.3/ |
| H A D | vlock-no_tally.patch | 37 --enable-shadow enable shadow authentication [disabled]
66 +# display a summary of failed authentication attempts after successfully
105 … fprintf(stderr, "%d failed authentication %s.\n", auth_tries, auth_tries > 1 ? "tries" : "try");
|
| /openbmc/openbmc/poky/meta/recipes-connectivity/ppp/ppp/ |
| H A D | 0001-pppd-pppdconf.h-remove-erroneous-generated-header.patch | 86 -/* Have EAP-SRP authentication support */
89 -/* Have EAP-TLS authentication support */
92 -/* Have PEAP authentication support */
|
| /openbmc/phosphor-user-manager/ |
| H A D | mfa_pam | 3 # Google Authenticator for two-factor authentication.
|
| /openbmc/docs/security/ |
| H A D | TLS-configuration.md | 1 # How to configure the server TLS certificates for authentication
9 …entication](https://github.com/openbmc/docs/blob/master/designs/redfish-tls-user-authentication.md)
16 authentication.
36 [Enable TLS authentication](#enable-tls-authentication) or go to
398 ## Enable TLS authentication
400 To check current state of the TLS authentication method use this command:
408 To enable TLS authentication use this command:
414 To disable TLS authentication use this command:
420 Other authentication methods like basic authentication can be enabled or
421 disabled as well using the same mechanism. All supported authentication methods
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-networking/cyrus-sasl/cyrus-sasl/ |
| H A D | saslauthd.service | 2 Description=SASL authentication daemon.
|
| /openbmc/openbmc/poky/meta/recipes-connectivity/inetutils/inetutils/ |
| H A D | telnet.xinetd.inetutils | 3 # unencrypted username/password pairs for authentication.
|