Commit 056f9005 authored by Tom Sepez's avatar Tom Sepez Committed by Commit Bot

Disable WebAssembly in proxy_resolver_v8.cc

Removes some potential attack surface since wasm isn't expected
as part of proxy resolution.

Change-Id: I82b6519a3d60a5577796fe0627f5750234032849
Reviewed-on: https://chromium-review.googlesource.com/c/1321578Reviewed-by: default avatarJochen Eisinger <jochen@chromium.org>
Commit-Queue: Tom Sepez <tsepez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#606073}
parent 26141200
...@@ -385,6 +385,11 @@ class SharedIsolateFactory { ...@@ -385,6 +385,11 @@ class SharedIsolateFactory {
static const char kNoOpt[] = "--noopt"; static const char kNoOpt[] = "--noopt";
v8::V8::SetFlagsFromString(kNoOpt, strlen(kNoOpt)); v8::V8::SetFlagsFromString(kNoOpt, strlen(kNoOpt));
// WebAssembly isn't encountered during resolution, so reduce the
// potential attack surface.
static const char kNoExposeWasm[] = "--no-expose-wasm";
v8::V8::SetFlagsFromString(kNoExposeWasm, strlen(kNoExposeWasm));
gin::IsolateHolder::Initialize( gin::IsolateHolder::Initialize(
gin::IsolateHolder::kNonStrictMode, gin::IsolateHolder::kNonStrictMode,
gin::IsolateHolder::kStableV8Extras, gin::IsolateHolder::kStableV8Extras,
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment