]> git.proxmox.com Git - mirror_edk2.git/blame - MdePkg/Include/Protocol/Security.h
clean up the un-suitable ';' location when declaring the functions.
[mirror_edk2.git] / MdePkg / Include / Protocol / Security.h
CommitLineData
d1f95000 1/** @file\r
4ca9b6c4 2 Security Architectural Protocol as defined in PI Specification VOLUME 2 DXE\r
d1f95000 3\r
4 Used to provide Security services. Specifically, dependening upon the \r
5 authentication state of a discovered driver in a Firmware Volume, the \r
6 portable DXE Core Dispatcher will call into the Security Architectural \r
7 Protocol (SAP) with the authentication state of the driver.\r
8\r
9 This call-out allows for OEM-specific policy decisions to be made, such\r
10 as event logging for attested boots, locking flash in response to discovering\r
11 an unsigned driver or failed signature check, or other exception response.\r
12\r
13 The SAP can also change system behavior by having the DXE core put a driver\r
14 in the Schedule-On-Request (SOR) state. This will allow for later disposition \r
15 of the driver by platform agent, such as Platform BDS.\r
16\r
4ca9b6c4 17 Copyright (c) 2006 - 2008, Intel Corporation \r
d1f95000 18 All rights reserved. This program and the accompanying materials \r
19 are licensed and made available under the terms and conditions of the BSD License \r
20 which accompanies this distribution. The full text of the license may be found at \r
21 http://opensource.org/licenses/bsd-license.php \r
22\r
23 THE PROGRAM IS DISTRIBUTED UNDER THE BSD LICENSE ON AN "AS IS" BASIS, \r
24 WITHOUT WARRANTIES OR REPRESENTATIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED. \r
25\r
d1f95000 26**/\r
27\r
28#ifndef __ARCH_PROTOCOL_SECURITY_H__\r
29#define __ARCH_PROTOCOL_SECURITY_H__\r
30\r
3f748e52 31#include <PiDxe.h>\r
32\r
99e8ed21 33///\r
34/// Global ID for the Security Code Architectural Protocol\r
35///\r
d1f95000 36#define EFI_SECURITY_ARCH_PROTOCOL_GUID \\r
37 { 0xA46423E3, 0x4617, 0x49f1, {0xB9, 0xFF, 0xD1, 0xBF, 0xA9, 0x11, 0x58, 0x39 } }\r
38\r
39typedef struct _EFI_SECURITY_ARCH_PROTOCOL EFI_SECURITY_ARCH_PROTOCOL;\r
40\r
41/**\r
42 The EFI_SECURITY_ARCH_PROTOCOL (SAP) is used to abstract platform-specific \r
43 policy from the DXE core response to an attempt to use a file that returns a \r
44 given status for the authentication check from the section extraction protocol. \r
45\r
46 The possible responses in a given SAP implementation may include locking \r
47 flash upon failure to authenticate, attestation logging for all signed drivers, \r
48 and other exception operations. The File parameter allows for possible logging \r
49 within the SAP of the driver.\r
50\r
51 If File is NULL, then EFI_INVALID_PARAMETER is returned.\r
52\r
53 If the file specified by File with an authentication status specified by \r
54 AuthenticationStatus is safe for the DXE Core to use, then EFI_SUCCESS is returned.\r
55\r
56 If the file specified by File with an authentication status specified by \r
57 AuthenticationStatus is not safe for the DXE Core to use under any circumstances, \r
58 then EFI_ACCESS_DENIED is returned.\r
59\r
60 If the file specified by File with an authentication status specified by \r
61 AuthenticationStatus is not safe for the DXE Core to use right now, but it \r
62 might be possible to use it at a future time, then EFI_SECURITY_VIOLATION is \r
63 returned.\r
64\r
65 @param This The EFI_SECURITY_ARCH_PROTOCOL instance.\r
66 @param AuthenticationStatus \r
67 This is the authentication type returned from the Section\r
68 Extraction protocol. See the Section Extraction Protocol\r
69 Specification for details on this type.\r
70 @param File This is a pointer to the device path of the file that is\r
71 being dispatched. This will optionally be used for logging.\r
72\r
73 @retval EFI_SUCCESS The file specified by File did authenticate, and the\r
74 platform policy dictates that the DXE Core may use File.\r
75 @retval EFI_INVALID_PARAMETER Driver is NULL.\r
76 @retval EFI_SECURITY_VIOLATION The file specified by File did not authenticate, and\r
77 the platform policy dictates that File should be placed\r
78 in the untrusted state. A file may be promoted from\r
79 the untrusted to the trusted state at a future time\r
80 with a call to the Trust() DXE Service.\r
81 @retval EFI_ACCESS_DENIED The file specified by File did not authenticate, and\r
82 the platform policy dictates that File should not be\r
83 used for any purpose.\r
84\r
85**/\r
86typedef \r
87EFI_STATUS\r
8b13229b 88(EFIAPI *EFI_SECURITY_FILE_AUTHENTICATION_STATE)(\r
d1f95000 89 IN EFI_SECURITY_ARCH_PROTOCOL *This,\r
90 IN UINT32 AuthenticationStatus,\r
91 IN EFI_DEVICE_PATH_PROTOCOL *File\r
ed66e1bc 92 );\r
d1f95000 93\r
94//\r
95// Interface stucture for the Timer Architectural Protocol\r
96//\r
97/**\r
98 @par Protocol Description:\r
99\r
100 The EFI_SECURITY_ARCH_PROTOCOL is used to abstract platform-specific policy\r
101 from the DXE core. This includes locking flash upon failure to authenticate, \r
102 attestation logging, and other exception operations.\r
103\r
104 The driver that produces the EFI_SECURITY_ARCH_PROTOCOL may also optionally \r
105 install the EFI_SECURITY_POLICY_PROTOCOL_GUID onto a new handle with a NULL \r
106 interface. The existence of this GUID in the protocol database means that \r
107 the GUIDed Section Extraction Protocol should authenticate the contents of \r
108 an Authentication Section. The expectation is that the GUIDed Section \r
109 Extraction protocol will look for the existence of the EFI_SECURITY_POLICY_ \r
110 PROTOCOL_GUID in the protocol database. If it exists, then the publication \r
111 thereof is taken as an injunction to attempt an authentication of any section \r
112 wrapped in an Authentication Section. See the Firmware File System \r
113 Specification for details on the GUIDed Section Extraction Protocol and \r
114 Authentication Sections.\r
115\r
4ca9b6c4
LG
116 @param FileAuthenticationState\r
117 This service is called upon fault with respect to \r
d1f95000 118 the authentication of a section of a file.\r
119\r
120**/\r
121struct _EFI_SECURITY_ARCH_PROTOCOL {\r
122 EFI_SECURITY_FILE_AUTHENTICATION_STATE FileAuthenticationState;\r
123};\r
124\r
125extern EFI_GUID gEfiSecurityArchProtocolGuid;\r
126\r
127#endif\r