GpgFrontend/gpgme
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Typesetting

Browse Source 
* Fixed sentence spacing and paragraph alignment following conversion
  from reST format.
This commit is contained in:
Ben McGinnes 2015-06-27 03:27:10 +10:00
parent 434dd67170
commit bd91d40ba5
2 changed files with 59 additions and 58 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

38
lang/gpygme/docs/FAQ.org
View File

@ -18,8 +18,8 @@ used by newer developers.
*2. Won't that create bottlenecks or performance issues?*
It might, but chances are these will be negligible for most
implementations. Projects which truly needs greater optimisation should
consider utilising the GPGME C code directly.
implementations. Projects which truly needs greater optimisation
should consider utilising the GPGME C code directly.
*3. I want (or need) to use a proprietary licence with my project, can I
use this?*
@ -38,8 +38,8 @@ lawyer for issues pertaining to your specific situation).
problems with ITAR and the Wassenaar Arrangement?*
I'm not developing a cryptosystem or any encryption algorithms, I'm
developing an API. So I should not be affected one way or the other by
the provisions of the [[http://www.austlii.edu.au/au/legis/cth/num_act/dtca2012207/][Defence Trade Control Act 2012]] (DTCA),
developing an API. So I should not be affected one way or the other
by the provisions of the [[http://www.austlii.edu.au/au/legis/cth/num_act/dtca2012207/][Defence Trade Control Act 2012]] (DTCA),
particularly with the 2015 amendments which have been passed by the
Australian Parliament.
@ -63,8 +63,8 @@ naming me and this work as falling under the purview of the DTCA, then
yes; otherwise no.
The only other way it could happen is if the Defence definition of
"public domain" changes or if exemptions based on something being in the
public domain are removed.
"public domain" changes or if exemptions based on something being in
the public domain are removed.
*4. What assurances can you give that this will remain the case and
everything will be fine?*
@ -86,21 +86,21 @@ results are clear that both supply and publication are fine. The
[[http://dfat.gov.au/international-relations/security/sanctions/sanctions-regimes/Pages/sanctions-regimes.aspx][definitions of supply and publishing]], however, indicate that this work
would likely only ever be considered publishing.
The reason for this is that all the existing software on which this work
is built is what Defence classifies as being in the public domain. In
this context that is not the same as the term is used for copyright and
licensing, it means that the software and information is already freely
available to anyone. Thus it would be the same for all or almost all
free (libre) and open source software.
The reason for this is that all the existing software on which this
work is built is what Defence classifies as being in the public
domain. In this context that is not the same as the term is used for
copyright and licensing, it means that the software and information is
already freely available to anyone. Thus it would be the same for all
or almost all free (libre) and open source software.
Only Australian cryptographers developing entirely new encryption
algortithms are likely to be directly impacted by the provisions of the
DCTA. I am very much /not/ in that category. Furthermore, any algorithm
added to the specifications for GPG would need to pass through an
international selection process anyway, by which stage it would be
exempt from these types of restrictions because it would already be in
the public domain as far as Australia's Department of Defence is
concerned.
algortithms are likely to be directly impacted by the provisions of
the DCTA. I am very much /not/ in that category. Furthermore, any
algorithm added to the specifications for GPG would need to pass
through an international selection process anyway, by which stage it
would be exempt from these types of restrictions because it would
already be in the public domain as far as Australia's Department of
Defence is concerned.
The results of my completed questionnaire are available [[Australian_DCTA_export_DECO_Questionnaire_Results.pdf][here]] (PDF) and
a GPG signature of the file is [[Australian_DCTA_export_DECO_Questionnaire_Results.pdf.sig][here]]. The file is signed with my key

39
lang/gpygme/docs/README.org
View File

@ -4,21 +4,22 @@
Intended as both a replacement of the older PyME bindings for Python 2
and Python 3, though it will only be implemented in Python 3. Some
effort may be made to allow it to work as a module or series of modules
in Python 2, but there are no guarantees.
effort may be made to allow it to work as a module or series of
modules in Python 2, but there are no guarantees.
GPyGME is intended to be the official API for third party (i.e. non-C)
languages and bindings. While it should be able to be imported into any
Python 3 code as a normal Python module or library, this is not the
principal goal. The real value is in providing an API for everyone by
providing a pseudo-REST style API. It is not actually a REST API because
it is not purely web-based, though could be implemented that way (and
almost certainly will be by many).
GPyGME is intended to be the official API for third party (i.e.
non-C) languages and bindings. While it should be able to be imported
into any Python 3 code as a normal Python module or library, this is
not the principal goal. The real value is in providing an API for
everyone by providing a pseudo-REST style API. It is not actually a
REST API because it is not purely web-based, though could be
implemented that way (and almost certainly will be by many).
GPyGME will accept and respond with JSON data types to provide a method
of interaction with GPGME with which most, if not all, modern
application developers are familiar. Consequently the bindings ought to
be usable by anyone for any purpose for which GPGME could meet the need.
GPyGME will accept and respond with JSON data types to provide a
method of interaction with GPGME with which most, if not all, modern
application developers are familiar. Consequently the bindings ought
to be usable by anyone for any purpose for which GPGME could meet the
need.
** Project Name
@ -28,16 +29,16 @@ ability to unlock just as much power.
** Licensing
GPyGME utilises the LGPL 2.1+ license, the same as GPGME itself. As it
is built on GPGME this is a requirement. Documentation will be covered
by both the GPLv3+ as with the GPGME documentation and a Creative
Commons license.
GPyGME utilises the LGPL 2.1+ license, the same as GPGME itself. As
it is built on GPGME this is a requirement. Documentation will be
covered by both the GPLv3+ as with the GPGME documentation and a
Creative Commons license.
Note that interacting with the GPyGME API as a stand alone interface
(i.e. sending and receiving JSON data to it via a socket, command or
other connection type) does not require conforming with either the GPL
or LGPL licenses. Only when importing or integrating this code into your
own application does that become a requirement.
or LGPL licenses. Only when importing or integrating this code into
your own application does that become a requirement.
** Feedback