<feed xmlns='http://www.w3.org/2005/Atom'>
<title>gpgme/lang/js/BrowserTestExtension/testkey2.pub, branch gpgme-2.1.2</title>
<subtitle>GnuPG Made Easy.</subtitle>
<id>http://git.bktus.com/gpgfrontend/gpgme/atom?h=gpgme-2.1.2</id>
<link rel='self' href='http://git.bktus.com/gpgfrontend/gpgme/atom?h=gpgme-2.1.2'/>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/'/>
<updated>2018-05-28T15:26:56Z</updated>
<entry>
<title>js: Keyring listing keys</title>
<updated>2018-05-28T15:26:56Z</updated>
<author>
<name>Maximilian Krambach</name>
<email>maximilian.krambach@intevation.de</email>
</author>
<published>2018-05-28T15:26:56Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=53ce2b94bc35243710dec9b7972c7aaaa79dbc75'/>
<id>urn:sha1:53ce2b94bc35243710dec9b7972c7aaaa79dbc75</id>
<content type='text'>
--

* implementing Keyring methods:

  - Keyring.getKeys: has an additional option that retrieves the armor
    and secret state once at the beginning. This is power hungry, but
    allows for Keys to be used directly (without querying gpgme-json
    each call)
  * permittedOperations.js: reflect recent changes in the native
    counterpart, adding more options
  * Key: adding two methods for retrieving the armored Key block and
    for finding out if the Key includes a secret subkey.
</content>
</entry>
</feed>
