<feed xmlns='http://www.w3.org/2005/Atom'>
<title>gpgme/lang/js/src/Helpers.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-11-08T05:34:27Z</updated>
<entry>
<title>spelling: fix misspellings</title>
<updated>2018-11-08T05:34:27Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2018-11-08T05:34:27Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=2557d0ae6ff0336b041129b7bf5c1e3a8c20a805'/>
<id>urn:sha1:2557d0ae6ff0336b041129b7bf5c1e3a8c20a805</id>
<content type='text'>
Signed-off-by: Daniel Kahn Gillmor &lt;dkg@fifthhorseman.net&gt;
</content>
</entry>
<entry>
<title>doc: convert more http:// links to https://</title>
<updated>2018-10-18T04:28:51Z</updated>
<author>
<name>Daniel Kahn Gillmor</name>
<email>dkg@fifthhorseman.net</email>
</author>
<published>2018-10-18T04:10:19Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=a81534fed8ff34b67a2726d333d9725454663c82'/>
<id>urn:sha1:a81534fed8ff34b67a2726d333d9725454663c82</id>
<content type='text'>
--

Signed-off-by: Daniel Kahn Gillmor &lt;dkg@fifthhorseman.net&gt;
</content>
</entry>
<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>js: fix error in toKeyIdArray</title>
<updated>2018-09-06T08:11:10Z</updated>
<author>
<name>Maximilian Krambach</name>
<email>maximilian.krambach@intevation.de</email>
</author>
<published>2018-09-06T08:11:10Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=6463b1cd3b52f7b8a0bbaa838ae7b29da9f458e4'/>
<id>urn:sha1:6463b1cd3b52f7b8a0bbaa838ae7b29da9f458e4</id>
<content type='text'>
--
* src/Helpers.js: GPGME_Keys were not parsed as valid, as their
  fingerprint getter is not a fingerprint 'property'.

* BrowserTestExtension: fixed a dsplay typo in counting of tests.
</content>
</entry>
<entry>
<title>js: documentation cleanup</title>
<updated>2018-09-05T16:46:28Z</updated>
<author>
<name>Maximilian Krambach</name>
<email>maximilian.krambach@intevation.de</email>
</author>
<published>2018-09-05T16:46:28Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=1c618166fcd296b4e95f3a6ea9c415d3dca5ce0a'/>
<id>urn:sha1:1c618166fcd296b4e95f3a6ea9c415d3dca5ce0a</id>
<content type='text'>
--
</content>
</entry>
<entry>
<title>js: decoding of information</title>
<updated>2018-08-30T13:37:37Z</updated>
<author>
<name>Maximilian Krambach</name>
<email>maximilian.krambach@intevation.de</email>
</author>
<published>2018-08-30T13:37:37Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=5d6039f6bf9bbbfec572055dcf5ca660041461af'/>
<id>urn:sha1:5d6039f6bf9bbbfec572055dcf5ca660041461af</id>
<content type='text'>
--

* src/Helpers.js: This additional escape should 'repair' special
  characters like spaces in filenames. In the strange world of
  encoding there is little hope that this captures all cases, or
  that it will never fail to return some value, let alone meaningful.
  In my test cases it worked.
</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: improve decryption performance</title>
<updated>2018-08-22T14:32:31Z</updated>
<author>
<name>Maximilian Krambach</name>
<email>maximilian.krambach@intevation.de</email>
</author>
<published>2018-08-22T14:32:31Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=129fa919b935d97d995bc6b457c7f6984c06e825'/>
<id>urn:sha1:129fa919b935d97d995bc6b457c7f6984c06e825</id>
<content type='text'>
--
* src/Connection.js, src/Helpers.js: performance of decoding incoming
  base64 data was improved to about 4 times the speed by introducing
  two more efficient functions (thanks to rrenkert@intevation.de for
  finding and testing them)

* src/gpgmejs.js: Decrypted data will now return as Uint8Array, if the
  caller does not wish for a decoding. Decoding binary data will return
  invalid data, and a Uint8Array may be desired. This can be indicated
  by using the (new) 'binary' option in decrypt.

* src/Errors.js A new error in case this decoding fails

* src/Message.js, src/Connection.js: expected is change from base64
  to binary, to avoid confusion later on.
</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: decode arriving gpg message strings</title>
<updated>2018-08-17T17:20:35Z</updated>
<author>
<name>Maximilian Krambach</name>
<email>maximilian.krambach@intevation.de</email>
</author>
<published>2018-08-17T17:20:35Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=74684f24c663af12c88b196fecd5f44863b893e4'/>
<id>urn:sha1:74684f24c663af12c88b196fecd5f44863b893e4</id>
<content type='text'>
--

* Arriving strings (i.e. user id names, error messages) are not
  always in javascript encoding. This is an attempt to go through
  the whole gpgme answer (with the exception of payload data) and
  to fix the encoding of these
</content>
</entry>
</feed>
