gpgme/lang/js/src, branch javascript-bindingGnuPG Made Easy.http://git.bktus.com/gpgfrontend/gpgme/atom?h=javascript-binding2018-08-22T10:44:05Zjs: changed verify signature result infos2018-08-22T10:44:05ZMaximilian Krambachmaximilian.krambach@intevation.de2018-08-22T10:44:05Zurn:sha1:d8fd4aad8a93f7745c63814b3779469b610a8db0
--
* the resulting information of verify now are as documented,
and the same as in a decrypt callback
js: throw errors in sync functions2018-08-22T10:18:55ZMaximilian Krambachmaximilian.krambach@intevation.de2018-08-22T10:18:55Zurn:sha1:93f674d33d4dacb115398196a7218c28323fd708
--
* synchronous functions should throw errors if something goes wrong,
Promises should reject. This commit changes some error cases that
returned Error objects instead of throwing them
- src/Key.js: createKey() and sync Key.get() throw errors
- src/Error.js: Exporting the list of errors to be able to test and
compare against these strings
- src/Keyring.js: Setting a null value in pattern is not useful, and
now caused an error with the new changes.
- src/Message.js: createMessage and Message.setParameter now throw
errors
js: update decrypt/verify results2018-08-21T13:26:17ZMaximilian Krambachmaximilian.krambach@intevation.de2018-08-21T13:26:17Zurn:sha1:6d720137dd9564931bf313a7e7078e63fb00287c
--
* 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)
js: Fix library name mentioned in js Makefiles2018-08-21T11:58:51ZAndre Heineckeaheinecke@intevation.de2018-08-21T11:58:06Zurn:sha1:0036b9bc493f0482cc7c4619867649481393163e
--
js: set expiry of generatedKey to seconds from now2018-08-21T09:42:11ZMaximilian Krambachmaximilian.krambach@intevation.de2018-08-21T09:42:11Zurn:sha1:8b8c009dee8ae5493e7f888ee518468dbfcf5375
--
* src/Keyring.js: Changed key ecpiration from Date to seconds from
creation, as in gpgme. The Date parameter used before was due to a
misunderstanding in documentation and requests from potential users.
js: add option "subkey-algo" to generateKey2018-08-20T16:05:34ZMaximilian Krambachmaximilian.krambach@intevation.de2018-08-20T16:05:34Zurn:sha1:d77a1c887d6a5e892329534c94f95eaf8bb88492
--
* The option was recently added to gpgme-json; this reflects this on
javascript side
js: set expiry date on generateKey2018-08-20T15:46:29ZMaximilian Krambachmaximilian.krambach@intevation.de2018-08-20T15:46:29Zurn:sha1:91c2362550f787cc28d764c0e571e911c740f74f
--
* on the javascript side a Date is expected, gpggme-json expects
seconds from 'now'
js: add and apply eslint rules2018-08-20T13:12:01ZMaximilian Krambachmaximilian.krambach@intevation.de2018-08-20T13:12:01Zurn:sha1:dd32daad0bb21e3d5567326d0b2e548ff8510431
--
* mainly spacing, see .eslintrc.json for details
js: revert changes to class read/write restriction2018-08-20T10:12:43ZMaximilian Krambachmaximilian.krambach@intevation.de2018-08-20T10:12:43Zurn:sha1:1954d27be86b8e4eb801ca6ddcb670f8cfb149f5
--
* undoes 94ee0988d4eaac27785de6efb7c19ca9976e1e9c and
e16a87e83910ebb6bfdc4148369165f121f0997e.
I do not fully understand why my approach was bad, but I am not in
a position to argue. This revert was requested to me after a review,
and I'm doing it in the assumption that more experienced people know
better than me.
* unittests: Also changed some outdated tests that stopped working
since 754e799d35fd62d7a979452f44342934659908c7 (as GPGME_Key is not
exported, one cannot check for instanceof in the tests anymore)
js: decode arriving gpg message strings2018-08-17T17:20:35ZMaximilian Krambachmaximilian.krambach@intevation.de2018-08-17T17:20:35Zurn:sha1:74684f24c663af12c88b196fecd5f44863b893e4
--
* 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