| Commit message (Collapse) | Author | Age |
|---|
| |\
| |
| |
| | |
[dgit --quilt=gbp --overwrite]
|
| | |\ |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Origin: vendor
Bug: https://github.com/bestpractical/gnupg-interface/issues/8
Bug-Debian: https://bugs.debian.org/1016125
Last-Update: 2022-07-29
Gbp-Pq: Name version-stdin.patch
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Bug-Debian: https://bugs.debian.org/981647
Forwarded: Not-Needed
Reviewed-by: gregor herrmann <gregoa@debian.org>
Last-Update: 2021-08-18
Gbp-Pq: Name hardcode-path
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
Bug: https://rt.cpan.org/Ticket/Display.html?id=133041
Last-Update: 2021-01-28
Gbp-Pq: Name detect-taint-mode
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The test scripts require that gpg1, gpg and gnupg all exist and are
executable, otherwise warnings will be thrown.
This patch provides those "binaries", but they actually only print the
a version number that matches the binary.
It is still necessary to have at least one real GnuPG binary installed
for the test suite to pass. For Debian, but gpg and gpg1 need to be
present.
The patch to t/update_version.t isn't required on Debian, but is included
as this patch set has been forwarded upstream, and may be required
elsewhere. This is also why dummy scripts for gpg, gpg1 and gnupg are
provided.
Author: Andrew Ruthven
Bug: https://rt.cpan.org/Ticket/Display.html?id=133039
Last-Update: 2020-07-23
Gbp-Pq: Name test-dummy-binaries
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Bug: https://rt.cpan.org/Ticket/Display.html?id=133021
Last-Update: 2020-07-19
This test is checking that the old setter/getter interface
works. My fix to resetting the version causes this test to
fail on Debian as we have no binary called 'gnupg'. Since
the test is testing the setter/getter we don't care if
loading the version fails.
Gbp-Pq: Name test-allow-interface-to-fail
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Forwarded: not-needed
Last-Update: 2020-07-18
The test cases only test "gpg" which for Debian is v2. As the module also
supports v1 which we ship, we should test against it.
Gbp-Pq: Name test-gnupg1
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Bug: https://rt.cpan.org/Ticket/Display.html?id=133021
Last-Update: 2021-01-28
GnuPG::Interface allows the use of the 'call' method to change
the program to be used. Test that this works.
Gbp-Pq: Name test_reset_version_on_call_change
|
| | | |\
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
[ Debian Janitor ]
* Update renamed lintian tag names in lintian overrides.
[dgit import unpatched libgnupg-interface-perl 1.02-3]
|
| | | |
| | |
| | |
| | | |
[dgit import tarball libgnupg-interface-perl 1.02-3 libgnupg-interface-perl_1.02-3.debian.tar.xz]
|
| | |
| |
| |
| | |
[dgit import orig libgnupg-interface-perl_1.02.orig.tar.gz]
|
| | |\
| | |
| | |
| | | |
[dgit --quilt=gbp]
|
| | | |\
| | | |
| | | |
| | | | |
[dgit --quilt=gbp --overwrite]
|
| | | | |\ |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Last-Update: 2021-02-10
Forwarded: Not-Needed
Bug-Debian: https://bugs.debian.org/981647
Gbp-Pq: Name hardcode-path
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Bug: https://rt.cpan.org/Ticket/Display.html?id=133041
Last-Update: 2021-01-28
Gbp-Pq: Name detect-taint-mode
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The test scripts require that gpg1, gpg and gnupg all exist and are
executable, otherwise warnings will be thrown.
This patch provides those "binaries", but they actually only print the
a version number that matches the binary.
It is still necessary to have at least one real GnuPG binary installed
for the test suite to pass. For Debian, but gpg and gpg1 need to be
present.
The patch to t/update_version.t isn't required on Debian, but is included
as this patch set has been forwarded upstream, and may be required
elsewhere. This is also why dummy scripts for gpg, gpg1 and gnupg are
provided.
Author: Andrew Ruthven
Bug: https://rt.cpan.org/Ticket/Display.html?id=133039
Last-Update: 2020-07-23
Gbp-Pq: Name test-dummy-binaries
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Bug: https://rt.cpan.org/Ticket/Display.html?id=133021
Last-Update: 2020-07-19
This test is checking that the old setter/getter interface
works. My fix to resetting the version causes this test to
fail on Debian as we have no binary called 'gnupg'. Since
the test is testing the setter/getter we don't care if
loading the version fails.
Gbp-Pq: Name test-allow-interface-to-fail
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Forwarded: not-needed
Last-Update: 2020-07-18
The test cases only test "gpg" which for Debian is v2. As the module also
supports v1 which we ship, we should test against it.
Gbp-Pq: Name test-gnupg1
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Bug: https://rt.cpan.org/Ticket/Display.html?id=133021
Last-Update: 2021-01-28
GnuPG::Interface allows the use of the 'call' method to change
the program to be used. Test that this works.
Gbp-Pq: Name test_reset_version_on_call_change
|
| | | | | |\
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
* Explicitly specify path to gpg to avoid taint mode problems
(Closes: #981647)
[dgit import unpatched libgnupg-interface-perl 1.01-2]
|
| | | | | |
| | | | |
| | | | |
| | | | | |
[dgit import tarball libgnupg-interface-perl 1.01-2 libgnupg-interface-perl_1.01-2.debian.tar.xz]
|
| | | | |
| | | |
| | | |
| | | | |
[dgit import orig libgnupg-interface-perl_1.01.orig.tar.gz]
|
| | | | |\
| | | | |
| | | | |
| | | | | |
[dgit --quilt=gbp]
|
| | | | | |\
| | | | | |
| | | | | |
| | | | | | |
[dgit --quilt=gbp]
|
| | | | | | |\
| | | | | | |
| | | | | | |
| | | | | | | |
[dgit --quilt=gbp]
|
| | | | | | | |\
| | | | | | | |
| | | | | | | |
| | | | | | | | |
[dgit --quilt=gbp --overwrite]
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
GnuPG 2.2.8 onwards issues a hard failure when decrypting
messages not using the MDC mode.
Bug-Debian: https://bugs.debian.org/900051
Bug: https://github.com/bestpractical/gnupg-interface/pull/1
Gbp-Pq: Name 0001-Fix-test-suite-for-GnuPG-2.2.8-compatibility.patch
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
GnuPG 2.2.6 (commit 1a5d95e7319e7e6f) started marking signatures
with an expired key with '?', as seen with for instance
GNUPGHOME=./test/gnupghome/ gpg --list-sigs 0xF950DA9C
Adapt the test suite accordingly.
See https://dev.gnupg.org/rG1a5d95e7319e7e6f0dd11064a26cbbc371b05214
Bug-Debian: https://bugs.debian.org/900051
Bug: https://github.com/bestpractical/gnupg-interface/pull/1
Gbp-Pq: Name 0001-Fix-test-suite-for-GnuPG-2.2.6-compatibility.patch
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
* avoid sending --pinentry-mode=loopback if gpg is invoked as gpg1
* fix up t/list_secret_keys to account for the varied output
* t/decrypt.t still fails two agent-only tests, but presumably folks
who use gpg1 are not expecting to use the agent.
Gbp-Pq: Name 0019-Make-things-work-with-gpg1-assuming-plain-gpg-is-mod.patch
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
This avoids problems with the length of the path to the homedir as
compared to the size limits of sockaddr_un.sun_path, particularly on
systems where /run/user/$(id -u) is not present or available (such as
many minimalist build environments).
Gbp-Pq: Name 0018-Use-a-short-temporary-homedir-during-the-test-suite.patch
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
This helps to ensure that the test suite daemon is started fresh at
every test suite run. And it also avoids leaving a daemon running
after the test suite, assuming the test suite manages to reach the
end.
This is considered a reasonable practice by upstream.
Gbp-Pq: Name 0017-Kill-any-GnuPG-agent-before-and-after-the-test-suite.patch
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
The modern GnuPG suite encourages the use of gpg-agent to control
access to secret key material. In this use case, we avoid setting an
explicit passphrase in code, and rely on either a correctly-configured
and primed gpg-agent or a dedicated pinentry program to supply the
passphrase.
This additional test verifies that the passphrase can be handled by
the agent. Note that the passphrase for this additional test key is
*not* the default passphrase, so this test should fail in the event
that gpg can't use the agent and the pinentry for this task.
Unfortunately, this all assumes that we're using GnuPG "Modern". I've
noted concerns about writing forward- and backward-compatible bindings
for GnuPG here:
https://lists.gnupg.org/pipermail/gnupg-devel/2016-October/031800.html
Gbp-Pq: Name 0016-Test-use-of-gpg-without-explicit-passphrase-agent-pi.patch
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Adding a new secret key with a different passphrase should allow us to
differentiate between passing the passphrase explicitly and relying on
the agent + pinentry.
Gbp-Pq: Name 0015-added-new-secret-key-with-different-passphrase.patch
|
| | | | | | | | |
| | | | | | | |
| | | | | | | | |
Gbp-Pq: Name 0014-fix-spelling-s-convience-convenience.patch
|
| | | | | | | | |
| | | | | | | |
| | | | | | | | |
Gbp-Pq: Name 0013-move-key-files-to-generic-names.patch
|
| | | | | | | | |
| | | | | | | |
| | | | | | | | |
Gbp-Pq: Name 0012-use-fingerprints-as-inputs-during-tests-to-demonstra.patch
|
| | | | | | | | |
| | | | | | | |
| | | | | | | | |
Gbp-Pq: Name 0011-ommand_args-should-be-command_args.patch
|
| | | | | | | | |
| | | | | | | |
| | | | | | | | |
Gbp-Pq: Name 0010-fix-capitalization-of-GnuPG.patch
|
| | | | | | | | |
| | | | | | | |
| | | | | | | | |
Gbp-Pq: Name 0009-clean-up-trailing-whitespace.patch
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
In the modern GnuPG suite, where the passphrase is always managed by
the agent, gpg itself doesn't emit the GOOD_PASSPHRASE status.
Instead, if signing is successful it emits plain old SIG_CREATED.
There are probably even better ways to test whether a given key is
unlocked in this case, but this is a straightforward baseline fix that
should get this part of the test suite to pass with all available
versions of GnuPG.
Gbp-Pq: Name 0008-fix-test_default_key_passphrase-when-passphrase-come.patch
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
The human-readable version of --list-keys is *not* expected to be
static over time or as the user's environment changes (e.g. LANG or
LC_MESSAGES), so expecting it to be machine-parseable is probably a
mistake.
That said, some users might want to pull textual information about
specific keys to display directly to the user, so it's not a terrible
idea to have it in the test suite.
Modern GnuPG (2.1 or later) changes the default structure of the
human-readable output in a few significant ways:
* it writes the path to the keyring as an absolute path, even if
$GNUPGHOME is set to a non-absolute path.
* it shows the calculated user id validity by default (see
show-uid-validity in gpg's --list-options). (note that this is a
translated string, so that "unknown" (in the default C locale)
becomes "inconnue" when LANG or LC_MESSAGES is set to fr_CH.UTF-8,
for example.
* it writes the key algorithm names differently (e.g. rsa2048 instead
of 2048R)
* it does not display the key ID at all by default
* it displays the full fingerprint in compact form by default
This changeset fixes the test suite so that it can do a rough
verification of the human-readable text output by list_secret_keys in
the C locale in modern versions of GnuPG, while leaving it working for
older GnuPG suites.
Gbp-Pq: Name 0007-test-suite-match-plaintext-output-across-versions-of.patch
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
the GnuPG "modern" suite (version 2.1 or later) reports more detail
about secret keys than previous versions did. In particular, it
reports stored ownertrust, public key data, and designated revokers
for secret keys. Older versions only reported those attributes for
public keys.
This patch adjusts the test suite to ensure that our handmade key
matches the produced key when /usr/bin/gpg is supplied by the modern
suite.
Gbp-Pq: Name 0006-Modern-GnuPG-2.1-reports-more-detail-about-secret-ke.patch
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
MyTestSpecific.pm now produces a new variable indicating whether it
the version of GnuPG we run against is from the "Modern" line of GnuPG
development (2.1 or later). This will be useful when comparing output
that we can't expect from earlier versions.
Gbp-Pq: Name 0005-add-gpg_is_modern-to-test-suite.patch
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
The earlier test wasn't reporting on one of the known self-sigs for
the test key for some reason.
This change ensures that all known signatures are present.
Gbp-Pq: Name 0004-ensure-that-test-covers-all-signatures.patch
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
This apparently isn't tested by deep comparisons, though, so it was
never caught.
Gbp-Pq: Name 0003-subkey-validity-of-an-key-when-we-have-established-n.patch
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
The test suite currently assumes it knows something about the internal
state of GnuPG's homedir.
It's safer and less brittle to rely explicitly on the public interface
that GnuPG has committed to, such as --import-keys and --list-keys,
rather than assuming that certain files are in certain places in the
GnuPG homedir.
It's also better to create a fresh homedir and allow GnuPG to populate
it during the test suite, cleaning it up at the end, rather than hope
that GnuPG will leave a pre-existing homedir untouched.
With this change, many more of the tests pass when /usr/bin/gpg is
provided by GnuPG 2.1.
Gbp-Pq: Name 0002-Generalize-the-test-suite.patch
|
| | | | | | | | |
| | | | | | | |
| | | | | | | | |
Gbp-Pq: Name 0001-fix-spelling-error-settting-should-be-setting.patch
|
| | | | | | | | |\
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
* Team upload.
[ Salvatore Bonaccorso ]
* Update Vcs-* headers for switch to salsa.debian.org
[ Niko Tyni ]
* Patch the test suite for GnuPG >= 2.2.8 compatibility.
(Closes: #900051)
* Update to debhelper compat level 10
* Update to Standards-Version 4.1.4
* Declare that the package does not need (fake)root to build
[dgit import unpatched libgnupg-interface-perl 0.52-10]
|
