Overview
Request 668267 accepted
- Enable tests
- Update to 0.4.4:
* Changed how any return value from the ``on_data`` callable is processed. In
earlier versions, the return value was ignored. In this version, if the
return value is ``False``, the data received from ``gpg`` is not buffered.
Otherwise (if the value is ``None`` or ``True``, for example), the data is
buffered as normal. This functionality can be used to do your own
buffering, or to prevent buffering altogether. The ``on_data`` callable is
also called once with an empty byte-string to signal the end of data from
``gpg``.
* Added an additional attribute ``check_fingerprint_collisions`` to
``GPG`` instances, which defaults to ``False``. It seems that ``gpg`` is
happy to have duplicate keys and fingerprints in a keyring, so we can't be
too strict. A user can set this attribute of an instance to ``True`` to
trigger a check for collisions.
* With GnuPG 2.2.7 or later, provide the fingerprint of a signing key for a
failed signature verification, if available.
* For verification where multiple signatures are involved, a mapping of
signature_ids to fingerprint, keyid, username, creation date, creation
timestamp and expiry timestamp is provided.
* Added a check to disallow certain control characters ('\r', '\n', NUL) in
passphrases.
- Created by scarabeus_iv
- In state accepted
Request History
scarabeus_iv created request
- Enable tests
- Update to 0.4.4:
* Changed how any return value from the ``on_data`` callable is processed. In
earlier versions, the return value was ignored. In this version, if the
return value is ``False``, the data received from ``gpg`` is not buffered.
Otherwise (if the value is ``None`` or ``True``, for example), the data is
buffered as normal. This functionality can be used to do your own
buffering, or to prevent buffering altogether. The ``on_data`` callable is
also called once with an empty byte-string to signal the end of data from
``gpg``.
* Added an additional attribute ``check_fingerprint_collisions`` to
``GPG`` instances, which defaults to ``False``. It seems that ``gpg`` is
happy to have duplicate keys and fingerprints in a keyring, so we can't be
too strict. A user can set this attribute of an instance to ``True`` to
trigger a check for collisions.
* With GnuPG 2.2.7 or later, provide the fingerprint of a signing key for a
failed signature verification, if available.
* For verification where multiple signatures are involved, a mapping of
signature_ids to fingerprint, keyid, username, creation date, creation
timestamp and expiry timestamp is provided.
* Added a check to disallow certain control characters ('\r', '\n', NUL) in
passphrases.
licensedigger accepted review
ok
factory-auto added opensuse-review-team as a reviewer
Please review sources
factory-auto added repo-checker as a reviewer
Please review build success
factory-auto accepted review
Check script succeeded
staging-bot added as a reviewer
Being evaluated by staging project "openSUSE:Factory:Staging:adi:28"
staging-bot accepted review
Picked openSUSE:Factory:Staging:adi:28
jengelh accepted review
repo-checker accepted review
cycle and install check passed
staging-bot accepted review
ready to accept
staging-bot approved review
ready to accept
dimstar_suse accepted request
Accept to openSUSE:Factory