►
Description
A video from the Study Circle session hosted by Hyperledger Sweden on August 22, 2020 featuring Roland Bole speaking about enabling TLS in Hyperledger Fabric.Github Link: https://samlinux.at/blog/fabric-06/ More about the Study Circles are at: https://www.meetup.com/Hyperledger-Sweden/
----
Hyperledger – Open Source Blockchain Technologies
Hyperledger is an open source community focused on developing a suite of stable frameworks, tools and libraries for enterprise-grade blockchain deployments.
It serves as a neutral home for various distributed ledger frameworks including Hyperledger Besu, Fabric, Sawtooth, Indy, as well as tools like Hyperledger Avalon, Cactus and libraries like Hyperledger Aries, Ursa. Learn more about Hyperledger projects: https://www.hyperledger.org/use
Case Studies: https://www.hyperledger.org/learn/case-studies
Training & Certification: https://www.hyperledger.org/learn/training
Tutorials: https://www.hyperledger.org/use/tutorials
Webinars: https://www.hyperledger.org/learn/webinars
Events: https://www.hyperledger.org/events
Vendor Directory: https://www.hyperledger.org/use/vendor-directory
Subscribe to the Hyperledger Newsletter: https://www.hyperledger.org/newsletter
Follow-us on Twitter @Hyperledger
Learn about Hyperledger Membership: https://www.hyperledger.org/about/join
#Hyperledger #HyperledgerMeetups #Blockchain
A
A
What
we
would
like
to
do
today,
as
some
of
you
know
that
we
have
a
larger
example,
so
there's
a
consortium
called
sunshine.com
and
in
the
last
session
we
have
did
some
work.
We
have
created
a
basic
consortium
and
today
we
are
going
to
extend
this
consortium
with
tls
and
I
will
give
you
some
theoretical
background.
A
high
level
overview,
what
is
tls
and
which
kind
of
methods
are
can
be
used.
A
We
have
a
one-way
tls,
that's
the
normal
tls,
which
you
also
know
from
your
browser
when
you
serve
in
the
internet
and
you
use
https
protocol
to
send
secure
or
to
self
secure
on
the
internet,
and
the
second
way
is
the
two
way
tls
and
also
known
as
mutual
tls,
and
I
will
show
you
the
difference
between
these
both
metals
and
favorite,
candle
and
fabric
in
favorite.
You
can
use
both
methods
and
we
will
see
how
we
can
extend
our
existing
network
with
this
level
of
security
and
because
of
that
that
we
are
using
cryptogram.
A
And,
of
course,
in
the
end,
I
will
show
you
the
practical
implementation
of
this
tls
example
and
how
we
can
extend
our
network
with
this
and
and
then,
as
I
have
mentioned,
also
for
the
next
session
we
will
have.
I
hope
it
will
be
a
guest
speaker
and
this
guest
speaker
will
tell
us
a
little
bit
about
the
raft
ordering
system.
So
I
hope
that
will
be
and
yeah
we
will
see
next
week.
We
will
hear
really
interesting
stuff
about
the
raft
ordering
system
okay.
A
So
what
about
tls
tls
stands
for
transport
layer,
security
and
ferric
supports
two
kind
of
methods
to
communicate
between
with
two
kinds
of
methods.
You
can
secure
the
communication
between
the
beer,
another
beer,
the
orderer
and
also
the
clients
with
interact
with
the
system
and,
as
I
have
mentioned,
we
have
the
one-way
tls
version.
A
A
So
it's
a
little
bit
complicated
than
here
in
the
in
the
in
the
picture,
but
I
think
we
can
understand
with
this
the
main
difference
between
the
one
way
into
two-way
tls.
So
we
can
see
the
client
sent
a
message.
The
client
says
hello
and
then
the
certificate
and
the
public
key
in
the
certificate
is
also
the
public
key
will
send
to
the
client
and
the
client
checks.
Is
this
certificate
valid
with
a
number
of
certified
authorities
in
the
browser?
A
Your
browser
knows
knows:
certificate
authorities
and
checks
if
there's
a
valid
certificate,
and
if
this
is
true,
there
is
a
key
validation.
Some
key
validation,
because
tls
is
a
mix
of
symmetric
and
asymmetric
encrypted
encryption
methods,
and
there
is,
when
you
want
to
know
more
about
this
casey
wrote
published
this
week
a
very
interesting
article.
A
I
can
show
you
the
link
later,
and
this
is
really
interesting
and
you
can
read
a
lot
of
more
about
the
history
of
tls
and
how
the
things
work
together.
So
that's
really
good
article
and
I
recommend
to
read
this
article.
If
you
want
to
know
more
about
the
tls
and
then
we
have
encrypted
data,
but
the
main
thing
here
is
that
the
client
doesn't
have
any
key
store.
Declined,
doesn't
have
any
certificate
or
private
key.
Only
the
server
has
this
and
declined
only
looks
okay.
Is
this
a
valid
certificate?
A
The
server,
and
can
I
trust
this
server
from
the
server
side?
From
the
sorry
from
the
server
side,
there
is
no
control
about
the
client,
so
the
server
cannot
say
in
this
in
the
one-way
tls
that
the
client
belongs
to
this
certified
authority
and
has
a
valid
certificate
and
that's
basically
how
the
one
way
tls
works
and
yeah,
and
the
two-way
certificate
does
basically
the
same.
A
A
So
in
this
scenario,
with
the
two-way
tls
or
mutualist,
we
can
say
that
the
client
this
the
server
knows
something
about
the
client
and
the
client
knows
something
about
the
server
and
when
bo.
When
both
say,
okay,
we
are
from
the
same
certified
authority.
We
trust
the
the
issuer
from
the
certified
authority.
A
Then
we
have
a
valid
communication
and
we
have
a
secure
communication,
so
I
have
here
a
sentence,
so
the
main
intent
to
use
a
two-way
tls
connection
is
when
a
server
should
only
accept
tls
connections
from
a
limited
group
of
allowed
clients.
So
with
this
you
can
say
only
my
members,
my
certificates,
my
members
of
the
favorite
network,
can
communicate
with
this
system,
and
for
this
we
have
a
separate
certificate.
You
can,
we
will
see
it
a
little
bit
later.
A
That's
called
a
third,
so
the
the
the
name
is
third
key
and
pop,
and
we
will
find
it
and
yeah
so
and
that's
the
difference
between
this,
both
methods
in
a
high
level.
So
when
you
see
when
you're
prepared,
the
client
has
no
key
store
in
the
first
in
the
first
version
and
declined,
the
server
can
decline
can
only
check
that
the
server
is
a
valid
server
and
I
trust
this
server.
A
A
So
these
are
the
difference
between
these
two
versions
and
when
it
comes
to
the
cryptogram
tool.
So
that's
interested
to
see
so
cryptogen
creates
all
the
crypto
material
and
creates
a
lot
of
and
different
in
a
specific
structure,
and
we
have
in
this
tree
in
this
folder
tree.
We
have
two
leaves
one
is
the
order
of
our
organization,
and
one
is
the
peer
organization
and
in
the
in
the
other
organization
you
have.
You
will
see
in
our
structure
this
this
this
folder
structure,
so
we
have
other
organizations.
A
So
this
is
our
certified
authority
for
tls
and
in
general
you
can
say
you,
you
have
a
certified
authority
for
tls
and
you
have
a
certified
authority
for
the
order
organization
and
or
for
the
organization
and
for
their
member.
So
for
the
tls,
you
have
always
a
own
certified
authority
and
this
certified
authority
issue
certificates
only
for
the
tls
process.
So
in
our
scenario,
we
have
only
one
order,
so
the
order
of
sunshine.com-
and
here
we
have
in
this
in
the
structure-
tls
folder,
the
tls
folder-
and
there
we
have
three
files.
A
We
have
the
server
tab,
we
have
a
server
key
and
we
have
a
ca,
dot,
cert
file,
and
it's
the
same
as
here
so
the
cryptogen
copies
this
certificate
in
every
in
in
a
lot
of
different
folders.
So
therefore
here's
the
same
color
and
this
certificate,
tlsca
samsung.com
search
pam-
is
the
same
like
this.
So
when
we
configure
our
system
for
tls,
then
we
can
use
this
one
for
the
order
or
this
one.
A
So
it's
the
same
and
later
I
will
show
you
how
you
can
inspect
this
with
the
open
ssl
tool,
and
then
you
can
see
it's
exactly
the
same
file
in
the
same
certificate
so
encrypt
again
copies.
Simply
this
this
certificate
and
name
it
the
c8
cell
so
and
that's
the
the
root
tls
set
for
the
order
here
and
the
the
server
third
file.
This
is
the
certificate
of
the
server,
and
in
this
certificate
we
will
have
the
public
key
and
the
signing
search
and
the
server
key.
That's
the
private
key.
A
The
private
key
will
never
send
to
any
other
position
here,
and
this
is
the
this
is,
I
think,
an
important
part
that
we
have
for
the
order.
We
have
an
order
and
and
own
order,
our
certified
authority
yeah.
We
can
find
this
in
this
structure
here
and
this
certified
authority
creates
for
every
order
here,
a
key
pair,
a
server
set
and
a
server
key,
and
when
we
see
next
week,
when
we
here
next
week
the
presentation
about
raft,
then
we
will
see
that
we
need
for
raft
more
than
one
order.
A
A
The
server
and
tear
the
server
key
here
and
the
tr
third
file
is
only
a
copy
from
this
one,
and
you
can
use
this
one
or
this
one
so
and
when
it
comes
to
the
peer
and
then
appears
scenario,
we
have
the
same
structure.
So
we
have
our
organization
anthony
on
this.
On
the
same
level,
we
have
peer
organizations
and
sorry
and
dp
organization.
A
A
This
is
our
organization,
the
order
organization
and
when
it
comes
to
the
thea
organization
we
have
here
this
is
this
is
our
pr
or
peer
organization.
When
we
have
a
second
organization
in
our
network,
then
we'll
have
to
then
we
will
have
the
same
structure
on
a
on
another
level.
So,
but
you
have
here
producer
sanction.com
and
you
have
for
this
organization,
your
own
certified
authority.
A
When
you
have
here
trading
dot
sunshine.com,
you
will
have
here
another
certified
authority
with
this
a
separate
certified
authority
for
this
organization,
but
the
the
process
is
the
same.
So
this
is
our
root
certificate
for
this
organization,
and
this
is
the
the
and
when
we
inspect
this
file,
you
will
see
that
the
issuer
is
the
same
as
the
subject.
So
the
issuer
is
always
the
the
issue.
A
I
don't
know
how
I
should
explain
this,
and
the
subject
is
the
name
of
the
of
the
owner
of
this
certificate
and
when
we
have
here
at
tls
certificate
for
the
ps0,
then
we
will.
We
can
see
that
the
issuer
is
not
equal
to
the
subject
and
the
subject
in
this
case
is
the
pseudoproducersanction.com
and
the
issuer
is
the
tlsca
producers.com
and
also
the
server
third
and
yeah,
and
the
server
key
here
is
created,
and
here
also
cryptogram
copies
the
the
root
tls
certificate
into
this
folder.
A
So
I
think
important
here
is
to
recognize
that
every
organization
order
organization
or
a
peer
organization
has
its
own
certified
certificate
authority
for
the
tls
process
and
that's
important
and
yeah,
and
the
rest
is
the
same.
As
you
can
see
here,
we
have
the
server
key.
We
have
the
chat
and
we
have
here
a
copy.
A
It
tls
wood
certificate,
and
so
this
is
the
this
is
the
structure
and
when,
when
we
want
to
enable
this,
for
example,
for
the
tls
one
one-way
version,
we
can
do
this
with
a
set
of
environment
variables
and
this
environment
various
set
in
the
docker
compose
file,
and
I
think
there
are
three
files
or
three
variables
and
one
variable
is
to
enable
tls
in
general.
So
but
the
variable
names
are
not
the
same
so
in
for
order
we
have
for
order.
A
A
And
we
have
here
the
private
key,
the
tls
certificate
and
the
root
tls
certificate,
and
these
are
the
three
files
I
have
shown
you
previously
and
for
this
three
variables
we
have
to
set
a
path
to
the
server
key
to
the
server
third,
and
also
to
the
ca
third,
and
you
have
to
do
it
in
a
full
qualified
path.
So
that's
maybe
something
I
would
like
to
to
note.
So
that
means
that
that's
an
absolute
path
and
not
a
relative
path.
So
a
absolute
path
in
in
the
linux
environment
starts
with
the
slash.
A
A
So
so,
and
this
must
be
full
qualified
parse
so
and
that's
it.
So
I
think
that's
clear
and
for
the
appears
we
have
the
same,
but
but
the
name
is
a
little
bit
different,
so
the
name
is
co-appear
tls
enabled
co-appear
tls
key
file
and
cooperate
listed
file
and
so
on
so
but
the
the
meaning
is
the
same.
So
the
key
file
is
the
server
key
here
and
the
third
file.
This
is
the
private
key
yeah
and
the
server
third
is
the
certificate
with
the
public
key
and
the
signing,
charts
included
and
yeah.
A
It
could
also
be
an
away
and
it's
the
crt
file
so
encrypt
again,
as
I
mentioned,
copied
these
three
files
in
one
order
in
one
folder,
and
that
makes
it
easy
to
link
to
this
position
and
also
when
you
have
distributed
the
network.
So
in
our
scenario,
we
have
one
machine
and
every
docker
container
runs
on
the
same
machine
and
have
access
to
the
same
crypto
game
folder.
So
that's
that's.
That's
easy
to
link
all
our
files
and
and
and
and
organizations
and
peers
to
this
cryptogen
folder.
A
But
when
it
comes
to
a
decentralized
system
when
you
have,
for
example,
a
docker
swarm
system
and
you
use
the
overlay
network
and
you
have
one
peer
in
data
center
a
and
the
second
b
and
a
data
center
b,
then
you
don't
have
the
crypto
folder
on
the
same
place.
So
then
you
have
to
copy
the
crypto
folder
to
the
proper
location
and
maybe
for
that
they
they
copied
all
three
files
on
the
same
position.
A
A
Maybe
you
have
a
no
you
when
you
have
your
nodejs
application
and
you
try
to
connect
to
appear
with
the
nodejs
application,
then
you
need
also
a
client
from
there
from
the
certified
authority
and-
and
these
are
from
from
the
type
user
are
client
and
the
beer
is
clear,
that's
their
the
peer
nodes
and
for
the
other
rights
the
same.
There
are
two
environment
variables
and
also
a
general
environment.
Very
able
to
enable
this
this.
A
Here's
an
example
for
the
chain
code
invoke
command
when
we
say
here
that
we
have
here,
the
tls
enabled
so
it's
done
with
this
option,
and
then
here
we
have
the
the
ca
file
here
and
then
we
have
the
declined
out.
Yeah.
The
client
out
is
true
here
and
we
have
the
key
file
and
we
have
this
search
file.
So
when
one
way
or
two-way
tls
is
enabled.
A
Then
you
have
to
use
this
environment
variables
in
different
kind
of
ways.
When
you
have
the
cla
version,
then
you
have
to
do
it
in
this
way.
When
you
use
the
node.js
version
to
connect
to
invoke
or
create
some
data,
then
you
have
to
do
it
in
a
little
bit
a
different
way.
So,
but
that
comes
with
with
sn
as
an
maybe
as
an
overhead
for
the
cli
version.
A
A
And
then
we
can
try
to
switch
between
these
two
types
of
user
users,
and
then
we
will
see
that
when
we
change
that
they
have
the
user,
one
has
an
as
another
client
certificate.
Then
the
admin
user,
so
of
course,
but
the
this
is
important
to
know
that
every
client
has,
of
course,
its
own
set
its
own
tls
certificate
and
its
own
tls
private,
key
yeah.
But
okay
so
and
that's
also
important
part.
You
have
to
know
that
only
when
you
invoke
something
with
the
order.
A
You
have
to
use
this
tls
variables
and
client
out
variables.
But
when
you
query
your
peer
from
the
cli
yeah,
you
don't
have
to
use
it,
so
we
can
test
it.
So
we
can
only
say
when
we
query,
because
we
query
the
peer
which
we
are
belongs
to
through
the
environment
variables
which
are
set
when
we
create
the
cli
here.
A
A
A
A
A
The
tls
enabled
environment
variable
for
the
peer,
and
here
are
these
certificate,
and
you
see
the
paths
here
to
the
server
search,
server,
key
and
tls,
and
you
see
these
paths
doesn't
look
like
that.
They
belongs
to
the
crypto
game
program
so
and
that's
the
the
basic
structure
where,
where
the
peer
looks
for
this
tls
certificate
and
we
mount
when
we
look
here
when
we
see
here
it
appears
zero.
A
So
we
have
here
a
mount
point.
So
under
the
volume
section
so
here
we
mount
this
yeah.
So
it's
basically
the
same.
What
we
have
done
for
the
membership
service
provider
folder.
So
from
the
from
the
viewpoint
from
the
beer
the
structure
is,
is
the
same,
so
you
have
etc
hyper
electro
fabric
part,
and
there
is
a
msp
and
tls
folder
and
we
mapped
this
with
our
cryptogram
further.
A
So
and
here
you
can
see
so
we
have
pier
0
yeah
and
the
crypto
config
path
is
something
like
we
have
seen
in
the
picture.
So
we
have
to
be
your
organization.
We
are,
we
are
in
the
producer
sunshine.com,
we
have
different
beers,
so
we
pick
beer
zero
and
be
a
serum.
We'll
have
a
tls
certificate
so
and
we
can
check
if
this
is
true.
So
when
we
look
in
this
cryptoconfig.
A
A
This
mount
point
here
mounts
the
tls
files
to
this
location
and
in
the
pbase
command.
We
see
here
the
final
destination
from
the
files
and
they
are
mounted
here.
So
you
cannot
say
you
cannot
give
here
the
crypto
config
park
path
from
the
crypto
config,
because
the
crypto
config
path
doesn't
exist
in
into
the
pier
so
and
that's
the
reason
why
we
have
to
do
this
in
this
way
so
and
that's
important,
so
we
mount
the
tls
folder
and
it
doesn't
matter
where
this
tls
files
are
stored.
A
And
and
that's
for
all
these
files
so
and
yeah,
if
you
did
the
server
cell,
the
key
file
and
the
cfl,
and
now
you
can
see
so
it's
pretty
easy
when
cryptogen
a
copies.
The
wood
tls
certificate
in
the
same
folder
structure
and
the
only
thing
we
have
to
do
is
we
name
this
file
here
and
then
we
have
a
proper
path
to
the
wood
setup.
So
that's
pretty
fine,
and
the
same
is
for
the
two
two-way
tls.
A
So
we
have
to
set
for
the
client
this
client
out
required
wherever
to
true,
and
then
we
have
to
set
this
server
setup
and
a
server
key
file
as
well.
So
and
as
you
see,
these
are
the
same
files
for
this
one
and
for
the
authorized
the
same
so
and
we
have
here
the
order.
The
tls-
and
you
see
here
this
the
example
with
the
with
the
aoa.
A
So
we
can
have
here
more
than
one
good
certificate
and
so
that's
sent
away
and
the
system
is
the
same.
Only
the
the
environment,
where
evils
have
a
little
bit
different
name.
So
yeah,
that's
the
only
difference
here,
but
also
for
the
order.
We
have
mounted
this
folder
here:
here's
the
crypt
again
auto
organization
sunshine.com
order
us
this
is
the
other
one
water
assumption.com
and
has
a
tls
folder,
and
this
folder
is
mounted
to
this
standard
position
here
to
the
standard
structure.
A
And
then
we
can
make
the
same,
so
we
have
also
here,
but
here
notice-
that
here
is
the
order
and
not
and
not
the
parts
a
little
bit
different,
but
this
is
also
the
standard
path
and
you
see
here
it
is
a
hyperledger
favorite
and
your
wow
hyperletter
ottawa.
So
that's
a
little
bit
different
power
for
this
and
to
enable
two-way
tier
less
it's
the
same
here.
A
A
A
A
So,
okay,
we
have
a
channel
name
and
we
have
a
tls
order,
a
ca
path
so
yeah
and
we
can
this
export
in
our
peer
container.
So
yeah,
please
note
the
printf
command,
and
so
here
with
the
core
yeah
when
we
grab
this
with
the
core.
So
we
see
these
specific
environment
variables
which
are
set
so
here
also
ps0
cli,
you
know,
tls
is
enabled
and
so
on
so
client
how
to
require
this
also
enable
it
and
the
channel
okay.
A
A
A
A
A
A
A
A
And
then
we
have
to
install
the
chain
code,
so
we
go
back
to
the
p0
and
then
we
install
the
chain
code.
It's
the
same
train
code
like
last
week
so-
and
you
see
here
on
this
command,
it's
the
same
command.
There
is
no
tls
information
because
we
install
this
chain
card
on
this
spear,
so
nobody
else
is
involved
in
this
process.
So
we
don't
need
tillers.
A
And
you'll
see
everything
should
work,
then
we
can
switch
to
the
second
here
and
we
we
do
also
the
install
command.
So
when
we
have
in
our
scenario,
we
have
one
organization.
We
have
two
peers
and
we
want
that.
Both
beers
are
endorsement
beers.
Then
we
have
to
install
on
both
piers
our
chain
crop,
but
we
only
have
to
instantiate
the
chain
code
once
so.
When
we
add
a
third
pier
we
can
it,
it
doesn't
make
sense
to
instantiate
the
the
the
the
chain
code
again
because
we
have
channel.
A
A
Okay!
So
now
we
have
the
ampere
one.
So,
okay,
here
we
have
a
in
this
instantiation
in
this
instantiation
we
have
also
for
our
first
transaction
was
is
done,
and
this
is
the
the
key
message
one
and
now
we
are
on
p2
so
and
we
can
query
now
so
for
the
we
can
query
disappear,
one
and
you
see
okay,
hello,
so,
and
but
we
don't
have.
A
A
A
A
A
A
So
the
admin
yes
so
and
of
course
we
need
this
admin
user,
because
only
the
the
admin
user
has
the
proper
rights
to
create
the
trender
and
install
train
code.
But
a
normal
invoke
transaction
or
a
query.
Transaction
can
also
be
done
by
by
another
user
so
and
not
not
for
the
admin
user.
So
we
can
change
this
as
well
so
and
but
when
we
do
this,
we
have
also
to
change
the
decline
key,
but
I
will
we
will
do
it
in
two
ways.
A
A
A
A
And
you
see
here,
this
is
the
ottawa
server
certificate
and
you
see
here
the
wood
certificate.
The
issuer
is
the
tlsca
sanction.com,
but
the
subject
has
an
other
common
name.
So
cn
stands
for
common
name
and
it's
the
order
of
sanctions.com
so
and
this
certificate
is
the
certificate
from
the
subject
from
the
ordersanction.com
and
this
certificate
belongs
to
this
root
certificate.
A
A
And
you
see
the
issuer
yeah
and
you
see
the
subject
so
then
the
issue
a
common
name
and
the
subject
common
name
is
the
same.
Then
we
will
have
a
self-signed
certificate
and
yeah
so
and
that's
maybe
not
the
best
form
that
when
it
comes
to
security,
so
here
it
must
be
another
certificate
from
other
root.
Ca.
A
A
and
you
have
here
for
every
organization,
a
tls
certificate,
and
so
that's
that's
an
important
part
and
and
that
you
will
have
for
every
organization
for
for
the
order
organization
and
for
the
normal
organizations.
You
have
a
single
certified
authority,
which
is
only
responsible
for
tls
and
cryptogen.
A
A
I
think
this
question
depends
on
your
business
so
and
but
the
I
think,
the
most
most
times
one
way
tls
is
used,
and
but
you
have
seen
you
can
easily
extend
or
increase
your
security
with
these
two
way:
tls
here,
okay
and
for
the
auto,
it's
the
same
yeah
notice
that
you
have
different
names,
different
variable
names
here,
the
order
of
tls
yeah
and
the
client
authentication.
So
so,
if
you
want
normal
tls,
you
don't
need
the
two-way.
So
you
can.
You
are
good
to
go
only
with
a
one-way
tls.
A
It
only
works
and
when
you
are
do
prototyping
and
you
have
a
solo
order
and
you
have
oil
on
the
same
machine,
then
I
think
you
don't
need
tls,
it's
my
opinion,
because
nobody
has
access
to
your
traffic
on
your
own
machine
on
the
same
host
and,
of
course,
in
the
docker,
the
docker
network,
and
when
it
comes
to
a
decentralized
system.
When
you
have
a
docker
swarm
system,
then
you
can
also
say:
okay
now
we
have
a
data
center.
A
One
and
we
have
a
data
center
too,
between
is
the
internet
and
we
have
to
send
the
data
from
a
to
b.
Then
you,
I
would
like
to
mention
that
docker
swan
has
also
an
in
layer
of
encryption,
so
you
can
also
encrypt
the
overlay
network
from
the
communication
and
that's
also
another
way
of
security
where
you
can
increase
the
level
of
security
when
it
comes
to
these
transport
topics.
A
So,
okay,
I
think
now
I'm
in
the
end
of
my
presentation
later
I
will
upload
my
slides
and
post
it
on
there
in
the
slack
channel
and
in
this
github
repo.
Here
you
can
find
the
example,
so
please
try
it
and
you
can.
I
think
you
can
easily
reproduce
this
example.
You
find
all
the
informations
here
and
I
have
done
a
lot
of
documentation
here
so
that
you
know
what
is-
and
maybe
this
is
a
good
point
here
when
it
comes
to
problems
and
error
logging.
A
So
you
can
lock
the
order
locks
for
example,
or
errors
with
this
command,
and
we
direct
the
error
and
the
normal
commands
to
to
the
swipe
command,
and
then
you
can
filter
only
errors.
For
example,
so
because
when
you
look
here,
you
see
a
lot
of
traffic
happened
and
you
can't
see
the
error
here,
and
so
you
can
with
this
web
command,
then
you
can
filter
this
error
here
out.
A
A
Next
time,
as
I
have
mentioned,
we
will
maybe
we
will
have
a
guest
speaker
and
this
is
nathan
and
he
will
tell
us
something
about
the
rust
ordering
system
and
that's
pretty
cool
and
the
tl
the
tls
section
from
today.
This
is
a
good
starting
point,
because
we
only
can
use
raft
as
an
ordering
system
when
we
have
enabled
tls.