<feed xmlns='http://www.w3.org/2005/Atom'>
<title>gpgme/lang/js/src/Connection.js, branch gpgme-1.14.0</title>
<subtitle>GnuPG Made Easy.</subtitle>
<id>http://git.bktus.com/gpgfrontend/gpgme/atom?h=gpgme-1.14.0</id>
<link rel='self' href='http://git.bktus.com/gpgfrontend/gpgme/atom?h=gpgme-1.14.0'/>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/'/>
<updated>2019-07-03T14:19:44Z</updated>
<entry>
<title>js: improve connection check</title>
<updated>2019-07-03T14:19:44Z</updated>
<author>
<name>Maximilian Krambach</name>
<email>maximilian.krambach@intevation.de</email>
</author>
<published>2019-07-03T14:19:44Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=ed1dffb4748e686e525883b5efde9288b8e003d3'/>
<id>urn:sha1:ed1dffb4748e686e525883b5efde9288b8e003d3</id>
<content type='text'>
--

* Connection.js: In some cases, the browser disconnect does not
  happen inmediately (e.g. wrong extension for the app). I added a
  delay of 25 ms to see if the connection was closed by the browser.
  Also, I tried to make the checkConnection more readable.
</content>
</entry>
<entry>
<title>js: Error handling for browser errors</title>
<updated>2019-06-19T10:58:44Z</updated>
<author>
<name>Maximilian Krambach</name>
<email>maximilian.krambach@intevation.de</email>
</author>
<published>2019-06-19T10:57:20Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=f5e27a12d3fd22b95e83c03a5650659bfa2299b9'/>
<id>urn:sha1:f5e27a12d3fd22b95e83c03a5650659bfa2299b9</id>
<content type='text'>
--

* Connection.js
  - Add some meaningful nativeMessaging feedback for failing
    communication due to misconfiguration or other browser-originated
    fails
  - add an "isDisconnected" property
  - "isNativeHostUnknown" tries to match browser's feedback string if
    the browser does not find gpgme-json
* init.js
  - initialization will now reject with a more meaningful error if the
    configuration is not set up or other browser-based errors
    (chrome.runtime.lastError) are present. This should speed up
    the normal initialization (not having to waiting for a timeout
    any more in case of improper setup)
* errors.js
  - CONN_NATIVEMESSAGE: New error that passes the browser's
    nativeMessaging error
  - CONN_NO_CONFIG: native messaging error indicating that the
    nativeMessaging host was not set up properly
* unittests.js:
  - added the "isDisconnected" property to the startup tests
  - added tests for proper behavior of connection checks
</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: add configuration option on startup</title>
<updated>2018-09-19T08:56:36Z</updated>
<author>
<name>Maximilian Krambach</name>
<email>maximilian.krambach@intevation.de</email>
</author>
<published>2018-09-19T08:56:36Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=7f149586062ebae8114f64078771cb25579f5003'/>
<id>urn:sha1:7f149586062ebae8114f64078771cb25579f5003</id>
<content type='text'>
--

* src/index.js: Added an optional configuration object for the startup.

* configuration: timeout - the initial check for a connection ran into
  timeouts on slower testing machines. 500ms for initial startup is
  not sufficient everywhere. The default timeout was raised to 1000ms,
  and as an option this timeout can be increased even further.

* BrowsertestExtension: Set the initial connection timeouts to 2
  seconds, to be able to test on slower machines.
</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: 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: 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: add decrypt result options</title>
<updated>2018-08-22T17:07:05Z</updated>
<author>
<name>Maximilian Krambach</name>
<email>maximilian.krambach@intevation.de</email>
</author>
<published>2018-08-22T17:07:05Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=24a00058652233775cbe51446cba337b70cefdf1'/>
<id>urn:sha1:24a00058652233775cbe51446cba337b70cefdf1</id>
<content type='text'>
--

* As a decrypt result cannot be known beforehand, the decrypt operation
  may add an 'expect' property, taking either 'uint8' or 'base64',
  which will return the decrypted data in the appropiate formats.
  the return property 'format' will give a feedback on which option
  was taken.
  A test was added to reflect these changes.
</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>
</feed>
