<feed xmlns='http://www.w3.org/2005/Atom'>
<title>gpgme/src, branch ben/estreams-fix</title>
<subtitle>GnuPG Made Easy.</subtitle>
<id>http://git.bktus.com/gpgfrontend/gpgme/atom?h=ben%2Festreams-fix</id>
<link rel='self' href='http://git.bktus.com/gpgfrontend/gpgme/atom?h=ben%2Festreams-fix'/>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/'/>
<updated>2018-08-30T05:41:31Z</updated>
<entry>
<title>python bindings: estreams fix</title>
<updated>2018-08-30T05:41:31Z</updated>
<author>
<name>Ben McGinnes</name>
<email>ben@adversary.org</email>
</author>
<published>2018-08-30T05:41:31Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=1d00fb987b903e245d484bddfe3c0a0aba670ac1'/>
<id>urn:sha1:1d00fb987b903e245d484bddfe3c0a0aba670ac1</id>
<content type='text'>
* lang/python/src/core.py: Adjusted new_from_estream function to alias
  new_from_stream instead of fd.
* fixed the _gpgme import errors introduced in commit
  08cd34afb762975b0273575035dacf69449ef241 by changing the exported
  functions/types to match the inner module where all the work is
  done, rather than the outer one(s).

Tested-by: Ben McGinnes &lt;ben@adversary.org&gt;
Signed-off-by: Ben McGinnes &lt;ben@adversary.org&gt;
</content>
</entry>
<entry>
<title>json: Fix detached verify</title>
<updated>2018-08-29T12:32:36Z</updated>
<author>
<name>Andre Heinecke</name>
<email>aheinecke@intevation.de</email>
</author>
<published>2018-08-29T12:32:36Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=1420c3bd681648b032d756536311621a3627bedb'/>
<id>urn:sha1:1420c3bd681648b032d756536311621a3627bedb</id>
<content type='text'>
* src/gpgme-json.c (op_verify): Only create output and
use it for clearsigned and opaque signed.

--
Just passing output to gpgme_op_verify changes the behavior to
no longer do a verify of the signature.
</content>
</entry>
<entry>
<title>json: Delete primary key if subkey gen fails</title>
<updated>2018-08-28T06:35:06Z</updated>
<author>
<name>Andre Heinecke</name>
<email>aheinecke@intevation.de</email>
</author>
<published>2018-08-28T06:35:06Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=3bdf8be6d2c57319399fe14e27e52b323a17750a'/>
<id>urn:sha1:3bdf8be6d2c57319399fe14e27e52b323a17750a</id>
<content type='text'>
* src/gpgme-json.c (op_delete): Delete primary key on
subkey gen error.

--
This can happen for example if the user cancels the
pinentry to unlock the primary key when adding the
subkey.  To avoid an artifact of a pimary key without
an encryption capable subkey we delete the created
key and treat the whole operation as failed.
</content>
</entry>
<entry>
<title>json: Allow NULL request in encode and chunk</title>
<updated>2018-08-28T06:05:46Z</updated>
<author>
<name>Andre Heinecke</name>
<email>aheinecke@intevation.de</email>
</author>
<published>2018-08-28T06:05:30Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=7d3c13df263ed88c17005920e75e0486abeae5b9'/>
<id>urn:sha1:7d3c13df263ed88c17005920e75e0486abeae5b9</id>
<content type='text'>
* src/gpgme-json.c (encode_and_chunk): Don't error on NULL
request.

--
This fixes the error that is passed when parthing the json
object failed and request would be NULL.
Instead of the JSON parser error it would otherwise report
that encode and chunk failed.
</content>
</entry>
<entry>
<title>json: Do not put FILE_NAME into the verify result.</title>
<updated>2018-08-27T09:43:02Z</updated>
<author>
<name>Werner Koch</name>
<email>wk@gnupg.org</email>
</author>
<published>2018-08-27T09:42:27Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=53c5b9a265d33f2cc54f489375a929602338aee8'/>
<id>urn:sha1:53c5b9a265d33f2cc54f489375a929602338aee8</id>
<content type='text'>
* src/gpgme-json.c (verify_result_to_json): Remove "file_name".
--

Having the file name in the verify result may lead developers to
assume that the file name is covered by the signature.  This is not
the case and can easily be checked by hex-editing a signed message.
We better don't output it at all.

The same is true for the is_mime flag but that is anyway only an
advisory and I can't see damage from a faulty one.

Note that we keep file_name in gpgme's output for ABI stability and
because some tools want to display meta information even if they are
subject to tampering.  This is similar to the non-encrypted subject in
mails.

Signed-off-by: Werner Koch &lt;wk@gnupg.org&gt;
</content>
</entry>
<entry>
<title>doc: Add warning that FILE_NAME is not part of the signed data.</title>
<updated>2018-08-27T09:43:02Z</updated>
<author>
<name>Werner Koch</name>
<email>wk@gnupg.org</email>
</author>
<published>2018-08-27T09:34:30Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=702566b36c1138b2154ce054254641edcbe472fb'/>
<id>urn:sha1:702566b36c1138b2154ce054254641edcbe472fb</id>
<content type='text'>
--
</content>
</entry>
<entry>
<title>core: Export gpgme_data_new_from_estream function.</title>
<updated>2018-08-27T07:06:20Z</updated>
<author>
<name>Jasper Spaans</name>
<email>jasper@startmail.com</email>
</author>
<published>2018-08-27T07:04:16Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=08cd34afb762975b0273575035dacf69449ef241'/>
<id>urn:sha1:08cd34afb762975b0273575035dacf69449ef241</id>
<content type='text'>
Signed-off-by: Werner Koch &lt;wk@gnupg.org&gt;
</content>
</entry>
<entry>
<title>json: Add sender and file name to encrypt</title>
<updated>2018-08-23T18:50:18Z</updated>
<author>
<name>Andre Heinecke</name>
<email>aheinecke@intevation.de</email>
</author>
<published>2018-08-23T18:49:26Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=a5f8dac77d50480a208c99398df323c58ce6dc58'/>
<id>urn:sha1:a5f8dac77d50480a208c99398df323c58ce6dc58</id>
<content type='text'>
* src/gpgme-json.c (hlp_encrypt, op_encrypt): Support sender
and file_name.
</content>
</entry>
<entry>
<title>json: Add proper decrypt_result_t handling</title>
<updated>2018-08-21T12:36:42Z</updated>
<author>
<name>Andre Heinecke</name>
<email>aheinecke@intevation.de</email>
</author>
<published>2018-08-21T12:36:42Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=263dadb04aed4f973248b32c52af6ca59bcb7c1f'/>
<id>urn:sha1:263dadb04aed4f973248b32c52af6ca59bcb7c1f</id>
<content type='text'>
* src/gpgme-json.c (recipient_to_json, decrypt_result_to_json):
New.
(op_decrypt, hlp_decrypt): Update.

--
The op_decrypt as one of the first operations did not yet
match the current 1 &lt;&gt; 1 mapping of gpgme types to json
dictonaries.

info and dec_info are bad names but used for compatibility reasons.
</content>
</entry>
<entry>
<title>json: Add subkey_algo and defaults to createkey</title>
<updated>2018-08-20T14:38:36Z</updated>
<author>
<name>Andre Heinecke</name>
<email>aheinecke@intevation.de</email>
</author>
<published>2018-08-20T14:38:36Z</published>
<link rel='alternate' type='text/html' href='http://git.bktus.com/gpgfrontend/gpgme/commit/?id=8103eeba809b6e7156d861783309574b93909169'/>
<id>urn:sha1:8103eeba809b6e7156d861783309574b93909169</id>
<content type='text'>
* src/gpgme-json.c (op_createkey, hlp_createkey): Add subkey_algo
handling.
(hlp_createkey): Fix documentation of expiry.
--
Due to the funny quick-gen-key interface generating a key
with an explicit algo would result in bad defaults (only an SC key),
without a subkey.

This adds handling that should probably be in GnuPG proper to fix
the semantics of createkey by adding default subkey_algo handling.
</content>
</entry>
</feed>
