►
From YouTube: GSoC 2021 Git credentials binding 2021 05 28
Description
Git credentials binding project mentoring in Google Summer of Code 2021.
A
B
No
for
now
first
I
am
working
on
the
private
key
and
the
passphrase.
Then
I
will.
I
will
set
up
the
environment
properly,
so
windows
and
other
platforms
like
centos
and
the
great
version.
Also
I
have
to
test
on
vs
git
versions
like
1.8,
so
then
I
will
continue
further,
but
for
now
my
focus
is
the
private
key,
with
passwords.
A
B
B
B
A
A
C
A
B
B
A
A
A
A
A
A
A
B
A
A
B
B
A
And
once
we've
done
that,
then
we
need
to
create
a
new
private
key
which
is
decrypted
and
pass
that
and
that
new
private
key
needs
to
be
accepted
needs
to
be
acceptable
to
open
ssh.
Because
it'll
do
the
work
it
will.
It
will
be
the
one
that,
when
command
line
git
connects
through
ssh
protocol,
it
actually
delegates
to
ssh
to
do
the
to
do.
The.
B
Communication
I
mean
I
have
not
checked,
I'm
not
checking
with
the
openness
as
such
effect.
I
mean
I
have
converted
the
key
using
the
ssh
keys
and
commands,
so
it
was
accepting
for
back
then,
but
I
don't
know
if
I
have
I'm
converting
the
key
using
bouncy
castle.
If
it
supports,
then
it
will
support
the
open,
assisted
format
or
not.
A
A
B
A
A
A
A
A
B
B
C
B
A
So
I
assume
that
you've
probably
not
tried
anything
on
windows,
yet
this
is,
I
think,
all
maybe
we
should
put
that
note.
This
is
just
this
is
linux
for
right
now
and,
and
that
seems
like
you're
investigating
the
most
the
what
I'd
call
the
highest
risk
part
of
the
entire
thing.
So
this
is
a
great
thing
for
you
to
be
investigating
and
exploring
everything
else
can
wait.
A
A
A
B
There
was
one
thing,
but
it
is
not
in
the
priority
list,
but
like
I
am
so
the
implementation
that
of
the
bindings
is
that
I'm
carrying
out
is
like.
I
am
not.
I
mean
the
these
bindings
are
only
one
second
one.
Second,
I
mean
okay,
so
the
git
environment
variables
such
as
get
ask
pass
or
get
ssh
are
only
used
to
perform
the
operations
like
in
the
previous
bindings
of
credential
binding.
A
And-
and
I
think
that
is
exactly
correct
because
we
don't
want
the
user
to
so.
Let's
let
me
say
it
this
way.
The
binding
implementations
are
intentionally
only
using
git
specific
by
environment
variables
that
avoids
confusing
the
user
with
required
by
requiring
them
to
choose
correct
names
for
those
variables.
B
A
Then
the
user,
okay,
then
the.
If
we
don't
use
the
correct,
then
the
the
git
commands
won't
work
right.
They
expect
exactly
those
environment,
variables
and
and
the
files
associated
with
them
right,
because,
in
addition
to
defining
the
environment
variables,
you're
also
defining
placing
files
on
the
disk
that
contain
the
specific
content
that
we
need,
the
username
prompt,
the
password,
prompt,
etc.
A
Yeah,
okay
yeah,
so
for
me
that
the
fact
that
you're,
using
only
get
specific
environment
variables
is
exactly
correct.
We
we
aren't
trying
to
give
them
a
general
purpose.
This
is
how
you
pass
pass.
Ssh
configuration
things
to
ssh.
That's
not
what
this
this
binding
does.
It's
just
to
focus
on
command
line,
git.
B
A
A
A
A
Yes,
and
and
and
that
matches
with
what
jesse
glick
had
suggested,
he
said:
hey
mark
you're,
doing
an
awful
lot
of
heroic
efforts
in
the
get
client
plug-in
to
use
passphrase
protected
private
keys,
and
you
could
just
crack
the
break
decrypt
the
passphrase
protected
into
a
non-protected
and
use
it
and
avoid
a
whole
lot
of
problems
and
so
you're
absolutely
right.
That
would
be
a
bonus
if
we
found
a
way
to
do
that.
B
A
B
A
A
A
A
B
B
I
mean
it
could
be
a
problem.
The
display
was,
I,
like,
I
don't
know
so
let
me
put
that
again,
so
I
was
working
on
the
asset
binding
and
I
figured
out
that
it
will
work.
I
put
the
environment
variable
and
set
the
environment
where
you'll
get
ssh
and
at
I
be
and
started
the
build
now
process
and
it
would
not
go
further.
It
just
froze
on
that.
B
B
A
Made
might
be
due
to
this
it.
It
could
be
yes,
because,
because
what
happens
if
well,
it
depends.
If
you
were
using
an
ssh
private
key
with
a
passphrase,
then
it
may
be
attempting
to
open
the
terminal.
And
if
you
were
running
your
build
from
a
terminal
window,
it's
actually
got
a
controlling
terminal,
then,
and
then
it
really
can
do
a
blocking
read
and
it
will
wait
for
human
input
and
usually
the
way
to
test.
That
is
if
it
seems
to
freeze
if
it
seems
to
pause
and
you're
running
a
command
line
program
like
maven.
A
A
So
at
least
that's
a
now.
That's
even
that's
not
a
guarantee,
because
terminals
are
sometimes
complicated
in
how
they
connect,
how
they
connect
to
the
keyboard
and
and
disconnect
so,
but
but
if
it
blocks,
if
it
pauses
during
a
build
during
an
operation
that
may
indicate
exactly
this
now
there
is,
there
is
a
command
on
some
linux
systems.
A
A
And
if
you,
if
you
were
to
look
up
the
this
system,
call
exists
in
bsd
and
in
linux
and
others.
This
is
a
system
call
to
choose
to,
or
a
library
call
that's
used
to
disconnect
standard
en
and
standard
out
and
standard
error
and
do
those
kind
of
things
so
in
in
this
case.
I
hope
you
don't
have
to
use
it
because
there
is
code
in
the
git
client
plug-in.
That
knows
how
to
do
this.
A
A
A
A
The
the
problem
with
that
checking
the
version
of
command
line
git
is
it
requires
a
call
to
command
line
git
and
I'm
not
sure
if
you
want
to
do
that
in
the
comment
in
the
credential
binding
right
now,
you
you
aren't
doing
any
calls
to
external
programs
before
entering
the
binding
right.
There's,
no,
no
need
for
you
to
call
separate
programs,
you
just
initialize
environment
variables
and
files.
B
A
Yeah
so
then
my
preference
is
that
we
would
use
get
ssh
command
as
first
choice
if,
if
we've
got
a
new
enough
command
line,
git
version
to
do
it
now,
if
you
find
that
hey,
there's,
not
a
real,
a
real
benefit
to
using
git
ssh
command
instead
of
get
ssh,
that's
something
you
could
you
could
educate
us
on.
I
had
understood
it
was
simpler
syntax,
but
because
of
the
complexity
of
centos
7,
I
didn't
implement
anything
to
support
the
simpler
syntax.