pyme-help Mailing List for PyMe
Status: Beta
Brought to you by:
belyi
You can subscribe to this list here.
2005 |
Jan
|
Feb
|
Mar
|
Apr
(7) |
May
|
Jun
|
Jul
(1) |
Aug
(5) |
Sep
|
Oct
(5) |
Nov
(3) |
Dec
(3) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2006 |
Jan
(1) |
Feb
|
Mar
|
Apr
(5) |
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
2007 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2008 |
Jan
|
Feb
|
Mar
(5) |
Apr
|
May
|
Jun
|
Jul
(4) |
Aug
(7) |
Sep
(4) |
Oct
|
Nov
(7) |
Dec
|
2009 |
Jan
|
Feb
|
Mar
(7) |
Apr
|
May
|
Jun
(3) |
Jul
|
Aug
|
Sep
(1) |
Oct
(5) |
Nov
(3) |
Dec
|
2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(3) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2013 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(7) |
Oct
|
Nov
|
Dec
|
2014 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
(11) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2017 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
2018 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
From: Fabian A. S. <fsa...@de...> - 2018-12-13 22:20:34
|
hello, how do i best get this package installed on a fresh ubuntu 18.04 server? Thanks. -- -- Thanks, Fabian S. OpenPGP: 0xE05BF5EEFDD6549DAD3EDF64AE4E3D03B4F2DF29 |
From: Andreas L. <an...@kt...> - 2017-11-01 20:10:54
|
Hi pyme community! We have an old installation using pyme which made some trouble now and I fail setting up a simple environment already. Maybe somebody can help me or tell me it's hopeless. I wonder whether pyme is still maintained? Coming to the issue with the simple environment. I have trouble running the examples on a simple Ubuntu 14 LTS with the libgpgme11 and python-pyme (ships as 0.8) packages. Alternatively I compiled pyme 0.9 after installing the libgpgme11-dev package. The compilation and installation (actually overwriting the package files in the /usr/lib/python-2.7 folder. After compiling and installing, I could get the example simple.py to work. But genkey.py fails with "pyme.errors.GPGMEError: Invocation of gpgme_op_genkey: GPGME: General error (7,1)", and sign.py fails with "pyme.errors.GPGMEError: Invocation of gpgme_op_sign: GPGME: Unusable secret key (7,54)". These messages seem very odd and I cannot see any reason why. Does somebody have an idea what I'm doing wrong? Best Regards, Andreas |
From: Martin A. <mar...@go...> - 2014-05-12 09:23:18
|
On Monday 12 May 2014 09:29:54 Bernhard Reiter wrote: > Am Sonntag, 11. Mai 2014 15:12:18 schrieb Martin Albrecht: > > # Changes # > > > > * new maintainer: me > > * pip install git+https://bitbucket.org/malb/pyme should work > > > > * python setup.py calls make swig > > > > * svn → git (also: sourceforge → bitbucket) > > * fixing op_export_keys() > > > > Note that MinGW32 support is effectively dead, I don't have access to > > Windows boxes to test the outcome, so unless someone steps up to help with > > that, it's probably broken by the good ol' rule: what isn't tested is > > broken. > > Just a few remarks on this point: > a) I believe windows-support would be an important feature, so we are in > need of a maintainer of it. I'm starting windows too rarely to be of > practical help here. > b) We (at Intevation) mostly moved to http://mingw-w64.sourceforge.net/ > for windows builds, they also build 32bit, but the Initiative seems to be > more solid. Or http://mxe.cc/. I agree Windows support is good to have and I didn't take any active steps to remove it. I am all for finding a maintainer for it! I will mention the lack of Windows support prominently in the release notes, let's see if someone steps up. Btw. judging from Makefile and setup.py pyme was supposed to compile under cygwin (cygwin paths hardcoded), That is, I don't think these targets are for cross-compilation, but I could be wrong. Cross-compilation would slightly less daunting as it can be done from the comfort of POSIX :) Cheers, Martin |
From: Bernhard R. <ber...@in...> - 2014-05-12 07:30:19
|
Am Sonntag, 11. Mai 2014 15:12:18 schrieb Martin Albrecht: > I think 0.9.0 is about ready to go. Cool! > # Changes # > > * new maintainer: me > * pip install git+https://bitbucket.org/malb/pyme should work > * python setup.py calls make swig > * svn → git (also: sourceforge → bitbucket) > * fixing op_export_keys() > > Note that MinGW32 support is effectively dead, I don't have access to > Windows boxes to test the outcome, so unless someone steps up to help with > that, it's probably broken by the good ol' rule: what isn't tested is > broken. Just a few remarks on this point: a) I believe windows-support would be an important feature, so we are in need of a maintainer of it. I'm starting windows too rarely to be of practical help here. b) We (at Intevation) mostly moved to http://mingw-w64.sourceforge.net/ for windows builds, they also build 32bit, but the Initiative seems to be more solid. Or http://mxe.cc/. > # Todo # > > I'd be great if you could test this version as I plan to submit it as is to > to the PyPI and Debian. Also, anything I should add to README.md? > > # Roadmap # > > * PyME doesn't have unittests as far as I can tell, this should change > * PyME's build system is - in my eyes - a bit messy, I'd like to clean it > up > > Cheers, > Martin -- www.intevation.de/~bernhard (CEO) www.fsfe.org (Founding GA Member) Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998 Geschäftsführer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner |
From: Martin A. <mar...@go...> - 2014-05-11 13:12:26
|
Hi all, I think 0.9.0 is about ready to go. # Changes # * new maintainer: me * pip install git+https://bitbucket.org/malb/pyme should work * python setup.py calls make swig * svn → git (also: sourceforge → bitbucket) * fixing op_export_keys() Note that MinGW32 support is effectively dead, I don't have access to Windows boxes to test the outcome, so unless someone steps up to help with that, it's probably broken by the good ol' rule: what isn't tested is broken. # Todo # I'd be great if you could test this version as I plan to submit it as is to to the PyPI and Debian. Also, anything I should add to README.md? # Roadmap # * PyME doesn't have unittests as far as I can tell, this should change * PyME's build system is - in my eyes - a bit messy, I'd like to clean it up Cheers, Martin |
From: Bernhard R. <ber...@in...> - 2014-05-07 13:39:08
|
Am Mittwoch, 7. Mai 2014 15:28:56 schrieb Martin Albrecht: > > Do you want to continue this mailinglist? > > Might as well keep it around? Could bite us since we're not admins but for > now I'd say: baby steps :) Fine with me, just making sure! So the central public communication point for the "pyme Initiative" is pym...@li...! :) > > Yes, a new version like 1.0 or 0.9 would be cool! > > Actually because I don't have an overview what is missing, > > why not call it v1.0? > > I've no overview either. It's only bugfixes so far, hence I'd simply go for > 0.8.2. But maybe 0.9 to indicate there's been some major social change? 1.0 > is too ambitious in my view. Then my recommendation is to go with 0.9. Bernhard -- www.intevation.de/~bernhard (CEO) www.fsfe.org (Founding GA Member) Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998 Geschäftsführer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner |
From: Martin A. <mar...@go...> - 2014-05-07 13:28:51
|
On Wednesday 07 May 2014 14:55:34 Bernhard Reiter wrote: > Am Mittwoch, 7. Mai 2014 13:12:17 schrieb Martin Albrecht: > > :) To be honest, I'd just stick with bitbucket for the time being, > > Fine, I've updated http://wiki.gnupg.org/APIs accordingly. > > Do you want to continue this mailinglist? Might as well keep it around? Could bite us since we're not admins but for now I'd say: baby steps :) > > Okay, PyME it is. I'll merge my fixes branch into master and bump the > > version number, i.e. I shall do a new release. > > Yes, a new version like 1.0 or 0.9 would be cool! > Actually because I don't have an overview what is missing, > why not call it v1.0? I've no overview either. It's only bugfixes so far, hence I'd simply go for 0.8.2. But maybe 0.9 to indicate there's been some major social change? 1.0 is too ambitious in my view. > Best, > Bernhard Cheers, Martin |
From: Bernhard R. <ber...@in...> - 2014-05-07 12:55:47
|
Am Mittwoch, 7. Mai 2014 13:12:17 schrieb Martin Albrecht: > :) To be honest, I'd just stick with bitbucket for the time being, Fine, I've updated http://wiki.gnupg.org/APIs accordingly. Do you want to continue this mailinglist? > Okay, PyME it is. I'll merge my fixes branch into master and bump the > version number, i.e. I shall do a new release. Yes, a new version like 1.0 or 0.9 would be cool! Actually because I don't have an overview what is missing, why not call it v1.0? Best, Bernhard -- www.intevation.de/~bernhard (CEO) www.fsfe.org (Founding GA Member) Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998 Geschäftsführer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner |
From: Martin A. <mar...@go...> - 2014-05-07 11:12:07
|
On Tuesday 06 May 2014 16:48:00 Bernhard Reiter wrote: > > > Martin do you intent to at least maintain pyme a bit? > > > > I'm using it, so I'll maintain it to some extend. > > Very cool! Then it is your choice, I'm just trying to help you > come to a good decision. :) To be honest, I'd just stick with bitbucket for the time being, this way it fits most naturally into my workflow. If anyone has strong feelings about this, we can revisit and move at a later date. > > I'd appreciate help/advise from more experienced members of the community > > (most of my coding projects are fairly academic), though. For example, I > > wouldn't actively pursue, say, Debian updating its repositories as I have > > no experience with that. If someone would help with that, I'd appreciate > > it. > > I certainly is a good idea to communicate with the Debian package > maintainers. You can write problem reports in their trackers or contact > them right away. Everytime you believe something is interesting for them: > http://packages.qa.debian.org/p/pyme.html I shall add this to my todo list. > > Shall we rename it to PyME2 or something though? > > As Igor is missing in action, I believe we should keep the name > and just continue as the original. I mean, if he comes back, he is very > welcome and we could still change the name. From my point of view, this is > the legitimate continuation. Okay, PyME it is. I'll merge my fixes branch into master and bump the version number, i.e. I shall do a new release. Cheers, Martin |
From: Bernhard R. <ber...@in...> - 2014-05-06 14:48:10
|
Am Dienstag, 6. Mai 2014 16:00:53 schrieb Martin Albrecht: > On Monday 05 May 2014 15:34:55 Bernhard Reiter wrote: > > The manual (*) say we should fork now. > > Does it make sense to still do this on SF? > > > > I see two advantages of forking on SF. > > a) people will mor easily find the "continuation" > > b) SF uses Allura a Free Software hosting platform, were bitbucket is > > proprietary > > Drawbacks: > > c) effort > > d) advertisment on sf > > It should be easy to migrate from BitBucket to SF. TBH I don't mind either > way: GitHub, BitBucket, SourceForge. As SF is the service running a Free Software platform, that usually is may choice (with hg instead of git, but that is just my preferance). > Doing it on GitHub might encourage people to send pull requests and stuff, > so GitHub might have that going for itself. I don't know if BB vs. SF makes > a difference in that regard. I hope Allura will implement this sooner or later. > > Martin do you intent to at least maintain pyme a bit? > > I'm using it, so I'll maintain it to some extend. Very cool! Then it is your choice, I'm just trying to help you come to a good decision. > I'd appreciate help/advise from more experienced members of the community > (most of my coding projects are fairly academic), though. For example, I > wouldn't actively pursue, say, Debian updating its repositories as I have > no experience with that. If someone would help with that, I'd appreciate > it. I certainly is a good idea to communicate with the Debian package maintainers. You can write problem reports in their trackers or contact them right away. Everytime you believe something is interesting for them: http://packages.qa.debian.org/p/pyme.html > Shall we rename it to PyME2 or something though? As Igor is missing in action, I believe we should keep the name and just continue as the original. I mean, if he comes back, he is very welcome and we could still change the name. From my point of view, this is the legitimate continuation. Best, Bernhard -- www.intevation.de/~bernhard (CEO) www.fsfe.org (Founding GA Member) Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998 Geschäftsführer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner |
From: Martin A. <mar...@go...> - 2014-05-06 14:00:46
|
On Monday 05 May 2014 15:34:55 Bernhard Reiter wrote: > The manual (*) say we should fork now. > Does it make sense to still do this on SF? > I see two advantages of forking on SF. > a) people will mor easily find the "continuation" > b) SF uses Allura a Free Software hosting platform, were bitbucket is > proprietary > Drawbacks: > c) effort > d) advertisment on sf It should be easy to migrate from BitBucket to SF. TBH I don't mind either way: GitHub, BitBucket, SourceForge. Doing it on GitHub might encourage people to send pull requests and stuff, so GitHub might have that going for itself. I don't know if BB vs. SF makes a difference in that regard. I used BitBucket because they gave me an ultimate account for free (being an academic) so it's my default choice for most stuff. > Martin do you intent to at least maintain pyme a bit? I'm using it, so I'll maintain it to some extend. I'd appreciate help/advise from more experienced members of the community (most of my coding projects are fairly academic), though. For example, I wouldn't actively pursue, say, Debian updating its repositories as I have no experience with that. If someone would help with that, I'd appreciate it. Shall we rename it to PyME2 or something though? > Then I'll just change the link on wiki.gnupg.org > (*) http://sourceforge.net/p/forge/documentation/Abandoned Projects/ Cheers, Martin |
From: Bernhard R. <ber...@in...> - 2014-05-05 13:35:06
|
Am Samstag, 3. Mai 2014 20:50:35 schrieb Martin Albrecht: > Hi all, > > on a related note: I've applied my old-ish patch + some "fixes" to setup.py > to the fixes branch of: > > https://bitbucket.org/malb/pyme > > In particular, > > $ pip install git+https://bitbucket.org/malb/pyme@fixes > > now works on my machine. The manual (*) say we should fork now. Does it make sense to still do this on SF? I see two advantages of forking on SF. a) people will mor easily find the "continuation" b) SF uses Allura a Free Software hosting platform, were bitbucket is proprietary Drawbacks: c) effort d) advertisment on sf Martin do you intent to at least maintain pyme a bit? Then I'll just change the link on wiki.gnupg.org (*) http://sourceforge.net/p/forge/documentation/Abandoned Projects/ -- www.intevation.de/~bernhard (CEO) www.fsfe.org (Founding GA Member) Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998 Geschäftsführer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner |
From: Martin A. <mar...@go...> - 2014-05-03 18:50:46
|
Hi all, on a related note: I've applied my old-ish patch + some "fixes" to setup.py to the fixes branch of: https://bitbucket.org/malb/pyme In particular, $ pip install git+https://bitbucket.org/malb/pyme@fixes now works on my machine. Cheers, Martin On Saturday 26 Apr 2014 22:46:46 Bernhard Reiter wrote: > Am Dienstag, 17. September 2013, 10:31:34 schrieb Martin Albrecht: > > I'll drop Igor an e-mail directly, let's see what he says. Thanks > > for the hint re pygpgme. > > Am Dienstag, 17. September 2013, 10:38:03 schrieben Sie: > > FYI, his e-mail address is defunct. > > I've now followed advise on > http://sourceforge.net/p/forge/documentation/Abandoned Projects/ > and used the internal sf messaging service to drop Igor a line. > > Best, > Bernhard |
From: Martin A. <mar...@go...> - 2014-04-27 08:54:20
|
Thanks Bernhard, keep us posted if he gets back to you. On Saturday 26 Apr 2014 22:46:46 Bernhard Reiter wrote: > Am Dienstag, 17. September 2013, 10:31:34 schrieb Martin Albrecht: > > I'll drop Igor an e-mail directly, let's see what he says. Thanks > > for the hint re pygpgme. > > Am Dienstag, 17. September 2013, 10:38:03 schrieben Sie: > > FYI, his e-mail address is defunct. > > I've now followed advise on > http://sourceforge.net/p/forge/documentation/Abandoned Projects/ > and used the internal sf messaging service to drop Igor a line. > > Best, > Bernhard |
From: Bernhard R. <ber...@in...> - 2014-04-26 20:47:01
|
Am Dienstag, 17. September 2013, 10:31:34 schrieb Martin Albrecht: > I'll drop Igor an e-mail directly, let's see what he says. Thanks > for the hint re pygpgme. Am Dienstag, 17. September 2013, 10:38:03 schrieben Sie: > FYI, his e-mail address is defunct. I've now followed advise on http://sourceforge.net/p/forge/documentation/Abandoned Projects/ and used the internal sf messaging service to drop Igor a line. Best, Bernhard -- www.intevation.de/~bernhard (CEO) www.fsfe.org (Founding GA Member) Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998 Geschäftsführer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner |
From: Martin A. <mar...@go...> - 2013-09-17 09:31:45
|
Hi all, I am not that keen on maintaining it, since I don't know yet how often I'll use it, yet. I'll drop Igor an e-mail directly, let's see what he says. Thanks for the hint re pygpgme. Cheers, Martin On Monday 16 Sep 2013 21:36:34 Bernhard Reiter wrote: > Am Montag, 16. September 2013, 13:30:06 schrieb Martin Albrecht: > > > So where is Igor that we can commit this stuff? > > > If Igor does not reappear could be claim the SF entry somehow? Or > > > would be move to a different place with hg hosting or so? > > > > How long to wait before forking? > > I wouldn't call it forking, but moving the pyme initiative to a different > place. If you are willing to do it, why not send Igor a personal email > and then wait about 14 days? I think 3 weeks is important, because > everybody can be on vacation for this time and offline and it just would > be nice. At least the mailinglist archives some of the contributions, so > they are not lost. > > I'd prefer to move the hg, btw, it is possible with sf. > But I only occasionally use pyme. There is a pygpgme which also looks > promissing, because it is a native binding. > > Best, > Bernhard -- name: Martin Albrecht _pgp: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x6532AFB4 _otr: 47F43D1A 5D68C36F 468BAEBA 640E8856 D7951CCF _www: http://martinralbrecht.wordpress.com/ _jab: mar...@ja... |
From: Bernhard R. <ber...@in...> - 2013-09-16 19:36:45
|
Am Montag, 16. September 2013, 13:30:06 schrieb Martin Albrecht: > > So where is Igor that we can commit this stuff? > > If Igor does not reappear could be claim the SF entry somehow? Or > > would be move to a different place with hg hosting or so? > How long to wait before forking? I wouldn't call it forking, but moving the pyme initiative to a different place. If you are willing to do it, why not send Igor a personal email and then wait about 14 days? I think 3 weeks is important, because everybody can be on vacation for this time and offline and it just would be nice. At least the mailinglist archives some of the contributions, so they are not lost. I'd prefer to move the hg, btw, it is possible with sf. But I only occasionally use pyme. There is a pygpgme which also looks promissing, because it is a native binding. Best, Bernhard -- www.intevation.de/~bernhard (CEO) www.fsfe.org (Founding GA Member) Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998 Geschäftsführer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner |
From: Martin A. <mar...@go...> - 2013-09-16 12:30:17
|
On Friday 13 Sep 2013 15:06:06 Bernhard Reiter wrote: > Am Freitag, 13. September 2013 12:14:47 schrieb Martin Albrecht: > > On Friday 13 Sep 2013 11:12:15 Bernhard Reiter wrote: > > > Can you give some more details about the problem and how it can be > > > triggered? I found small testing scripts ideal. > > > > I've attached a hacked together script which exports all keys, it's based > > on encrypt-to-all.py in the examples directory. If you run PyMe without my > > patch it will complain about expecting gpgme_key_t [], with my patch you > > get all keys. > > Cool, I can confirm that the script shows a defect that the patch fixes. > (Tested on Debian Squeeze with python2.6 and gpgme-0.8.1.tar.gz.) > > Thanks again Martin! > > So where is Igor that we can commit this stuff? > If Igor does not reappear could be claim the SF entry somehow? Or would be > move to a different place with hg hosting or so? > > Best, > Bernhard How long to wait before forking? :) -- name: Martin Albrecht _pgp: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x6532AFB4 _otr: 47F43D1A 5D68C36F 468BAEBA 640E8856 D7951CCF _www: http://martinralbrecht.wordpress.com/ _jab: mar...@ja... |
From: Bernhard R. <ber...@in...> - 2013-09-13 13:06:24
|
Am Freitag, 13. September 2013 12:14:47 schrieb Martin Albrecht: > On Friday 13 Sep 2013 11:12:15 Bernhard Reiter wrote: > > Can you give some more details about the problem and how it can be > > triggered? I found small testing scripts ideal. > > I've attached a hacked together script which exports all keys, it's based > on encrypt-to-all.py in the examples directory. If you run PyMe without my > patch it will complain about expecting gpgme_key_t [], with my patch you > get all keys. Cool, I can confirm that the script shows a defect that the patch fixes. (Tested on Debian Squeeze with python2.6 and gpgme-0.8.1.tar.gz.) Thanks again Martin! So where is Igor that we can commit this stuff? If Igor does not reappear could be claim the SF entry somehow? Or would be move to a different place with hg hosting or so? Best, Bernhard -- www.intevation.de/~bernhard (CEO) www.fsfe.org (Founding GA Member) Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998 Geschäftsführer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner |
From: Martin A. <mar...@go...> - 2013-09-13 10:15:19
|
Hi Berhard, On Friday 13 Sep 2013 11:12:15 Bernhard Reiter wrote: > Can you give some more details about the problem and how it can be > triggered? I found small testing scripts ideal. I've attached a hacked together script which exports all keys, it's based on encrypt-to-all.py in the examples directory. If you run PyMe without my patch it will complain about expecting gpgme_key_t [], with my patch you get all keys. Cheers, Martin -- name: Martin Albrecht _pgp: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x6532AFB4 _otr: 47F43D1A 5D68C36F 468BAEBA 640E8856 D7951CCF _www: http://martinralbrecht.wordpress.com/ _jab: mar...@ja... |
From: Bernhard R. <ber...@in...> - 2013-09-13 09:12:26
|
Hi Martin, Am Donnerstag, 12. September 2013 22:16:37 schrieb Martin Albrecht: > let's see if this list can still be activated :) at least I'm still reading and writing here. ;) > I found and fixed a bug - I think - in pyme: op_export_keys() failed > because the conversion of gpgme_key_t [] was restricted to gpgme_key_t [] > with the name recv, i.e. only the use-cases of encryption were covered. > I've attached the diff. Cool, thanks a lot for sharing! Can you give some more details about the problem and how it can be triggered? I found small testing scripts ideal. Best Regards, Bernhard -- www.intevation.de/~bernhard (CEO) www.fsfe.org (Founding GA Member) Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998 Geschäftsführer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner |
From: Martin A. <mar...@go...> - 2013-09-12 20:44:05
|
Hi there, let's see if this list can still be activated :) I found and fixed a bug - I think - in pyme: op_export_keys() failed because the conversion of gpgme_key_t [] was restricted to gpgme_key_t [] with the name recv, i.e. only the use-cases of encryption were covered. I've attached the diff. Cheers, Martin -- name: Martin Albrecht _pgp: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x6532AFB4 _otr: 47F43D1A 5D68C36F 468BAEBA 640E8856 D7951CCF _www: http://martinralbrecht.wordpress.com/ _jab: mar...@ja... |
From: Jerome C. <je...@ri...> - 2010-07-21 17:16:58
|
Le 2010-07-21 08:46, Werner Koch a écrit : >> Am Mittwoch, 21. Juli 2010 09:18:22 schrieb Jerome Charaoui: >>> I'd like to know if it's possible to retrieve a PGP key from a keyserver >>> with PyMe. >>> >>> According to the GPGME documentation, this should be possible by >>> combining mode.LOCAL with mode.EXTERN. However when I try this I >>> consistently get a EOF error. > > > What this kludge dioes is to use the --locate-keys option of gpg: > > --locate-keys > Locate the keys given as arguments. This command basically uses > the same algorithm as used when locating keys for encryption or > signing and may thus be used to see what keys gpg2 might use. > In particular external methods as defined by --auto-key-locate > may be used to locate a key. Only public keys are listed. Thanks for the explanation. It seems that --locate-keys is designed to be used when doing encryption or signing operations. What I need is, given a fingerprint, simply download the corresponding public key from a keyserver and load it into a PyMe key object. If PyMe/GPGME doesn't support this kind of operation, are there other alternatives to calling /usr/bin/gpg ? Thanks, -- Jerome |
From: Bernhard R. <ber...@in...> - 2010-07-21 09:45:50
|
Am Mittwoch, 21. Juli 2010 09:18:22 schrieb Jerome Charaoui: > I'd like to know if it's possible to retrieve a PGP key from a keyserver > with PyMe. > > According to the GPGME documentation, this should be possible by > combining mode.LOCAL with mode.EXTERN. However when I try this I > consistently get a EOF error. A good question. I would direct it to gnupg-devel@ and ask if it is possible with GPGME. In order to facilitate the question I directly post it there. If it is possible with GPGME, it should be possible with pyme as well. Make sure to use the right gpgme gnupg2 version before trying. > I verified my GPG confguration and the correct keyservers are in there. > Also, retrieving keys from command-line GPG works fine. The gpg2 command line does not use gpgme, but it demonstrates the the configuration and the helpers are all there. -- Managing Director - Owner: www.intevation.net (Free Software Company) Deputy Coordinator Germany: fsfe.org. Board member: www.kolabsys.com. Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998 Geschäftsführer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner |
From: Jerome C. <je...@ri...> - 2010-07-21 07:33:58
|
Hello, I'd like to know if it's possible to retrieve a PGP key from a keyserver with PyMe. According to the GPGME documentation, this should be possible by combining mode.LOCAL with mode.EXTERN. However when I try this I consistently get a EOF error. I verified my GPG confguration and the correct keyservers are in there. Also, retrieving keys from command-line GPG works fine. Thanks, -- Jerome |