/openbmc/linux/Documentation/filesystems/ |
H A D | adfs.rst | 53 - Owner read 54 - Owner write 64 Owner read -> -r--r--r-- 65 Owner write -> --w--w---w 66 Owner read and filetype UnixExec -> ---x--x--x
|
/openbmc/linux/Documentation/ABI/testing/ |
H A D | securityfs-secrets-coco | 10 the Guest Owner during VM's launch. The secrets are encrypted 11 by the Guest Owner and decrypted inside the trusted enclave, 49 Guest Owner is described in
|
/openbmc/openbmc/poky/meta/files/common-licenses/ |
H A D | BSD-3-Clause-Clear | 3 Copyright (c) [xxxx]-[xxxx] [Owner Organization] 17 * Neither the name of [Owner Organization] nor the names of its
|
H A D | NCSA | 3 Copyright (c) <Year> <Owner Organization Name>
|
H A D | ASWF-Digital-Assets-1.0 | 5 <Asset Name> Copyright <Year> <Asset Owner>. All rights reserved.
|
H A D | ASWF-Digital-Assets-1.1 | 5 <Asset Name> Copyright <Year> <Asset Owner>. All rights reserved.
|
/openbmc/linux/LICENSES/preferred/ |
H A D | BSD-3-Clause-Clear | 12 Copyright (c) [xxxx]-[xxxx] [Owner Organization] 26 * Neither the name of [Owner Organization] nor the names of its
|
/openbmc/openbmc/meta-hpe/meta-common/recipes-hpe/vehci/host-ehci-owner-reset/ |
H A D | host-ehci-owner-reset@.service | 2 Description=GXP EHCI Owner Reset Service
|
/openbmc/linux/security/integrity/ |
H A D | Kconfig | 66 bool "Provide a keyring to which Machine Owner Keys may be added" 72 If set, provide a keyring to which Machine Owner Keys (MOK) may 84 and all Machine Owner Keys (MOK) are added to the machine keyring.
|
/openbmc/linux/Documentation/filesystems/ext4/ |
H A D | inodes.rst | 47 - Lower 16-bits of Owner UID. 198 - S_IXUSR (Owner may execute) 200 - S_IWUSR (Owner may write) 202 - S_IRUSR (Owner may read) 391 - Upper 16-bits of the Owner UID. 426 - Upper 16-bits of the Owner UID.
|
/openbmc/openbmc/meta-hpe/meta-common/recipes-hpe/vehci/ |
H A D | host-ehci-owner-reset.bb | 1 SUMMARY = "GXP EHCI Owner Reset"
|
/openbmc/docs/ |
H A D | REST-cheatsheet.md | 232 …nt-Type: application/json" -X PUT -d '{"data": "xyz.openbmc_project.Time.Owner.Owners.BMC" }' htt… 233 …nt-Type: application/json" -X PUT -d '{"data": "xyz.openbmc_project.Time.Owner.Owners.Host" }' ht… 234 …nt-Type: application/json" -X PUT -d '{"data": "xyz.openbmc_project.Time.Owner.Owners.Split" }' h… 235 …nt-Type: application/json" -X PUT -d '{"data": "xyz.openbmc_project.Time.Owner.Owners.Both" }' ht…
|
H A D | community-membership.md | 183 ## Subproject Owner 200 The per-repository requirements for becoming an subproject Owner should be
|
H A D | rest-api.md | 150 "TimeOwner": "xyz.openbmc_project.Time.Owner.Owners.BMC"
|
/openbmc/linux/Documentation/security/secrets/ |
H A D | coco.rst | 38 Guest Owner secret data should be a GUIDed table of secret values; the binary 55 Consider a guest performing computations on encrypted files. The Guest Owner
|
/openbmc/openbmc/meta-hpe/meta-dl360poc/recipes-kernel/linux/linux-obmc/ |
H A D | gxp.dts | 609 label = "Port Owner"; 615 label = "Port Owner"; 621 label = "Port Owner";
|
/openbmc/linux/Documentation/locking/ |
H A D | rt-mutex.rst | 75 BTW, there is still technically a "Pending Owner", it's just not called
|
H A D | mutex-design.rst | 99 - Owner tracking.
|
/openbmc/qemu/docs/specs/ |
H A D | sev-guest-firmware.rst | 110 Guest Owner secret (using SEV_LAUNCH_SECRET).
|
/openbmc/linux/Documentation/gpu/ |
H A D | kms-properties.csv | 1 Owner Module/Drivers,Group,Property Name,Type,Property Values,Object attached,Description/Restricti…
|
/openbmc/openbmc/poky/meta/recipes-devtools/syslinux/syslinux/ |
H A D | 0001-ext2_fs.h-do-not-carry-an-outdated-copy.patch | 200 - uint16_t i_uid; /* Owner Uid */ 698 - __u16 i_uid; /* Low 16 bits of Owner Uid */ 746 - __u16 i_uid; /* Low 16 bits of Owner Uid */
|
/openbmc/linux/fs/affs/ |
H A D | Changes | 237 - Owner/Group defaults now to the fs user (i.e.
|
/openbmc/linux/fs/ntfs3/ |
H A D | ntfs.h | 1202 __le32 Owner; member
|
/openbmc/linux/drivers/firmware/efi/ |
H A D | Kconfig | 261 Guest Owner to securely inject secrets during guest VM launch.
|
/openbmc/qemu/docs/system/i386/ |
H A D | amd-memory-encryption.rst | 124 In order to verify the guest launch measurement, The Guest Owner must compute
|