Discussion:
[edk2] [patch 0/2] Do TPer Reset for all encrypted drives
Tian Feng
2015-06-25 04:00:45 UTC
Permalink
At past we only did TPer Reset for ATA device in AtaBus driver.
Now a common logic to do TPer Reset is extracted and putted in TcgMor module.

By this way, all encrypted drives whose driver produces EFI_STORAGE_SECURITY_
COMMAND_PROTOCOL could be force reset at EndOfDxe.

Tian Feng (2):
MdeModulePkg/AtaBus: remove TPer Reset operation in DriverBindingStart
SecurityPkg/TcgMor: move TPer Reset operation to this module

MdeModulePkg/Bus/Ata/AtaBusDxe/AtaBus.c | 208 +----------------
MdeModulePkg/Bus/Ata/AtaBusDxe/AtaBus.h | 17 +-
SecurityPkg/Tcg/MemoryOverwriteControl/TcgMor.c | 264 +++++++++++++++++++++-
SecurityPkg/Tcg/MemoryOverwriteControl/TcgMor.h | 22 +-
SecurityPkg/Tcg/MemoryOverwriteControl/TcgMor.inf | 13 +-
5 files changed, 296 insertions(+), 228 deletions(-)
--
1.9.5.msysgit.0
Tian Feng
2015-06-25 04:00:46 UTC
Permalink
The TPer Reset operation would be moved into SecurityPkg/Tcg/
MemoryOverwriteControl/TcgMor.inf module and be triggered at EndOfDxe.

By this way, all encrypted drives which produce EFI_STORAGE_SECURITY_
RPOTOCOL interface would be force reset when MOR is set.

Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Tian Feng <***@intel.com>
---
MdeModulePkg/Bus/Ata/AtaBusDxe/AtaBus.c | 208 +-------------------------------
MdeModulePkg/Bus/Ata/AtaBusDxe/AtaBus.h | 17 +--
2 files changed, 4 insertions(+), 221 deletions(-)

diff --git a/MdeModulePkg/Bus/Ata/AtaBusDxe/AtaBus.c b/MdeModulePkg/Bus/Ata/AtaBusDxe/AtaBus.c
index 2678316..e7449f9 100644
--- a/MdeModulePkg/Bus/Ata/AtaBusDxe/AtaBus.c
+++ b/MdeModulePkg/Bus/Ata/AtaBusDxe/AtaBus.c
@@ -4,7 +4,7 @@
This file implements protocol interfaces: Driver Binding protocol,
Block IO protocol and DiskInfo protocol.

- Copyright (c) 2009 - 2014, Intel Corporation. All rights reserved.<BR>
+ Copyright (c) 2009 - 2015, Intel Corporation. All rights reserved.<BR>
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
@@ -18,8 +18,6 @@

#include "AtaBus.h"

-UINT8 mMorControl;
-
//
// ATA Bus Driver Binding Protocol Instance
//
@@ -379,17 +377,6 @@ RegisterAtaDevice (
DEBUG ((EFI_D_INFO, "Successfully Install Storage Security Protocol on the ATA device\n"));
}

-
- if (((mMorControl & 0x01) == 0x01) && ((AtaDevice->IdentifyData->trusted_computing_support & BIT0) != 0)) {
- DEBUG ((EFI_D_INFO,
- "mMorControl = %x, AtaDevice->IdentifyData->trusted_computing_support & BIT0 = %x\n",
- mMorControl,
- (AtaDevice->IdentifyData->trusted_computing_support & BIT0)
- ));
- DEBUG ((EFI_D_INFO, "Try to lock device by sending TPer Reset command...\n"));
- InitiateTPerReset(AtaDevice);
- }
-
gBS->OpenProtocol (
AtaBusDriverData->Controller,
&gEfiAtaPassThruProtocolGuid,
@@ -1556,7 +1543,7 @@ AtaStorageSecurityReceiveData (
ATA_DEVICE *Private;
EFI_TPL OldTpl;

- DEBUG ((EFI_D_INFO, "EFI Storage Security Protocol - Read"));
+ DEBUG ((EFI_D_INFO, "EFI Storage Security Protocol - Read\n"));
if ((PayloadBuffer == NULL || PayloadTransferSize == NULL) && PayloadBufferSize != 0) {
return EFI_INVALID_PARAMETER;
}
@@ -1666,7 +1653,7 @@ AtaStorageSecuritySendData (
ATA_DEVICE *Private;
EFI_TPL OldTpl;

- DEBUG ((EFI_D_INFO, "EFI Storage Security Protocol - Send"));
+ DEBUG ((EFI_D_INFO, "EFI Storage Security Protocol - Send\n"));
if ((PayloadBuffer == NULL) && (PayloadBufferSize != 0)) {
return EFI_INVALID_PARAMETER;
}
@@ -1712,7 +1699,6 @@ InitializeAtaBus(
)
{
EFI_STATUS Status;
- UINTN DataSize;

//
// Install driver model protocol(s).
@@ -1727,194 +1713,6 @@ InitializeAtaBus(
);
ASSERT_EFI_ERROR (Status);

- //
- // Get the MorControl bit.
- //
- DataSize = sizeof (mMorControl);
- Status = gRT->GetVariable (
- MEMORY_OVERWRITE_REQUEST_VARIABLE_NAME,
- &gEfiMemoryOverwriteControlDataGuid,
- NULL,
- &DataSize,
- &mMorControl
- );
-
- if (EFI_ERROR (Status)) {
- DEBUG ((EFI_D_INFO, "AtaBus:gEfiMemoryOverwriteControlDataGuid doesn't exist!!***\n"));
- mMorControl = 0;
- Status = EFI_SUCCESS;
- } else {
- DEBUG ((EFI_D_INFO, "AtaBus:Get the gEfiMemoryOverwriteControlDataGuid = %x!!***\n", mMorControl));
- }
-
return Status;
}

-/**
- Send TPer Reset command to reset eDrive to lock all protected bands.
- Typically, there are 2 mechanism for resetting eDrive. They are:
- 1. TPer Reset through IEEE 1667 protocol.
- 2. TPer Reset through native TCG protocol.
- This routine will detect what protocol the attached eDrive comform to, TCG or
- IEEE 1667 protocol. Then send out TPer Reset command separately.
-
- @param[in] AtaDevice ATA_DEVICE pointer.
-
-**/
-VOID
-InitiateTPerReset (
- IN ATA_DEVICE *AtaDevice
- )
-{
-
- EFI_STATUS Status;
- UINT8 *Buffer;
- UINTN XferSize;
- UINTN Len;
- UINTN Index;
- BOOLEAN TcgFlag;
- BOOLEAN IeeeFlag;
- EFI_BLOCK_IO_PROTOCOL *BlockIo;
- EFI_STORAGE_SECURITY_COMMAND_PROTOCOL *Ssp;
- SUPPORTED_SECURITY_PROTOCOLS_PARAMETER_DATA *Data;
-
- Buffer = NULL;
- TcgFlag = FALSE;
- IeeeFlag = FALSE;
- Ssp = &AtaDevice->StorageSecurity;
- BlockIo = &AtaDevice->BlockIo;
-
- //
- // ATA8-ACS 7.57.6.1 indicates the Transfer Length field requirements a multiple of 512.
- // If the length of the TRUSTED RECEIVE parameter data is greater than the Transfer Length,
- // then the device shall return the TRUSTED RECEIVE parameter data truncated to the requested Transfer Length.
- //
- Len = ROUNDUP512(sizeof(SUPPORTED_SECURITY_PROTOCOLS_PARAMETER_DATA));
- Buffer = AllocateZeroPool(Len);
-
- if (Buffer == NULL) {
- return;
- }
-
- //
- // When the Security Protocol field is set to 00h, and SP Specific is set to 0000h in a TRUSTED RECEIVE
- // command, the device basic information data shall be returned.
- //
- Status = Ssp->ReceiveData (
- Ssp,
- BlockIo->Media->MediaId,
- 100000000, // Timeout 10-sec
- 0, // SecurityProtocol
- 0, // SecurityProtocolSpecifcData
- Len, // PayloadBufferSize,
- Buffer, // PayloadBuffer
- &XferSize
- );
- if (EFI_ERROR (Status)) {
- goto Exit;
- }
-
- //
- // In returned data, the ListLength field indicates the total length, in bytes,
- // of the supported security protocol list.
- //
- Data = (SUPPORTED_SECURITY_PROTOCOLS_PARAMETER_DATA*)Buffer;
- Len = ROUNDUP512(sizeof (SUPPORTED_SECURITY_PROTOCOLS_PARAMETER_DATA) +
- (Data->SupportedSecurityListLength[0] << 8) +
- (Data->SupportedSecurityListLength[1])
- );
-
- //
- // Free original buffer and allocate new buffer.
- //
- FreePool(Buffer);
- Buffer = AllocateZeroPool(Len);
- if (Buffer == NULL) {
- return;
- }
-
- //
- // Read full supported security protocol list from device.
- //
- Status = Ssp->ReceiveData (
- Ssp,
- BlockIo->Media->MediaId,
- 100000000, // Timeout 10-sec
- 0, // SecurityProtocol
- 0, // SecurityProtocolSpecifcData
- Len, // PayloadBufferSize,
- Buffer, // PayloadBuffer
- &XferSize
- );
-
- if (EFI_ERROR (Status)) {
- goto Exit;
- }
-
- Data = (SUPPORTED_SECURITY_PROTOCOLS_PARAMETER_DATA*)Buffer;
- Len = (Data->SupportedSecurityListLength[0] << 8) + Data->SupportedSecurityListLength[1];
-
- //
- // Iterate full supported security protocol list to check if TCG or IEEE 1667 protocol
- // is supported.
- //
- for (Index = 0; Index < Len; Index++) {
- if (Data->SupportedSecurityProtocol[Index] == SECURITY_PROTOCOL_TCG) {
- //
- // Found a TCG device.
- //
- TcgFlag = TRUE;
- DEBUG ((EFI_D_INFO, "This device is a TCG protocol device\n"));
- break;
- }
-
- if (Data->SupportedSecurityProtocol[Index] == SECURITY_PROTOCOL_IEEE1667) {
- //
- // Found a IEEE 1667 device.
- //
- IeeeFlag = TRUE;
- DEBUG ((EFI_D_INFO, "This device is a IEEE 1667 protocol device\n"));
- break;
- }
- }
-
- if (!TcgFlag && !IeeeFlag) {
- DEBUG ((EFI_D_INFO, "Neither a TCG nor IEEE 1667 protocol device is found\n"));
- goto Exit;
- }
-
- if (TcgFlag) {
- //
- // As long as TCG protocol is supported, send out a TPer Reset
- // TCG command to the device via the TrustedSend command with a non-zero Transfer Length.
- //
- Status = Ssp->SendData (
- Ssp,
- BlockIo->Media->MediaId,
- 100000000, // Timeout 10-sec
- SECURITY_PROTOCOL_TCG, // SecurityProtocol
- 0x0400, // SecurityProtocolSpecifcData
- 512, // PayloadBufferSize,
- Buffer // PayloadBuffer
- );
-
- if (!EFI_ERROR (Status)) {
- DEBUG ((EFI_D_INFO, "Send TPer Reset Command Successfully !\n"));
- } else {
- DEBUG ((EFI_D_INFO, "Send TPer Reset Command Fail !\n"));
- }
- }
-
- if (IeeeFlag) {
- //
- // TBD : Perform a TPer Reset via IEEE 1667 Protocol
- //
- DEBUG ((EFI_D_INFO, "IEEE 1667 Protocol didn't support yet!\n"));
- }
-
-Exit:
-
- if (Buffer != NULL) {
- FreePool(Buffer);
- }
-}
diff --git a/MdeModulePkg/Bus/Ata/AtaBusDxe/AtaBus.h b/MdeModulePkg/Bus/Ata/AtaBusDxe/AtaBus.h
index 04ae47c..621f7d3 100644
--- a/MdeModulePkg/Bus/Ata/AtaBusDxe/AtaBus.h
+++ b/MdeModulePkg/Bus/Ata/AtaBusDxe/AtaBus.h
@@ -4,7 +4,7 @@
This file defines common data structures, macro definitions and some module
internal function header files.

- Copyright (c) 2009 - 2013, Intel Corporation. All rights reserved.<BR>
+ Copyright (c) 2009 - 2015, Intel Corporation. All rights reserved.<BR>
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
@@ -85,21 +85,6 @@
#define ATA_SUB_TASK_SIGNATURE SIGNATURE_32 ('A', 'S', 'T', 'S')
#define IS_ALIGNED(addr, size) (((UINTN) (addr) & (size - 1)) == 0)

-#define ROUNDUP512(x) (((x) % 512 == 0) ? (x) : ((x) / 512 + 1) * 512)
-
-#define SECURITY_PROTOCOL_TCG 0x02
-#define SECURITY_PROTOCOL_IEEE1667 0xEE
-
-//
-// ATA Supported Security Protocols List Description.
-// Refer to ATA8-ACS Spec 7.57.6.2 Table 69.
-//
-typedef struct {
- UINT8 Reserved1[6];
- UINT8 SupportedSecurityListLength[2];
- UINT8 SupportedSecurityProtocol[1];
-} SUPPORTED_SECURITY_PROTOCOLS_PARAMETER_DATA;
-
//
// ATA bus data structure for ATA controller
//
--
1.9.5.msysgit.0
Tian Feng
2015-06-25 04:00:47 UTC
Permalink
The TPer Reset operation is a common logic. So it's added into
SecurityPkg/Tcg/MemoryOverwriteControl/TcgMor.inf module and
would be triggered at EndOfDxe.

By this way, all encrypted drives which produce EFI_STORAGE_SECURITY_
RPOTOCOL interface would be force reset when MOR is set.

Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Tian Feng <***@intel.com>
---
SecurityPkg/Tcg/MemoryOverwriteControl/TcgMor.c | 264 +++++++++++++++++++++-
SecurityPkg/Tcg/MemoryOverwriteControl/TcgMor.h | 22 +-
SecurityPkg/Tcg/MemoryOverwriteControl/TcgMor.inf | 13 +-
3 files changed, 292 insertions(+), 7 deletions(-)

diff --git a/SecurityPkg/Tcg/MemoryOverwriteControl/TcgMor.c b/SecurityPkg/Tcg/MemoryOverwriteControl/TcgMor.c
index a4acc14..e691a08 100644
--- a/SecurityPkg/Tcg/MemoryOverwriteControl/TcgMor.c
+++ b/SecurityPkg/Tcg/MemoryOverwriteControl/TcgMor.c
@@ -2,9 +2,10 @@
TCG MOR (Memory Overwrite Request) Control Driver.

This driver initilize MemoryOverwriteRequestControl variable. It
- will clear MOR_CLEAR_MEMORY_BIT bit if it is set.
+ will clear MOR_CLEAR_MEMORY_BIT bit if it is set. It will also do TPer Reset for
+ those encrypted drives through EFI_STORAGE_SECURITY_COMMAND_PROTOCOL at EndOfDxe.

-Copyright (c) 2009 - 2014, Intel Corporation. All rights reserved.<BR>
+Copyright (c) 2009 - 2015, Intel Corporation. All rights reserved.<BR>
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
@@ -63,6 +64,242 @@ OnReadyToBoot (
}
}

+/**
+ Send TPer Reset command to reset eDrive to lock all protected bands.
+ Typically, there are 2 mechanism for resetting eDrive. They are:
+ 1. TPer Reset through IEEE 1667 protocol.
+ 2. TPer Reset through native TCG protocol.
+ This routine will detect what protocol the attached eDrive comform to, TCG or
+ IEEE 1667 protocol. Then send out TPer Reset command separately.
+
+ @param[in] Ssp The pointer to EFI_STORAGE_SECURITY_COMMAND_PROTOCOL instance.
+ @param[in] MediaId ID of the medium to receive data from or send data to.
+
+**/
+VOID
+InitiateTPerReset (
+ IN EFI_STORAGE_SECURITY_COMMAND_PROTOCOL *Ssp,
+ IN UINT32 MediaId
+ )
+{
+
+ EFI_STATUS Status;
+ UINT8 *Buffer;
+ UINTN XferSize;
+ UINTN Len;
+ UINTN Index;
+ BOOLEAN TcgFlag;
+ BOOLEAN IeeeFlag;
+ SUPPORTED_SECURITY_PROTOCOLS_PARAMETER_DATA *Data;
+
+ Buffer = NULL;
+ TcgFlag = FALSE;
+ IeeeFlag = FALSE;
+
+ //
+ // ATA8-ACS 7.57.6.1 indicates the Transfer Length field requirements a multiple of 512.
+ // If the length of the TRUSTED RECEIVE parameter data is greater than the Transfer Length,
+ // then the device shall return the TRUSTED RECEIVE parameter data truncated to the requested Transfer Length.
+ //
+ Len = ROUNDUP512(sizeof(SUPPORTED_SECURITY_PROTOCOLS_PARAMETER_DATA));
+ Buffer = AllocateZeroPool(Len);
+
+ if (Buffer == NULL) {
+ return;
+ }
+
+ //
+ // When the Security Protocol field is set to 00h, and SP Specific is set to 0000h in a TRUSTED RECEIVE
+ // command, the device basic information data shall be returned.
+ //
+ Status = Ssp->ReceiveData (
+ Ssp,
+ MediaId,
+ 100000000, // Timeout 10-sec
+ 0, // SecurityProtocol
+ 0, // SecurityProtocolSpecifcData
+ Len, // PayloadBufferSize,
+ Buffer, // PayloadBuffer
+ &XferSize
+ );
+ if (EFI_ERROR (Status)) {
+ goto Exit;
+ }
+
+ //
+ // In returned data, the ListLength field indicates the total length, in bytes,
+ // of the supported security protocol list.
+ //
+ Data = (SUPPORTED_SECURITY_PROTOCOLS_PARAMETER_DATA*)Buffer;
+ Len = ROUNDUP512(sizeof (SUPPORTED_SECURITY_PROTOCOLS_PARAMETER_DATA) +
+ (Data->SupportedSecurityListLength[0] << 8) +
+ (Data->SupportedSecurityListLength[1])
+ );
+
+ //
+ // Free original buffer and allocate new buffer.
+ //
+ FreePool(Buffer);
+ Buffer = AllocateZeroPool(Len);
+ if (Buffer == NULL) {
+ return;
+ }
+
+ //
+ // Read full supported security protocol list from device.
+ //
+ Status = Ssp->ReceiveData (
+ Ssp,
+ MediaId,
+ 100000000, // Timeout 10-sec
+ 0, // SecurityProtocol
+ 0, // SecurityProtocolSpecifcData
+ Len, // PayloadBufferSize,
+ Buffer, // PayloadBuffer
+ &XferSize
+ );
+
+ if (EFI_ERROR (Status)) {
+ goto Exit;
+ }
+
+ Data = (SUPPORTED_SECURITY_PROTOCOLS_PARAMETER_DATA*)Buffer;
+ Len = (Data->SupportedSecurityListLength[0] << 8) + Data->SupportedSecurityListLength[1];
+
+ //
+ // Iterate full supported security protocol list to check if TCG or IEEE 1667 protocol
+ // is supported.
+ //
+ for (Index = 0; Index < Len; Index++) {
+ if (Data->SupportedSecurityProtocol[Index] == SECURITY_PROTOCOL_TCG) {
+ //
+ // Found a TCG device.
+ //
+ TcgFlag = TRUE;
+ DEBUG ((EFI_D_INFO, "This device is a TCG protocol device\n"));
+ break;
+ }
+
+ if (Data->SupportedSecurityProtocol[Index] == SECURITY_PROTOCOL_IEEE1667) {
+ //
+ // Found a IEEE 1667 device.
+ //
+ IeeeFlag = TRUE;
+ DEBUG ((EFI_D_INFO, "This device is a IEEE 1667 protocol device\n"));
+ break;
+ }
+ }
+
+ if (!TcgFlag && !IeeeFlag) {
+ DEBUG ((EFI_D_INFO, "Neither a TCG nor IEEE 1667 protocol device is found\n"));
+ goto Exit;
+ }
+
+ if (TcgFlag) {
+ //
+ // As long as TCG protocol is supported, send out a TPer Reset
+ // TCG command to the device via the TrustedSend command with a non-zero Transfer Length.
+ //
+ Status = Ssp->SendData (
+ Ssp,
+ MediaId,
+ 100000000, // Timeout 10-sec
+ SECURITY_PROTOCOL_TCG, // SecurityProtocol
+ 0x0400, // SecurityProtocolSpecifcData
+ 512, // PayloadBufferSize,
+ Buffer // PayloadBuffer
+ );
+
+ if (!EFI_ERROR (Status)) {
+ DEBUG ((EFI_D_INFO, "Send TPer Reset Command Successfully !\n"));
+ } else {
+ DEBUG ((EFI_D_INFO, "Send TPer Reset Command Fail !\n"));
+ }
+ }
+
+ if (IeeeFlag) {
+ //
+ // TBD : Perform a TPer Reset via IEEE 1667 Protocol
+ //
+ DEBUG ((EFI_D_INFO, "IEEE 1667 Protocol didn't support yet!\n"));
+ }
+
+Exit:
+
+ if (Buffer != NULL) {
+ FreePool(Buffer);
+ }
+}
+
+/**
+ Notification function of END_OF_DXE.
+
+ This is a notification function registered on END_OF_DXE event.
+ It is to get VarCheckPcdBin.
+
+ @param[in] Event Event whose notification function is being invoked.
+ @param[in] Context Pointer to the notification function's context.
+
+**/
+VOID
+EFIAPI
+TPerResetAtEndOfDxe (
+ IN EFI_EVENT Event,
+ IN VOID *Context
+ )
+{
+ EFI_STORAGE_SECURITY_COMMAND_PROTOCOL *Ssp;
+ EFI_BLOCK_IO_PROTOCOL *BlockIo;
+ EFI_STATUS Status;
+ UINTN HandleCount;
+ EFI_HANDLE *HandleBuffer;
+ UINTN Index;
+
+ //
+ // Locate all SSP protocol instances.
+ //
+ HandleCount = 0;
+ HandleBuffer = NULL;
+
+ Status = gBS->LocateHandleBuffer (
+ ByProtocol,
+ &gEfiStorageSecurityCommandProtocolGuid,
+ NULL,
+ &HandleCount,
+ &HandleBuffer
+ );
+
+ if (EFI_ERROR (Status) || (HandleCount == 0) || (HandleBuffer == NULL)) {
+ return;
+ }
+
+ for (Index = 0; Index < HandleCount; Index ++) {
+ //
+ // Get the SSP interface.
+ //
+ Status = gBS->HandleProtocol(
+ HandleBuffer[Index],
+ &gEfiStorageSecurityCommandProtocolGuid,
+ (VOID **) &Ssp
+ );
+
+ if (EFI_ERROR (Status)) {
+ continue;
+ }
+
+ Status = gBS->HandleProtocol(
+ HandleBuffer[Index],
+ &gEfiBlockIoProtocolGuid,
+ (VOID **) &BlockIo
+ );
+
+ if (EFI_ERROR (Status)) {
+ continue;
+ }
+
+ InitiateTPerReset (Ssp, BlockIo->Media->MediaId);
+ }
+}

/**
Entry Point for TCG MOR Control driver.
@@ -120,8 +357,27 @@ MorDriverEntryPoint (
NULL,
&Event
);
- }
-
+ if (EFI_ERROR (Status)) {
+ return Status;
+ }
+
+ //
+ // Register EFI_END_OF_DXE_EVENT_GROUP_GUID event.
+ //
+ DEBUG ((EFI_D_INFO, "TcgMor: Create EndofDxe Event for Mor TPer Reset!\n"));
+ Status = gBS->CreateEventEx (
+ EVT_NOTIFY_SIGNAL,
+ TPL_CALLBACK,
+ TPerResetAtEndOfDxe,
+ NULL,
+ &gEfiEndOfDxeEventGroupGuid,
+ &Event
+ );
+ if (EFI_ERROR (Status)) {
+ return Status;
+ }
+ }
+
return Status;
}

diff --git a/SecurityPkg/Tcg/MemoryOverwriteControl/TcgMor.h b/SecurityPkg/Tcg/MemoryOverwriteControl/TcgMor.h
index 24ecdf6..a4aae48 100644
--- a/SecurityPkg/Tcg/MemoryOverwriteControl/TcgMor.h
+++ b/SecurityPkg/Tcg/MemoryOverwriteControl/TcgMor.h
@@ -1,7 +1,7 @@
/** @file
The header file for TcgMor.

-Copyright (c) 2009 - 2012, Intel Corporation. All rights reserved.<BR>
+Copyright (c) 2009 - 2015, Intel Corporation. All rights reserved.<BR>
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
@@ -20,9 +20,29 @@ WITHOUT WARRANTIES OR REPRESENTATIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED.
#include <Guid/MemoryOverwriteControl.h>

#include <Library/UefiDriverEntryPoint.h>
+#include <Library/UefiBootServicesTableLib.h>
#include <Library/UefiRuntimeServicesTableLib.h>
#include <Library/DebugLib.h>
#include <Library/UefiLib.h>
+#include <Library/MemoryAllocationLib.h>
+
+#include <Protocol/StorageSecurityCommand.h>
+#include <Protocol/BlockIo.h>
+
+//
+// Supported Security Protocols List Description.
+// Refer to ATA8-ACS Spec 7.57.6.2 Table 69 or SPC4 7.7.1.3 Table 511.
+//
+typedef struct {
+ UINT8 Reserved1[6];
+ UINT8 SupportedSecurityListLength[2];
+ UINT8 SupportedSecurityProtocol[1];
+} SUPPORTED_SECURITY_PROTOCOLS_PARAMETER_DATA;
+
+#define SECURITY_PROTOCOL_TCG 0x02
+#define SECURITY_PROTOCOL_IEEE1667 0xEE
+
+#define ROUNDUP512(x) (((x) % 512 == 0) ? (x) : ((x) / 512 + 1) * 512)

#endif

diff --git a/SecurityPkg/Tcg/MemoryOverwriteControl/TcgMor.inf b/SecurityPkg/Tcg/MemoryOverwriteControl/TcgMor.inf
index 45cb311..d5a7da8 100644
--- a/SecurityPkg/Tcg/MemoryOverwriteControl/TcgMor.inf
+++ b/SecurityPkg/Tcg/MemoryOverwriteControl/TcgMor.inf
@@ -1,9 +1,11 @@
## @file
# Initilizes MemoryOverwriteRequestControl variable
#
-# This module will clear MOR_CLEAR_MEMORY_BIT bit if it is set.
+# This module will clear MOR_CLEAR_MEMORY_BIT bit if it is set. It will also do
+# TPer Reset for those encrypted drives through EFI_STORAGE_SECURITY_COMMAND_PROTOCOL
+# at EndOfDxe.
#
-# Copyright (c) 2009 - 2014, Intel Corporation. All rights reserved.<BR>
+# Copyright (c) 2009 - 2015, Intel Corporation. All rights reserved.<BR>
# 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
@@ -39,15 +41,22 @@

[LibraryClasses]
UefiDriverEntryPoint
+ UefiBootServicesTableLib
UefiRuntimeServicesTableLib
ReportStatusCodeLib
DebugLib
UefiLib
+ MemoryAllocationLib

[Guids]
## SOMETIMES_CONSUMES ## Variable:L"MemoryOverwriteRequestControl"
## PRODUCES ## Variable:L"MemoryOverwriteRequestControl"
gEfiMemoryOverwriteControlDataGuid
+ gEfiEndOfDxeEventGroupGuid ## SOMETIMES_CONSUMES ## Event
+
+[Protocols]
+ gEfiStorageSecurityCommandProtocolGuid ## SOMETIMES_CONSUMES
+ gEfiBlockIoProtocolGuid ## SOMETIMES_CONSUMES

[Depex]
gEfiVariableArchProtocolGuid AND
--
1.9.5.msysgit.0
Zeng, Star
2015-06-26 05:15:54 UTC
Permalink
Also need to remove #include <Guid/MemoryOverwriteControl.h> from AtaBus.h and gEfiMemoryOverwriteControlDataGuid from AtaBusDxe.inf?

Others are good to me.

Thanks,
Star
-----Original Message-----
From: Tian Feng [mailto:***@intel.com]
Sent: Thursday, June 25, 2015 12:01 PM
To: ***@intel.com; Yao, Jiewen
Cc: edk2-***@lists.sourceforge.net
Subject: [edk2] [patch 0/2] Do TPer Reset for all encrypted drives

At past we only did TPer Reset for ATA device in AtaBus driver.
Now a common logic to do TPer Reset is extracted and putted in TcgMor module.

By this way, all encrypted drives whose driver produces EFI_STORAGE_SECURITY_ COMMAND_PROTOCOL could be force reset at EndOfDxe.

Tian Feng (2):
MdeModulePkg/AtaBus: remove TPer Reset operation in DriverBindingStart
SecurityPkg/TcgMor: move TPer Reset operation to this module

MdeModulePkg/Bus/Ata/AtaBusDxe/AtaBus.c | 208 +----------------
MdeModulePkg/Bus/Ata/AtaBusDxe/AtaBus.h | 17 +-
SecurityPkg/Tcg/MemoryOverwriteControl/TcgMor.c | 264 +++++++++++++++++++++-
SecurityPkg/Tcg/MemoryOverwriteControl/TcgMor.h | 22 +-
SecurityPkg/Tcg/MemoryOverwriteControl/TcgMor.inf | 13 +-
5 files changed, 296 insertions(+), 228 deletions(-)

--
1.9.5.msysgit.0


------------------------------------------------------------------------------
Monitor 25 network devices or servers for free with OpManager!
OpManager is web-based network management software that monitors
network devices and physical & virtual servers, alerts via email & sms
for fault. Monitor 25 devices for free with no restriction. Download now
http://ad.doubleclick.net/ddm/clk/292181274;119417398;o
_______________________________________________
edk2-devel mailing list
edk2-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/edk2-devel
Tian, Feng
2015-06-26 05:20:39 UTC
Permalink
Yes, you are right. I forget removing these from AtaBus driver.

-----Original Message-----
From: Zeng, Star [mailto:***@intel.com]
Sent: Friday, June 26, 2015 13:16
To: edk2-***@lists.sourceforge.net; Yao, Jiewen
Subject: Re: [edk2] [patch 0/2] Do TPer Reset for all encrypted drives

Also need to remove #include <Guid/MemoryOverwriteControl.h> from AtaBus.h and gEfiMemoryOverwriteControlDataGuid from AtaBusDxe.inf?

Others are good to me.

Thanks,
Star
-----Original Message-----
From: Tian Feng [mailto:***@intel.com]
Sent: Thursday, June 25, 2015 12:01 PM
To: ***@intel.com; Yao, Jiewen
Cc: edk2-***@lists.sourceforge.net
Subject: [edk2] [patch 0/2] Do TPer Reset for all encrypted drives

At past we only did TPer Reset for ATA device in AtaBus driver.
Now a common logic to do TPer Reset is extracted and putted in TcgMor module.

By this way, all encrypted drives whose driver produces EFI_STORAGE_SECURITY_ COMMAND_PROTOCOL could be force reset at EndOfDxe.

Tian Feng (2):
MdeModulePkg/AtaBus: remove TPer Reset operation in DriverBindingStart
SecurityPkg/TcgMor: move TPer Reset operation to this module

MdeModulePkg/Bus/Ata/AtaBusDxe/AtaBus.c | 208 +----------------
MdeModulePkg/Bus/Ata/AtaBusDxe/AtaBus.h | 17 +-
SecurityPkg/Tcg/MemoryOverwriteControl/TcgMor.c | 264 +++++++++++++++++++++-
SecurityPkg/Tcg/MemoryOverwriteControl/TcgMor.h | 22 +-
SecurityPkg/Tcg/MemoryOverwriteControl/TcgMor.inf | 13 +-
5 files changed, 296 insertions(+), 228 deletions(-)

--
1.9.5.msysgit.0


------------------------------------------------------------------------------
Monitor 25 network devices or servers for free with OpManager!
OpManager is web-based network management software that monitors network devices and physical & virtual servers, alerts via email & sms for fault. Monitor 25 devices for free with no restriction. Download now http://ad.doubleclick.net/ddm/clk/292181274;119417398;o
_______________________________________________
edk2-devel mailing list
edk2-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/edk2-devel

------------------------------------------------------------------------------
Monitor 25 network devices or servers for free with OpManager!
OpManager is web-based network management software that monitors network devices and physical & virtual servers, alerts via email & sms for fault. Monitor 25 devices for free with no restriction. Download now http://ad.doubleclick.net/ddm/clk/292181274;119417398;o
_______________________________________________
edk2-devel mailing list
edk2-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/edk2-devel
Anbazhagan, Baraneedharan
2015-06-26 12:45:02 UTC
Permalink
Whether EFI_STORAGE_SECURITY_COMMAND_PROTOCOL will be available on EndOfDxe callback? I thought both AtaBusDxe and NvmExpressDxe modules will install EFI_STORAGE_SECURITY_COMMAND_PROTOCOL as part of ConnectController in Bds which is after EndOfDxe.

-Baranee
Post by Zeng, Star
-----Original Message-----
Sent: Friday, June 26, 2015 12:21 AM
Subject: Re: [edk2] [patch 0/2] Do TPer Reset for all encrypted drives
Yes, you are right. I forget removing these from AtaBus driver.
-----Original Message-----
Sent: Friday, June 26, 2015 13:16
Subject: Re: [edk2] [patch 0/2] Do TPer Reset for all encrypted drives
Also need to remove #include <Guid/MemoryOverwriteControl.h> from AtaBus.h and
gEfiMemoryOverwriteControlDataGuid from AtaBusDxe.inf?
Others are good to me.
Thanks,
Star
-----Original Message-----
Sent: Thursday, June 25, 2015 12:01 PM
Subject: [edk2] [patch 0/2] Do TPer Reset for all encrypted drives
At past we only did TPer Reset for ATA device in AtaBus driver.
Now a common logic to do TPer Reset is extracted and putted in TcgMor module.
By this way, all encrypted drives whose driver produces EFI_STORAGE_SECURITY_
COMMAND_PROTOCOL could be force reset at EndOfDxe.
MdeModulePkg/AtaBus: remove TPer Reset operation in DriverBindingStart
SecurityPkg/TcgMor: move TPer Reset operation to this module
MdeModulePkg/Bus/Ata/AtaBusDxe/AtaBus.c | 208 +----------------
MdeModulePkg/Bus/Ata/AtaBusDxe/AtaBus.h | 17 +-
SecurityPkg/Tcg/MemoryOverwriteControl/TcgMor.c | 264
+++++++++++++++++++++-
SecurityPkg/Tcg/MemoryOverwriteControl/TcgMor.h | 22 +-
SecurityPkg/Tcg/MemoryOverwriteControl/TcgMor.inf | 13 +-
5 files changed, 296 insertions(+), 228 deletions(-)
--
1.9.5.msysgit.0
------------------------------------------------------------------------------
Monitor 25 network devices or servers for free with OpManager!
OpManager is web-based network management software that monitors network
devices and physical & virtual servers, alerts via email & sms for fault. Monitor 25
devices for free with no restriction. Download now
http://ad.doubleclick.net/ddm/clk/292181274;119417398;o
_______________________________________________
edk2-devel mailing list
https://lists.sourceforge.net/lists/listinfo/edk2-devel
------------------------------------------------------------------------------
Monitor 25 network devices or servers for free with OpManager!
OpManager is web-based network management software that monitors network
devices and physical & virtual servers, alerts via email & sms for fault. Monitor 25
devices for free with no restriction. Download now
http://ad.doubleclick.net/ddm/clk/292181274;119417398;o
_______________________________________________
edk2-devel mailing list
https://lists.sourceforge.net/lists/listinfo/edk2-devel
Yao, Jiewen
2015-06-26 13:22:30 UTC
Permalink
Hi
According to WHCK: https://msdn.microsoft.com/en-us/library/windows/hardware/jj128256.aspx
==============================
UEFI 2.3.1
The implementation of the Trusted Computing Group Platform Reset Attack Mitigation Specification (http://www.trustedcomputinggroup.org/resources/pc_client_work_group_platform_reset_attack_mitigation_specification_version_10) MUST unconditionally issue TPer Reset (OPAL v2.0 in section 3.2.3) for all scenarios whenever memory is cleared.
The EFI_STORAGE_SECURITY_COMMAND_PROTOCOL and the TPer Reset command MUST be included in the base UEFI image (not in a separate image of a UEFI driver).
The system MUST enumerate all Encrypted Drives and TPer Reset MUST be issued prior to executing any firmware code not provided by the platform manufacturer in the base UEFI image.
============================

It seems platform MUST enumerate all Encrypted Drives and TPer reset before EndOfDxe, if MOR happens.

Thank you
Yao Jiewen

-----Original Message-----
From: Anbazhagan, Baraneedharan [mailto:***@hp.com]
Sent: Friday, June 26, 2015 8:45 PM
To: edk2-***@lists.sourceforge.net; Yao, Jiewen; Zeng, Star
Subject: RE: [edk2] [patch 0/2] Do TPer Reset for all encrypted drives

Whether EFI_STORAGE_SECURITY_COMMAND_PROTOCOL will be available on EndOfDxe callback? I thought both AtaBusDxe and NvmExpressDxe modules will install EFI_STORAGE_SECURITY_COMMAND_PROTOCOL as part of ConnectController in Bds which is after EndOfDxe.

-Baranee
Post by Zeng, Star
-----Original Message-----
Sent: Friday, June 26, 2015 12:21 AM
Subject: Re: [edk2] [patch 0/2] Do TPer Reset for all encrypted drives
Yes, you are right. I forget removing these from AtaBus driver.
-----Original Message-----
Sent: Friday, June 26, 2015 13:16
Subject: Re: [edk2] [patch 0/2] Do TPer Reset for all encrypted drives
Also need to remove #include <Guid/MemoryOverwriteControl.h> from
AtaBus.h and gEfiMemoryOverwriteControlDataGuid from AtaBusDxe.inf?
Others are good to me.
Thanks,
Star
-----Original Message-----
Sent: Thursday, June 25, 2015 12:01 PM
Subject: [edk2] [patch 0/2] Do TPer Reset for all encrypted drives
At past we only did TPer Reset for ATA device in AtaBus driver.
Now a common logic to do TPer Reset is extracted and putted in TcgMor module.
By this way, all encrypted drives whose driver produces
EFI_STORAGE_SECURITY_ COMMAND_PROTOCOL could be force reset at EndOfDxe.
MdeModulePkg/AtaBus: remove TPer Reset operation in DriverBindingStart
SecurityPkg/TcgMor: move TPer Reset operation to this module
MdeModulePkg/Bus/Ata/AtaBusDxe/AtaBus.c | 208 +----------------
MdeModulePkg/Bus/Ata/AtaBusDxe/AtaBus.h | 17 +-
SecurityPkg/Tcg/MemoryOverwriteControl/TcgMor.c | 264
+++++++++++++++++++++-
SecurityPkg/Tcg/MemoryOverwriteControl/TcgMor.h | 22 +-
SecurityPkg/Tcg/MemoryOverwriteControl/TcgMor.inf | 13 +-
5 files changed, 296 insertions(+), 228 deletions(-)
--
1.9.5.msysgit.0
----------------------------------------------------------------------
-------- Monitor 25 network devices or servers for free with
OpManager!
OpManager is web-based network management software that monitors
network devices and physical & virtual servers, alerts via email & sms
for fault. Monitor 25 devices for free with no restriction. Download
now http://ad.doubleclick.net/ddm/clk/292181274;119417398;o
_______________________________________________
edk2-devel mailing list
https://lists.sourceforge.net/lists/listinfo/edk2-devel
----------------------------------------------------------------------
-------- Monitor 25 network devices or servers for free with
OpManager!
OpManager is web-based network management software that monitors
network devices and physical & virtual servers, alerts via email & sms
for fault. Monitor 25 devices for free with no restriction. Download
now http://ad.doubleclick.net/ddm/clk/292181274;119417398;o
_______________________________________________
edk2-devel mailing list
https://lists.sourceforge.net/lists/listinfo/edk2-devel
Anbazhagan, Baraneedharan
2015-06-26 23:25:55 UTC
Permalink
Post by Zeng, Star
-----Original Message-----
Sent: Friday, June 26, 2015 8:23 AM
Subject: RE: [edk2] [patch 0/2] Do TPer Reset for all encrypted drives
Hi
According to WHCK: https://msdn.microsoft.com/en-
us/library/windows/hardware/jj128256.aspx
==============================
UEFI 2.3.1
The implementation of the Trusted Computing Group Platform Reset Attack
Mitigation Specification
(http://www.trustedcomputinggroup.org/resources/pc_client_work_group_platform
_reset_attack_mitigation_specification_version_10) MUST unconditionally issue
TPer Reset (OPAL v2.0 in section 3.2.3) for all scenarios whenever memory is cleared.
The EFI_STORAGE_SECURITY_COMMAND_PROTOCOL and the TPer Reset command
MUST be included in the base UEFI image (not in a separate image of a UEFI driver).
The system MUST enumerate all Encrypted Drives and TPer Reset MUST be issued
prior to executing any firmware code not provided by the platform manufacturer in
the base UEFI image.
============================
It seems platform MUST enumerate all Encrypted Drives and TPer reset before
EndOfDxe, if MOR happens.
Does it make sense to have sample implementation in PlatformBdsLib? Platform can provide device path for those controllers similar to Console devices in PlatformData.c. PlatformBdsLib can make use of that device path if MOR happens and connect to it before EndOfDxe?
Post by Zeng, Star
Thank you
Yao Jiewen
-----Original Message-----
Sent: Friday, June 26, 2015 8:45 PM
Subject: RE: [edk2] [patch 0/2] Do TPer Reset for all encrypted drives
Whether EFI_STORAGE_SECURITY_COMMAND_PROTOCOL will be available on
EndOfDxe callback? I thought both AtaBusDxe and NvmExpressDxe modules will
install EFI_STORAGE_SECURITY_COMMAND_PROTOCOL as part of ConnectController
in Bds which is after EndOfDxe.
-Baranee
Post by Zeng, Star
-----Original Message-----
Sent: Friday, June 26, 2015 12:21 AM
Subject: Re: [edk2] [patch 0/2] Do TPer Reset for all encrypted drives
Yes, you are right. I forget removing these from AtaBus driver.
-----Original Message-----
Sent: Friday, June 26, 2015 13:16
Subject: Re: [edk2] [patch 0/2] Do TPer Reset for all encrypted drives
Also need to remove #include <Guid/MemoryOverwriteControl.h> from
AtaBus.h and gEfiMemoryOverwriteControlDataGuid from AtaBusDxe.inf?
Others are good to me.
Thanks,
Star
-----Original Message-----
Sent: Thursday, June 25, 2015 12:01 PM
Subject: [edk2] [patch 0/2] Do TPer Reset for all encrypted drives
At past we only did TPer Reset for ATA device in AtaBus driver.
Now a common logic to do TPer Reset is extracted and putted in TcgMor module.
By this way, all encrypted drives whose driver produces
EFI_STORAGE_SECURITY_ COMMAND_PROTOCOL could be force reset at EndOfDxe.
MdeModulePkg/AtaBus: remove TPer Reset operation in DriverBindingStart
SecurityPkg/TcgMor: move TPer Reset operation to this module
MdeModulePkg/Bus/Ata/AtaBusDxe/AtaBus.c | 208 +----------------
MdeModulePkg/Bus/Ata/AtaBusDxe/AtaBus.h | 17 +-
SecurityPkg/Tcg/MemoryOverwriteControl/TcgMor.c | 264
+++++++++++++++++++++-
SecurityPkg/Tcg/MemoryOverwriteControl/TcgMor.h | 22 +-
SecurityPkg/Tcg/MemoryOverwriteControl/TcgMor.inf | 13 +-
5 files changed, 296 insertions(+), 228 deletions(-)
--
1.9.5.msysgit.0
----------------------------------------------------------------------
-------- Monitor 25 network devices or servers for free with
OpManager!
OpManager is web-based network management software that monitors
network devices and physical & virtual servers, alerts via email & sms
for fault. Monitor 25 devices for free with no restriction. Download
now http://ad.doubleclick.net/ddm/clk/292181274;119417398;o
_______________________________________________
edk2-devel mailing list
https://lists.sourceforge.net/lists/listinfo/edk2-devel
----------------------------------------------------------------------
-------- Monitor 25 network devices or servers for free with
OpManager!
OpManager is web-based network management software that monitors
network devices and physical & virtual servers, alerts via email & sms
for fault. Monitor 25 devices for free with no restriction. Download
now http://ad.doubleclick.net/ddm/clk/292181274;119417398;o
_______________________________________________
edk2-devel mailing list
https://lists.sourceforge.net/lists/listinfo/edk2-devel
Yao, Jiewen
2015-06-27 00:24:31 UTC
Permalink
Yes, providing sample in PlatformBds makes a lots of sense.

Thank you
Yao Jiewen

-----Original Message-----
From: Anbazhagan, Baraneedharan [mailto:***@hp.com]
Sent: Saturday, June 27, 2015 7:26 AM
To: Yao, Jiewen; edk2-***@lists.sourceforge.net; Zeng, Star
Subject: RE: [edk2] [patch 0/2] Do TPer Reset for all encrypted drives
Post by Zeng, Star
-----Original Message-----
Sent: Friday, June 26, 2015 8:23 AM
Subject: RE: [edk2] [patch 0/2] Do TPer Reset for all encrypted drives
Hi
According to WHCK: https://msdn.microsoft.com/en-
us/library/windows/hardware/jj128256.aspx
==============================
UEFI 2.3.1
The implementation of the Trusted Computing Group Platform Reset
Attack Mitigation Specification
(http://www.trustedcomputinggroup.org/resources/pc_client_work_group_p
latform
_reset_attack_mitigation_specification_version_10) MUST
unconditionally issue TPer Reset (OPAL v2.0 in section 3.2.3) for all scenarios whenever memory is cleared.
The EFI_STORAGE_SECURITY_COMMAND_PROTOCOL and the TPer Reset command
MUST be included in the base UEFI image (not in a separate image of a UEFI driver).
The system MUST enumerate all Encrypted Drives and TPer Reset MUST be
issued prior to executing any firmware code not provided by the
platform manufacturer in the base UEFI image.
============================
It seems platform MUST enumerate all Encrypted Drives and TPer reset
before EndOfDxe, if MOR happens.
Does it make sense to have sample implementation in PlatformBdsLib? Platform can provide device path for those controllers similar to Console devices in PlatformData.c. PlatformBdsLib can make use of that device path if MOR happens and connect to it before EndOfDxe?
Post by Zeng, Star
Thank you
Yao Jiewen
-----Original Message-----
Sent: Friday, June 26, 2015 8:45 PM
Subject: RE: [edk2] [patch 0/2] Do TPer Reset for all encrypted drives
Whether EFI_STORAGE_SECURITY_COMMAND_PROTOCOL will be available on
EndOfDxe callback? I thought both AtaBusDxe and NvmExpressDxe modules
will install EFI_STORAGE_SECURITY_COMMAND_PROTOCOL as part of
ConnectController in Bds which is after EndOfDxe.
-Baranee
Post by Zeng, Star
-----Original Message-----
Sent: Friday, June 26, 2015 12:21 AM
Subject: Re: [edk2] [patch 0/2] Do TPer Reset for all encrypted drives
Yes, you are right. I forget removing these from AtaBus driver.
-----Original Message-----
Sent: Friday, June 26, 2015 13:16
Subject: Re: [edk2] [patch 0/2] Do TPer Reset for all encrypted drives
Also need to remove #include <Guid/MemoryOverwriteControl.h> from
AtaBus.h and gEfiMemoryOverwriteControlDataGuid from AtaBusDxe.inf?
Others are good to me.
Thanks,
Star
-----Original Message-----
Sent: Thursday, June 25, 2015 12:01 PM
Subject: [edk2] [patch 0/2] Do TPer Reset for all encrypted drives
At past we only did TPer Reset for ATA device in AtaBus driver.
Now a common logic to do TPer Reset is extracted and putted in TcgMor module.
By this way, all encrypted drives whose driver produces
EFI_STORAGE_SECURITY_ COMMAND_PROTOCOL could be force reset at EndOfDxe.
MdeModulePkg/AtaBus: remove TPer Reset operation in DriverBindingStart
SecurityPkg/TcgMor: move TPer Reset operation to this module
MdeModulePkg/Bus/Ata/AtaBusDxe/AtaBus.c | 208 +----------------
MdeModulePkg/Bus/Ata/AtaBusDxe/AtaBus.h | 17 +-
SecurityPkg/Tcg/MemoryOverwriteControl/TcgMor.c | 264
+++++++++++++++++++++-
SecurityPkg/Tcg/MemoryOverwriteControl/TcgMor.h | 22 +-
SecurityPkg/Tcg/MemoryOverwriteControl/TcgMor.inf | 13 +-
5 files changed, 296 insertions(+), 228 deletions(-)
--
1.9.5.msysgit.0
--------------------------------------------------------------------
--
-------- Monitor 25 network devices or servers for free with
OpManager!
OpManager is web-based network management software that monitors
network devices and physical & virtual servers, alerts via email &
sms for fault. Monitor 25 devices for free with no restriction.
Download now http://ad.doubleclick.net/ddm/clk/292181274;119417398;o
_______________________________________________
edk2-devel mailing list
https://lists.sourceforge.net/lists/listinfo/edk2-devel
--------------------------------------------------------------------
--
-------- Monitor 25 network devices or servers for free with
OpManager!
OpManager is web-based network management software that monitors
network devices and physical & virtual servers, alerts via email &
sms for fault. Monitor 25 devices for free with no restriction.
Download now http://ad.doubleclick.net/ddm/clk/292181274;119417398;o
_______________________________________________
edk2-devel mailing list
https://lists.sourceforge.net/lists/listinfo/edk2-devel
Loading...