Searched refs:authenticate (Results 1 – 11 of 11) sorted by relevance
/linux-6.12.1/drivers/staging/greybus/ |
D | authentication.c | 211 struct cap_ioc_authenticate *authenticate; in cap_ioctl() local 242 size = sizeof(*authenticate); in cap_ioctl() 243 authenticate = memdup_user(buf, size); in cap_ioctl() 244 if (IS_ERR(authenticate)) in cap_ioctl() 245 return PTR_ERR(authenticate); in cap_ioctl() 247 ret = cap_authenticate(cap, authenticate->auth_type, in cap_ioctl() 248 authenticate->uid, in cap_ioctl() 249 authenticate->challenge, in cap_ioctl() 250 &authenticate->result_code, in cap_ioctl() 251 authenticate->response, in cap_ioctl() [all …]
|
/linux-6.12.1/drivers/staging/greybus/Documentation/firmware/ |
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()
|
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
|
/linux-6.12.1/Documentation/networking/ |
D | mac80211-auth-assoc-deauth.txt | 14 userspace->mac80211: authenticate 50 note over mac80211,driver: cleanup like for authenticate
|
/linux-6.12.1/Documentation/arch/arm64/ |
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
|
/linux-6.12.1/drivers/block/drbd/ |
D | Kconfig | 16 NOTE: In order to authenticate connections you have to select
|
/linux-6.12.1/Documentation/ABI/testing/ |
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
|
D | sysfs-driver-intel_sdsi | 57 the On Demand NVRAM for the CPU. The AKC is used to authenticate
|
/linux-6.12.1/Documentation/filesystems/ |
D | fsverity.rst | 72 files can be trusted to authenticate them. Consider e.g. an 73 application that wants to authenticate data files before using them, 77 authenticate applications before loading them. In these cases, this 78 trusted userspace code can authenticate a file's contents by 755 authenticate them, or add them to a measurement list.
|
D | ubifs-authentication.rst | 378 no need to authenticate individual nodes of the tree. It suffices to 390 available on creation of the filesystem (`mkfs.ubifs`) to authenticate the
|
/linux-6.12.1/Documentation/gpu/ |
D | drm-uapi.rst | 139 authenticate to a DRM-Master prior to getting GPU access. To avoid this
|