|  | Commit message (Collapse) | Author | Age | Files | Lines | 
|---|
| | 
| 
| 
| 
| 
| 
| 
| | * Clarified which English dialects this is written in.
* Translating to American can happen *after* it's done.
** The Yank version would probably want to change some of the examples
   anyway.
* Began the description for normal/default signing. | 
| | 
| 
| 
| 
| 
| 
| 
| | * Added a section on key selection.
* Included recommendation for using fingerprint when selecting one
  specific key.
* Also included the most ironically amusing example of multiple key
  selection in a GPG guide.  Hey, it's public data ... (heh). | 
| | 
| 
| 
| 
| 
| 
| | * Added explanation of the ascendance of Python 3 over Python 2 in the
  guide to the intro.
* Expanded key selection description so people know what not to
  include regarding key IDs with this key selection method. | 
| | 
| 
| 
| | * Added key selection for specifying signing key or keys. | 
| | 
| 
| 
| 
| 
| 
| | * During the course of working out the updated signature methods,
  determined that key selection (including counting) will beed to be
  presented before the basic functions.
* Moved "working with keys" up. | 
| | 
| 
| 
| 
| 
| | * Signatures have changed as a result of the recent update from Justus.
* Sample code updated.
* Text to follow later. | 
| | 
| 
| 
| | * Added text description for the decryption example. | 
| | 
| 
| 
| 
| 
| 
| 
| | * Added a miscellaneous work-arounds section at the end.
* Included code in said miscellaneous section for accessing the groups
  specified in a gpg.conf file.
* It's a bit ugly since it does require subprocess (but not call,
  Popen or shell access and only accesses one command). | 
| | 
| 
| 
| | * Fixed a spelling error in the key counting text. | 
| | 
| 
| 
| 
| 
| 
| | * updated multi-encryption final example to be complete.
* second example shows most likely method of reading plaintext.
* updated example filenames to stick with running gag
  (i.e. secret_plans.txt). | 
| | 
| 
| 
| 
| 
| 
| | * error corrections.
* multiple typesetting fixes only required due to certain archaic
  eccentricities of LaTeX.
* a couple of minor python PEP8 compliance corrections. | 
| | 
| 
| 
| | * Fixed an error in the encryption try/except statement. | 
| | 
| 
| 
| 
| 
| 
| | * Added a more complicated encryption example with a few variations on
  the encryption method to account for untrusted recipient keys,
  signing or not signing, including or excluding default keys and so
  on. | 
| | 
| 
| 
| 
| 
| 
| 
| | * Switched from links to some external docs to using footnotes where
  necessary.
* Ideally the howto should be as stand alone as possible.
* Also it makes it difficult to convert to another format for
  proof-reading if there are links that the conversion can't find. | 
| | 
| 
| 
| 
| | * Added instructions and code to count the number of public and secret
  keys available since it was quick and easy. | 
| | 
| 
| 
| | * Slightly tweaked one heading to make it clear it wasn't a duplicate. | 
| | 
| 
| 
| 
| 
| 
| | * Wrote the text description explaining each step in the most basic
  encryption operation.
* Will need to include additional examples for encrypting to multiple
  recipients using Context().encrypt instead of Context().op_encrypt. | 
| | 
| 
| 
| 
| | * Updated to reflect the most recent work on the HOWTO for the Python
  bindings. | 
| | 
| 
| 
| | * Added example for verifying both detached and "in-line" signatures. | 
| | 
| 
| 
| 
| 
| 
| | * Added all four signing code examples that are most likely to be
  used: armoured, clearsigned, detached armoured and detached binary.
* May remove some examples and just discuss the differences, but it
  depends on the way the text is filled out. | 
| | 
| 
| 
| 
| 
| | * Added example of decryption.
* included some quick notes for myself regarding aspects to explain
  when I flesh out the explanatory text. | 
| | 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| | * Added sample code for encrypting some text to a single key.
* Basically I'm just lifting existing production code and changing the
  key IDs from mine to "0x12345678DEADBEEF" for these first few
  examples.
* I'll fill in the text description after.
* Note: due to my regional location, I might split some tasks into
  more commits in order to be sure no work gets lost in case of
  emergency (or to put it another way: I know Telstra too well to
  trust them). | 
| | 
| 
| 
| 
| 
| 
| 
| 
| | * Added a section for those pythonistas who are too used to web
  programming.  Stressed that it's not simply not RESTful, it's not
  even REST-like.
* Letting me move on to drawing a very loose parallel between a
  session and a context.  The differences should become obvious in the
  subsequent sections. | 
| | 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| | * Some instructions to include are fairly obvious; as with encryption,
  decryption and signature verification.
* Some are a little less obvious.
* This includes the requests received to specifically include subkey
  management (adding and revoking subkeys on a primary key that's
  being retained.
* Added the UID equivalents to the list, as well as key selection
  matters (and may or may not include something for handling group
  lines since that involves wrapping a CLI binary).
* Key control documentation and examples requested by Mike Ingle of
  confidantmail.org. | 
| | 
| 
| 
| 
| | * Added the same, slightly modified GPL based license that is used in
  other parts of GnuPG. | 
| | 
| 
| 
| 
| 
| 
| 
| | * removed one bit of whitespace.
* Marked up references to gpgme.h.
* Fixed one spelling error.
* Removed py2.6 from python search order since even if it is
  supported, it shouldn't be encouraged. | 
| | 
| 
| 
| 
| 
| 
| | * Started work on the GPGME Python bindings HOWTO.
* 1,050 words to begin with at approx. 7.5KB.
* Got as far as installation.
* Includes instruction not to use PyPI for this. | 
| | 
| 
| 
| 
| | * Added suv-entry for the new HOWTO being started and, since it has
  been started, checked it off. | 
| | 
| 
| 
| | * Slightly expanded the list. | 
| | 
| 
| 
| | * Whitespace removal. | 
| |\  
| | 
| | 
| | 
| | 
| | | * Documentation and the first brush strokes towards the future.
Signed-off-by: Ben McGinnes <[email protected]> | 
| | | 
| | 
| | 
| | 
| | 
| | 
| | | * Set LaTeX headers to enable ligatures and a 12pt font by default.
* Paper size left for regional defaults.
* Using XeLaTeX for easier font control.
* Using default LaTeX font of Latin Main, but that's easy enough to change. | 
| | | 
| | 
| | 
| | | * Dropped the .txt from the end of the file ... | 
| | | 
| | 
| | 
| | 
| | | * Exported from Org Mode to UTF-8 text.
* Removed my name from just under the title. | 
| | | 
| | 
| | 
| | | * Fixed title. | 
| | | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | 
| | | * The developers of Phabricator, the web front-end on dev.gnupg.org
  have not implemented renderers for Markdown, Org-Mode or any other
  common markdown like language.
* They also refuse to do so.
* Instead they re-invented the wheel and implemented their own version
  of Markdown-like thing which is incompatible with everything else.
  It is called Remarkup.
* The developers of Phabricator and Remarkup have refused to provide
  conversion tools to move files to/from any format to/from Remarkup.
* They expect everyone to learn their new favourite pet project.
* Remarkup may or may not display Org Mode files, but if so then it is
  likely to only want to do so as plain text.
* There is an unaffiliated and unofficial project to convert Github
  Markdown to Remarkup via Pandoc.  This might be adapted for our use,
  but requires testing.
* Until then exporting from Org Mode to UTF-8 text is likely the least
  worst plan.
* Which means renaming this file to README.org first. | 
| | | 
| | 
| | 
| | 
| | 
| | | * Removed Markdown style heading underlining.
* Removed in-line file type declaration (which is not correctly parsed
  by the web interface on dev.gnupg.org). | 
| | | 
| | 
| | 
| | 
| | 
| | | * Fixed a typo in a filepath reference.
* Moved conjecture regarding the first version of Python used to a
  footnote. | 
| | |\  
| | | 
| | | 
| | | | ben/python-docs-01 | 
| | | | 
| | | 
| | | 
| | | 
| | | | * Added LaTeX header for 1 inch margins in the quite likely event that
  all PDF output ultimately uses LaTeX. | 
| | | | 
| | | 
| | | 
| | | | * Checked off the decision to stick with Org Mode. | 
| | | | 
| | | 
| | | 
| | | 
| | | | * Beginning to turn the first part of this into something kind of like
  an actual TODO list as Org Mode uses it (maybe). | 
| | | | 
| | | 
| | | 
| | | 
| | | 
| | | | * Fixed or updated the most fundamental errors.
* Also included some details on which modules are available on PyPI,
  as well as what happened to the PyME commit log. | 
| | | | 
| | | 
| | | 
| | | 
| | | 
| | | | * Split the main parts down into subsections.
* Still need to cull the incorrect stuff towards the end and add more
  recent changes. | 
| | | | 
| | | 
| | | 
| | | 
| | | 
| | | | * Reshaping the history file to fit Org Mode's structuring for docs.
* Also said history needs to be a bit more clear (it was kind of
  unfinished). | 
| | | | 
| | | 
| | | 
| | | 
| | | 
| | | 
| | | 
| | | | * Updated TODO.
* The entirety of the old TODO has been replaced with either more
  relevant tasks or goals for the examples and a more measured
  approach to the docs and why, in this project, Org Mode trumps reST,
  even though it's Python through and through. | 
| | | | 
| | | 
| | | 
| | | | * Removed reST version of file. | 
| | | | 
| | | 
| | | 
| | | | * Converted document from reST to org-mode. | 
| | | | 
| | | 
| | | 
| | | | * Removed reST version. | 
| | | | 
| | | 
| | | 
| | | | * Converted document from reST to org-mode. |