gpgme/lang, branch pyme3GnuPG Made Easy.http://git.bktus.com/gpgfrontend/gpgme/atom?h=pyme32015-08-02T01:06:14ZMore GTK2 removal2015-08-02T01:06:14ZBen McGinnesben@adversary.org2015-08-02T01:06:14Zurn:sha1:a7fbd5293ed0ba2c179837a4a2b859376d30e35e
* Missed a couple of files, these 2 go for the same reason as the
previous 3.
Removed GUI examples2015-08-02T01:01:02ZBen McGinnesben@adversary.org2015-08-02T01:01:02Zurn:sha1:1cd0aef0afb196094d90673002d4c210a04911c9
* GUI examples written with pygtk, which has not been ported to Python
3 and won't be as it is for GTK2 and GNOME is moving to GTK3.
* New GUI examples may be required in future using any of several GUI
frameworks (e.g. wxPython, PyQt, PySide, PyGObject, etc.).
Python 3 port of PyME2015-05-16T19:31:35ZBen McGinnesben@adversary.org2015-05-16T19:31:35Zurn:sha1:90405ac84b78ba7e5458ea09986749594a01195a
* Port of PyME 0.9.0 for Python 2 to Python 3 along with most of the
example scripts.
* Intended to be developed in parallel with the original Python 2
version until such time as a rewrite of GPGME leads to developing an
IO API in Python 3 from scratch.
* Python 3 PyME and API maintainer has entered, stage left with current
GPG key ID 0x321E4E2373590E5D, primary fingerprint is "DB47 24E6 FA42
86C9 2B4E 55C4 321E 4E23 7359 0E5D" and signing subkey fingerprint is
"B7F0 FE75 9387 430D D0C5 8BDB 7FF2 D371 35C7 553C" for future
reference with git commit signatures.
Explaining why not all scripts work2015-05-16T19:14:47ZBen McGinnesben@adversary.org2015-05-16T19:14:47Zurn:sha1:29887c9b28c0db14bf75e227a8082d23a2c151d2
* Some of them cannot be properly tested on OS X, especially with GTK in
the mix (it works on OS X, but is unlikely to be as easily accessible
as Cocoa or Qt).
* Most major functions are showcased and do work, albeit sometimes with
false positives of error messages, at least on OS X.
Byte encoding2015-05-16T19:07:12ZBen McGinnesben@adversary.org2015-05-16T19:07:12Zurn:sha1:c39cea7a07cec9ab34cd2026f47b6fba80fea3c8
* More string updates.
* verifydetails.py still fails, but as Bernhard is still contactable, it
might be worth him checking on it instead.
No change, note added to explain why.2015-05-16T18:57:26ZBen McGinnesben@adversary.org2015-05-16T18:57:26Zurn:sha1:0e6e6689ef1aea36c1cb3cb47e94f1f2ebbd97cbStrings vs. Bytes2015-05-16T18:43:53ZBen McGinnesben@adversary.org2015-05-16T18:43:53Zurn:sha1:40290507bcdc63ab9023393d071167d455d70737
* CLI input must be byte encoded.
More byte changes and passphrase changes2015-05-16T18:22:53ZBen McGinnesben@adversary.org2015-05-16T18:22:53Zurn:sha1:325b0ca341ae3ac8c3232f557ea2c381b4843969
* exportimport works, but will still segfault for an as yet unknown
reason.
* genkey produces a traceback error, but does create the key as
intended.
* matched passphrase in signverify.
More bytes good2015-05-16T18:09:38ZBen McGinnesben@adversary.org2015-05-16T18:09:38Zurn:sha1:ba3c9f2617955dc828309a4800e4f5b3f1c3a949
* Another string to byte change.
Updated encrypt-to-all2015-05-16T18:03:49ZBen McGinnesben@adversary.org2015-05-16T18:03:49Zurn:sha1:1c87ecb86ae364b18f69bca726021271fefaa1c1
* Changed plaintext string to byte literal.
* Nested key selection in a try/except statement in case of
UnicodeEncodeError instances.
* Tested successfully on over 9,000 keys.