| Commit message (Collapse) | Author | Age | Files | Lines | 
| ... |  | 
| | 
| 
| 
| 
| 
|  | 
* lang/python/docs/gpgme-python-howto.org: Identified and fixed the
  headings which kept generating lines with trailing whitespace when
  exporting to Texinfo format and adjusted them to prevent that.
 | 
| | 
| 
| 
| 
| 
| 
| 
|  | 
* lang/python/docs/gpgme-python-howto.org: Renamed file to better fit
  the rest of the project's docs.
* Added a section on the very unofficial drafts I periodically post
  links to since they're often the easiest way to get a web version in
  front of someone in a hurry.
 | 
| | 
| 
| 
| 
| 
| 
| 
|  | 
* lang/python/docs/GPGMEpythonHOWTOen.org: Added corresponding GPGME
  version number to table at the start and cut the shortcut from the
  groups.py example.
* doc/gpgme-python-howto.texi: New export of Texinfo file for docs
  build.
 | 
| | 
| 
| 
| 
| 
| 
|  | 
* lang/python/docs/GPGMEpythonHOWTOen.org: Fixed a few errors in the
  newer sections.
* Updated code in the examples using secret key exporting and group
  lines to reflect the Python 2.7 compatibility fixes added.
 | 
| | 
| 
| 
| 
| 
|  | 
* lang/python/examples/howto/export-secret-keys.py and groups.py:
  Updated the backwards compatibility adjustments to account for
  unicode differences between python 2 and 3.
 | 
| | 
| 
| 
| 
| 
| 
| 
| 
| 
| 
|  | 
* lang/python/examples/howto/groups.py: subprocess update
* lang/python/examples/howto/export-secret-keys.py: subprocess update
  Both of these try the nice and easy method of getting the subprocess
  output available in Python 3, but will fall back to the older Popen
  method if it doesn't work.  Essentially this is to be a little nicer
  to Python 2.7.15 (even though the examples are filled with warnings
  that py2 support is not guaranteed with the examples).
 | 
| | 
| 
| 
| 
| 
|  | 
* minor typographic update.
Signed-off-by: Ben McGinnes <[email protected]>
 | 
| | 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
|  | 
* lang/python/src/core.py: Adjusted new_from_estream function to alias
  new_from_stream instead of fd.
* fixed the _gpgme import errors introduced in commit
  08cd34afb762975b0273575035dacf69449ef241 by changing the exported
  functions/types to match the inner module where all the work is
  done, rather than the outer one(s).
Tested-by: Ben McGinnes <[email protected]>
Signed-off-by: Ben McGinnes <[email protected]>
 | 
| | 
| 
| 
|  | 
* lang/python/src/core.py: expanded gpgme_error check lists.
 | 
| | 
| 
| 
| 
|  | 
* lang/python/src/core.py: added gpgme_data_set_flag to the errorcheck
  funtion.
 | 
| | 
| 
| 
| 
|  | 
* lang/python/src/core.py: added new function new_from_estream to wrap
  new_from_fd just like new_from_stream does and for the same reason.
 | 
| | 
| 
| 
| 
| 
| 
| 
|  | 
* lang/python/docs/GPGMEpythonHOWTOen.org: Updated links to the
  ProtonMail keyserver import scripts and added a warning regarding
  being unable to update third party keys.
* lang/python/examples/howto/pmkey-import-alt.py: added usage.
* lang/python/examples/howto/pmkey-import.py: added usage.
 | 
| | 
| 
| 
| 
| 
|  | 
* Finished CFFI vs SWIG bit in known issues.
* tidied up some of the structure.
* Fixed some minor errors and links.
 | 
| | 
| 
| 
|  | 
* Added section on why no CFFI.
 | 
| | 
| 
| 
|  | 
* Added another key import example using ProtonMail's new keyserver.
 | 
| | 
| 
| 
|  | 
* Added details on installation troubleshooting.
 | 
| | 
| 
| 
| 
| 
| 
|  | 
* import-key.py: fixed a minor typo.
* pmkey-import.py: locates and imports keys from the ProtonMail keyserver.
* pmkey-import-alt.py: the same as the previous except with setting an
  alternative $GNUPGHOME directory.
 | 
| | 
| 
| 
| 
| 
|  | 
* Moved the build import back up where it belongs.
* Included comments indicating how to build and install for multiple
  Python versions beyond the first 2 on the same system.
 | 
| | 
| 
| 
|  | 
* PEP8 compliance for the vast majoeity of the tests.
 | 
| | 
| 
| 
|  | 
* Appears to be complete compliance.
 | 
| | 
| 
| 
| 
| 
|  | 
* lang/python/version.py.in: Fixed most things, but there's still an
  issue near the build portion with the existing Python bugs referenced.
* lang/python/setup.py.in: Now PEP8 compliant.
 | 
| | 
| 
| 
| 
| 
|  | 
* PEP8 compliance for all constants except the globals in
  src/constants/__init__.py depending on whether the import sequence
  affects the globals themselves.
 | 
| | 
| 
| 
| 
|  | 
* import namespace clearance for src/*.py.
* Fixed a handful of is/is not None checks as well.
 | 
| | 
| 
| 
| 
| 
| 
| 
|  | 
* lang/python/examples/howto/symcrypt-file.py: *sigh*; passphrase was
  right the first time, just the error check that wasn't.
* I really should stop second guessing myself one of these days ...
Signed-off-by: Ben McGinnes <[email protected]>
 | 
| | 
| 
| 
| 
|  | 
* lang/python/examples/howto/symcrypt-file.py: Fixed the error code
  and the passphrase key word arg.
 | 
| | 
| 
| 
| 
|  | 
* lang/python/examples/howto/symcrypt-file.py: A variation on standard
  key based encryption.
 | 
| | 
| 
| 
| 
| 
| 
| 
| 
| 
| 
|  | 
* Ran all the .py files in src/ and below through Yapf.
* Included some manual edits of core.py, this time successfully making
  two notorious sections a bit more pythonic than scheming.
* Left the module imports as is.
* This will be committed if it passes the most essential test:
  compiling, installing and running it.
Signed-off-by: Ben McGinnes <[email protected]>
 | 
| | 
| 
| 
|  | 
* lang/python/README: Fixed links in both versions of the README.
 | 
| | 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
|  | 
* lang/python/tests/Makefile.am,
lang/qt/tests/Makefile.am,
tests/Makefile.am,
tests/gpg/Makefile.am,
tests/gpgsm/Makefile.am,
tests/opassuan/Makefile.am (GNUPGHOME): Make variable explict.
--
If the build directory has too long path, gpgme could fail.
This is similar to
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847206
In order to fix that, this patch extracts the GNUPGHOME variable
to be presented directly in the Makefile and thus overridable by
command line option.
A build system can then create a symlink to the GNUPGHOME directory
in /tmp and use that symlink as the GNUPGHOME directory
thus making the path very short.
GnuPG-Bug-Id: T4091
Patch provided by vlmarek
 | 
| | 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
|  | 
* Fixed and tested the changes necessary for org-mode to correctly
  parse pythonic (Python 3) indentation.
* Updated the source blocks to recommended upper case for BEGIN_SRC
  and END_SRC.
* Tested and confirmed XHTML output matches correct examples.
* Tested against pseudo-control output via exporting from org-mode to
  org-mode and then exporting that to XHTML.  Remaining differences
  appear to be discarding the custom tags used to provide X[HT]ML id
  elements to each section which does not appear to offer any benefit.
* Exporting directly to XHTML or other HTML output should no longer
  cause problems, but if there are any then the first step should be
  exporting from org-to-org and then exporting that to XHTML.
Tested-by: Ben McGinnes <[email protected]>
Signed-off-by: Ben McGinnes <[email protected]>
 | 
| | 
| 
| 
| 
| 
|  | 
* Another retrofitting of the HOWTO Python example code, this time
  following adjustments to python-mode configuration and having
  trawled through the org-mode mailing lists for clues.
 | 
| | 
| 
| 
|  | 
* Added org-mode byline.
 | 
| | 
| 
| 
| 
| 
|  | 
* Fixed incorrect mention of output prompt referencing secret keys
  when the scripts are only for exporting public keys in whole or
  minimised forms.
 | 
| | 
| 
| 
|  | 
* fixed three typos which were guaranteed to break said script.
 | 
| | 
| 
| 
| 
| 
| 
| 
| 
| 
| 
|  | 
* Complete typographic overhaul.
* Removed all section level indentation since it does not affect
  output formatting, but might affect source code examples.
* In text-mode stripped out all tabs which had crept in and replaced
  them with four spaces.
* Updated all code examples (again) to conform with Python-mode.
* Bumped version number in preparation for next release of GPG 2.2.9
  and corresponding GPGME release.
 | 
| | 
| 
| 
| 
|  | 
* Made sure all example scripts meet PEP8 compliance.
* Required fixing approx. a dozen of them in minor ways.
 | 
| | 
| 
| 
| 
| 
|  | 
* Apparently I am wrong and Scheme is the new Python after all.
* Non-import related PEP8 compliance must wait for another day, though
  the other PEP8 fixes remain.
 | 
| | 
| 
| 
| 
| 
| 
| 
| 
|  | 
* Changed id/else statements to a more pythonic form from scheme
  masquerading as python - sorry Justus, it had to go ;).
* With the added bonus of enabling PEP8 compliance in those sections.
* Fixed remaining PEP8 compliance issues with the exception of the
  imports at the beginning of the file (changing those will break the
  entire module, so we'll cope with it as it is).
 | 
| | 
| 
| 
| 
| 
| 
| 
|  | 
* Bindings confirmed to work with the newly released 3.7.0.
* Updated M4 file to reflect this change and correct the Python binary
  search order (3.7 is not yet given priority, but will still be found
  first via the more generic python3 executable).
* Updated setup.py.in, bindings documentation and README to reflect this.
 | 
| | 
| 
| 
|  | 
* There's always one or, in this case, two.
 | 
| | 
| 
| 
| 
|  | 
* Updated official doc (the org-mode file) with the instructions on
  importing and exporting both public and secret keys.
 | 
| | 
| 
| 
| 
| 
|  | 
* Added a secret key export variant which saves output as both GPG
  binary and ASCII armoured, plus saves in $GNUPGHOME and uses
  multiple methods of determining what that location is.
 | 
| | 
| 
| 
| 
|  | 
* Added a key import variant which accesses the SKS keyservers in a
  RESTful fashion and then imports or attempts to import the response.
 | 
| | 
| 
| 
| 
| 
| 
| 
|  | 
* Example of default exporting keys.
* Example of exporting minimised keys.
* Example of exporting secret keys to a file with correct permissions.
Signed-off-by: Ben McGinnes <[email protected]>
 | 
| | 
| 
| 
| 
|  | 
* Added an example script for importing a key from a file (either
  ASCII armoured or not).
 | 
| | 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
|  | 
* The holy grail: a function to export secret keys.
* GPGME will still invoke pinentry and gpg-agent as usual to authorise
  the export.
* Mostly similar to the two previous export functions for public keys
  except that it will return None if the result had a length of zero
  bytes.  Meaning that the difference between the specified pattern
  (if any) not matching available keys and an incorrect passphrase is
  not able to be determined from this function (or the underlying one
  for that matter).
Signed-off-by: Ben McGinnes <[email protected]>
 | 
| | 
| 
| 
| 
| 
|  | 
* Updated key_export and key_export_minimal to return None where a
  pattern matched no keys in a manner simnilar to the possible result
  of key_export_secret.
 | 
| | 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
|  | 
* Added functions for exporting public keys to gpg.core in both
  complete form and in minimised form.
* Rather than letting people need to worry about the export modes we
  are simply separating the functions as people would be more familiar
  with from the command line usage anyway.
* Functions added for Context are: ctx.key_export_minimal and
  ctx.key_export as the default or full export.
Signed-off-by: Ben McGinnes <[email protected]>
 | 
| | 
| 
| 
|  | 
* Fixed the bit I broke while fixing the PEP8 compliance issues.
 | 
| | 
| 
| 
| 
| 
| 
| 
|  | 
* Fixed most of the PEP8 errors in core.py
* Those remaining may need more than little edits and are a bit
  strange (too clearly the result of a programmer who has spent far
  too much time dealing with Lisp so that for Python it looks
  ... strange).
 |