Delete Old Stack Cookie Library and Supporting Code

Description

Delete the old stack cookie logic.

- [x] Impacts functionality?
  - **Functionality** - Does the change ultimately impact how firmware functions?
  - Examples: Add a new library, publish a new PPI, update an algorithm, ...
- [ ] Impacts security?
  - **Security** - Does the change have a direct security impact on an application,
    flow, or firmware?
  - Examples: Crypto algorithm change, buffer overflow fix, parameter
    validation improvement, ...
- [ ] Breaking change?
  - **Breaking change** - Will anyone consuming this change experience a break
    in build or boot behavior?
  - Examples: Add a new library class, move a module to a different repo, call
    a function in a new library class in a pre-existing module, ...
- [ ] Includes tests?
  - **Tests** - Does the change include any explicit test code?
  - Examples: Unit tests, integration tests, robot tests, ...
- [ ] Includes documentation?
  - **Documentation** - Does the change contain explicit documentation additions
    outside direct code modifications (and comments)?
  - Examples: Update readme file, add feature readme file, link to documentation
    on an a separate Web page, ...

How This Was Tested

Tested on GCC and VS builds of Q35

Integration Instructions

N/A

MdePkg/Include/IndustryStandard/PeImage.h

@@ -134,34 +134,6 @@ typedef struct {
   UINT32    Size;
 } EFI_IMAGE_DATA_DIRECTORY;
 
-// MS_CHANGE_? - Something to do with Stack Cookies?
-//
-// Load Config Directory from PeCoff
-//
-typedef struct {
-  UINTN    Size;
-  UINTN    TimeDateStamp;
-  UINT8    MajorVersion;
-  UINT8    MinorVersion;
-  UINTN    GlobalFlagsClear;
-  UINTN    GlobalFlagsSet;
-  UINTN    CriticalSectionDefaultTimeout;
-  UINTN    DeCommitFreeBlockThreshold;
-  UINTN    DeCommitTotalFreeThreshold;
-  UINTN    LockPrefixTable;                 // VA
-  UINTN    MaximumAllocationSize;
-  UINTN    VirtualMemoryThreshold;
-  UINTN    ProcessHeapFlags;
-  UINTN    ProcessAffinityMask;
-  UINT8    CSDVersion;
-  UINT8    Reserved1;
-  UINTN    EditList;                        // VA
-  UINTN    SecurityCookie;
-  VOID     **SEHandlerTable;
-  UINTN    SEHandlerCount;
-} EFI_IMAGE_LOAD_CONFIG_DIRECTORY;
-// END
-
 //
 // Directory Entries
 //

MdePkg/Include/Library/PeCoffLib.h

@@ -230,37 +230,6 @@ PeCoffLoaderGetImageInfo (
   IN OUT PE_COFF_LOADER_IMAGE_CONTEXT  *ImageContext
   );
 
-// MS_CHANGE_? START
-
-/**
-Retrieves the address of the SecurityCookie from the PE/COFF image.
-
-This function locations the EFI_IMAGE_LOAD_CONFIG_DIRECTORY in the PE/COFF image
-and gets the SecurityCookie field from this structure.  This structure will only
-exist in binaries built with the VS2013/VS2015 compilers without the /GS- flag.
-
-NOTE: Only X64 binaries are supported at the moment
-
-@param  ImageContext              The pointer to the image context structure that
-                                  describes the PE/COFF image that needs to be
-                                  examined by this function.
-@param  SecurityCookieAddress     The pointer that receives the address of the
-                                  security cookie upon successful execution of this function
-
-@retval RETURN_SUCCESS            The information on the PE/COFF image was collected.
-@retval RETURN_INVALID_PARAMETER  ImageContext is NULL.
-@retval RETURN_UNSUPPORTED        The PE/COFF image is not supported.
-
-**/
-RETURN_STATUS
-EFIAPI
-PeCoffLoaderGetSecurityCookieAddress (
-  IN OUT PE_COFF_LOADER_IMAGE_CONTEXT  *ImageContext,
-  OUT    UINT64                        **SecurityCookieAddress
-  );
-
-// END
-
 /**
   Applies relocation fixups to a PE/COFF image that was loaded with PeCoffLoaderLoadImage().