| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
Declare GIT_CREDTYPE_SSH_MEMORY to have consistent API independently of
whether libgit2 was built with or without in-memory key passing support.
Or rather, to have it at all since build-time definitions are not stored
in headers.
|
| |
|
|
| |
To not modify the external api.
|
| | |
|
| |
|
|
|
|
|
| |
Instead of having it set in a different place from every other callback,
put it the main structure. This removes some state from the remote and
makes it behave more like clone, where the constructors are passed via
the options.
|
| | |
|
| |
|
|
|
| |
The user may have the data hashed as MD5 or SHA-1, so we should provide
both types for consumption.
|
| |
|
|
|
| |
Instead of using the libssh2 defines, provide our own, which eases usage
as we do not need to check whether libgit2 was built with libssh2 or not.
|
| |
|
|
|
|
| |
Instead of spreading the data in function arguments, some of which
aren't used for ssh and having a struct only for ssh, use a struct for
both, using a common parent to pass to the callback.
|
| |
|
|
| |
This should make the mingw compiler happy.
|
| |
|
|
|
|
| |
Instead of the parsed data, we can ask OpenSSL to give us the
DER-encoded version of the certificate, which the user can then parse
and validate.
|
| |
|
|
|
|
|
|
|
| |
If the certificate validation fails (or always in the case of ssh),
let the user decide whether to allow the connection.
The data structure passed to the user is the native certificate
information from the underlying implementation, namely OpenSSL or
WinHTTP.
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* Move the transport registration mechanisms into a new header under
'sys/' because this is advanced stuff.
* Remove the 'priority' argument from the registration as it adds
unnecessary complexity. (Since transports cannot decline to operate,
only the highest priority transport is ever executed.) Users who
require per-priority transports can implement that in their custom
transport themselves.
* Simplify registration further by taking a scheme (eg "http") instead
of a prefix (eg "http://").
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
git allows you to set which paths to use for the git server programs
when connecting over ssh; and we want to provide something similar.
We do this by providing a factory function which can be set as the
remote's transport callback which will set the given paths upon
creation.
|
| | | |
|
| | |
| |
| |
| |
| | |
This lets a user decide they do want to use keyboard-interactive after
they've compiled.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When linking against libssh2, create the transport.h such that it
contains its definition for custom crypto and keyboard-interactive
callbacks.
If we don't link against libssh2, create an equivalent signature which
has void pointers instead of pointers to libssh2 structures.
This would be one way to fix #2438.
|
| | |
| |
| |
| |
| | |
Since each cred defines the username on their own, introduce
git_cred__username to retrieve the username pointer from them.
|
| |/
|
|
|
| |
This exists as ssh needs to know about the username to use before it can
query for the supported authentication methods.
|
| |
|
|
|
| |
There were a couple of "init_opts()" functions a few more cases
of structure initialization that I somehow missed.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
This allows for keyboard-interactive based SSH authentication
|
| | |
|
| |
|
|
| |
The basic structure of each function is courtesy of arrbee.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
The callback-based method of listing remote references dates back to the
beginning of the network code's lifetime, when we didn't know any
better.
We need to keep the list around for update_tips() after disconnect() so
let's make use of this to simply give the user a pointer to the array so
they can write straightforward code instead of having to go through a
callback.
|
| |\
| |
| | |
Rename the ssh credentials
|
| | |
| |
| |
| |
| |
| | |
The names from libssh2 are somewhat obtuse for us. We can simplify the
usual key/passphrase credential's name, as well as make clearer what the
custom signature function is.
|
| |/
|
|
|
| |
There are any number of issues that can come up in the progress
callback, and we should let the user cancel at that point as well.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
Key-based authentication also needs an username, so include it in each
one.
Also stop assuming a default username of "git" in the ssh transport
which has no business making such a decision.
|
| |
|
|
| |
clang's docparser highlighted these.
|
| |
|
|
|
|
| |
The SSH APIs will just return an error code and state that the
library was built without SSH support if they are called in
that case.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
