<feed xmlns='http://www.w3.org/2005/Atom'>
<title>gpgme/lang/js, branch ben/estreams-fix</title>
<subtitle>GnuPG Made Easy.</subtitle>
<id>http://git.bktus.com/gpgfrontend/gpgme/atom?h=ben%2Festreams-fix</id>
<link rel='self' href='http://git.bktus.com/gpgfrontend/gpgme/atom?h=ben%2Festreams-fix'/>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/'/>
<updated>2018-08-29T15:45:55Z</updated>
<entry>
<title>js: return base64 after encrypt with armor=false</title>
<updated>2018-08-29T15:45:55Z</updated>
<author>
<name>Maximilian Krambach</name>
<email>maximilian.krambach@intevation.de</email>
</author>
<published>2018-08-29T15:45:55Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=61ac70cfb5cf58f92cd97abdde7152040c51201c'/>
<id>urn:sha1:61ac70cfb5cf58f92cd97abdde7152040c51201c</id>
<content type='text'>
--

* src/gpgmejs.js/encrypt: the encrypted data were converted back to a
  (incorrect) string, whereas they should be data with no encoding
  specified. Returning base64 data is the expected way.
* DemoExtension: caught yet another usage of old syntax.
</content>
</entry>
<entry>
<title>js: small documentation update</title>
<updated>2018-08-27T11:25:58Z</updated>
<author>
<name>Maximilian Krambach</name>
<email>maximilian.krambach@intevation.de</email>
</author>
<published>2018-08-27T11:24:18Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=8aa61fd3a270c167bf85cdd3f4148c48f5ae9ff7'/>
<id>urn:sha1:8aa61fd3a270c167bf85cdd3f4148c48f5ae9ff7</id>
<content type='text'>
--
</content>
</entry>
<entry>
<title>js: make non-payload data more encoding-tolerant</title>
<updated>2018-08-27T11:00:50Z</updated>
<author>
<name>Maximilian Krambach</name>
<email>maximilian.krambach@intevation.de</email>
</author>
<published>2018-08-27T11:00:50Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=28086252f15e2c124a2a00c2abc87a815d227fbe'/>
<id>urn:sha1:28086252f15e2c124a2a00c2abc87a815d227fbe</id>
<content type='text'>
--

* src/Helpers.js: As non-payload data might come in different
  encodings, a conversion has been introduced that worked in most
  cases. Data like the userid might come in different encodings,
  which we don't know of. For now, a try..catch returns the data
  as they are if the utf-8 decoding fails. Sometimes this yields the
  correct result, sometimes it may not work, but it won't stop the
  whole operation anymore.
</content>
</entry>
<entry>
<title>js: typecheck destructured parameters</title>
<updated>2018-08-27T10:38:32Z</updated>
<author>
<name>Maximilian Krambach</name>
<email>maximilian.krambach@intevation.de</email>
</author>
<published>2018-08-27T10:32:28Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=766d42c248a8c526b831685e93d54db81492f5a8'/>
<id>urn:sha1:766d42c248a8c526b831685e93d54db81492f5a8</id>
<content type='text'>
--

* destructuring just takes the input argument and treats it as object.
  In cases like in src/Keyring/generateKey, where I forgot to change
  the old syntax, the fingerprint as string was destructured into an
  object without "pattern", which caused all Keys to be retrieved.
  So, methods with a destructuring now check if the first argument is
  an object and get a default empty object if no parameter is
  submitted. This allows the further use of destructured parameters,
  while still ensuring nothing vastly incorrect is used.
* src/Kering.js, unittsets.js: fixed old syntax in method usage
</content>
</entry>
<entry>
<title>js: extend information on decoding in decrypt</title>
<updated>2018-08-27T09:50:09Z</updated>
<author>
<name>Maximilian Krambach</name>
<email>maximilian.krambach@intevation.de</email>
</author>
<published>2018-08-27T09:50:09Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=4f28fbddd3d70eb7e3ce874b1673630142110b72'/>
<id>urn:sha1:4f28fbddd3d70eb7e3ce874b1673630142110b72</id>
<content type='text'>
--

* src/Connection.js: resulting data, if not pure ascii, is base64
  encoded in the result message. A further decoding attempt into
  javascript 'string' will be attempted by default, unless specified
  at the decrypt() method. The return value 'format' now shows which
  of the possibilities has been applied. The old boolean 'base64'
  now turns into format:'base64' if the returned payload is a base64
  string after decryption.
</content>
</entry>
<entry>
<title>js: fix file_name return on decrypt</title>
<updated>2018-08-27T09:21:02Z</updated>
<author>
<name>Maximilian Krambach</name>
<email>maximilian.krambach@intevation.de</email>
</author>
<published>2018-08-27T09:21:02Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=557fec600248e6ad413af01c9a53d4993f36af0c'/>
<id>urn:sha1:557fec600248e6ad413af01c9a53d4993f36af0c</id>
<content type='text'>
--
* src/gpgmejs: Line 228 checked the wrong variable. To avoid further
  confusion, _result was renamed to returnValue in the whole file
</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: fix syntax inside Keyring methods</title>
<updated>2018-08-23T15:58:22Z</updated>
<author>
<name>Maximilian Krambach</name>
<email>maximilian.krambach@intevation.de</email>
</author>
<published>2018-08-23T15:55:35Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=f62dd4bb27c36e44acf93af1daf24eefda3029c2'/>
<id>urn:sha1:f62dd4bb27c36e44acf93af1daf24eefda3029c2</id>
<content type='text'>
--

* recent changes in parameter calling led to a forgotten internal call
  in getDefaultKey using old syntax (and failing in case a default key
  is configured)
</content>
</entry>
<entry>
<title>js: offer an always-trust parameter on encrypt</title>
<updated>2018-08-23T10:30:49Z</updated>
<author>
<name>Maximilian Krambach</name>
<email>maximilian.krambach@intevation.de</email>
</author>
<published>2018-08-23T10:30:49Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=352c53040d75e70dcda16c153d10c21e8eee0e01'/>
<id>urn:sha1:352c53040d75e70dcda16c153d10c21e8eee0e01</id>
<content type='text'>
--

* src/gpgmejs.js: Setting the default to 'always trust' assumes that
  most api users will already have made their internal checks, but may
  not have the gnupg web-of-trust model implemented, thus trusting the
  key themselves, without gnupg having full or even any information.
  Still it should stay an option to have gnupg decide.
</content>
</entry>
<entry>
<title>js: use destructured option parameters</title>
<updated>2018-08-23T10:15:59Z</updated>
<author>
<name>Maximilian Krambach</name>
<email>maximilian.krambach@intevation.de</email>
</author>
<published>2018-08-23T10:15:59Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=3fd6837fce9b339b8b09a800a969e0950e78250c'/>
<id>urn:sha1:3fd6837fce9b339b8b09a800a969e0950e78250c</id>
<content type='text'>
--
* Adds to f0409bbdafcbd4f8b0be099a6b3ce0d5352c9bcd and makes use of
  destructuring, allowing for defaults, and cleaning up the
  validation.
</content>
</entry>
</feed>
