/openbmc/phosphor-fan-presence/monitor/ |
H A D | trust_group.hpp | 10 namespace trust namespace 26 * An abstract sensor trust group base class. 33 * and the trust of all sensors depends on something about those sensors. 36 * have the same trust value. 38 * Trust is calculated when checkTrust() is called after a group 123 * Determines the trust for this group based on this 135 * field 0 - the trust value 136 * field 1 - if that trust value changed since last call 143 auto trust = checkGroupTrust(); in checkTrust() local 145 setTrust(trust); in checkTrust() [all …]
|
H A D | trust_manager.hpp | 14 namespace trust namespace 20 * The sensor trust manager class. It can be asked if a tach sensor's 21 * reading can be trusted or not, based on the trust groups the sensor 24 * When it finds a group's trust status changing, it will either stop or 27 * See the trust::Group documentation for more details on sensor trust. 42 * @param[in] functions - trust group creation function vector 53 * Says if trust groups have been created and 56 * @return bool - If there are any trust groups 70 * While checking group trust, the code will also check 71 * if the trust status has just changed. If the status [all …]
|
H A D | nonzero_speed_trust.hpp | 9 namespace trust namespace 15 * A trust group where the sensors in the group are trusted as long 33 * determining trust for the group 42 * if any sensor included in the trust determination 56 } // namespace trust
|
H A D | system.hpp | 123 * @brief Parses and populates the fan monitor trust groups and list of fans 156 /* Trust manager of trust groups */ 157 std::unique_ptr<phosphor::fan::trust::Manager> _trust; 230 * @brief Retrieve the configured trust groups 234 * @return List of functions applied on trust groups 239 * @brief Set the trust manager's list of trust group functions 241 * @param[in] groupFuncs - list of trust group functions
|
H A D | json_parser.cpp | 45 // Get a constructed trust group class for a non-zero speed group 47 getNonZeroSpeed(const std::vector<trust::GroupDefinition>& group) in getNonZeroSpeed() 50 return std::make_unique<trust::NonzeroSpeed>(std::move(group)); in getNonZeroSpeed() 75 "Missing required fan monitor trust group parameters", in getTrustGrps() 78 "Missing required fan trust group parameters"); in getTrustGrps() 81 std::vector<trust::GroupDefinition> group; in getTrustGrps() 89 "Missing required fan monitor trust group member name", in getTrustGrps() 92 "Missing required fan monitor trust group member name"); in getTrustGrps() 99 group.emplace_back(trust::GroupDefinition{ in getTrustGrps() 102 // The class for fan sensor trust groups in getTrustGrps() [all …]
|
H A D | fan.hpp | 79 * @param trust - the tach trust manager 84 std::unique_ptr<trust::Manager>& trust, const FanDefinition& def, 162 * any trust groups the sensor may be included in 168 * trust groups. 290 * The tach trust manager object 292 std::unique_ptr<trust::Manager>& _trustManager;
|
H A D | json_parser.hpp | 37 // Trust group class handler function 39 const std::vector<trust::GroupDefinition>&)>; 56 * @brief Get any configured trust groups 60 * @return List of functions applied on trust groups
|
/openbmc/linux/drivers/media/radio/ |
H A D | radio-trust.c | 2 /* radio-trust.c - Trust FM Radio card driver for Linux 2.2 30 MODULE_DESCRIPTION("A driver for the Trust FM Radio card."); 47 MODULE_PARM_DESC(io, "I/O addresses of the Trust FM Radio card (0x350 or 0x358)"); 51 struct trust { struct 58 struct trust *tr = kzalloc(sizeof(*tr), GFP_KERNEL); in trust_alloc() argument 73 static void write_i2c(struct trust *tr, int n, ...) in write_i2c() 121 struct trust *tr = container_of(isa, struct trust, isa); in trust_s_mute_volume() 131 struct trust *tr = container_of(isa, struct trust, isa); in trust_s_stereo() 149 struct trust *tr = container_of(isa, struct trust, isa); in trust_s_frequency() 166 struct trust *tr = container_of(isa, struct trust, isa); in trust_s_ctrl() [all …]
|
/openbmc/linux/Documentation/admin-guide/hw-vuln/ |
H A D | core-scheduling.rst | 8 group of tasks don't trust another), or for performance usecases (some 96 mentioned in `Usage`_, tasks with the same cookie value are assumed to trust 121 The scheduler tries its best to find tasks that trust each other such that all 149 Trust model 151 Core scheduling maintains trust relationships amongst groups of tasks by 153 When a system with core scheduling boots, all tasks are considered to trust 155 trust relationships until userspace uses the above mentioned interfaces, to 161 within such groups are considered to trust each other, but do not trust those 162 outside. Tasks outside the group also don't trust tasks within. 187 siblings run tasks which trust each other, when the kernel is executing [all …]
|
/openbmc/u-boot/drivers/crypto/fsl/ |
H A D | Kconfig | 18 Secure boot and trust architecture compatible version 2 23 Secure boot and trust architecture compatible version 4 28 Secure boot and trust architecture compatible version 5 33 Secure boot and trust architecture compatible version 6
|
/openbmc/u-boot/lib/optee/ |
H A D | Kconfig | 18 hex "Amount of Trust-Zone RAM for the OPTEE image" 21 The size of pre-allocated Trust Zone DRAM to allocate for the OPTEE 25 hex "Base address of Trust-Zone RAM for the OPTEE image" 28 The base address of pre-allocated Trust Zone DRAM for
|
/openbmc/linux/Documentation/security/keys/ |
H A D | trusted-encrypted.rst | 9 of a Trust Source for greater security, while Encrypted Keys can be used on any 14 Trust Source 17 A trust source provides the source of security for Trusted Keys. This 18 section lists currently supported trust sources, along with their security 19 considerations. Whether or not a trust source is sufficiently safe depends 22 environment is, and there is no metric of trust, it is dependent on the 23 consumer of the Trusted Keys to determine if the trust source is sufficiently 26 * Root of trust for storage 31 provides crypto operation to establish root of trust for storage. 41 mode, trust is rooted to the OTPMK, a never-disclosed 256-bit key [all …]
|
/openbmc/linux/include/uapi/linux/ |
H A D | vbox_vmmdev_types.h | 145 /* Note: trust level is for windows guests only, linux always uses not-given */ 146 /* Requestor trust level: Unspecified */ 148 /* Requestor trust level: Untrusted (SID S-1-16-0) */ 150 /* Requestor trust level: Untrusted (SID S-1-16-4096) */ 152 /* Requestor trust level: Medium (SID S-1-16-8192) */ 154 /* Requestor trust level: Medium plus (SID S-1-16-8448) */ 156 /* Requestor trust level: High (SID S-1-16-12288) */ 158 /* Requestor trust level: System (SID S-1-16-16384) */ 160 /* Requestor trust level >= Protected (SID S-1-16-20480, S-1-16-28672) */ 162 /* Requestor trust level mask */
|
/openbmc/linux/Documentation/arch/x86/ |
H A D | intel_txt.rst | 13 - Provides dynamic root of trust for measurement (DRTM) 34 http://www.trust-conference.eu/downloads/Keynote-Speakers/ 67 To get trust in the initial kernel without using Intel TXT, a 68 static root of trust must be used. This bases trust in BIOS 81 By using the hardware-based root of trust that Intel TXT provides, 83 pre-launch components can be removed from the trust chain, DMA 91 almost all parts of the trust chain is available (excepting SMM and 101 processor instruction that initiates the dynamic root of trust.
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/sedutil/ |
H A D | sedutil_git.bb | 3 SUMMARY = "The Drive Trust Alliance Self Encrypting Drive Utility" 4 HOMEPAGE = "https://github.com/Drive-Trust-Alliance/sedutil" 12 SRC_URI = "git://github.com/Drive-Trust-Alliance/sedutil.git;branch=master;protocol=https \
|
/openbmc/phosphor-fan-presence/docs/monitor/ |
H A D | class.md | 5 A trust group determination class that implements a way to check a group of fan 6 sensors trust state. Each of these 'classes' override a required function that 8 the trust group against an algorithm that returns whether they can be trusted or
|
H A D | group.md | 5 A list of sensor object names to include in determining trust of their values 16 - By default, the sensor is included in determining trust of the group. 18 but not have it included in the determination of trust.
|
/openbmc/linux/crypto/asymmetric_keys/ |
H A D | pkcs7_trust.c | 2 /* Validate the trust chain of a PKCS#7 message. 20 * Check the trust on one PKCS#7 SignedInfo block. 54 * is apparently the same as one we already trust. in pkcs7_validate_trust_one() 135 * pkcs7_validate_trust - Validate PKCS#7 trust chain 140 * keys we already know and trust. 147 * (*) 0 if at least one signature chain intersects with the keys in the trust
|
/openbmc/phosphor-fan-presence/monitor/example/ |
H A D | monitor.yaml | 54 # * NonzeroSpeed - Only trust if at least one sensor in the group 59 # [Include in trust determination or not. Default = true] 67 # Sensor trust groups are used to specify that the speed values for the 70 # sensors in the group go in and out of trust based on those defined 71 # to be part of determining the trust. This section is optional.
|
/openbmc/docs/designs/management-console/ |
H A D | Authorities_List_Management.md | 10 verify different clients. For example, In Google, a trust bundle file ( which is 20 certs; however, Google's trust bundle file contains multiple PEM encoded 89 We can also create a trust bundle interface (instead of using multiple 91 existing codes. However, trust bundle isn't in BMCWeb, neither in Redfish
|
/openbmc/linux/drivers/net/ethernet/microchip/sparx5/ |
H A D | sparx5_dcb.c | 111 /* Requested trust configuration is not supported */ in sparx5_dcb_apptrust_validate() 318 const struct sparx5_dcb_apptrust *trust; in sparx5_dcb_getapptrust() local 320 trust = sparx5_port_apptrust[port->portno]; in sparx5_dcb_getapptrust() 322 memcpy(selectors, trust->selectors, trust->nselectors); in sparx5_dcb_getapptrust() 323 *nselectors = trust->nselectors; in sparx5_dcb_getapptrust() 394 /* Initialize [dscp, pcp] default trust */ in sparx5_dcb_init()
|
/openbmc/bmcweb/static/google/v1/schema/ |
H A D | RootOfTrust_v1.xml | 62 … <Annotation Term="OData.Description" String="The bytes to forward to the root of trust device."/> 63 …ng="This parameter shall contain the bytes to be forwarded to the root of trust device. The string… 65 … <Annotation Term="OData.Description" String="The bytes returned by the root of trust device."/> 66 …String="This return value shall contain the bytes returned by the root of trust device. The string…
|
/openbmc/u-boot/arch/arm/cpu/armv8/fsl-layerscape/doc/ |
H A D | README.soc | 48 - QorIQ platform's trust architecture 2.1 78 - QorIQ platform's trust architecture 3.0 122 - QorIQ platform's trust architecture 3.0 166 - QorIQ platform's trust architecture 2.1 207 - QorIQ platform's trust architecture 2.1 249 - QorIQ platform's trust architecture 3.0 316 QorIQ platform Trust Architecture 3.0
|
/openbmc/linux/Documentation/admin-guide/media/ |
H A D | gspca-cardlist.rst | 234 nw80x 06a5:d800 Divio Chicony TwinkleCam, Trust SpaceCam 238 sunplus 06d6:0031 Trust 610 LCD PowerC@m Zoom 265 mr97310a 08ca:0110 Trust Spyc@m 100 296 pac7311 093a:2608 Trust WB-3300p 297 pac7311 093a:260e Gigaware VGA PC Camera, Trust WB-3350p, SIGMA cam 2350 410 ov519 0e96:c001 TRUST 380 USB2 SPACEC@M 419 pac207 145f:013a Trust WB-1300N 420 pac7302 145f:013c Trust 421 sn9c20x 145f:013d Trust WB-3600R 437 sq930x 2770:930c Trust WB-3500T / NSG Robbie 2.0
|
/openbmc/linux/Documentation/process/ |
H A D | maintainer-pgp-guide.rst | 47 that trust must always be placed with developers and never with the code 52 want to make sure that by placing trust into developers we do not simply 160 - sign other people's keys for web of trust purposes 485 trust: ultimate validity: ultimate 848 delegated trust technologies, namely DNSSEC and TLS, to get you going if 849 the prospect of starting your own Web of Trust from scratch is too 877 Web of Trust (WOT) vs. Trust on First Use (TOFU) 880 PGP incorporates a trust delegation mechanism known as the "Web of 881 Trust." At its core, this is an attempt to replace the need for 886 Unfortunately, very few people understand how the Web of Trust works. [all …]
|