PythonUmbrella
ActivePublic

Recent Activity

Mar 19 2019

aheinecke added a comment to T4276: Context.decrypt() throws an error if *any* signature is bad.

@dkg If you propose a patch here I'm pretty sure that we will accept it. As one of our Python binding users you know better then us how the API should behave.

Mar 19 2019, 3:51 PM · gpgme, Python, Bug Report
werner triaged T4276: Context.decrypt() throws an error if *any* signature is bad as Normal priority.
Mar 19 2019, 1:44 PM · gpgme, Python, Bug Report

Mar 12 2019

bernhard added a comment to T3505: Port GPGME's Python bindings to Windows.

Reading through this issue and the related documentation: Thanks for writing this all down and adding links!

Mar 12 2019, 5:50 PM · Feature Request, gpgme, Python

Jan 9 2019

aheinecke closed T3815: tests fail in 2021 as Resolved.

I sent a message to gnupg-devel about this issue as it will probably hit more people now that the keys used are expired :-(

Jan 9 2019, 8:52 AM · qt, Python, gpgme, Bug Report
aheinecke added a commit to T3815: tests fail in 2021: rM66376f3e206a: qt: Use tofu conflict test keys without expiry.
Jan 9 2019, 8:46 AM · qt, Python, gpgme, Bug Report
aheinecke added a comment to T3815: tests fail in 2021.

Oh,.. it is even worse. The conflict keys expired 2019-01-06 so they are actually expired right now.

Jan 9 2019, 8:18 AM · qt, Python, gpgme, Bug Report
aheinecke claimed T3815: tests fail in 2021.
Jan 9 2019, 8:12 AM · qt, Python, gpgme, Bug Report
werner reopened T3815: tests fail in 2021 as "Open".

I don't know why @BenM closed this bug given that he mentioned that the qt part is yet not solved.

Jan 9 2019, 8:00 AM · qt, Python, gpgme, Bug Report

Jan 8 2019

hedning added a comment to T3815: tests fail in 2021.

We've run into the testTofuConflict failure on NixOS. gpgme v1.12, gnupg v2.2.12.

Jan 8 2019, 8:05 PM · qt, Python, gpgme, Bug Report

Dec 15 2018

BenM added a comment to T3505: Port GPGME's Python bindings to Windows.

Though not directly related to our issues, this bug report on the MSYS2 site reported by their users encountering trouble with GPGME provides additional weight to irreconcilable differences between MSYS2 and GnuPG:

Dec 15 2018, 8:18 PM · Feature Request, gpgme, Python

Dec 10 2018

BenM closed T3815: tests fail in 2021 as Resolved.

Though apparently resolved back in May, this is what ultimately led to T4191 and was thus only properly resolved quite recently.

Dec 10 2018, 6:19 AM · qt, Python, gpgme, Bug Report
BenM closed T4271: python gpg.Context.decrypt(verify=False) no longer works as Resolved.

Confirmed that this is indeed fixed and made the (rather minor) change to the HOWTO that was needed. No changes were needed for the example script (decrypt-file.py).

Dec 10 2018, 6:08 AM · Python, gpgme, Bug Report
BenM closed T4191: gpgme python bindings test t-callbacks.py fails on 32-bit platforms as Resolved.

This has now been tested on a 32-bit Gentoo VM and it behaves as expected with 32-bit system detection and creating keys with pre-2038 expirations working.

Dec 10 2018, 4:51 AM · Python, gpgme, Bug Report

Dec 8 2018

BenM updated subscribers of T3505: Port GPGME's Python bindings to Windows.

Commit 8613727f1ee985c3cfa2c815523312914f033ffd adds considerable detail on both the issues affecting compiling and installing a Windows version of the bindings and what it would take to actually resolve it.

Dec 8 2018, 7:02 AM · Feature Request, gpgme, Python

Dec 6 2018

BenM added a comment to T4191: gpgme python bindings test t-callbacks.py fails on 32-bit platforms.

I'll deploy one on AWS somewhere briefly once I've replaced a certain external keyboard, there will almost certainly be an existing image of some Linux distro in the AWS marketplace and I'd be very surprised if it took more than an hour or two of compute time to confirm.

Dec 6 2018, 2:50 PM · Python, gpgme, Bug Report

Dec 5 2018

dkg added a comment to T4276: Context.decrypt() throws an error if *any* signature is bad.

One more semantic question about how folks think Context.decrypt(verify=True) should work: if the decrypted thing has no signature at all, should the function succeed without throwing an exception? it currently does, but the returned verify_result has its signatures member set to the empty list.

Dec 5 2018, 6:30 PM · gpgme, Python, Bug Report
BenM added a comment to T4271: python gpg.Context.decrypt(verify=False) no longer works.

Ooh, nice catch @dkg, I just stepped through each of your changes and it all looks good. I'll tweak the relevant sections of the HOWTO dealing with this in the next few days (I need to replace a keyboard here before properly diving back in) and then close this case once done.

Dec 5 2018, 4:14 PM · Python, gpgme, Bug Report
dkg added a comment to T4271: python gpg.Context.decrypt(verify=False) no longer works.

since @aheinecke merged my changes, i think this bug is now resolved. I'll let @BenM close it though :)

Dec 5 2018, 2:06 PM · Python, gpgme, Bug Report
dkg added a comment to T4276: Context.decrypt() throws an error if *any* signature is bad.

@aheinecke thanks for the merge of my other branch! sadly, that branch does *not* address this issue yet. It doesn't even test for it. :( I can work on trying to fix it (and test it) if there's a consensus that we want this particular change in behavior.

Dec 5 2018, 2:04 PM · gpgme, Python, Bug Report
aheinecke added a comment to T4276: Context.decrypt() throws an error if *any* signature is bad.

Is this fixed now?

Dec 5 2018, 11:54 AM · gpgme, Python, Bug Report
aheinecke added a commit to T4271: python gpg.Context.decrypt(verify=False) no longer works: rM65c28da4e49a: python: overhaul logic of Context.decrypt().
Dec 5 2018, 11:50 AM · Python, gpgme, Bug Report
aheinecke changed the status of T4271: python gpg.Context.decrypt(verify=False) no longer works from Open to Testing.

Ben is not even subscribed to this issue.
With the volatility of gpgme-python I think that this can easily be merged. I did a quick review and it looked good to me.

Dec 5 2018, 11:49 AM · Python, gpgme, Bug Report
werner added a comment to T4271: python gpg.Context.decrypt(verify=False) no longer works.

Needs to be merged. (Note that Phabricator does not show the branch in the tooltip for commit ids.)

Dec 5 2018, 10:44 AM · Python, gpgme, Bug Report
dkg added a comment to T4271: python gpg.Context.decrypt(verify=False) no longer works.

note that the branch also updates the test suite to make sure the verify=False case is tested.

Dec 5 2018, 6:34 AM · Python, gpgme, Bug Report
dkg created T4276: Context.decrypt() throws an error if *any* signature is bad.
Dec 5 2018, 6:18 AM · gpgme, Python, Bug Report
dkg added a commit to T4271: python gpg.Context.decrypt(verify=False) no longer works: rMac8d7238dbf1: python: overhaul logic of Context.decrypt().
Dec 5 2018, 12:51 AM · Python, gpgme, Bug Report
dkg added a comment to T4271: python gpg.Context.decrypt(verify=False) no longer works.

I've just pushed a branch dkg/fix-T4271 , currently at ac8d7238dbf165950c9844e5cb41da8eb4d37bc0 that resolves this problem.

Dec 5 2018, 12:51 AM · Python, gpgme, Bug Report

Nov 28 2018

werner triaged T4271: python gpg.Context.decrypt(verify=False) no longer works as Unbreak Now! priority.

Regression introduced with 1.12.0.

Nov 28 2018, 9:30 AM · Python, gpgme, Bug Report

Nov 27 2018

dkg added a comment to T4271: python gpg.Context.decrypt(verify=False) no longer works.

please add a unit to the test suite to make sure something like this doesn't happen in the future!

Nov 27 2018, 10:14 PM · Python, gpgme, Bug Report
dkg created T4271: python gpg.Context.decrypt(verify=False) no longer works.
Nov 27 2018, 10:10 PM · Python, gpgme, Bug Report

Nov 22 2018

dkg added a comment to T4191: gpgme python bindings test t-callbacks.py fails on 32-bit platforms.

i'd be happy to help you set up your own x86 32-bit guest VM for testing
if you like, even if you're running on x86_64 hardware. they're cheap
and easy to run, and have a delightfully small memory footprint :P just
let me know!

Nov 22 2018, 1:44 PM · Python, gpgme, Bug Report
BenM changed the status of T4191: gpgme python bindings test t-callbacks.py fails on 32-bit platforms from Open to Testing.
Nov 22 2018, 10:31 AM · Python, gpgme, Bug Report

Nov 5 2018

werner closed T3354: gpgme only builds against two versions of python at once as Resolved.

I consider this bug to be solved.

Nov 5 2018, 8:44 AM · Python, gpgme, Bug Report

Nov 3 2018

BenM added a comment to T3354: gpgme only builds against two versions of python at once.

MacPorts doesn't currently ship the bindings at all, but I'll see what they need to make that a reality too.

Nov 3 2018, 12:54 PM · Python, gpgme, Bug Report
BenM added a comment to T3354: gpgme only builds against two versions of python at once.

While this is now ideal for Debian, it may cause conflicts with other downstream vendors with slightly different needs to build their packages. In particular the FreeBSD ports and/or pkg system.

Nov 3 2018, 12:43 PM · Python, gpgme, Bug Report

Oct 29 2018

werner closed T4192: python gpg segfaults when first parameter to gpg.Context().op_genkey() is None or otherwise malformed as Resolved.
Oct 29 2018, 9:43 AM · Python, gpgme

Oct 20 2018

BenM added a comment to T4191: gpgme python bindings test t-callbacks.py fails on 32-bit platforms.

Nesting the op_genkey() calls inside try/except statements with the exceptions being caught as "oops" and otherwise "oops" being set to None provides a means of checking whether the 2099 expiration is a problem and 2037 is not.

Oct 20 2018, 2:37 AM · Python, gpgme, Bug Report
BenM added a comment to T4191: gpgme python bindings test t-callbacks.py fails on 32-bit platforms.

Well, I guess this answers my question in T4192 regarding why op_genkey was in use.

Oct 20 2018, 1:40 AM · Python, gpgme, Bug Report
BenM added a comment to T4192: python gpg segfaults when first parameter to gpg.Context().op_genkey() is None or otherwise malformed.

Interesting, I'll look into it, but is there a reason for using op_genkey instead of create_key (optionally with create_subkey and/or key_add_uid)? The latter should be easier and more pythonic.

Oct 20 2018, 1:16 AM · Python, gpgme
BenM added a comment to T3354: gpgme only builds against two versions of python at once.

This should already be possible, iirc the Arch Linux maintainer patched
it in. I believe there is a 'prepare' target that takes care of all the
preparations (duh), and then you can build for every Python version by
executing the Python build system with the Python version of your choice.

Oct 20 2018, 12:53 AM · Python, gpgme, Bug Report

Oct 19 2018

dkg added a comment to T3354: gpgme only builds against two versions of python at once.

@werner, thanks for rMff6ff616aea6 -- i've backported it to debian's packaging and it lets us cleanly build against all installed versions of python.

Oct 19 2018, 11:47 PM · Python, gpgme, Bug Report

Oct 18 2018

werner added a comment to T4191: gpgme python bindings test t-callbacks.py fails on 32-bit platforms.

That is up to @BenM

Oct 18 2018, 7:56 PM · Python, gpgme, Bug Report
dkg added a comment to T4191: gpgme python bindings test t-callbacks.py fails on 32-bit platforms.

the error i'd seen earlier after reverting the change was an error due to running t-callbacks.py on its own, without the rest of the test suite framework. running it within the test suite framework (with the change reverted), it passes without a problem. I've uploaded 1.12.0-4 to debian with a patch to t-callbacks.py. I can apply it upstream, if you want me to.

Oct 18 2018, 6:20 PM · Python, gpgme, Bug Report
werner added a comment to T4191: gpgme python bindings test t-callbacks.py fails on 32-bit platforms.

See T4195 for the general problem

Oct 18 2018, 6:10 PM · Python, gpgme, Bug Report
werner assigned T4191: gpgme python bindings test t-callbacks.py fails on 32-bit platforms to BenM.

I have not looked at the new error but the year 2099 is clearly a y2k38 problem. gpg has some precautions but I have not checked the key generation code. The gpgme interface uses a signed long for the expiration time, although that it parses the dates received from gpg as an unsigned long. Right now, I am not sure why we did this because an unsigned long would just work. Maybe we can change or enhance the interface. But in any case this is a general problem and not specific to this bug.

Oct 18 2018, 5:54 PM · Python, gpgme, Bug Report
werner changed the status of T4192: python gpg segfaults when first parameter to gpg.Context().op_genkey() is None or otherwise malformed from Open to Testing.
Oct 18 2018, 5:41 PM · Python, gpgme
werner added a commit to T4192: python gpg segfaults when first parameter to gpg.Context().op_genkey() is None or otherwise malformed: rMfbac11b19d97: core: Fix segv in genkey when no endtag is provided..
Oct 18 2018, 5:41 PM · Python, gpgme
werner added a comment to T4192: python gpg segfaults when first parameter to gpg.Context().op_genkey() is None or otherwise malformed.

@BenM thinks that swig is still the best option. Actually this case helped to find a bug in gpgme. See my next commit.

Oct 18 2018, 5:40 PM · Python, gpgme
dkg added a comment to T4191: gpgme python bindings test t-callbacks.py fails on 32-bit platforms.

The error might have to do with rM46da79e3de99a7b65748994921d6aab73b9974e7 which looks like it might run afoul of 32-bit time_t (Y2K38 problem?).

Oct 18 2018, 5:33 PM · Python, gpgme, Bug Report
dkg added a comment to T4191: gpgme python bindings test t-callbacks.py fails on 32-bit platforms.

here's me running just the specific test:

Oct 18 2018, 5:20 PM · Python, gpgme, Bug Report