►
From YouTube: PHP 7.2 support - weekly meeting, 1 Mar 2018
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
I'll,
just
I'll
just
remind
what
what
kind
of
items
we
have
here.
So
we
have
the
most
important
column,
which
will
be,
which
is
a
backlog,
and
those
are
the
items
which
are
ready
for
work.
We
are
still
investigating
Crypt
removal
and
sunshine.
What
one
a
braid
or
removal
of
some
libraries
and
in
this
icebox
we
have
right
now,
just
items
broken
down
from
something
or
one
works.
It's
for
library
and
mostly
so,
let's
go
through
updates.
A
Can
you
so
much
scream?
No
okay!
So
again
we
have
the
backlog
items
column
and
we
have
couple
items
in
the
investigation
and
the
icebox
on
the
left
is
just
very
McDonald.
Wasn't
famous
one
items
follow
the
progress
from
from
my
side,
I
was
reviewing
and
margin
for
requests.
I
was
validating
the
Redis
one
subject
of
peace
peer
or
at
this
session
obstruct
the
request
is
made
by
inner
project.
A
A
A
A
A
B
B
A
A
B
A
B
A
A
A
C
All
right,
can
you
all
see
that
okay,
so
I've
been
working
on
trying
to
get
docker
environment
together
and
the
the
environment
that
we
have
now
that
the
that
people
are
using
every
is
basically
every
time
you
make
changes.
You
have
to
copy
your
changes
into
the
container
from
the
host,
and
so
I
was
trying
to
set
one
up
that
had
a
shared
environment.
So
right
here,
this
development,
environment
section.
This
is
on
the
the
very
the
first
page
of
the
wiki.
C
C
You
basically
just
go
through
these
steps
and
you
can
actually
build
the
the
container
that
in
the
image
and
create
the
containers
and
install
Magento
into
that,
it's
supposed
to
be
a
little
bit
slower
than
the
second
environment
use
uses
Union
to
to
basically
do
a
file
synchronization
and
it's
supposed
to
be
quicker.
But
the
fact
that
you
have
to
change
the
image
every
every
single
time
that
you
make
a
change
to
your
to
your
codebase
kind
of
makes
it
a
little
cumbersome.
C
I
would
say
so,
but
anyway
they're
both
up
here
and
this
one
has
obviously
it's
an
instruction
as
well
so
they're
both
available
to
use.
If
you
want
them-
and
you
know
it's
bit-
it's
a
lot
easier
than
setting
everything
up
and
I'm,
not
a
big
fan
of
vagrant.
So
that's
why
I
was
really
trying
to
make
sure
that
I
got
this
working
and
you
know
and
I
did
this
week,
so
the
instructions
are
there.
C
C
C
You
know
the
features
of
a
good
security
library
and
our
goals,
but
the
strategy
section
is
I
guess
my
premise:
there
was
PHP
before
PHP
7
to
encrypt
was
the
library
that
was
used
for
cryptographic,
security
and
in
72
they
upgraded
it
to
lib
sodium
because
encrypt
was
not
being
supported
anymore
by
the
creator's
and
and
so
it
basically
fell
behind.
As
far
as
security
goes
and
lib
sodium
is
sort
of
the
considered,
probably
the
just
the
most
secure
library
there
is
and
I
think
that's.
C
So
that's
sort
of
what
this
strategy
section
goes
through
and
then
you
know
basically
what
this
means
for
third-party
modules.
If
you're
going
to
be
developing
them
and
then
the
section
6
goes
through
sort
of
what
we
needed
to
change
to
to
support
encryption
and
the
basically,
this
the
the
the
nonce
is
what's
new
to
to
our
cryptographic,
security
and
so,
and
so
I
was
trying
to.
This
section
basically
explains
how
we
integrate
the
nonce
without
making
any
backwards
incompatible
changes
to
our
interfaces
and
I've
I've
created
some
code
here.
Just
some.
C
You
know
boilerplate
type
stuff
for
whoever's,
gonna
do
the
implementation,
and
then
this
is
the
interface
basically
submit.
This
is
an
addition,
and
then
this
is
sort
of
a
an
example
implementation
of
that
interface,
so
the
nonce
is
used
in
an
authenticated
encryption,
which
is
basically
you
know
you
give
me
a
nonce
I'm,
gonna
encrypt
it
on
my
side,
send
it
to
you
with
the
nonce
and
then
I
want
you
to
decrypt
it
once
it
gets
on
your
side.
So
this
is
used
in
scenarios
like
rest
services.
C
Things
like
that,
so
it's
not
necessarily
you're
not
going
to
use
this.
If
you're
gonna
in
crypt
date
and
put
in
the
database,
a
nonce
is
still
used
because
of
Lib
sodium,
but
it
doesn't
have
to
be
generated
right
then
sent
to
the
client
and
sent
back
so
anyway.
This
this
just
gives
our
our
users
the
ability
to
have
more
secure
communications
from
the
client
to
the
server
and
that's
kind
of
what
we
were
lacking
before
now
so
anyway.
C
This
is
once
again
just
an
example,
implementation
of
how
that
would
be
done
and
then
for
their
normal
encryption.
Basically,
the
idea
is
is
before
so
normal
encryption
would
be
the
example
of
like,
if
you're
gonna,
crypt
something
and
put
in
the
database.
So
all
of
those
instances
we
know
so
that
can
be
done
during
installation
and
we
can
take
anything
that
was
encrypted
using
dim,
crypt
decrypt
it
using
imp
then
encrypted
again
using
Lib
sodium
and
that
can
be
done
on
installer
or
some.
C
Hashing
section
basically
goes
through
and
explains
what
needs
to
be
done
to
you
know,
because
hashing,
the
way
hashing
works
is
there's
a
very
important
piece
of
information
that
you
need
to
know
that
we
don't
know.
So
that's
not
something
we
can
do
ahead
of
time,
so
the
hashing
has
to
be
fixed.
You
know
as
soon
as
the
user
comes
in
and
puts
their
password
in
that's
the
important
piece
of
information
that
we
need.
C
So
what
we're
gonna
the
ideal
would
be
to
use
encrypt
to
decrypt,
to
create
the
hash,
validate
that
it's
true
and
then
use
Lib
sodium
to
regenerate
the
hash
and
store
it
in
the
database.
And
then
this
is
the
random
number
generation
section.
It's
pretty
straightforward,
there's
not
a
lot
that
needs
to
be
changed
and
and
that's
it
so
it's
kind
of
lengthy.
But
but
you
know
if,
if
anybody
the
person
who
decides
to
do
the
the
refactor,
if
they,
if
they
walk
through
this,
it
should
be
pretty
straightforward.
A
C
C
A
C
A
C
Introducing
this
interface-
and
so
you
know
for
for
clients
that
are
for
third-party
developers,
who
who
don't
need
to
add
this,
this
layer
of
encryption,
they
don't
have
to
change
their
modules,
they
can
just
keep
them
how
they
are
and
they
can
call
into
you
know.
The
existing
interface
is
the
encryption
interface
and
and
they're
there.
There
shouldn't
be
any
change
for
them.
C
A
A
D
It's
not
it's
not
great.
As
long
as
we
have
you
know,
we
have
those
search
interfaces
that
will
stay
the
same.
You
know
when
we
move
to
rip
sodium
and
whatever
just
compatibility.
This
might
be
our
only
chance
to
get.
You
know
the
breaking
other
breaking
changes
down,
so
so
I
think
it
might
be.
Okay,.
A
A
A
But
then
I
mean
it
means
that
they
are
not
incompatible,
they
are
incompatible
which
we
sounded
anyways,
but
they
will
be
working
a
second
sound
at
1:00,
so
I
see
it
is
that
if
we
are
not
implementing
this
magenta
plus
extensions
on
seven,
that
one
will
be
working
just
fine,
then,
as
soon
as
we
implement
this,
they
will
start
working
on
seven
to
two
and
extensions
that
depend
directly
and
great.
They
will
have
to
to
use
our
interfaces,
but
we
will
implement
correct,
but
so
yeah
I
agree
that
it's
not
great
to
skip
this.
A
C
A
Cool,
so
I
will
be
reviewing
it.
I
was
also
talking
to
you
about
updating,
Enterprise,
Edition
or
magenta
commerce.
Oh
now,
right
so
then
I
guess
you
will
be
working
on.
That
ban
is
joining
our
project.
We
are
really
happy
about
that.
So
I
do
not
burn.
Maybe
you
can,
if
you're
familiar
with
that
framework
one.
Maybe
you
can
take
a
look
at
the
data
items.
I
can
discuss
it
with
you.
You
should
make
sense
right.
Okay,.