[Assword] maybe use -compress-algo NULL by default?
Daniel Kahn Gillmor
dkg at fifthhorseman.net
Thu May 8 08:44:00 EDT 2014
On 05/02/2014 03:35 AM, Jameson Graef Rollins wrote:
> On Tue, Mar 18 2014, Daniel Kahn Gillmor <dkg at fifthhorseman.net> wrote:
>> we should ensure that assword always uses --compress-algo
>> NULL when encrypting its data file.
>
> Hi, Daniel. Do you know how this might be achieved via the python gpgme
> interface? I've looked in the python gpgme help documentation and I
> don't see any way to specify the compression algorithm.
I've just asked on gnupg-devel, and it looks like this isn't possible
directly in GPGME at the moment.
Werner just committed an update to gpgme so that future versions will
have a GPGME_ENCRYPT_NO_COMPRESS flag for encrypt and encrypt_sign, but
for assword to take advantage of that, we'll have to wait for that
update to propagate into python-gpgme as well.
Presumably, it would propagate into the same place as
gpgme.ENCRYPT_ALWAYS_TRUST -- that is, as gpgme.ENCRYPT_NO_COMPRESS. i
don't know the safest/simplest way to test for the presence of a
constant in a python module -- but we could just test for its presence,
and if it exists, bitwise-or it into the flags argument.
Perhaps something like the attached patch would enable assword to do the
right thing automagically once python-gpgme is updated?
--dkg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: no-compress-where-supported.diff
Type: text/x-patch
Size: 826 bytes
Desc: not available
URL: <https://lists.mayfirst.org/mailman/private/assword/attachments/20140508/2d9e5a2d/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 1010 bytes
Desc: OpenPGP digital signature
URL: <https://lists.mayfirst.org/mailman/private/assword/attachments/20140508/2d9e5a2d/attachment.pgp>
More information about the Assword
mailing list