Revert of [Windows Sandbox] Turn on MITIGATION_EXTENSION_POINT_DISABLE.

Revert of [Windows Sandbox] Turn on MITIGATION_EXTENSION_POINT_DISABLE. (patchset #6 id:200001 of https://codereview.chromium.org/1854323002/ )

Reason for revert:
Reverting the "on switch" temporarily.  Want to look at the scope/details of broken IMEs more before re-landing.  What percentage of Chrome IMEs are actually still using legacy hooking techniques to inject DLLs into our processes?

Ref: https://bugs.chromium.org/p/chromium/issues/detail?id=634192

Original issue's description:
> [Windows Sandbox] Turn on MITIGATION_EXTENSION_POINT_DISABLE.
>
> This CL is part of a chain of CLs:
> 1) "MITIGATION_EXTENSION_POINT_DISABLE support for children" (https://codereview.chromium.org/1835003003)
> 2) "MITIGATION_EXTENSION_POINT_DISABLE emergency off finch" (https://codereview.chromium.org/1836523004/)
> 3) "New NT registry API" (https://codereview.chromium.org/1841573002)
> 4) "Early browser security support" (https://codereview.chromium.org/1656453002)
> -> THIS
>
> This CL only turns on the new mitigation (in all child processes, and early for the browser process).
>
> BUG=557798
> CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.win:win10_chromium_x64_rel_ng
>
> Committed: https://crrev.com/df585142df9fd58299ef02b64da3381d8b733cb8
> Cr-Commit-Position: refs/heads/master@{#409264}

TBR=wfh@chromium.org,robertshield@chromium.org,nick@chromium.org,bradnelson@chromium.org,bradnelson@google.com
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=557798
Committed: https://crrev.com/406b433e8b3468b8c252a552119c0d65c7be874f
Cr-Commit-Position: refs/heads/master@{#410293}

[penny, 2016-08-08 02:05:13]

The CQ bit was checked by pennymac@chromium.org

[penny, 2016-08-08 02:05:14]

Created Revert of [Windows Sandbox] Turn on MITIGATION_EXTENSION_POINT_DISABLE.

[commit-bot: I haz the power, 2016-08-08 02:05:24]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-08-08 03:02:43]

Description was changed from

==========
Revert of [Windows Sandbox] Turn on MITIGATION_EXTENSION_POINT_DISABLE.
(patchset #6 id:200001 of https://codereview.chromium.org/1854323002/ )

Reason for revert:
Reverting the "on switch" temporarily.  Want to look at the scope/details of
broken IMEs more before re-landing.  What percentage of Chrome IMEs are actually
still using legacy hooking techniques to inject DLLs into our processes?  

Ref: https://bugs.chromium.org/p/chromium/issues/detail?id=634192

Original issue's description:
> [Windows Sandbox] Turn on MITIGATION_EXTENSION_POINT_DISABLE.
> 
> This CL is part of a chain of CLs:
> 1) "MITIGATION_EXTENSION_POINT_DISABLE support for children"
(https://codereview.chromium.org/1835003003)
> 2) "MITIGATION_EXTENSION_POINT_DISABLE emergency off finch"
(https://codereview.chromium.org/1836523004/)
> 3) "New NT registry API" (https://codereview.chromium.org/1841573002)
> 4) "Early browser security support"
(https://codereview.chromium.org/1656453002)
> -> THIS
> 
> This CL only turns on the new mitigation (in all child processes, and early
for the browser process).
> 
> BUG=557798
> CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.win:win10_chromium_x64_rel_ng
> 
> Committed: https://crrev.com/df585142df9fd58299ef02b64da3381d8b733cb8
> Cr-Commit-Position: refs/heads/master@{#409264}

TBR=wfh@chromium.org,robertshield@chromium.org,nick@chromium.org,bradnelson@c...
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=557798
==========

to

==========
Revert of [Windows Sandbox] Turn on MITIGATION_EXTENSION_POINT_DISABLE.
(patchset #6 id:200001 of https://codereview.chromium.org/1854323002/ )

Reason for revert:
Reverting the "on switch" temporarily.  Want to look at the scope/details of
broken IMEs more before re-landing.  What percentage of Chrome IMEs are actually
still using legacy hooking techniques to inject DLLs into our processes?  

Ref: https://bugs.chromium.org/p/chromium/issues/detail?id=634192

Original issue's description:
> [Windows Sandbox] Turn on MITIGATION_EXTENSION_POINT_DISABLE.
> 
> This CL is part of a chain of CLs:
> 1) "MITIGATION_EXTENSION_POINT_DISABLE support for children"
(https://codereview.chromium.org/1835003003)
> 2) "MITIGATION_EXTENSION_POINT_DISABLE emergency off finch"
(https://codereview.chromium.org/1836523004/)
> 3) "New NT registry API" (https://codereview.chromium.org/1841573002)
> 4) "Early browser security support"
(https://codereview.chromium.org/1656453002)
> -> THIS
> 
> This CL only turns on the new mitigation (in all child processes, and early
for the browser process).
> 
> BUG=557798
> CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.win:win10_chromium_x64_rel_ng
> 
> Committed: https://crrev.com/df585142df9fd58299ef02b64da3381d8b733cb8
> Cr-Commit-Position: refs/heads/master@{#409264}

TBR=wfh@chromium.org,robertshield@chromium.org,nick@chromium.org,bradnelson@c...
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=557798
==========

[commit-bot: I haz the power, 2016-08-08 03:02:44]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-08-08 03:05:19]

Description was changed from

==========
Revert of [Windows Sandbox] Turn on MITIGATION_EXTENSION_POINT_DISABLE.
(patchset #6 id:200001 of https://codereview.chromium.org/1854323002/ )

Reason for revert:
Reverting the "on switch" temporarily.  Want to look at the scope/details of
broken IMEs more before re-landing.  What percentage of Chrome IMEs are actually
still using legacy hooking techniques to inject DLLs into our processes?  

Ref: https://bugs.chromium.org/p/chromium/issues/detail?id=634192

Original issue's description:
> [Windows Sandbox] Turn on MITIGATION_EXTENSION_POINT_DISABLE.
> 
> This CL is part of a chain of CLs:
> 1) "MITIGATION_EXTENSION_POINT_DISABLE support for children"
(https://codereview.chromium.org/1835003003)
> 2) "MITIGATION_EXTENSION_POINT_DISABLE emergency off finch"
(https://codereview.chromium.org/1836523004/)
> 3) "New NT registry API" (https://codereview.chromium.org/1841573002)
> 4) "Early browser security support"
(https://codereview.chromium.org/1656453002)
> -> THIS
> 
> This CL only turns on the new mitigation (in all child processes, and early
for the browser process).
> 
> BUG=557798
> CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.win:win10_chromium_x64_rel_ng
> 
> Committed: https://crrev.com/df585142df9fd58299ef02b64da3381d8b733cb8
> Cr-Commit-Position: refs/heads/master@{#409264}

TBR=wfh@chromium.org,robertshield@chromium.org,nick@chromium.org,bradnelson@c...
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=557798
==========

to

==========
Revert of [Windows Sandbox] Turn on MITIGATION_EXTENSION_POINT_DISABLE.
(patchset #6 id:200001 of https://codereview.chromium.org/1854323002/ )

Reason for revert:
Reverting the "on switch" temporarily.  Want to look at the scope/details of
broken IMEs more before re-landing.  What percentage of Chrome IMEs are actually
still using legacy hooking techniques to inject DLLs into our processes?

Ref: https://bugs.chromium.org/p/chromium/issues/detail?id=634192

Original issue's description:
> [Windows Sandbox] Turn on MITIGATION_EXTENSION_POINT_DISABLE.
>
> This CL is part of a chain of CLs:
> 1) "MITIGATION_EXTENSION_POINT_DISABLE support for children"
(https://codereview.chromium.org/1835003003)
> 2) "MITIGATION_EXTENSION_POINT_DISABLE emergency off finch"
(https://codereview.chromium.org/1836523004/)
> 3) "New NT registry API" (https://codereview.chromium.org/1841573002)
> 4) "Early browser security support"
(https://codereview.chromium.org/1656453002)
> -> THIS
>
> This CL only turns on the new mitigation (in all child processes, and early
for the browser process).
>
> BUG=557798
> CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.win:win10_chromium_x64_rel_ng
>
> Committed: https://crrev.com/df585142df9fd58299ef02b64da3381d8b733cb8
> Cr-Commit-Position: refs/heads/master@{#409264}

TBR=wfh@chromium.org,robertshield@chromium.org,nick@chromium.org,bradnelson@c...
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=557798

Committed: https://crrev.com/406b433e8b3468b8c252a552119c0d65c7be874f
Cr-Commit-Position: refs/heads/master@{#410293}
==========

[commit-bot: I haz the power, 2016-08-08 03:05:21]

Patchset 1 (id:??) landed as
https://crrev.com/406b433e8b3468b8c252a552119c0d65c7be874f
Cr-Commit-Position: refs/heads/master@{#410293}