Re: [Pyme-help] Re: PyME: Segmentation Faults
Status: Beta
Brought to you by:
belyi
From: Igor B. <be...@us...> - 2005-04-29 12:37:54
|
Robin Brandt wrote: > We tried several other setups during the last days and got the following > results. We used the "signverify.py" example from the pyme-0.6.2-tarball > as a reference. We didn"t change anything but the "user" variable at the > top of the script to an existing user in the keyring. You could also temporary create another key with genkey.py to avoid possibility that there's something wrong with the key itself. > #1: ibook g4, ubuntu 5.04 stable. > I tried the prepackaged gpg, libgpgme, swig packages and built a pyme > package from the tarball. Everything works as expected. Especially > "result.signatures.summary" is != zero for a valid signature. > #2: p4 laptop, debian unstable: > Everything from the distribution, pyme debian package from the > sourceforge-website. "result.signatures.summary" is always 0, even for a > valid signature. > #3: p3, debian testing: > see #2. > > We tried to rebuild everything from source (gpg 1.4.1, gpgme 1.0.2, pyme > 0.6.2 and from cvs) on systems #1 and #2 but it didn"t change a thing. > System #1 was always giving the right answers, the others didn"t. We > even tried different swig-version but it still didn"t improve the > situation. Do you have an idea what to try next? What kind of system do > you use? I have XP 1900+, debian unstable: ii libgpgme11 1.0.2-1 GPGME - GnuPG Made Easy ii gnupg 1.4.0-3 GNU privacy guard - a free PGP replacement Do you have the same keyring on all those systems? If they are different and you update 'user' in signverify.py for each of them I would recommend to generate a new temporary key in each of them with genkey.py example. This way you will be sure that key itself which also influences the summary does not cause the difference. BTW, you probably changed something else in signverify.py since in the original form it does not print 'signatures.summary' :o) I've added its printing on my system and it gives me back 3. Next step I would do is to try eliminating pyme out of the picture by either writing signverify in C using libgpgme11-dev directly or using t-verify.c from the tests/gpg directory of the libgpgme11 source. Cheers, Igor |