<feed xmlns='http://www.w3.org/2005/Atom'>
<title>gpgme/NEWS, branch gpgme-1.16.0</title>
<subtitle>GnuPG Made Easy.</subtitle>
<id>http://git.bktus.com/gpgfrontend/gpgme/atom?h=gpgme-1.16.0</id>
<link rel='self' href='http://git.bktus.com/gpgfrontend/gpgme/atom?h=gpgme-1.16.0'/>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/'/>
<updated>2021-06-24T17:03:35Z</updated>
<entry>
<title>Release 1.16.0</title>
<updated>2021-06-24T17:03:35Z</updated>
<author>
<name>Werner Koch</name>
<email>wk@gnupg.org</email>
</author>
<published>2021-06-24T16:53:41Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=1021c8645555502d914afffaa3707609809c9459'/>
<id>urn:sha1:1021c8645555502d914afffaa3707609809c9459</id>
<content type='text'>
</content>
</entry>
<entry>
<title>python: Allow returning signatures made by unknown keys in `decrypt`</title>
<updated>2021-06-24T16:09:55Z</updated>
<author>
<name>Jasper Spaans</name>
<email>jasper@startmail.com</email>
</author>
<published>2021-02-09T10:29:07Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=14b148b7d34038fac863ab882de29c6d35d425f1'/>
<id>urn:sha1:14b148b7d34038fac863ab882de29c6d35d425f1</id>
<content type='text'>
--
This functionality got dropped somewhere after 1.12, as part of the
cleanup of the `Context.decrypt` call signature. Reintroduce it again,
now using an explicit keyword argument `filter_signatures` (which
defaults to hiding signatures by unknown keys).

GnuPG-bug-id: 5292
</content>
</entry>
<entry>
<title>core: Allow specifying an expiration date for key signatures</title>
<updated>2021-06-22T14:35:03Z</updated>
<author>
<name>Ingo Klöcker</name>
<email>dev@ingo-kloecker.de</email>
</author>
<published>2021-06-22T14:23:26Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=34d9defc42bacfaf2bb1ce70b2c3f0fdf0a106c3'/>
<id>urn:sha1:34d9defc42bacfaf2bb1ce70b2c3f0fdf0a106c3</id>
<content type='text'>
* src/context.h (struct gpgme_context): Add 'cert_expire'.
* src/engine-gpg.c (append_args_from_cert_expire): New.
(gpg_edit): Set option according to the new flag.
* src/gpgme.c (gpgme_release): Free 'cert_expire'.
(gpgme_set_ctx_flag, gpgme_get_ctx_flag): Add "cert-expire".

* tests/gpg/Makefile.am (c_tests): Add new test.
(gpg.conf): Write "allow-weak-key-signatures" to gpg.conf.
* tests/gpg/t-edit-sign.c: New.
--

The new context flag "cert-expire" allows setting the expiration date
for key signatures created with gpgme_op_interact.

GnuPG-bug-id: 5336, 5505
</content>
</entry>
<entry>
<title>Update NEWS.</title>
<updated>2021-06-21T08:48:06Z</updated>
<author>
<name>Ingo Klöcker</name>
<email>dev@ingo-kloecker.de</email>
</author>
<published>2021-06-21T08:48:06Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=ab1d4ef580794a86da754d516db35091f6997e2c'/>
<id>urn:sha1:ab1d4ef580794a86da754d516db35091f6997e2c</id>
<content type='text'>
* NEWS: Add news for recent changes
--

GnuPG-bug-id: 5421, 5217
</content>
</entry>
<entry>
<title>cpp: Add getters for the attributes of a trust signature</title>
<updated>2021-05-05T17:25:48Z</updated>
<author>
<name>Ingo Klöcker</name>
<email>dev@ingo-kloecker.de</email>
</author>
<published>2021-05-04T16:35:47Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=e391a08c6f96cd2d93c49b888459ee3f42058118'/>
<id>urn:sha1:e391a08c6f96cd2d93c49b888459ee3f42058118</id>
<content type='text'>
* lang/cpp/src/key.h (TrustSignatureTrust): New enum.
* lang/cpp/src/key.h, lang/cpp/src/key.cpp
(UserID::Signature::isTrustSignature): New.
(UserID::Signature::trustValue): New.
(UserID::Signature::trustDepth): New.
(UserID::Signature::trustScope): New.
--

GnuPG-bug-id: 5245, 5420
</content>
</entry>
<entry>
<title>core: Extend gpgme_key_sig_t with trust signature members.</title>
<updated>2021-05-05T17:23:48Z</updated>
<author>
<name>Ingo Klöcker</name>
<email>dev@ingo-kloecker.de</email>
</author>
<published>2021-05-04T16:35:29Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=276187f6b62a73e92b1c20f589510f80ab9e88d2'/>
<id>urn:sha1:276187f6b62a73e92b1c20f589510f80ab9e88d2</id>
<content type='text'>
* src/gpgme.h.in (struct _gpgme_key_sig): Add fields 'trust_depth',
'trust_value', and 'trust_scope'.
* src/key.c (gpgme_key_unref): Free trust_scope.
* src/keylist.c (keylist_colon_handler): Set the fields.
* tests/run-keylist.c (main): Print the fields.
--

The trust signature values are part of gpg's output since the year 2003.
This now adds support to gpgme.

GnuPG-bug-id: 5245, 5419
</content>
</entry>
<entry>
<title>core: New flag GPGME_KEYSIGN_FORCE.</title>
<updated>2021-03-11T10:49:07Z</updated>
<author>
<name>Werner Koch</name>
<email>wk@gnupg.org</email>
</author>
<published>2021-03-11T10:49:07Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=0821e2b1495e8944a5a1b5ba20ad5f403dde0dd0'/>
<id>urn:sha1:0821e2b1495e8944a5a1b5ba20ad5f403dde0dd0</id>
<content type='text'>
* src/gpgme.h.in (GPGME_KEYSIGN_FORCE): New.
* src/engine-gpg.c (gpg_keysign): Implement.

* tests/run-keysign.c (show_usage): Add option --force
--

GnuPG-bug-id: 4584
</content>
</entry>
<entry>
<title>qt: Add method for getting config entries for components by entry name</title>
<updated>2021-03-05T08:24:01Z</updated>
<author>
<name>Ingo Klöcker</name>
<email>dev@ingo-kloecker.de</email>
</author>
<published>2021-03-04T16:35:57Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=fe900a41bf809b263f05d5df21b6ed7fbfb2bbbc'/>
<id>urn:sha1:fe900a41bf809b263f05d5df21b6ed7fbfb2bbbc</id>
<content type='text'>
* lang/qt/src/cryptoconfig.h, lang/qt/src/cryptoconfig.cpp
(CryptoConfig::entry): Move implementation to cpp. Add overload not
requiring a group name.
--

The group name is not needed for identifying a config entry because the
groups only provide a logical grouping of config entry for user
interfaces. To improve usability entries are sometimes moved to a
different group, but this shouldn't break existing applications trying
to access those entries. The new group-agnostic overload makes
applications robust against regrouping of config entries.

GnuPG-bug-id: 5217
</content>
</entry>
<entry>
<title>Post release updates</title>
<updated>2021-01-08T18:01:50Z</updated>
<author>
<name>Werner Koch</name>
<email>wk@gnupg.org</email>
</author>
<published>2021-01-08T18:01:50Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=13221933ed4f414142e641d1a242325e97df514a'/>
<id>urn:sha1:13221933ed4f414142e641d1a242325e97df514a</id>
<content type='text'>
--
</content>
</entry>
<entry>
<title>Release 1.15.1</title>
<updated>2021-01-08T17:14:33Z</updated>
<author>
<name>Werner Koch</name>
<email>wk@gnupg.org</email>
</author>
<published>2021-01-08T17:14:33Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=bb9880778fb16cdb6de83905e45bf6c965770013'/>
<id>urn:sha1:bb9880778fb16cdb6de83905e45bf6c965770013</id>
<content type='text'>
</content>
</entry>
</feed>
