<feed xmlns='http://www.w3.org/2005/Atom'>
<title>gpgme/lang/js/src/permittedOperations.js, branch wk/new-wait</title>
<subtitle>GnuPG Made Easy.</subtitle>
<id>http://git.bktus.com/gpgfrontend/gpgme/atom?h=wk%2Fnew-wait</id>
<link rel='self' href='http://git.bktus.com/gpgfrontend/gpgme/atom?h=wk%2Fnew-wait'/>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/'/>
<updated>2018-10-18T04:28:51Z</updated>
<entry>
<title>doc: use https:// for www.gnu.org</title>
<updated>2018-10-18T04:28:51Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2018-10-18T03:56:27Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=2f12427e416a0a40bf680a421f9ed20340d5bb96'/>
<id>urn:sha1:2f12427e416a0a40bf680a421f9ed20340d5bb96</id>
<content type='text'>
--

Signed-off-by: Daniel Kahn Gillmor &lt;dkg@fifthhorseman.net&gt;
</content>
</entry>
<entry>
<title>json: Remove subkey-algo from createkey command.</title>
<updated>2018-09-19T09:51:31Z</updated>
<author>
<name>Werner Koch</name>
<email>wk@gnupg.org</email>
</author>
<published>2018-09-19T09:51:31Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=c569adb5e3e3082bd68cdc34a2d349b7c28d3768'/>
<id>urn:sha1:c569adb5e3e3082bd68cdc34a2d349b7c28d3768</id>
<content type='text'>
* src/gpgme-json.c (op_createkey): Remove subkey-algo param.
(GPG_AGENT_ALLOWS_KEYGEN_TRHOUGH_BROWSER): Fix typo.
* lang/js/src/Keyring.js: Remove subkey-algo support.
* lang/js/src/permittedOperations.js: Ditto.
--

We do not want to expose details of the protocol's key generation and
thus the subkey-algo does not make sense.  Right now we support only
the default and future-default algorithms.  A user can configure them
anyway using new-default-key-algo in gpg.conf.  Eventually we may
officially support a more flexible way of creating special structured
OpenPGP keys but right now that is not part of the API.

Signed-off-by: Werner Koch &lt;wk@gnupg.org&gt;
</content>
</entry>
<entry>
<title>js: separate gpgme answer by type of data</title>
<updated>2018-08-30T10:09:26Z</updated>
<author>
<name>Maximilian Krambach</name>
<email>maximilian.krambach@intevation.de</email>
</author>
<published>2018-08-30T10:04:50Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=a9863717b1b82b3077edd0db85454ba801eac9bd'/>
<id>urn:sha1:a9863717b1b82b3077edd0db85454ba801eac9bd</id>
<content type='text'>
--

* src/Connection.js; src/permittedOperations.js: To avoid further
  encoding problems, data sent by gpgme is now sorted  as either
  'payload' or 'info'. Payload data may come in any encoding, and here
  the 'expected' and 'format' options are used, 'info' data may
  contain text created by gnupg which may need re-encoding, but this
  should not be affected by 'expected' and 'format'
</content>
</entry>
<entry>
<title>js: add new options to permittedOperations</title>
<updated>2018-08-24T08:33:42Z</updated>
<author>
<name>Maximilian Krambach</name>
<email>maximilian.krambach@intevation.de</email>
</author>
<published>2018-08-24T08:33:42Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=138e1dde027338358a8da19ff8592b7369494534'/>
<id>urn:sha1:138e1dde027338358a8da19ff8592b7369494534</id>
<content type='text'>
--

* reflecting the new optional strings accepted by the backend.
  'file_name' and 'sender' can be  used via the 'additional'
  parameter in encrypt operations
</content>
</entry>
<entry>
<title>js: update decrypt/verify results</title>
<updated>2018-08-21T13:26:17Z</updated>
<author>
<name>Maximilian Krambach</name>
<email>maximilian.krambach@intevation.de</email>
</author>
<published>2018-08-21T13:26:17Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=6d720137dd9564931bf313a7e7078e63fb00287c'/>
<id>urn:sha1:6d720137dd9564931bf313a7e7078e63fb00287c</id>
<content type='text'>
--

* src/gpgmejs.js: Decrypt now parses additional optional dec_info
  information, as well as any verify information, if present

* src/permittedOperations: Now decrypt also expect the new return
  object dec_inf (containing info such as is_mime and file_name)
</content>
</entry>
<entry>
<title>js: add option "subkey-algo" to generateKey</title>
<updated>2018-08-20T16:05:34Z</updated>
<author>
<name>Maximilian Krambach</name>
<email>maximilian.krambach@intevation.de</email>
</author>
<published>2018-08-20T16:05:34Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=d77a1c887d6a5e892329534c94f95eaf8bb88492'/>
<id>urn:sha1:d77a1c887d6a5e892329534c94f95eaf8bb88492</id>
<content type='text'>
--

* The option was recently added to gpgme-json; this reflects this on
  javascript side
</content>
</entry>
<entry>
<title>js: add and apply eslint rules</title>
<updated>2018-08-20T13:12:01Z</updated>
<author>
<name>Maximilian Krambach</name>
<email>maximilian.krambach@intevation.de</email>
</author>
<published>2018-08-20T13:12:01Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=dd32daad0bb21e3d5567326d0b2e548ff8510431'/>
<id>urn:sha1:dd32daad0bb21e3d5567326d0b2e548ff8510431</id>
<content type='text'>
--

* mainly spacing, see .eslintrc.json for details
</content>
</entry>
<entry>
<title>js: correct decrypt result info (2)</title>
<updated>2018-08-17T16:25:57Z</updated>
<author>
<name>Maximilian Krambach</name>
<email>maximilian.krambach@intevation.de</email>
</author>
<published>2018-08-17T16:25:57Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=3cbafb97ec4d94c1b9a2232a74f19f432ba67384'/>
<id>urn:sha1:3cbafb97ec4d94c1b9a2232a74f19f432ba67384</id>
<content type='text'>
--

* the permittedOperation from last commit ended up in the wrong place.
  sign does not return an additional 'info' object.
</content>
</entry>
<entry>
<title>js: expect additional 'info' to arrive on decrypt, too</title>
<updated>2018-08-17T15:55:11Z</updated>
<author>
<name>Maximilian Krambach</name>
<email>maximilian.krambach@intevation.de</email>
</author>
<published>2018-08-17T15:55:11Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=fff365ffc583ef87ac585df2ac84fd8586202b8e'/>
<id>urn:sha1:fff365ffc583ef87ac585df2ac84fd8586202b8e</id>
<content type='text'>
--

* src/permittedOperations.js: if decrypt includes a verification,
  this info needs to pass, too.
</content>
</entry>
<entry>
<title>js: typo in comment</title>
<updated>2018-07-18T11:43:47Z</updated>
<author>
<name>Maximilian Krambach</name>
<email>maximilian.krambach@intevation.de</email>
</author>
<published>2018-07-18T11:43:47Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=50da3ff2fddf0d35541f798313e881fef3cff869'/>
<id>urn:sha1:50da3ff2fddf0d35541f798313e881fef3cff869</id>
<content type='text'>
--

* Documentation typo that caused jsdoc to exit with an error
</content>
</entry>
</feed>
