gpgme/lang/js, branch gpgme-1.24-branch

js: improve connection check

2019-07-03T14:19:44Z

-- * 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.

js: Error handling for browser errors

2019-06-19T10:58:44Z

-- * 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

Add SPDX identifiers to most source files

2018-11-16T12:27:33Z

-- Signed-off-by: Werner Koch

spelling: fix misspellings

2018-11-08T05:34:27Z

Signed-off-by: Daniel Kahn Gillmor

doc: convert more http:// links to https://

2018-10-18T04:28:51Z

-- Signed-off-by: Daniel Kahn Gillmor

doc: use https:// for www.gnu.org

2018-10-18T04:28:51Z

-- Signed-off-by: Daniel Kahn Gillmor

js: increase default startup timeout

2018-10-17T11:13:31Z

-- * src/index.js: change the init default if none is given, so that all initialization defaults line up to 1000 miliseconds

js: renamed keygen algo option

2018-09-20T13:48:19Z

-- * src/Keyring.js: Confused default-future with future-default * reverts commit 34be6163f6c1057e2a87705925a9d0c70e4ecf17

js: add 'default-future' as createKey option

2018-09-19T15:56:55Z

-- * src/Keyring.js: default-future can be used now for key creation as algo.

json: Remove subkey-algo from createkey command.

2018-09-19T09:51:31Z

* src/gpgme-json.c (op_createkey): Remove subkey-algo param. (GPG_AGENT_ALLOWS_KEYGEN_TRHOUGH_BROWSER): Fix typo. * lang/js/src/Keyring.js: Remove subkey-algo support. * lang/js/src/permittedOperations.js: Ditto. -- We do not want to expose details of the protocol's key generation and thus the subkey-algo does not make sense. Right now we support only the default and future-default algorithms. A user can configure them anyway using new-default-key-algo in gpg.conf. Eventually we may officially support a more flexible way of creating special structured OpenPGP keys but right now that is not part of the API. Signed-off-by: Werner Koch