<feed xmlns='http://www.w3.org/2005/Atom'>
<title>gpgme/lang/js/BrowserTestExtension/browsertest.html, branch master</title>
<subtitle>GnuPG Made Easy.</subtitle>
<id>http://git.bktus.com/gpgfrontend/gpgme/atom?h=master</id>
<link rel='self' href='http://git.bktus.com/gpgfrontend/gpgme/atom?h=master'/>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/'/>
<updated>2018-08-16T09:25:50Z</updated>
<entry>
<title>js: consistently return uppercase fingerprint</title>
<updated>2018-08-16T09:25:50Z</updated>
<author>
<name>Maximilian Krambach</name>
<email>maximilian.krambach@intevation.de</email>
</author>
<published>2018-08-16T09:25:50Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=622db0d1de665dfd93c991cd2d517078b04b3a13'/>
<id>urn:sha1:622db0d1de665dfd93c991cd2d517078b04b3a13</id>
<content type='text'>
--

* src/Key.js: the fingerprint returned by a Key is now always upper
  case hex, even if the constructor had lower case input. This is to be
  more consistent with gpgme and to be more readable and reliable in
  comparisions.
</content>
</entry>
<entry>
<title>js: make init export immutable</title>
<updated>2018-08-01T10:51:12Z</updated>
<author>
<name>Maximilian Krambach</name>
<email>maximilian.krambach@intevation.de</email>
</author>
<published>2018-08-01T10:51:12Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=68a012deb3b501d7417778be12c88bd475a37cb5'/>
<id>urn:sha1:68a012deb3b501d7417778be12c88bd475a37cb5</id>
<content type='text'>
--

* src/index.js: The export now uses a freezed Object, which does not
  allow for simply overwriting the init method by e.g. a third-party
  library.
* BrowsertestExtension: Added some tests trying if decryption of bad
  data properly fails
</content>
</entry>
<entry>
<title>js: fix verify result reporting</title>
<updated>2018-07-09T09:57:01Z</updated>
<author>
<name>Maximilian Krambach</name>
<email>maximilian.krambach@intevation.de</email>
</author>
<published>2018-07-09T09:57:01Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=8964627f6ad7c407785a9fa5cb508c7c28be0d60'/>
<id>urn:sha1:8964627f6ad7c407785a9fa5cb508c7c28be0d60</id>
<content type='text'>
--

* src/Signature.js: searching for overall validity in the "summary"
  property
* BrowsertestExtension: Added two verify tests
</content>
</entry>
<entry>
<title>js: implement import/delete Key, some fixes</title>
<updated>2018-06-06T09:57:41Z</updated>
<author>
<name>Maximilian Krambach</name>
<email>maximilian.krambach@intevation.de</email>
</author>
<published>2018-06-06T09:57:41Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=0356a667c5a8b4fdb4404cebb57475ed3f39ade9'/>
<id>urn:sha1:0356a667c5a8b4fdb4404cebb57475ed3f39ade9</id>
<content type='text'>
--

* Keyring.js
   - implemented importKey: importing one or more armored public key
     blocks.
   - implemented deleteKey: deleting a public Key from gpg.

* Key.js renamed property Key.armor to Key.armored

* Helpers.js: toKeyIDArray does not complain anymore if there are no
  keys. Not having Keys in e.g. signing keys in encrypt is legitimate
  and common, the complaints were getting spammy

* Errors.js: gpgme_errors now always pass an optional additional
  message, for easier debugging in minified code

* Connection.js: Fix in gpgme-json responses containing objects

* eslintrc.json: Start using eslint. A cleanup to conform to it is not
  done yet

* Added further tests for the new functionality
</content>
</entry>
<entry>
<title>js: adding sign method</title>
<updated>2018-05-24T13:16:18Z</updated>
<author>
<name>Maximilian Krambach</name>
<email>maximilian.krambach@intevation.de</email>
</author>
<published>2018-05-24T13:16:18Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=a4ba80c553c2ac42f9e311344302c04ec9aa715b'/>
<id>urn:sha1:a4ba80c553c2ac42f9e311344302c04ec9aa715b</id>
<content type='text'>
--

  * src/gpgmejs.js: method, update in src/permittedOperations
  * basic testing in BrowsertestExtension
</content>
</entry>
<entry>
<title>js: more testing of nativeMessaging connection</title>
<updated>2018-05-09T17:40:57Z</updated>
<author>
<name>Maximilian Krambach</name>
<email>maximilian.krambach@intevation.de</email>
</author>
<published>2018-05-09T17:40:57Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=c92326cc257cf7c8b6c0ddc43ec81573c409bc64'/>
<id>urn:sha1:c92326cc257cf7c8b6c0ddc43ec81573c409bc64</id>
<content type='text'>
--

* There were some inconsistencies between utf-8, transfer and browsers'
  utf16, which broke characters that were split between individual
  messages. src/Connection now contains a workaround that reassembles
  javascripts' format from passed base64 strings. This needs someone
  more experienced looking.
* Added several new tests which were failing during initial debugging
  of this issue
* reorganized BrowsertestExtension to avoid cluttering.
</content>
</entry>
<entry>
<title>js: fixing errors found by testing: encrypt/decrypt</title>
<updated>2018-05-07T16:27:25Z</updated>
<author>
<name>Maximilian Krambach</name>
<email>maximilian.krambach@intevation.de</email>
</author>
<published>2018-05-07T16:27:25Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=8f3d83e5f0903323ec92f588f60dcecb0ae96de4'/>
<id>urn:sha1:8f3d83e5f0903323ec92f588f60dcecb0ae96de4</id>
<content type='text'>
--

* Key.js: Error code for wrong parameter in createKey should be
  "PARAM_WRONG"
* Helpers.js: The property openpgpjs-like Objects were checked for in
  toKeyIdArray was not defined.
* src/permittedOperations.js: updated more expectations and assumptions
  for the native API

* new Problems:
  - There seems to be a message size limit of about 21 MB for
    nativeMessaging, much lower than the documented 4GB.
  - Some bytes are lost with random data in an encrypt-decrypt
    roundtrip. The culprit is unclear.
</content>
</entry>
<entry>
<title>js: Added browser testing for unit tests</title>
<updated>2018-05-03T16:03:22Z</updated>
<author>
<name>Maximilian Krambach</name>
<email>maximilian.krambach@intevation.de</email>
</author>
<published>2018-05-03T16:03:22Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=c755287ba845c4cbbf1d50e5aafecb2e687c7ac9'/>
<id>urn:sha1:c755287ba845c4cbbf1d50e5aafecb2e687c7ac9</id>
<content type='text'>
--

* Added unittests to be run inside a Browser. To be able to access
  the non-exposed functions and classes, a testing bundle will be
  created, containing the tests (unittests.js) and the items to be
  tested.
* src/Helpelpers, src/Key, src/Keyring: fixed some errors found
  during testing.
</content>
</entry>
<entry>
<title>js: created TestExtension and smaller fixes</title>
<updated>2018-04-26T15:13:34Z</updated>
<author>
<name>Maximilian Krambach</name>
<email>maximilian.krambach@intevation.de</email>
</author>
<published>2018-04-26T15:13:34Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=1f7b19512cfa7e1b153b99d6a2b40bad82a5496e'/>
<id>urn:sha1:1f7b19512cfa7e1b153b99d6a2b40bad82a5496e</id>
<content type='text'>
--

* Extensions:

  - Moved testapplication to Demoextension
  - Created BrowserTestExtension.
    Includes mocha and chai. For running tests that cannot be run
    outside a WebExtension

  Both Extensions can be found zipped in build/extensions after
  running build_extensions.sh

* Code changes:
  - src/Config: Place for the configuration
  - small fixes raised during testing in Keyring.js, Message.js,
  - src/gpgmejs_openpgpjs.js don't offer direct GpgME object to the
    outside, as it only causes confusion
  - index.js init() now checks the config for validity

* Tests:
  - Reordered tests in test/.
  - Input values are now in a separate file which may be of use for
    bulk testing

* moved the build directory from dist to build
</content>
</entry>
</feed>
