gpgme/lang/js/BrowserTestExtension/tests/inputvalues.js, branch dkg/fix-T4271

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

2018-10-18T04:28:51Z

-- Signed-off-by: Daniel Kahn Gillmor

js: tests for file name encoding

2018-08-30T14:16:13Z

-- * BrowsertestExtension/tests/decryptTest.js: There were cases in which file names returned in a wrong encoding from decryption. The test cases here are a 'Hello World' in a text file with different names, then being encrypted with cli gnupg.

js: add tests

2018-08-30T13:00:19Z

-- * BrowserTestExtension/tests: - decryptTest.js: Check Decryption and return values of binary data - encryptTest.js: Return data type of armored/non-armored encryption - added a small encoded input png for testing * DemoExtension/maindemo.js: Fixed unexpected usage of the Demo encrypt (non-armored)

js: update decrypt/verify results

2018-08-21T13:26:17Z

-- * 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: add and apply eslint rules

2018-08-20T13:12:01Z

-- * mainly spacing, see .eslintrc.json for details

js: decode arriving gpg message strings

2018-08-17T17:20:35Z

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

js: consistently return uppercase fingerprint

2018-08-16T09:25:50Z

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

js: make init export immutable

2018-08-01T10:51:12Z

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

js: change the write access for js class methods

2018-07-27T18:36:21Z

-- * src/ [Connection, Error, Key, Keyring, MEssage, Signature, gpgmejs]: Functions and values that are not meant to be overwritten are now moved into their constructors, thus eliminating the possibility of overwrites after initialization. * Key: The mode of use (synchronous cached, or async promises) ivs now determined at initialization of that Key. The property Key.isAsync reflects this state. * unittests: fixed old Key syntax for testing. * Message.js isComplete is now a method and not a getter anymore. * Added some startup tests.

js: clean up test extension

2018-07-27T09:20:33Z

-- Tests will now run with one instance of gpgmejs each block, which reduces overhead. Readability is (hopefully) improved), some negative tests are added. There is still a performance problem in base64 encoding/decoding, which causes some tests to fail due to time out.