Where to send a "patch" to scute.

[Dirk Gottschalk]

Hi.

I use scute to sign my documents in LibreOffice and I was in need to be
able to use a cert based upon my signature key.

So I changed scute tu build 2 shared objects. The usual  scute.so,
which uses the authentication key, and scutrsig.so, which uses the
signature key, for use with LibreOffice.

Where shoult I send this a suggested feature? Is somebody interested in
this out there?

I append my patch to this mail, if somebody is interested in this
"feature". There are only a few really small modigications, but it
works fine for me.

By the way, I forked the GitHub mirror of scute and made the changes
there. The appendet file is the output of "git diff" relative to the
latest commit in the official repository.

My repository can be found at: https://github.com/Dirk1980ac/scute

Regards,
Dirk

PS: The changes were made in some kind of dirty way, because I was in a
hurry to get this working. If somebody has suggestions to make this in
a cleaner way, feel free to comment.

-- 
Dirk Gottschalk
Paulusstrasse 6-8
52064 Aachen
Tel.: +49 1573 1152350
-------------- next part --------------
A non-text attachment was scrubbed...
Name: use-sig.patch
Type: text/x-patch
Size: 30438 bytes
Desc: not available
URL: <https://lists.gnupg.org/pipermail/gnupg-users/attachments/20180511/d77eecbc/attachment-0001.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <https://lists.gnupg.org/pipermail/gnupg-users/attachments/20180511/d77eecbc/attachment-0001.sig>