crypto: Use libdnf crypto API instead of using GnuPG/GpgME #1980
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jrohel
force-pushed
the
feature/use_libdnf_crypto_API
branch
from
4ec5fb7
to
26a0fad
Compare
- It is compatible with the new librepo. The new librepo may use a different backend than GpgME internally. - Removes dependency on GnuPG/gpgme.
jrohel
force-pushed
the
feature/use_libdnf_crypto_API
branch
2 times, most recently
from
73d25ab
to
d02d931
Compare
jrohel
force-pushed
the
feature/use_libdnf_crypto_API
branch
from
d02d931
to
fc97339
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Requires PR rpm-software-management/libdnf#1616