►
From YouTube: ROS 2 Security Working Group (08 Feb 2022)
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
A
A
B
A
All
right
second
topic:
I
did
open
a
request
for
the
addition
to
the
working
group
rules
concerning
the
the
downgrade
of
inactive
members-
nothing,
nothing
new
there,
that's
pretty
it's
pretty
much
what
we
discussed
during
the
last
working
group.
A
All
merged,
so
without
further
ado,
I
leave
the
floor
to
victor.
It's
gonna
tell
us
about
an
interesting
workshop
that
takes
place
tomorrow.
I
believe
victor.
B
Yeah
hi
everyone,
real,
quick
yeah.
I
posted
the
link
in
the
minutes.
Essentially,
there
is
a
workshop
organized
and
led
by
the
european
commission
to
try
to
understand
a
bit
better.
How
collaborative
robots
can
be
safety
secured
in
the
context
of
of
the
european
union.
We
are
participating
as
alias
robotics
I'll,
be
giving
a
short
speech
about
wars
to
security
and
dds
security
and
the
status
around
it.
There's
many
other
interesting
speakers
coming
from
government
and
industry
as
well
as
academia,
so
so
yeah.
B
Oh,
it's
it's
totally
open
and
free
to
access.
As
far
as
I
know,
as
far
as
I've
been
told,
there's
a
teams
link
in
the
link
that
I
posted
in
the
minutes,
I'm
just
joining
that
at
the
corresponding
time,
which
is
10
a.m,
ced
central
european
time
so,
depending
on
where
you
are,
might
be
a
bit
inconvenient,
especially
for
those
of
you
guys
in
canada
or
in
the
u.s.
I'm
sorry
about
it.
B
I
can't
tell
you
if
it's
going
to
be
recorded,
I'm
sorry
but
those
of
you
in
asia
or
euros.
It
should
be
reasonable
to
join.
A
B
A
So
we
don't
have
much
more
on
the
agenda,
so
I
I
propose
that
we
reopen
and
continue
the
discussion
around
the
reference
implementation.
B
B
I
can
share
a
few
bits
on
that,
so
a
group,
a
group-
and
I
are
well
a
group
where
we
can
I'm
there
as
well
we're
trying
to
push
forward
this
topic,
as
discussed
previously
around
some
of
the
previous
existing
work
that
we
featured
in
some
of
the
past
security
workshops
during
roscons,
particularly
we're
looking
at
the
work
that
was
done
around
the
turtle
3
and
around
the
navigation
stack.
B
It
hasn't
been
decided
just
yet,
but
just
as
a
heads
up
we're
looking
at
this,
I
understand
this
is
complementary
to
whatever
the
working
group
decides
to
do
with
regard
future
workshops
and
the
turtle
bought
four.
B
So
regardless
yeah
there's
this
ongoing
work,
that's
happening
and
that
hopefully,
will
raise
some
awareness
and
just
just
trying
to
convey
that
yeah
and
we'll
see
what
comes
out
of
it.
B
I
think
that
you,
I
think
that
you
are
going
to
merge.
I
mean
the
the
work
we
are
doing
is
aiming
again
not
to
create
so
much
new
content,
but
more
to
try
to
revamp
some
of
the
previous
content
and
give
it
a
bit
more
visibility.
B
But
I
think
the
end
goal
is
again
to
reinforce
the
watch
to
security
working
group,
the
ds
rush
to
work
unrelated,
so
I
think
I
think
it
makes
sense
to
converge
plus
this.
This
effort
is
time,
limited
we're
hoping
to
to
finalize
it
in
the
coming
weeks
and
then
switch
back
into
pushing
with
the
rest
of
the
group.
So
so
now
I
think
it's
gonna
match
and
I
think
yeah
it's
going
to
be
truthful.
A
A
And
now
I
do
believe
that
the
turtle.4
is
a
an
ideal
platform
for
this,
not
only
because,
hopefully
we
can
recycle
and
revamp
a
lot
of
the
work.
That's
been
done
for
the
the
tottenback
3
for
the
security
workshop
of
roscomm
209
team.
I
believe,
but
also
because
that's
you
know
the
new
platform.
That's
gonna
be
on
the
hype
for
a
little
while
and
it's
raspberry
p4
based,
it's
gonna,
be
a
really
neat
platform
and
yeah,
hopefully
that
that's
a
hype
way
if
we
can
ride
along
so
for
the
next
meeting.
A
I'd
like
you
to
consider
whether
you
can
commit
to
this
project
or
not
and
ask
you
to
fill
up
your
name
in
the
document
I'm
going
to
share
and
from
there
we
can
establish
a
battle
plan,
something
that
I
did
not
mention
also,
but
an
idea
that
came
to
mind
that
as
part
of
this
project,
or
maybe
in
parallel
to
this
project,
I'd
like
the
the
working
group
to
establish
also
a
reference
document
for
security,
good
practices
in
ross
and
robotics
in
general.
A
Much
like
what
good
practices
that
we
advocate
for
during
that
canonical
advocated
for
during
security
presentation
and
talks,
but
I'm
sure
you
guys
also
have
plenty
of
good
ideas
and
good
practices
to
advocate,
and
this
document
would
be
two-parted
first
from
general.
Good
practice
is
a
recommendation
and
the
second
part
would
be
the
practice
of
this.
Those
good
practices,
flashed
into
actual
you
know,
commands
to
run
and
scripts
to
install
a
new
robot
or
things
to
perform
to
perform.
A
So
again,
I
believe
that
this
second
part,
this
concrete
part,
should
at
first
target
the
the
turtle
butt
form.
So
I
don't
know:
if
we're
talking
about
disabling
usb
ports,
then
we
should
provide
the
the
actual
command
to
run
on
the
turtlebot
fault.
To
do
so,
and
those
would
be
practical
cases
that
one
can
then
transport
to
their
own
to
their
own
robot.
A
Right
then,
I
guess
we'll
kick
start
this
we'll
kick
start
this
list
of
good
recommendations,
share
it
with
the
working
group
and
then
invite
you
all
to
to
contribute
to
it.
A
B
A
That
looks
like
a
very
short
meeting.
We
don't
have
any
other
topic
on
the
agenda
for
this
month.
I
propose
that
we
take
the
discussion
asynchronous
on
the
matrix
chat
room.