►
From YouTube: Install "Hardware Wallet" for Consortium Blockchain -- Protect Hyperleger Fabric... - Mengzhe Yang
Description
Join us for Kubernetes Forums Seoul, Sydney, Bengaluru and Delhi - learn more at kubecon.io
Don't miss KubeCon + CloudNativeCon 2020 events in Amsterdam March 30 - April 2, Shanghai July 28-30 and Boston November 17-20! Learn more at kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects
Install "Hardware Wallet" for Consortium Blockchain -- Protect Hyperleger Fabric Node Private Keys with Intel SGX - Mengzhe Yang, Alibaba
Blockchain is a technology that uses a lot of cryptography. How to protect the security of core keys is a challenge that this technology always faces. Hyperledger Fabric supports using HSM to protect node keys, but this heterogeneous hardware has the problems of high cost and difficulty in deployment. We have explored a key protection scheme based on Intel SGX technology. We believe that this hardware security solution, which will be built into all Intel CPUs, is ideal for protecting node private keys in consortium blockchain and is also worth applying and promoting through open source technologies. The speech is mainly divided into three parts: 1. Introduce modifications of golang encryption library. 2. Introduce how to bridge the Fabric blockchain and Enclave by implementing Fabric's plugin bccsp module. 3. Introduce why we choose plugin bccsp in BaaS scenario.
https://sched.co/Nrvd
B
A
What
is
how,
where
wallet,
so,
let's
use
blockchain.
How
well
wallet
is
an
example.
We
know
that
the
most
important
seafood
blocking
wallet
is
private
key
and
we
need
to
have
a
hardware
to
protect
the
private
key.
So
maybe,
when
people
have
wallets,
they
have
a
lot
of
coins
or
they
paid
a
lot
attention
to
security.
So
there
are
several
steps.
The
first
step
is
that
you
need
to
put
the
private
key
into
the
wallet.
More
accurate
description
is
that
the
private
key
will
never
go
out
of
the
wallet.
A
B
A
Key
will
be
generated
by
the
wallet
and
when
you
are
doing
countries
a
transaction
with
blockchain,
you
need
to
have
a
signature
and
the
whole
transaction
process
after
you
do
the
transaction.
You
need
to
send
a
request
for
signature
and
internally,
the
quality
needs
to
calculate
about
the
signature
script
and
throughout
the
process
the
Bitcoin
will
be
in
a
very
secure
stage.
You
don't
need
to
worry
about
any
theft
or
any
virus
that
will
attack
your
wallet
in
the
consortium.
Blockchain.
A
If
we're
using
have
a
large
enough
average
is
an
example.
So
every
consortium
notes
will
have
private
key,
for
example,
for
pure.
It
needs
to
do
the
endorsement
after
every
transaction
for
our
and
needs
to
have
an
signature
of
the
transaction,
no
matter
for
peer
or
other
private
key.
It
will
reflect
the
authority
or
identity
which
are
essential
for
the
consortium.
This
is
also
something
we
want
to
protect
the
private
key
of
the
users.
A
A
Operations
will
be
encrypted
before
putting
on
the
CPU.
If
you
trust
the
Intel
CPU,
those
codes
will
be
encrypted,
so
it
can
play
the
role
of
how,
where
what
it
for
us.
So
our
goal
is
that
want
to
use
SGX
technology
to
protect
fabric.
Note
private
key,
so
we
gone
through
two
solutions
and
three
steps
to
achieve
that.
When
we
look
back
on
this,
the
first
one
is
about
the
public
part,
because
we
need
to
prepare
the
SGX
environment,
including
software
library
and
related
Intel's,
live
and
drives
also
needs
to
have
internal.
A
A
B
A
B
B
A
B
The
inside
of
the
garden,
we
are
rolling
it.
We
need
two
interfaces
to
be
realized
now.
This
will
be
very
easy
because
we
can
use
the
algorithm
of
the
open
classes
to
do
a
very
simple
in
packaging
encapsulation,
so
as
to
generate
the
interface
for
private
key
generation
role
and
also
for
the
private,
acknowledging
signature
interface.
Normally,
it
is
the
same,
although
they
include
in
the
renewal
term.
We
need
to
have
some
impact
encapsulation
of
the
open,
ssl
interface.
B
B
B
B
B
B
So
from
this
we
can
make
a
comparison
with
the
previous
one.
The
obvious
difference,
for
example,
is
if
you
have
a
look
at
this
interface
if
to
get
a
public
key
from
the
private
key
for
the
original
interface.
What
the
arsenic
is
a
key
which
is,
and,
for
example,
for
the
signature
interface,
it
is
inputting
some
like
private
keys
or
parameters,
so
that
means
interface.
This
interface
are
relying.
B
The
decoupling,
oh,
that
will
not
help
on
the
decoupling,
so
that
is
why
we
have
done
some
modifications.
If
there
is
an
interface
which
is
relying
or
have
some
dependence,
we
will
just
modify
it
into
the
plug-in
BC
CPPCC
SP
interface.
So
with
this
we
can
say
that
the
data
structure
of
the
BCC
SPE
is
consistent
of
the
key
data
structure
and
that
will
help
us
to
realize
a
total
plug-in
in
PS
s
CP
into
this.
B
A
B
Is
when
the
interface
has
been
consistent,
the
following
things
will
be
very
similar
to
the
proposal.
One
is
in
the
BBS
BC
CSP
we
going
to
have
the
like
generation
of
the
public,
probably
keys
the
signature
by
private
keys
and
then
there
and
a
private
key
to
get
the
public
key
interface,
so
others
interface
has
been
realized
and
well
implementing
this
interface.
We
will
redefine
the
related
logics
in
to
the
SD
x
and
Claver,
that
is
the
hardware
wallet
environment
and
then
the
private
key
in
that
wallet
can
help
generate
the
private
key.
B
So
that
means
the
private
keys
is
fixed
in
the
wallet
and
for
the
also,
this
allowed
to
instill
some
private
keys
into
the
wallet
and
for
the
signature,
travel
keys.
The
signature
will
be
generated
by
in
the
wallet
so
as
for
the
private
key
not
to
be
disclosed
program,
the
wallet.
So
after
doing
that,
we
can
carry
over
some
of
the
steps
in
proposal,
one
like
the
generation
of
the
private
keys
and
the
sealing
of
the
private
keys
sealing
of
private
keys.
B
It
means
that
if
you
want
to
have
a
private
key
durable,
you
can
have
a
cell
interference
from
STX
and
then
you
will
get
a
encrypted
result.
So
the
result
can
only
be
the
coded
of
the
cryptic
cryptid
in
the
same
computer
or
in
the
same
CPU,
and
then
the
following
steps
will
be
similar
to
the
proposal.
One.
A
A
A
That's
why
I
wanted
to
be
an
optional
configuration.
That
means
an
overall
we
will
hunt,
we
can
have
on
a
set
of
codes,
a
set
of
mirrors
or
fabric,
and
while
we
are
doing
the
deployment
or
user
triggered
blockchain
deployment
according
to
different
configurations,
we
will
determine
whether
we
need
to
turn
on
the
powers
wallet
logic
if
we're
choosing
the
option,
one
by
modifying
the
goal-line,
it's
very
difficult
to
transfer
the
public
key
through
the
existing
port.
A
A
A
So
our
platform
can
provide
an
Aikido
bility
where
the
user
can
provide
customized
to
include
solutions,
they
can
create
their
own
hardware
wallet
and
then
they
can
use
their
own
private
key
signature
to
upload
it
on
the
cloud.
That
means
the
user
has
completely
control
of
the
hardware
wallet,
although
for
the
physical,
physical
machines
and
the
cloud
is
controlled
by
us,
but
as
long
as
the
enclaved
mechanism
has
no
security
issues
and
we
have
no
way
touch
upon
on
the
coordinator
where
the
users
has
put
on
a
cloud
that
means
the
user.
A
B
A
B
A
B
A
We
can
only
generate
the
key
ones,
because
we
have
only
one
interface
when
we
have
the
bridge
from
fabric
to
the
inch
house
as
years,
so
the
key
is
generated
only
once
and
then
it
will
be
put
in
in
clave.
So
we
are
calling
that
key
every
time
when
we
are
using
that,
but
we
cannot
have
a
rotation
of
the
private
key
right.
You
understand
is
correct
in
fabric.
B
A
A
A
A
B
A
Fabric
is
not
doing
acute
issues,
it
has
an
IMAX
reload.
You
can
add
additional
outlet
for
the
key
rotate
if
you
have
rotate
the
key
and
it
can
load
the
key
I
think
they
have
already
done
that
in
1.4
version,
but
I'm
not
sure
about
at
this.
If
they
are
doing
that
with
version
1.4.
That
would
be
okay.
Second
question
is
I
understand
that
only
tongue
thing
can
use
Intel
SGX.
Yes,
as
I've
said,
because,
as
judge
she
has,
the
support
of
virtualization
is
not
so
good.
Now.
A
B
A
B
B
A
Is
the
peer
running
actually
for
Chinon
servers
for
bare
metal?
They
wouldn't
have
the
migration
of
the
service.
You
will
always
be
running
on
the
same
CPU
when
you
have
multiple
core
on
the
same
CPU.
My
this
is
my
personal
understanding
when
they
are
sharing
one
as
she
has
environment,
they
can
all
decrypt
the
sealed
thing.
So
if
it
is
not
migrated,
I
cannot
stand.
It
I
think.
If
that
my
grace
it.
A
B
A
B
B
B
A
A
A
Now
we
don't
have
authentication
mechanism.
The
main
reason
for
that
is
that
for
the
player
deployment
the
fabric
software
can
call
sign
a
times.
It's
not
easy
to
do
some
good
authentication
about
the
environment.
It
is
really
a
hardware
wallet.
Normally,
it
will
have
fingerprint
or
ping
code
to
access
that.
A
B
A
B
A
A
A
B
B
A
It's
like
and
I'm
private
key
input
export
between
two
decrypted
machines.
We
can
send
the
result
there
so
during
the
transport,
there's
no
open
message
and
the
process
of
recovering
that
the
same
so
we're
going
to
generate
an
public
key,
so
hsm
can
and
decrypt
that
that
and
for
the
local
and
clave
you
need
to
decrypt
their
private
key
and
then
use
the
proper
way
to
put
that
into
a
local
Drive.
So
the
whole
transfer
process
is
utilizing
an
additional
device
for
the
decryption
so
that
the
product
key
can
be
circulated
between
these
powers.