►
From YouTube: Memory Safety Sig (March 30, 2023)
B
A
A
B
B
A
C
C
All
right
and
let's
go
ahead
and
start
off
with
some
introductions,
because
I
know:
we've
got
some
newer
people
here.
So
let's
go
ahead
and
do
we'll
do
a
full
round
of
introductions:
I'm
Nell,
shamrel,
Harrington
I'm,
a
principal
engineer
at
Microsoft
I'm,
also
the
vice
chair
of
the
board
of
the
rust
Foundation
strong
interest
in
memory
safety,
not
just
in
Rust,
though
that
that
has
been
my
primary
area
of
focus
for
a
few
years,
glad
to
be
here
leading
this.
E
F
C
G
A
A
B
Hey
everybody
I'm
krobe
my
day,
job
is
I
work
at
Intel,
part
of
our
product
insurance
and
security
group,
but
my
fun
job
is
I,
get
to
work
with
the
open,
ssf
I
help
lead
and
facilitate
a
couple
working
groups
and
sigs,
and
until
Monday
I
am
a
current
member
of
the
attack,
which
is
technical,
advisory
committee
and
Monday.
We'll
see
what
happens
next.
Okay,.
D
Yeah,
hey
everyone,
I'm
Walter,
Pierce
I'm.
The
security
engineer
from
the
rust
foundation
so
obviously
have
some
interest
in
memory.
Safety,
as
it
pertains
to
rust
and
I've
also
got
a
background
in
all
kinds
of
security
in
the
past
15
years.
So
memory,
safety
and
braking
memory,
safety
is
kind
of
in
my
bag.
G
J
C
Awesome
cool
well
very,
very
glad
to
have
all
of
you
here
and
greetings
to
our
audience,
who
might
be
watching
the
recording
of
this,
so
I
will
put
a
link
to
the
agenda
in
the
chat
one
more
time
there.
We
are
so
first
item
on
the
agenda.
Is
we
are
now
part
of
the
developer
best
practices
Sig?
Can
we
consider
it
official
probe
awesome?
C
Awesome
and
then,
as
part
of
that,
we
have
a
shiny,
new,
git,
repo
or
GitHub
repo
that
I
just
put
in
the
chat
and
one
of
my
items.
Agenda
items
for
this
meeting
was
to
plan
out
a
little
bit
how
we
want
to
fill
this
out.
Thankfully,
thanks
to
Jay,
we
actually
have
our
motivation,
our
objective
and
our
scope
already,
which
should
be
pretty
easy
to
fill
in,
but
there's
some
other
work
you
know
putting
putting
in
some
prior
work.
B
C
C
You
can
communicate
over
Slack
throughout
the
week
that
is
potential
spam
I'm,
not
answering
that
call
and
awesome
all
right.
So
next
on
the
agenda,
one
of
my
ideas
for
our
first
project
as
a
Sig
now
that
we're
official,
if
this
is
something
the
group
will
be
interested
in-
is
rewriting
the
memory
safety,
language
stream
in
the
open
source
security,
mobilization
plan.
B
C
G
C
So
one
possibility
for
getting
started.
Is
we
or
someone
from
openssf
or
gives
me
access
to
create
a
Google
doc
with
the
current
language
in
it,
and
we
can
start
commenting
and
marking
up
that's
one
approach
that
we
could
take.
We
could
also
take
it
section
by
section
but
I
think
maybe
doing
a
general.
You
know
putting
it
in
a
Google
doc.
Doing
a
general
comments.
Overview
part
might
be
a
good
place
to
start.
B
So
a
lot
of
the
working
groups.
Typically,
what
they'll
do
when
you
have
an
item
of
kind
of
high
collaboration
where
you're
going
to
be
doing
a
lot
of
edits
and
kind
of
simultaneous
things?
Is
the
Google
Doc
approach?
You
copy
things
into
a
gdoc
and
then
once
things
are
generally
stable,
ish
or
you're
happy
enough,
then
you
move
it
into
GitHub
and
that
way
you
can
manage
all
changes
through
PRS
and
issues
afterwards.
C
B
Know
that's
what
like
with
the
Sig
and
the
education
plan.
That's
what
we
did
is
we
copied
things.
We
chopped
it
up
into
three
sections
that
when
we
split
up
into
little
groups
to
focus
on
those
sections
and
then
iterated
very
quickly
and
then
got
it
into
git
and
then
reviewed
it
more
as
a
big,
a
larger
group
from
that
point
forward
gotcha,
but
you're
free
we're
free
to
do.
However,
this
group
is
interested
in
doing
this,
just
how
others
have
done
it.
C
C
That's
awesome,
I,
but
that
that
might
be
a
good
place
to
start
get
us
all
on
the
same
page
with
it
again
and
something
I
know
many
of
you
in
this
room.
I've
worked
with
before
I
know.
We
all
know
that
there
were
constraints
that
this
was
written
under
and
even
when,
when
we
have
stuff
in
it
that
we're
made
critical
of
or
we
want
to
change,
we
always
you
know,
keep
that.
C
C
G
C
All
right:
well,
that
is
what
I
had
on
the
agenda.
Is
there
anything
else
anyone
would
like
to
bring
up
or
discuss?
We've
got
a
still
got
45
minutes
and,
of
course,
I
have
no
issue
with.
If
a
meeting
has
is
ready
to
end
ending
early,
but
is
there
anything
else
people
would
like
to
discuss
or
would
like
to
bring
up.
B
Go
ahead,
group
I
I
would
suggest,
just
as
you
stated
that
there
were
certain
constraints
in
a
timeline
when
the
original
doc
was
written.
So
don't
as
we
move
forward,
don't
let
that
limit
your
vision.
If
there's
new
ideas
or
new
things,
new
techniques,
we've
learned
tools,
keep
that
in
mind
and
then,
ultimately,
this
group
should
decide
kind
of
what
our
next
steps
are
like.
What
is
our
goal?
B
Do
we
just
want
to
write
a
position
paper
and
have
a
really
nice
blog
and
a
you
know,
Tech
paper,
that
kind
of
illustrates
how
to
do
things.
Are
we
looking
at
educating
developers
and
are
we
going
to
give
tools
on
how
to
convert
from
C
to
rest,
for
example,
and
then
you
know
think
about
at
the
end
of
the
day,
is
there
some
Financial
ask
and
having
lived
through
that
for
the
last
year,
I'll
be
glad
to
assist
in
kind
of
shepherding
us
up
to
the
governing
board?
B
C
Yeah
well,
one
of
the
things
that
was
discussed
at
the
very
beginning
of
this
group
was,
you
know
putting
together
after
we
rewrite
the
language,
putting
together
a
list
of
projects
and
initiatives.
This
could
include
some
of
the
work
that
prostamo
is
doing.
This
should
include
things
in
the
C
plus
world
like
profiles,
this
could
you
know
various
memory,
safety
initiatives
that
we
recommend
for
funding
from
the
open,
ssf
or
from
open
openssf
members.
B
C
C
B
Yeah
I
think
there's
a
lot
of
opportunity
we
want
to
think
about.
You
know:
are
there
other
foundations
like
the
rust
Foundation
we
want
to
partner
with
officially?
Are
there
any
other
people
kind
of
working
in
this
space?
We
might
want
to
go
out
and
tap
to
try
to
deputize
them
to
be
participants.
So
just
that
you
know
again,
don't
let
the
words
that
exist
there
today
limit
your
vision.
You
know,
if
you
can
make
this
it's
your
dream.
You
can
make
it
as
big
as
you
want
of.