►
From YouTube: SES Meeting: Import Reflection, WASM, and CSP
Description
Discuss the relationship of CSP (Content Security Policy) with the compilation and instantiation of WASM and ESM Import Reflection.
A
B
B
B
B
B
B
B
B
B
B
B
B
B
B
B
B
C
B
C
B
B
B
C
C
C
B
Guy
bedford:
that
it
was
during
the
check,,
so
both
checks
are
still
only
compilation,
checks,
and
therefore
there's
only
one
check,
which
is
a
compilation
check
right,
now.,
but
potentially
we
might
still
need
2
checks.
As
we
discussed
some
of
these
fine
grand
things.,
that's
yeah,
okay,,
it's
very
interesting.
B
B
B
B
B
B
B
C
Mark
s.
miller,
(mm,
agoric):,
I'm
guessable.,
guy
bedford:
and
therefore
knowledge
of
the
nonce
is
proof
of
legitimate
authority..
Exactly
the
problem
with
the
nonce
is
that
once
once
it's
done,
any
monitor
in
the
graph
is
allowed
to
load
anything
else..
So
you
don't
get
the
checks
down
the
module
br.
B
B
C
A
A
B
B
B
B
B
B
B
B
B
B
B
B
B
B
B
B
C
B
C
C
C
C
C
C
C
C
B
B
B
B
C
C
C
C
C
C
C
C
C
C
C
B
A
A
A
A
C
C
C
C
B
C
C
C
D
D
A
A
A
A
A
C
A
C
C
A
D
C
A
A
B
B
B
C
C
C
C
C
A
B
B
B
B
A
C
C
C
C
A
C
C
C
C
B
B
B
B
B
B
A
C
B
C
C
C
C
C
B
B
C
C
C
C
C
B
B
A
A
C
C
C
C
C
C
C
A
A
A
A
B
B
B
C
C
A
C
C
C
C
B
B
D
A
A
Mathieu
hofman:,
something
that
was
fetched.
mathieu,
hofman:
and
pass
the
unsafe
eval,,
and
if
it
wasn't
meanwhile,
or
something
that
was
import,
sourced,
and
and
then
end
up
having
a
different
behavior,.
I
think
those
2
things
should
end
up
being
the
same
thing..
So
we
may
be
constrained
there
into.