init. 1AQQW051HEADmaster

1 files changed, 146 insertions, 0 deletions

diff --git a/EDK/Foundation/Core/Dxe/ArchProtocol/Security/Security.h b/EDK/Foundation/Core/Dxe/ArchProtocol/Security/Security.h
new file mode 100644
index 0000000..96ced0a
--- /dev/null
+++ b/EDK/Foundation/Core/Dxe/ArchProtocol/Security/Security.h
@@ -0,0 +1,146 @@
+/*++
+
+Copyright (c) 2004, Intel Corporation                                                         
+All rights reserved. This program and the accompanying materials                          
+are licensed and made available under the terms and conditions of the BSD License         
+which accompanies this distribution.  The full text of the license may be found at        
+http://opensource.org/licenses/bsd-license.php                                            
+                                                                                          
+THE PROGRAM IS DISTRIBUTED UNDER THE BSD LICENSE ON AN "AS IS" BASIS,                     
+WITHOUT WARRANTIES OR REPRESENTATIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED.             
+
+Module Name:
+
+  Security.h
+
+Abstract:
+
+  Security Architectural Protocol as defined in the DXE CIS
+
+  Used to provide Security services.  Specifically, dependening upon the 
+  authentication state of a discovered driver in a Firmware Volume, the 
+  portable DXE Core Dispatcher will call into the Security Architectural 
+  Protocol (SAP) with the authentication state of the driver.
+
+  This call-out allows for OEM-specific policy decisions to be made, such
+  as event logging for attested boots, locking flash in response to discovering
+  an unsigned driver or failed signature check, or other exception response.
+
+  The SAP can also change system behavior by having the DXE core put a driver
+  in the Schedule-On-Request (SOR) state.  This will allow for later disposition 
+  of the driver by platform agent, such as Platform BDS.
+
+--*/
+
+#ifndef _ARCH_PROTOCOL_SECURITY_H_
+#define _ARCH_PROTOCOL_SECURITY_H_
+
+//
+// Global ID for the Security Code Architectural Protocol
+//
+#define EFI_SECURITY_ARCH_PROTOCOL_GUID  \
+  { 0xA46423E3, 0x4617, 0x49f1, 0xB9, 0xFF, 0xD1, 0xBF, 0xA9, 0x11, 0x58, 0x39 }
+
+EFI_FORWARD_DECLARATION (EFI_SECURITY_ARCH_PROTOCOL);
+
+typedef 
+EFI_STATUS
+(EFIAPI *EFI_SECURITY_FILE_AUTHENTICATION_STATE) (
+  IN EFI_SECURITY_ARCH_PROTOCOL  *This,
+  IN  UINT32                              AuthenticationStatus,
+  IN  EFI_DEVICE_PATH_PROTOCOL            *File
+  )
+/*++
+
+Routine Description:
+
+  The EFI_SECURITY_ARCH_PROTOCOL (SAP) is used to abstract platform-specific 
+  policy from the DXE core response to an attempt to use a file that returns a 
+  given status for the authentication check from the section extraction protocol.  
+
+  The possible responses in a given SAP implementation may include locking 
+  flash upon failure to authenticate, attestation logging for all signed drivers, 
+  and other exception operations.  The File parameter allows for possible logging 
+  within the SAP of the driver.
+
+  If File is NULL, then EFI_INVALID_PARAMETER is returned.
+
+  If the file specified by File with an authentication status specified by 
+  AuthenticationStatus is safe for the DXE Core to use, then EFI_SUCCESS is returned.
+
+  If the file specified by File with an authentication status specified by 
+  AuthenticationStatus is not safe for the DXE Core to use under any circumstances, 
+  then EFI_ACCESS_DENIED is returned.
+
+  If the file specified by File with an authentication status specified by 
+  AuthenticationStatus is not safe for the DXE Core to use right now, but it 
+  might be possible to use it at a future time, then EFI_SECURITY_VIOLATION is 
+  returned.
+
+Arguments:
+
+  This                 - The EFI_SECURITY_ARCH_PROTOCOL instance.
+
+  AuthenticationStatus - This is the authentication type returned from the Section 
+                         Extraction protocol.  See the Section Extraction Protocol 
+                         Specification for details on this type.
+
+  File                 - This is a pointer to the device path of the file that is 
+                         being dispatched.  This will optionally be used for logging.
+
+Returns:
+
+  EFI_SUCCESS            - The file specified by File did authenticate, and the 
+                           platform policy dictates that the DXE Core may use File.
+
+  EFI_INVALID_PARAMETER  - Driver is NULL.
+
+  EFI_SECURITY_VIOLATION - The file specified by File did not authenticate, and 
+                           the platform policy dictates that File should be placed 
+                           in the untrusted state.   A file may be promoted from 
+                           the untrusted to the trusted state at a future time 
+                           with a call to the Trust() DXE Service.
+
+  EFI_ACCESS_DENIED      - The file specified by File did not authenticate, and 
+                           the platform policy dictates that File should not be 
+                           used for any purpose. 
+
+--*/
+;
+
+//
+// Interface stucture for the Timer Architectural Protocol
+//
+typedef struct _EFI_SECURITY_ARCH_PROTOCOL {
+  EFI_SECURITY_FILE_AUTHENTICATION_STATE  FileAuthenticationState;
+} EFI_SECURITY_ARCH_PROTOCOL;
+/*++
+
+  Protocol Description:
+
+    The EFI_SECURITY_ARCH_PROTOCOL is used to abstract platform-specific policy
+    from the DXE core.  This includes locking flash upon failure to authenticate, 
+    attestation logging, and other exception operations.
+
+    The driver that produces the EFI_SECURITY_ARCH_PROTOCOL may also optionally 
+    install the EFI_SECURITY_POLICY_PROTOCOL_GUID onto a new handle with a NULL 
+    interface.  The existence of this GUID in the protocol database means that 
+    the GUIDed Section Extraction Protocol should authenticate the contents of 
+    an Authentication Section.  The expectation is that the GUIDed Section 
+    Extraction protocol will look for the existence of the EFI_SECURITY_POLICY_ 
+    PROTOCOL_GUID in the protocol database.  If it exists, then the publication 
+    thereof is taken as an injunction to attempt an authentication of any section 
+    wrapped in an Authentication Section.  See the Firmware File System 
+    Specification for details on the GUIDed Section Extraction Protocol and 
+    Authentication Sections.
+  
+  Parameters:
+    
+    FileAuthenticationState - This service is called upon fault with respect to 
+                              the authentication of a section of a file.
+
+--*/
+
+extern EFI_GUID gEfiSecurityArchProtocolGuid;
+
+#endif