/openbmc/linux/drivers/staging/greybus/ |
H A D | authentication.c | 208 struct cap_ioc_authenticate *authenticate; in cap_ioctl() local 239 size = sizeof(*authenticate); in cap_ioctl() 240 authenticate = memdup_user(buf, size); in cap_ioctl() 241 if (IS_ERR(authenticate)) in cap_ioctl() 242 return PTR_ERR(authenticate); in cap_ioctl() 244 ret = cap_authenticate(cap, authenticate->auth_type, in cap_ioctl() 245 authenticate->uid, in cap_ioctl() 246 authenticate->challenge, in cap_ioctl() 247 &authenticate->result_code, in cap_ioctl() 248 authenticate->response, in cap_ioctl() [all …]
|
/openbmc/linux/drivers/staging/greybus/Documentation/firmware/ |
H A D | authenticate.c | 24 struct cap_ioc_authenticate authenticate = { variable 78 memcpy(authenticate.uid, uid.uid, 8); in main() 80 ret = ioctl(fd, CAP_IOC_AUTHENTICATE, &authenticate); in main() 88 authenticate.result_code, authenticate.signature_size); in main()
|
H A D | firmware-management | 188 directory and will be named gb-authenticate-<N>. The number <N> is assigned at 195 gb-authenticate-N and user first needs to identify the character device used for 204 /sys/bus/greybus/devices/1-1/1-1.1/1-1.1.1/gb_authenticate/gb-authenticate-0 206 The last name in this path: gb-authenticate-0 is precisely the name of the char 209 /dev/gb-authenticate-0. 214 The Character device (/dev/gb-authenticate-0 in above example) can be opened by 299 This ioctl shall be used by the user to authenticate the Module attached to 331 The current directory also provides a authenticate.c test application, which can
|
/openbmc/u-boot/doc/imx/habv4/csf_examples/mx6_mx7/ |
H A D | csf_uboot.txt | 15 # Key used to authenticate the CSF data 21 # Key slot index used to authenticate the key to be installed 29 # Key slot index used to authenticate the image data
|
H A D | csf_uboot_fast_authentication.txt | 20 # Key slot index 0 used to authenticate the image data
|
/openbmc/u-boot/doc/imx/habv4/csf_examples/additional_images/ |
H A D | csf_additional_images.txt | 15 # Key used to authenticate the CSF data 21 # Key slot index used to authenticate the key to be installed 29 # Key slot index used to authenticate the image data
|
/openbmc/openbmc/meta-phosphor/recipes-phosphor/ipmi/ |
H A D | phosphor-ipmi-net_git.bb | 36 PACKAGECONFIG ??= "pam-authenticate rmcp-ping" 38 PACKAGECONFIG[pam-authenticate] = "-Dpam_authenticate=enabled,-Dpam_authenticate=disabled"
|
/openbmc/openbmc/meta-openembedded/meta-gnome/recipes-extended/polkit-gnome/polkit-gnome/ |
H A D | 0001-Select-the-current-user-to-authenticate-with-by-defa.patch | 4 Subject: Select the current user to authenticate with by default 67 + /* Disable password entry and authenticate until have a user selected */
|
/openbmc/linux/Documentation/networking/ |
H A D | mac80211-auth-assoc-deauth.txt | 14 userspace->mac80211: authenticate 50 note over mac80211,driver: cleanup like for authenticate
|
/openbmc/openbmc/meta-openembedded/meta-networking/recipes-protocols/pptp-linux/pptp-linux/ |
H A D | options.pptp | 7 # We don't need the tunnel server to authenticate itself
|
/openbmc/openbmc/meta-openembedded/meta-gnome/recipes-extended/polkit-gnome/ |
H A D | polkit-gnome_0.105.bb | 14 file://0001-Select-the-current-user-to-authenticate-with-by-defa.patch \
|
/openbmc/openbmc/poky/meta/recipes-connectivity/ppp/ppp/ |
H A D | provider | 33 # Do not ask the remote to authenticate.
|
/openbmc/u-boot/doc/imx/habv4/guides/ |
H A D | mx6_mx7_spl_secure_boot.txt | 19 final images, SPL and U-Boot proper. The HABv4 can be used to authenticate 101 to authenticate, which keys to install, use and etc.
|
H A D | mx6_mx7_secure_boot.txt | 76 to authenticate, which keys to install, use and etc. 106 (3) Start of area in RAM to authenticate. 311 The U-Boot supports this feature and can be used to authenticate the Linux
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-connectivity/mosh/ |
H A D | mosh_1.4.0.bb | 36 # mosh uses SSH to authenticate and the client uses OpenSSH-specific features
|
/openbmc/docs/architecture/ |
H A D | user-management.md | 16 3. Have applications use the PAM module to authenticate the user instead of 330 Applications must use `pam_authenticate()` API to authenticate user. Stacked PAM 410 |authenticate the user | 443 authenticate against an LDAP directory. IPMI interface cannot be used to 444 authenticate against LDAP, since IPMI needs the password in clear text at the
|
/openbmc/linux/Documentation/arch/arm64/ |
H A D | pointer-authentication.rst | 128 instructions to sign and authenticate function pointers and other pointers 130 the ABI to interoperate with legacy binaries that do not sign or authenticate
|
/openbmc/linux/drivers/block/drbd/ |
H A D | Kconfig | 16 NOTE: In order to authenticate connections you have to select
|
/openbmc/openbmc-test-automation/docs/ |
H A D | redfish_request_via_mTLS.md | 69 not need to use mTLS to authenticate login and logout. It can be replaced as
|
/openbmc/bmcweb/include/ |
H A D | authentication.hpp | 256 inline std::shared_ptr<persistent_data::UserSession> authenticate( in authenticate() function
|
/openbmc/linux/Documentation/ABI/testing/ |
H A D | sysfs-bus-thunderbolt | 219 area and authenticate the image in one action. 222 - Writing "3" will authenticate the image that is 236 Description: For supported devices, automatically authenticate the new Thunderbolt
|
H A D | sysfs-driver-intel_sdsi | 57 the On Demand NVRAM for the CPU. The AKC is used to authenticate
|
/openbmc/docs/designs/management-console/ |
H A D | VMI_Certificate_Exchange.md | 200 | pldm |pldm call to authenticate 213 sends Verify Password command to authenticate user to establish secure
|
/openbmc/openbmc/poky/meta/recipes-connectivity/ppp/ |
H A D | ppp_2.5.2.bb | 73 SUMMARY:${PN}-winbind = "Plugin for PPP to authenticate against Samba or Windows"
|
/openbmc/u-boot/doc/imx/habv4/ |
H A D | introduction_habv4.txt | 11 to authenticate and/or decrypt the program image by using cryptography 194 Starting in HAB v4.1.2 users can use a single SRK key to authenticate the both
|