►
From YouTube: ROS 2 Security Working Group (April 13, 2021)
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
Oh
yeah,
okay,
all
right
next
thing
I
put
on
the
agenda
was
just
a
a
reminder
about
six.
We
have
an
upcoming
foxy
sync
coming
and
then,
more
importantly,
the
galactic
feature
freeze
is
on
the
19th.
A
Do
you
have
any
concerns
or
any
comments
about
the
sros
2
code?
I
guess
anything
else
related
to
that
that
should
be
a
priority
or
something
that
has
to
be
taken
care
of
to
hit
that
date.
Any
comments
on
that.
C
A
Kyle
yeah,
I
believe,
there's
one
open
thing
that
miko
mentioned
when
he
updated
rolling.
A
If
that'll
make
it,
but
everything
else
seems
to
be
doing
okay,
I
don't
know
if
we
have
any
thoughts
on
the
you
know
we're
trying
to
get
some
more
stuff
with
the
lot
secure
and
the
plugins
whatnot
as
well.
As
you
know,
jeremy
put
some
work
into
logging
and
any
other
you
know
upstream
stuff.
Is
there
anything
else
that
we
need
to
really
focus
on
anybody
knows
of
or
he
calls
for.
A
Help
all
right
now,
I'm
not
hearing
anything
so
I'm
assuming
that
we're
in
good
shape.
If
anything
comes
up,
yeah
just
drop
it
in
the
chat
in
matrix.
B
Yep,
a
very
quick
update,
that's
something
I'm
hoping
to
be
able
to
resume.
B
That
is
the
ability
to
log
any
security
related
event.
B
B
D
B
So
what
what
you
see
on
screen
is
simply
the
secure
hello
world
example,
that's
already
available
in
the
first
dds
repository,
so
you
have
on
top
a
publisher,
a
subscriber
and
they
simply
well,
I
told
to
each
other
and
publish
hello
world
and
what
you
see
at
the
at
the
bottom
is
a
third,
a
third
fast
dds
node.
That's
only
subscribing
to
the
security
logging
topic,
so
this
guy
is
subscribing
directly
to
the
security
logging
topic
and
simply
printing
on
screen.
B
B
The
me
message
that
I'm
publishing
in
a
loop
simply
to
show
that
yeah
we're
getting
messages
directly
on
the
on
the
gds
topic.
So
as
a
proof
of
concept,
I'm
getting
there
what's
actually
missing.
The
main
work
that
remains
to
be
done
is
that
the
permissions
to
to
subscribe
and
publish
on
well
actually
to
to
publish
on
this
topic
should
be
automatically
granted
to
anyone
that
has
the
the
logging
feature
enabled,
and
this
should
be
baked
in
the
authentication
and
permission
plugins,
and
it
is
this
automation
that
that
remains
to
be
done.
C
So
you're
saying
there's
an
there's:
an
extra
read
and
write
permission
for
the
logger
readers
and
logger
writers
respectively.
Yes,
at
the
moment
and
and
nodes
inherently
just
need
right
access
to
the
the
dds
level
logging
topic
and
then
exactly
league
access
only
needs
to
be
allocated
to
an
administrating
tool
right.
B
B
That
last
chunk
of
work,
I'm
I'm
hoping
I'll
be
able
to
tackle
it
in
the
in
the
near
future
and
and
open
a
put
request
soon
enough.
C
B
Is
concerned,
there
is
still
a
still
a
little
yetis
there,
because
the
security
topic
contains
the
dds
security
topic
contains
characters
that
are
not
supported
on
the
roster
side.
So
after
briefly
discussing
it
upstream,
I
it
looks
like
at
least
at
first.
We
will
have
to
write
a
node
that
does
the
bridging
between
the
dds
craft
and
the
roscraft
to
to
be
able
to
republish
the
security
message,
although
it
may
not
be
necessary
for
everyone
to
have
the
security
topic
directly
available
in
the
roster
graph,
so
that.
D
B
B
C
To
so
what
will
be
the
use
case?
You
wanted
to
have
the
there's
an
idea
of
having
a
bridge
node
that
subscribes
to
the
dds
security
topic
and
then
publishes
over
ross
out
or
something.
B
D
C
B
A
Hearing
none,
I
think,
that's
good.
That's
neat
stuff,
thanks
a
lot
jeremy
for
the
update
thanks
so
does
anybody
else
have
anything
else
for
the
agenda
today.
C
So
I
posted
two
links
on
the
working
group
element
post
and
the
first
one
was
the
is
a
ticket
I
opened
on
rmw
faster,
faster
tps,
with
a
regression
I
encountered
with
foxy,
so
I
was
getting
the
turtlebot
demo
up
and
running
again.
C
I
had
found
the
minimum
spanning
policy
set.
I
think
I
was
actually
using
a
different
rmw
because
I
was
encountering
this
error
and
I
wasn't
quite
sure
whether
it
was
my
policy
was
bad
or
if
there
was
an
inherent
issue
in
the
rmw,
and
so
I
got
working
on
a
different
rmw
with
my
policy,
and
so
that's
how
I
kind
of
triaged
it.
So
then
I
opened
the
issue
and
then
yeah.
C
I
think
fast
dds
encountered
some
security
regressions
with
like
having
multiple
subscribers,
the
single
topic
kind
of
throwing
the
throwing
the
security
plug
in
for
a
loop.
There
do
do
we
want
to
talk
about
that.
I
I
went
through
the
some
of
the
issues
and
it's
kind
of
weird
that
it
fell
through
the
cracks
there
where
maybe
some
of
our
tests
aren't
covering
that
case
where
having
multiple
subscribers
or
something.
A
Yeah,
I
know
I'm
trying
to
think
back
to
the
last
time
I
worked
with
some
of
our
tests.
I
don't
remember
having
multiple
subscribers.
I
think
it
was
all
very
much.
You
know
one
talk
or
one
listener
and
then
changing.
A
Yeah
is
this:
do
you
think
this
issue
needs
to
be?
It
feels
like
something
that
needs
to
be
addressed
before
that
was
part
of
galactic
right.
C
I
think
the
personal
guys
have
fixed
it
with
the
the
latest
release
of
it's
just
back
porting
that
into
foxy.
So
maybe
we
want
to
open
up
a
ticket
to
kind
of
see
where
our
tests
can
help
catch.
That.
D
In
fact,
we
did
solve
not
just
that,
but
I
think
it
was
like
two
or
three
bugs
that
we
found
on
on
the
security
and
fast
dds,
and
they
are
all
of
them
solved
on
a
converted.
D
I
think
it
was
2-1-1
onwards,
so
it
I
think
it
would
be
really
interesting
if
we
could
just
push
that
into
into
foxy,
because
I
think
they
will
show
lots
of
issues
that
we
are
encountering
with
with
security.
At
that
point,.
A
Okay,
so
we
want
to
add
a
add,
an
item
or
add
an
issue
to
create
just
to
create
a
test.
I
think
that's
a
one
test
or
multiple
tests
to
look
for
multiple
readers
or
multiple
writers
and
make
sure
security
works
with
us.
Is
that
how
I
to
get
that
right.
D
A
Okay,
so
that's
the
there's
a
couple
both
I'm
looking
at
was
522
issue
22
and
rtps.
The
first
one
you
linked
and
then.
C
The
first
one
is
is
where
I
was
told
what
what
the
regression
was
and
then
the
second
link
is
the
discussion
on
backboarding
it
with
foxy
yeah,
okay,.
A
C
A
All
right,
so
the
only
other
thing
is,
you
know.
As
far
as
all
the
the
our
old
business,
we
continue
to
keep
the
sros
two
quality
issues
on
our
meeting
minutes
messages
are
related
to
documentation.
So
if
there's
a
chance,
you
have
to
help
out
with
the
documentation
or
things
like
that
feel
free
to
add
that
in
that's
something
that
I'm
working
on
as
well,
I
just
don't
have
any
updates
this
month
on
that.
It's
been
a
bit
of
a
busy
month.
D
C
How
so
there's
been
some
movements
and
the
wrong
student
documentation
for
consolidation?
Where,
where
do
we
author,
the
documentation?
Is
it
on
some
other
repo
with
the
index
or
is
it
is
that
just
the
readme
files
locally
in
the
package.
A
So
I
was
planning
on
adding
it
to
the
core
raws
documentation.
I
actually
haven't
looked
at
the
update,
since
you
know
it
was
reworked,
but
I
was
just
going
to
create
a
pull
request
into
the
into
the
raws
tutorial
section,
and
I
have
enough
content
to
start
with
to
create
a
new
section
in
the
tutorials
for
security.
A
A
Yeah,
that
was
my
thought
there,
unless
you
feel
like
it's.
You
know
that
we
should
keep
it
in
our
repository,
but
my
plan
was
just
to
add
it
to
the
court
documentation.
C
I
I
I
have
one
way
or
the
other.
I
have
to
have
to
read
up
on
the
what's
the
style
guide,
for
what
they're
trying
to
do
now.
Yeah.
D
C
D
D
A
All
right
so
I'll
go
ahead
and
capture
the
meeting
minutes
and
post
that
out
also
keep
in
mind.
Our
next
meeting
will
be
three
hours
earlier,
hopefully
to
accommodate
some
of
our
members
out
in
europe
and
even
asia,
pacific,
so
I'll
shoot
out.
Some
updated
meeting
invites
for
that
which
probably
will
change
the
link
as
well
for
the.
D
The
hangout.
A
So
expect
that,
sometime
within
the
next
few
weeks,
so
but
other
than
that,
thank
you
very
much
for
joining.
I
appreciate
it
and
yeah,
as
always,
feel
free
to
reach
out
on
matrix.
If
anything
comes
up,
we
should
take
a
look.