►
From YouTube: Kubernetes SIG Security Tooling 20220118
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
So
I'm
going
to
present
you
cadigger,
so
this
is
a
small
tool
I
made
for
penetration
testing.
So
I'm
going
to
talk
a
little
bit
about
me
first,
so
in
2019
I
joined
a
small
startup
alongside
my
studies
and
started
to
use
kubernetes
around
the
beginning
of
2020
and
started
to
build
some
production
with
it
for
like
almost
two
years,
but
in
2021
in
late
2021,
I
graduated
in
computer
security
and
joined
my
current
employer
as
an
rnd
engineer,
so
yeah
for
the
future.
A
I
plan
more
bets,
more
opponents,
open
source
stuff
and
maybe
more
security
for
me,
so
yeah.
The
first
question
I'm
going
to
answer
is
why
and
why?
Why
building
another
tool?
So,
firstly,
why
not
you
know,
because
I
wanted
to
build
one.
So,
yes,
that's
the
reason
and
like
the
the
main
reason
actually
is
because
I
participated
in
2021
europe
conclave
native
stf
and
it
was
very
interesting
to
see
some
experts
like
doing
a
live
solving
session
and
exchanging
ideas
about
how
what
to
look
for
and
some
ideas
and
yeah.
A
Another
reason
inside
that
that
I
liked
a
lot
contained
by
jesse
fraser.
So
maybe
you
are
familiar
with
this
tool:
it's
a
smaller
container
tool
to
take
some
information
about
your
situation
like
the
cisco
that
you
are
allowed
to
to
use
in
the
namespace
you
are.
You
are
in
some
stuff
like
that,
and
so
the
idea
was
why
to
automate
a
security
checklist
when
you
are
inside
the
board-
and
you
want
to
know
a
little
bit
more.
A
So
what
can
a
caddiga
actually
do,
like
my
contained,
can
try
to
get
your
container
on
them.
So
I'm
mostly
important
imported
code
from
my
content
for
for
that
for
the
container
runtime,
the
capabilities,
the
name
space,
I'm
going
to
to
explain
a
little
bit
more
and
the
cisco
scan,
but
it
has
more
functionalities
and
more
kubernetes
oriented
functionalities,
so
it
can
automatically
retrieve
the
service
account
token
scan
for
the
account
permissions.
A
This
is
interesting
environment,
viable
it's
a
minor
one
but
yeah.
It
can
retrieve
all
available
services
in
the
cluster.
So
we'll
talk
about
it
later,
it
can
scan
the
admission
controller
chain.
So
it's
a
new
useful
one
like
if
you
want
to
escalate
privilege
it
can
be
really
useful
and
you
do
some
basic
stuff,
but
it
does
some
basic
stuff,
but
it
does
it.
Does
it
automatically
so
check
mounts.
A
Do
your
id
the
processes
that
are
running
devices
in
the
version,
so,
as
you
see
it
mostly
just
collect,
informations
and
you'll
have
to
analyze
all
the
stuff
to
understand
and,
and
it
can
give
you
a
pretty
good
idea
of
which
kind
of
container
you
are
inside
or
stuff
like
that,
so
yeah.
I
wanted
to
emphasize
some
some
features
of
trying
to
when
I
dived
into
my
content.
A
I
learned
about
the
pd
namespace
feature,
so
I
was
really
impressed.
But
when
I
looked
at
the
actual
implementation,
it
was
relying
on
some
implementation
detail
in
in
the
kernel
the
link
channel
and
it
wasn't
working
anymore.
So
there
are
some
stuff
that
will
break
in
the
future
that
are
already
broken,
but
it's
difficult
to
mount
and
maintain
that,
and
I
I
just
like
speaked
about
a
feature
to
retrieve
all
the
services
running
inside
of
a
cluster
and
this
feature
is
we
can
name
it
as
the
coordinates
wildcard.
A
So
the
idea
is
that
you
can
query
a
specific
url
with
the
white
card
to
card
dns
and
it
will
give
you
back
all
the
the
all
the
entry.
So
so
all
the
services
basically
are
running
inside
of
your
cluster
and
there
are
discussions
about
removing
the
teacher
because
they
have
like
the
developers
have
seen
that
it
was
used
in
in
penetration
testing
tools.
So
they
don't
think
they
need
it
anymore
and
just
a
quick
wall
like
so
because
of
this
fragile
features
that
I
used.
A
It
needs
to
be
updated
and
I
want
to
update
it
a
little
bit
more
in
the
future
and
anybody
actually
can
extend
it
with
new
checks.
So
it's
it's
really
simple.
It's
a
really
simple
go
interface
to
to
implement
and
you
can
add
checks
to
the
to
the
category.
A
So,
let's,
let's
see
a
demonstration.
B
A
B
Wondering
the
second
one
especially
looks
like
a
good
opportunity
for
a
new
contributor
to
contribute
to
the
repo.
B
Nice
yeah,
if
I
think,
if
you
have
like
a
good,
well-written
github
issue
on
the
repo
or
in
terms
of
what
is
expected
to
change
people,
might
people
who
find
this
interesting
might
be
more.
It
might
make
it
easier
for
them
to
contribute.
A
Yeah
yeah,
why
not
fun?
For
now,
it's
so
small
that
I
don't.
I
didn't
actually
wrote
some
contributor
guide
and
stuff
like
that,
but
yeah.
Why.
C
A
So
I
installed
a
small
machine,
so
I'm
going
I'm
going
to
use
that
thing.
So
it's
a
little
ctf
that
I
made
just
to
explore
that
tool.
It
was
a
it's
mainly
like
a
copy
of
the
first
step
of
the
the
kubernetes
of
the
the
2021
ctf
from
europe.
A
So
this
is
really
simple
and
can
be
used
to
to
understand
a
little
bit
more
about
the
tool
and
how
you
can
like
speed
up
your
pen
testing
process
with
it.
So
I'm
gonna
show
you
it
works.
Basically,
I
just
cloned
the
repository
and
there
is
a
small
script.
A
There
is
a
small
script
to
set
up
your
machine.
It's
almost
so
yeah.
If
you
want
to
run
that
you
need
to
have
a
visualization
on
your
computer.
So
right
now,
I'm
using
a
vm
from
digitalocean
and
it
has
nested
naturalization,
so
it
works.
But
anyway
you
need
so
just
start
by
starting
the
scripts.
A
In
my
case,
I
already
started
the
script
earlier
to
make
it
faster
for
you,
so
it's
going
to
launch
some
some
pods
and
these
spots
are
part
of
a
step
of
the
challenges.
So
if
you
want
to
start
for
with
the
first
challenges,
just
run
start
one:
it's
going
to
execute
into
the
pod
and
you
will
have
some
scripts.
So
it's
a
real,
simple
script.
We
are
going
to
see
but
yeah.
A
The
idea
of
the
in
the
challenge,
basically,
is
that
you
are
dropping
into
a
container
and
you
just
want
to
to
see
what
you
can
exploit
in
this
container.
So
we
can
do
it
manually.
That's
that
was
the
case
when
I
was
resolving
the
kubecon
2021
ctf,
but
the
idea
is
to
to
show
you
how
category
can
speed
up
all
the
process.
So
I
can
show
you
that
cadigar
is
a.
I
think
it's
installed
in
the
in
the
container.
A
So
there
is
the
admissions
scan,
for
example,
the
authorization
of
the
token,
the
scanner
for
capabilities
devices,
environment,
stuff
and
all,
and
if
you
want
to
run
almost
all
the
the
plugin
you
just
have
to
write
d
all
and
here
the
id
for
this
step
of
the
challenge
is
to
realize
so
yeah
you,
you
just
type
category
goal
and
you
are
seeing
some
stuff.
So
the
token
it
reaches
the
token
you
check
for
the
rights,
nothing.
You
know
nothing.
Sorry!
A
Sorry,
sorry,
sorry,
nothing
very
special
here
we
haven't
any
particular
rights,
but
but
there
is
something
interesting
is
that
it
seems
that
we
have
a
lot
of
capabilities
and
we
have
capsis
admins.
So
so
it's
giving
you
some
hints
that
you
might
be
running
inside
of
a
privileged
container.
So
that
was
the
the
first
challenge
of
this
ctf.
It's
a
really
simple
one.
I
admit,
but
this
tool
can
give
you
some
hints
about
that.
A
For
example,
there
are
a
large
number
of
devices
available,
so
we
might
be
inside
of
the
privilege
container,
which
has
no
restriction
on
the
devices
accessible
from
the
host
and
yeah.
That's
mostly
it
and
we
can
see
that
there
is
some
stuff
wanted.
So
the
idea
is
to
realize
you
are
inside
of
a
responder
and
see
that
the
underlying
disk
of
the
host
is
accessible.
So
you
can.
Obviously,
if
you
want,
you
can
mount
a
dev
video
one
in
on
mount,
for
example,
and
then
you
have
access
to
the
underlying
host.
A
So
here
it's
a
bit
special
because
it's
the
minitube
vm,
but
you
can
access
the
vars
libs,
and
here
we
have
all
the
the
files
related
to
our
container
runtime,
and
here
we
are
using
docker,
and
the
idea
in
this
challenge
is
that
some
parallel
container
is
running
is
he's
having
the
flag
inside
of
his
file
system.
A
So
you
can
almost
grip
on
everything
in
the
file,
so
all
the
flags
start
with
a
quartz
flag
and
it's
a
bit
of
corporate
stuff
but
and
you
can
grab
inside
of
the
file
system
of
the
hosts
and
you
will
get
the
flag
that
is
into
the
the
other
container,
which
is
which
is
supposed
to
be
secured
so
yeah.
The
idea
in
this
first
step
was
to
show
that
privileged
corner.
A
I
basically
just
food
processes
running
on
the
host
that,
if
you
are
some
secure
container
on
the
side,
it
doesn't
mean
that
another
like
a
cotenant
container,
can
can
break
your
security,
can
cannot
break
your
security
and
and
category
can
help
you
to
determine
that
you
are
inside
of
a
predator.
A
B
Cool,
I
also
love
the
information
that
just
comes
out
with
all
of
the
different
flags
by
just
using
all.
So
that's
probably
going
to
save
a
lot
of
minutes
for
everyone
doing
ctfs,
because
if
you
have
most
of
the
information,
then
ctfs
become
a
bit
easier.
A
Thank
you.
Thank
you.
So
yeah,
I'm
not
inventing
stuff.
Actually
it's
it's
coming
from
a
youtube
concert
here,
but
yeah.
That's
the
idea,
like
you
have
some
rc
on
a
container.
A
You
can
break
into
other
containers
on
that
that
cluster,
so
we
can
move
on
the
second
step,
which
is
a
bit
more
challenging
actually
so
here
the
script
is
that
you
gain
access
to
the
shadow
of
this
machine
also,
and
you
got
into
the
system
because
you
already
know
that
in
the
root
folder
the
host
machine,
there
are
some
interesting
secrets
for
you.
So
this
is
pretty
similar
to
the
first
step.
A
But
here,
if
we
check
the,
for
example,
the
we
can
see
that
there
is
the
the
yeah
there
is
the
disk.
But
if
we
do
the
same
so
cadigar
did
all
we
will
see
that
we
don't
have
many
capabilities
and
that
we
don't
have
a
lot
of
devices
available
so
yeah
again.
The
idea
with
cadillac
is
to
provide
you
with
a
lot
of
information,
but
of
course
you
have
to
process
them
while,
while
digging
into
that
stuff,
so
it's
a
bit
more
difficult.
A
So
here
we
can
see
some
of
our
probes
so,
for
example,
oh
sorry,
for
example,
the
environment
variables.
We
can
see
that
we
are
just
running
inside
of
the
kubernetes
containers.
There
are
the
kubernetes
cluster.
They
are
the
traditional
environment
variables.
A
B
Have
one
suggestion
oh
looks
like
the
terminal.
A
Yeah,
this
is
better,
so,
yes,
we
have
the
version
of
the
cluster.
We
have
the
user
id.
We
retweet
some
tokens.
That's
that's
interesting!
Nowadays,
you
can,
you
know
not
like
it's
not
always
the
case.
You
know,
there's
not
always
token
mounted
inside
of
containers.
A
You
can
see
the
services
available,
okay,
nothing
very
interesting,
four
processes
in
the
container,
okay,
sleep,
bash,
caddy
and
some
stuff.
But
more
importantly,
what
you
can
see
here
is
the
it's
like
a
very
similar
result,
as
if
you
just
type
cube,
ctl
out
scanner,
etc.
But
it's
all
at
the
same
place.
You
know-
and
here
the
idea
is
that
you
can.
A
A
So
here
there
is
some
feature
that
we
can
use
in
is
cadillac
animation
to
actually
use
that
feature.
We
have
to
switch
to
active
flag
because
it
will
actively
create
some
resource
or
do
some
stuff
so
yeah.
He
will
warn
us
that
he
cannot
delete
the
pod
so
that,
if
we,
I
don't
know
if
we
have
to
tell
if
we
use
the
ctl,
can
I
list,
we
can
create
pods
attached
to
pods
exactly
in
two
pods
list,
etc.
But
we
can't
deal
both.
A
So
if
we
try
to
scan
the
admission
control
with
cadiga,
which
is
mostly
creating
pods,
with
very
special
capabilities
like
a
privilege
pod,
like
a
powered
with
a
host
path
mounted
stuff
like
that,
it
will
create
pods,
so
it
might
leave
trace
traces.
A
So
if
you
are
sure
you
want
to
do
that,
you
can
just
type
admission
force,
which
is
a
particular
flag
and
it
just
scan
the
animation,
and
we
can
see
that
there
is
almost.
It
seems
that
there
is
no
admission
control
security
policies
applied
here,
because
we
can
almost
create
any
any
potential
on
that
cluster
so
to
speed
up
the
process.
A
This
thing,
so
I
this
tool
that
was
made
by
another
user,
which
was
intended
as
a
admin
tool.
You
know
the
ecupstill
nutshell
was
a
small
shell
script
that
just
started
a
pod
with
a
root
access
to
access,
the
underlying
node,
when
you
don't
have
a
ssh
on
them
or
stuff
like
that,
so
I
decided
to
fork
that
and
and
and
modify
it
to
to
be
able
to
start
another.
You
know
a
shell
on
any
node
available
really
so
what
you
have
to
do.
A
Actually,
I
don't
remember
my
own,
my
own
syntax,
but
it's
cgl
and
no
change.
A
So
basically,
what
it
will
do
is
just
try
to
create
a
pod
on
any
nodes
available
and
try
to
create
a
privileged
spot
to
have
access
to
the
underlying
mode.
So
it
just
speed
up
the
process
of
writing.
Publicity
or
cryptic
ttl
applies
on
some
special
files
that
you
prefer.
A
So
it
select
this
this
random
node
and
try
to
center
on
it,
and
here
we
are
on
the
underlying
hosts,
so
the
mini
qvm
actually
and
we
can
see
in
the
root
folder.
Yes,
we
have
some
secrets
lying
around
and
we
can
retrieve
the
flag.
Basically.
A
A
So
that's
it
for
this
step
and
the
last
one.
Oh,
no,
I
just
wanted
to
do
something
real
quick.
So
you
saw
some
admission
controller
scanning
capabilities,
and
I
wanted
to
prove
it
to
you
that
you
that
it's
working
you
know
and
with
mini
cube,
it's
really
easy.
Actually,
you
can
just
delete
my
actual
cluster
and
I'm
just
running
this
small.
A
A
A
And
make
sure
that
we
have
category
installed
because
basically
the
admission
scan
you
can
run
it
outside
of
a
pod.
You
can
just
run
it
from
your
computer
to
talking
to
the
human
sap
api.
The
tool
will
just
try
to
use
a
like
the
the
current
configuration
if
you're
in
the
container
or
or
your
config,
so
yeah.
We
have
a
cluster
with
security
policies
on
and
wanted
to
prove
that.
A
So,
if
you
we
can
show
the
psp
rules
and
we
can
edit
the
privilege
one,
because
I
will
be
using
that
one
because
I
mean
psp
privileged
and
just,
for
example,
4b
or
pid
and
and
privilege
yeah.
Why
not?
A
So
it's
been
edited
and
now
we
can
run
category
from
from
our
perspective,
so
animation
forms
and
yeah.
I
just
try
to
create
those
pods.
You
can
see
some
some
artifact
of
that
they
are
going
to
be
deleted
and
it
just
shows
us
that
the
admission
the
admission
control
just
forbid
us
from
creating
a
board
with
rspid
or
privilege
stuff.
So
is
the
admission
scan
and
finally,.
A
Be
very
quick
to
start
so
when
you
want
to
start
here,
I'm
I'm
starting
the
the
stuff
again.
You
just
have
to
launch
that
script.
It
will
correctly
configure
the
the
cluster
for
you,
the
small
one,
using
kvm
or
virtualbox,
but
it's
mostly
working
on
a
new
second
adapt
to
make
it
work
on
another
computer.
B
A
Yeah
yeah,
I
will
just
do
the
the
final
step,
which
is
a
bit
more
interesting,
exploiting
cadillac
stuff,
but
it
will
be
quite
fast.
A
Yeah,
so
you
can
see
that
it's
not
the
latest
in
youtube
and
it's
beneficial.
It
was
made
some
some
months
ago,
so
it's
a
bit
harder
to
outdated
yeah.
Now.
A
B
Wha,
while
the
container
images
are
loading,
can
you
quickly
explain
a
bit
about
all
the
parts
we're
creating
here.
A
Yes,
these
spots
are
mostly
from
the,
but
they
are,
they
are
from
the
munich
stf,
so
it's
the
pods
that
are
building
all
the
changes,
so
you
can
spoil
yourself
by
looking
into
these
deployments.
There
is
some
spoiler
alert
down
here.
A
A
But
actually
because
it's
running
on
on
your
computer
or
just
running
on
the
computer,
you
want
to
install
it.
You
can
obviously
just
click
all
the
secrets
by
checking
the
deployment
stuff,
but
yeah
yeah.
That
makes
sense,
keep
going
sorry,
no
problem.
So
here
we
are
starting
the
third
challenge
and
it's
not
giving
you
any
information.
In
that
case,
it's
supposed
to
be
a
bit
more
difficult.
C
A
It
has
some
features
around
it,
so
it
tries
to
detect
the
username
space,
which
is
like
the
only
namespace
that
you
can
really
detect
or
true.
You
know,
but
you
try
to
have
some
guess.
It
tries
to
have
some
gates
on
the
pi
namespace,
and
here
the
the
idea
is
just
to
search
for
command
processes.
You
know,
and
and
for
example,
it's
just
it
just
found
the
posts
the
pose
processed
into
the
container.
So
if
you
are
a
bit
familiar
with
containers,
you
are
farther
away
kubernetes
deploy
mods.
A
You
know
that
there
is
some
process
that
holds
most
of
the
namespace,
especially
in
the
network,
namespace
and
so
on
that
that
will
be
created
at
the
creation
of
the
bird
and
then
the
other
container
will
be
will
be
put
into
the
same
namespace.
So
here
the
idea
that
we
can
find
the
pause
process
is
that
the
pod
might
have
share
process
name
space
to
true.
A
So
it's
an
interesting
fact,
because
actually
it
means
that
if
you
are
into
a
container
of
a
pod
composed
of
multiple
containers,
it
will
be
possible
for
you
to
like
drop
a
little
bit
on
the
information
of
other
containers
and
basically
that's
the
idea
in
this.
In
this
step.
If
you
go
and
do
the
proc
thing
you
can
see
so
that
there
is
a
pose
process,
but
there
is
some
other
containers,
so
there
is
a
sleep
1337
and
it's
pid
22.
A
So
if
you
go
to
pid
22,
you
can
check
about
this
process
a
little
bit,
but
the
idea
is
to
actually
check
this
environment
viable
on
the
environment,
viable,
sorry,
and
in
this
stuff
there
is
the
kubernetes
stuff
actually,
but
there
is
some
secrets
lying
around
that
you
can
actually
retrieve
so
yeah.
The
idea
of
this
step
is
when
you
are
in
the
container
in
a
pod
of
multiple
containers.
A
If
there
are
some
shared
pid
namespace
between
those
containers,
it
might
be
interesting
to
to
look
at
the
other
process,
and
category
can
give
you
some
hints
about
about
about
the
fact
that
you
are
showing
the
this.
This
pid
namespace
so
yeah,
that's
it.
I
hope
it
wasn't
too.
I
think
it
wasn't.
It
was
a
bit
quick.
You
know
to
go
around
all
these
challenges
that
fast
but
yeah.
D
Really
cool
demo,
I
had
a
question
yeah
the
so
it
looks
like
you
always
run
it
when
you're
like
on
a
part
right.
How
much
of
this
can
be
used
as
like
a
misconfiguration
tool
like
where
you
kind
of
run
it
outside
the
cluster
to
see
if
the
question
has
been
configured
correctly,.
A
A
A
You
can
scan
that
and
I
think
it's
the
main
stuff,
if
I'm
looking
into
it
all
the
rest,
is
local
stuff,
so
token
authorization
as
well.
Of
course
you
can
use
the
authorization
stuff
with
your
config,
but
it's
the
same
as
using
ctl.
What
can
I
so?
Yes,
I
think
the
admission
is
the
only
stuff
that
you
can
use
to
check
if
your
if
your
cluster
is
not
configured
properly,
but
you
know
it's
not
the
main
id
behind
the
tools.
D
Yeah
yeah,
absolutely
one
other
thing
might
also
be
cool.
Is
that
like
where
you
run
like
the
command
that
you
ran,
which
gives
you
like
all
the
like
things
that
are
off
about
the
container
right,
but
it
would
also
be
cool
to
have
like
common
attacks
that
can
occur
from
there.
D
Like
this
is
a
pretty
like
well
known
way
to
like,
if
you
have
a
pause
container
and
you're
sharing
like
pid
name
space
right,
then
you
can
like
pivot,
so
yeah
it'd
be
nice
for
like
people
who
are
like
learning,
because
I
think
this
is
a
great
tool
to
like
begin
ctfs
and
like
learn
as
you
go,
and
it
might
be
nice
to
have
like
here's
common
scenarios
of
attack.
A
Yeah,
I
I
think
he
I
completely
agree
with
you,
for
example,
you
know
at
first
I
I
didn't
know
about
the
service
discovery
stuff
on
on
core
dns,
and
the
idea
of
cadiga
was
also
to
build
a
small
base
of
knowledge
around
the
intestine
kubernetes.
A
So
the
idea
to
be
more
educational
could
be
really
really
nice
because,
for
example,
if
you,
if
we
go
into
the
second
step-
and
we
want
category
services-
we
have
all
that,
but
we
don't
have
any
explanation,
but
if
we
run
cadiga,
maybe
it's
better
in
the
first
step,
if
we
run
category
capabilities
so
cap,
there
is
a
command
that
maybe
we
can
improve
to
explain.
What's
the
situation.
A
So
here
we
see
that
we
have
a
lot
of
capabilities.
Maybe
not
everyone
is
familiar
with
linux
capabilities,
which
are
a
bit
complicated.
I
think-
and
here
it
tries
to
you,
know,
to
intuit
or
add
some
some
analyze
around
for
that
you
know
maybe
check
the
number
of
device
devices
available.
You
know
so
yeah
that
that
would
be
really
great.
D
Yeah,
like
messages
like
this
are
super
helpful,
just
in
the
moment
when
you're
trying
to
do
a
cdf
and
like
if
you
have
that,
have
all
this
information,
it
also
helps
you
in
actually
doing
the
ctfs
faster,
because
sometimes
you
forget,
like
a
attack
vector
that
you
like
saw
like
a
while
back
yeah,
but
exactly
a
demo.
Man
like
this
is
super
awesome.
A
B
A
Oh
yeah,
I
think,
if
you
guys
want
a
few
people
want
to
improve
that
stuff.
I
can
write
a
contribute
guide,
but
I
think
the
the
best
idea
is
to
write
another
probe,
another
plugin.
You
know
that
can
be
triggered
to
maybe
you
have
some
by
the
way.
A
A
It's
really
easy,
and
basically
I
I
wanted
to
show
it
to
you,
but
the
template
to
write
a
plugin.
There
is
a
template
here
and
you
just
have
to
fill
this
go
file
basically
type
the
the
name
of
the
the
probe,
the
description,
this
description
and
the
run
the
run
the
run
function
basically,
and
it
will
automatically
include
in
the
project
right.
Okay,.
B
Cool
thanks
so
much
shubham.
If
you
have
any
questions,
we
got
one
minute
more,
nothing,
nothing!
It's
a
great
session.
My
thanks!
Yes,
thank
you
all
right.
Thank
you.
Thank
you,
cool
thanks
a
lot
mai.
I
really
learned
a
lot
and
this
was
great
tool.
You
were
really
underselling
yourself,
and
you
said
this
is
a
very
small
tool.
Does
many
few
things
it's
really
nice
and
I
feel,
like
many
people,
might
find
it
useful.
B
So
thanks
so
much
once
the
recording
is
up
I'll
share
it
with
the
channel,
but
thank
you
again
and
hope
to
see
you
in
the
next
session.