/openbmc/qemu/include/crypto/ |
H A D | tlscreds.h | 42 * types of TLS handshake credentials. Most commonly the 44 * certificate credentials. 54 * @creds: pointer to a TLS credentials object 55 * @endpoint: type of network endpoint that will be using the credentials 58 * Check whether the credentials is setup according to 61 * Returns true if the credentials is setup for the endpoint, false otherwise
|
H A D | tlssession.h | 116 * @creds: pointer to a TLS credentials object 118 * @aclname: optional ACL to validate peer credentials against 130 * the server's credentials (aka x509 certificate). 134 * the peer's credentials. For x509 credentials, the ACL 187 * Validate the peer's credentials after a successful 192 * Returns 0 if the credentials validated, -1 on error 365 * credentials, this will return the CommonName from
|
/openbmc/openbmc-tools/reboot-ping-pong/ |
H A D | rpp | 10 Credentials = namedtuple("Credentials", "username, password") variable 11 Target = namedtuple("Target", "credentials, endpoint") 88 self.entity.console.credentials.username.encode() 92 self.entity.console.credentials.password.encode() 136 self.entity.console.credentials.username, 143 self.entity.console.credentials.password.encode() 181 bmccreds = Credentials("root", "0penBmc") 189 Credentials("user", "password"), Endpoint("host.somewhere.com", 22)
|
/openbmc/qemu/include/io/ |
H A D | channel-tls.h | 69 * @creds: the credentials to use for TLS handshake 75 * credentials provided in @creds. If the @aclname parameter 77 * credentials (ie a x509 client certificate) which will 99 * @creds: the credentials to use for TLS handshake 105 * credentials provided in @creds. The @hostname parameter 107 * and will be validated against the server's credentials
|
/openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/python3-requests-toolbelt/ |
H A D | 720240501dca0b4eacc3295665d7ced8719e11d2.patch | 53 - "Access-Control-Allow-Credentials": "true", 61 + "Access-Control-Allow-Credentials": [ 123 - "Access-Control-Allow-Credentials": "true", 131 + "Access-Control-Allow-Credentials": [ 193 - "Access-Control-Allow-Credentials": "true", 201 + "Access-Control-Allow-Credentials": [ 263 - "Access-Control-Allow-Credentials": "true", 271 + "Access-Control-Allow-Credentials": [ 333 - "Access-Control-Allow-Credentials": "true", 341 + "Access-Control-Allow-Credentials": [ [all …]
|
/openbmc/qemu/docs/system/ |
H A D | tls.rst | 245 QEMU has a standard mechanism for loading x509 credentials that will be 248 for the system emulators. Each set of credentials loaded should be given 250 credentials can be used for multiple network backends, so VNC, 251 migration, NBD, character devices can all share the same credentials. 252 Note, however, that credentials for use in a client endpoint must be 263 dynamically generate DH parameters when loading the credentials. 265 The ``endpoint`` parameter indicates whether the credentials will be 279 To load server credentials with client certificate validation enabled 285 while to load client credentials use 292 parameter which expects the ID of the TLS credentials object. For
|
/openbmc/openbmc-test-automation/security/ |
H A D | test_bmc_connections.robot | 147 # Every 100th iteration Login with correct credentials 175 Run Keyword And Ignore Error Login to GUI With Incorrect Credentials 221 Test BMCweb Stability On Continuous Redfish Login Attempts With Invalid Credentials 222 [Documentation] Make invalid credentials Redfish login attempts continuously and 223 ... verify bmcweb stability by login to Redfish with valid credentials. 226 Invalid Credentials Redfish Login Attempts 340 Login to GUI With Incorrect Credentials 348 Invalid Credentials Redfish Login Attempts 349 [Documentation] Continuous invalid credentials login attempts to Redfish and 350 ... login to Redfish with valid credentials at times and get failed login attempts. [all …]
|
/openbmc/qemu/crypto/ |
H A D | tlscredspsk.c | 101 error_setg(errp, "Cannot allocate credentials: %s", in qcrypto_tls_creds_psk_load() 114 error_setg(errp, "Cannot set PSK server credentials: %s", in qcrypto_tls_creds_psk_load() 138 error_setg(errp, "Cannot allocate credentials: %s", in qcrypto_tls_creds_psk_load() 146 error_setg(errp, "Cannot set PSK client credentials: %s", in qcrypto_tls_creds_psk_load() 186 error_setg(errp, "TLS credentials support requires GNUTLS"); in qcrypto_tls_creds_psk_load()
|
H A D | tlscredsanon.c | 54 error_setg(errp, "Cannot allocate credentials: %s", in qcrypto_tls_creds_anon_load() 70 error_setg(errp, "Cannot allocate credentials: %s", in qcrypto_tls_creds_anon_load() 107 error_setg(errp, "TLS credentials support requires GNUTLS"); in qcrypto_tls_creds_anon_load()
|
H A D | tlscreds.c | 122 "Unable to access credentials %s", in qcrypto_tls_creds_get_path() 268 error_setg(errp, "Expected TLS credentials for a %s endpoint", in qcrypto_tls_creds_check_endpoint()
|
/openbmc/openbmc-test-automation/openpower/ |
H A D | test_inband_bmc_auth_reset.robot | 26 @{credentials}= Create List ${OPENBMC_USERNAME} ${OPENBMC_PASSWORD} 27 ${data}= create dictionary data=@{credentials}
|
/openbmc/docs/designs/ |
H A D | expired-password.md | 26 1. Success, when the access credentials (such as username and password) are 28 2. Failure, when either the access credentials are invalid or the account being 31 3. PasswordChangeRequired, when the access credentials are correct and the 54 credentials, whether or not those credentials have expired and must be 103 credentials are otherwise correct and the reason for the authentication 109 The `/login` URI is enhanced. If it is used with correct credentials (userid
|
H A D | certificate-revocation-list.md | 36 Instead, Google has a dedicated daemon for credentials installation, and this 72 to reload newly installed credentials.
|
H A D | redfish-tls-user-authentication.md | 224 credentials according to processing sequence. It is recommended for user to use 225 only one set of credentials/authentication data in a single request to be sure 247 login credentials without password, so verification of user existence cannot be
|
/openbmc/openbmc-test-automation/extended/ |
H A D | test_bmc_stress_buster.robot | 62 @{credentials}= Create List ${rest_username} ${rest_password} 63 ${data}= Create Dictionary data=@{credentials}
|
/openbmc/phosphor-host-ipmid/oem/nvidia/ |
H A D | meson.build | 5 'bootstrap-credentials-oem-cmds.cpp',
|
/openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
H A D | HostInterface.v1_3_3.json | 179 …ecated": "This property has been deprecated in favor of newer methods of negotiating credentials.", 190 …ecated": "This property has been deprecated in favor of newer methods of negotiating credentials.", 230 …ecated": "This property has been deprecated in favor of newer methods of negotiating credentials.", 241 …ecated": "This property has been deprecated in favor of newer methods of negotiating credentials.", 344 …ecated": "This property has been deprecated in favor of newer methods of negotiating credentials.", 352 …ecated": "This property has been deprecated in favor of newer methods of negotiating credentials.",
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/pam/ |
H A D | pam-plugin-ccreds_11.bb | 1 SUMMARY = "PAM cached credentials module"
|
/openbmc/openbmc-test-automation/redfish/service_root/ |
H A D | test_sessions_management.robot | 26 Create Session And Verify Response Code Using Different Credentials 28 ... credentials. 40 Create Session And Verify Response Code Using Operator Credentials 42 ... credentials.
|
/openbmc/qemu/migration/ |
H A D | tls.c | 40 error_setg(errp, "No TLS credentials with id '%s'", tls_creds); in migration_tls_get_creds() 46 error_setg(errp, "Object with id '%s' is not TLS credentials", in migration_tls_get_creds()
|
/openbmc/qemu/qapi/ |
H A D | crypto.json | 14 # The type of network endpoint that will be using the credentials. 482 # @verify-peer: if true the peer credentials will be verified once the 484 # credentials. (default: true) 489 # credentials will be acting as a client or as a server 535 # credentials (default: true)
|
/openbmc/docs/ |
H A D | console.md | 13 port 2200. Use the same login credentials you would for a normal ssh session:
|
/openbmc/qemu/docs/tools/ |
H A D | qemu-nbd.rst | 43 credentials for the ``qemu-nbd`` server or client. 174 of the TLS credentials object previously created with the 175 :option:`--object` option; or provide the credentials needed for
|
/openbmc/docs/security/ |
H A D | network-security-considerations.md | 191 header, and returns no credentials. This method is deprecated by RFC 3986. 197 credentials. For example, you can create a Redfish session, and use your 198 credentials to invoke Phosphor D-Bus REST APIs. Note, however, that the X-Auth
|
/openbmc/openbmc/meta-openembedded/meta-networking/files/waf-cross-answers/ |
H A D | cross-answers-aarch64.txt | 30 Checking whether we can use Linux thread-specific credentials: OK
|