8000 Allow consumers to query the "backends" that libgit2 was built with by ethomson · Pull Request #6971 · libgit2/libgit2 · GitHub
[go: up one dir, main page]

Skip to content

Allow consumers to query the "backends" that libgit2 was built with #6971

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Dec 23, 2024

Conversation

ethomson
Copy link
Member

Provide a mechanism to understand the backend provider for feature
within libgit2. For example, one can query the mechanism that provides
HTTPS by asking for the backend for the GIT_FEATURE_HTTPS.

This is particularly useful for features that are not completely
isomorphic; the HTTPS providers may have slightly different
functionality that can be controlled (eg, certificates or cipher
support). And the SSH feature is very different between libssh2 and
OpenSSH.

It may also be useful to understand the support for things like the SHA1
or SHA256 backends to ensure that sha1dc is used, or that FIPS mode is
enabled.

Move the test for querying version information out of the
`core::features` test and into the `core::version` test.
@ethomson ethomson force-pushed the ethomson/features branch 7 times, most recently from 75b6665 to 7bd1cb8 Compare December 22, 2024 15:12
Add the status of the zlib backend (builtin or external) to
`git2_features.h`.
Provide a mechanism to understand the backend provider for feature
within libgit2. For example, one can query the mechanism that provides
HTTPS by asking for the backend for the `GIT_FEATURE_HTTPS`.

This is particularly useful for features that are not completely
isomorphic; the HTTPS providers may have slightly different
functionality that can be controlled (eg, certificates or cipher
support). And the SSH feature is _very_ different between libssh2 and
OpenSSH.

It may also be useful to understand the support for things like the SHA1
or SHA256 backends to ensure that sha1dc is used, or that FIPS mode is
enabled.
@ethomson ethomson merged commit 95dfb83 into main Dec 23, 2024
19 checks passed
@ethomson ethomson deleted the ethomson/features branch December 23, 2024 09:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant
0