<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hello,</p>
<p>Ok here we go...</p>
<p>Here at work we are looking at either using PGP or X.509 certs
for signing documents.</p>
<p>Personnaly I was pushing for the use of PGP, but there are are
two sticking points:</p>
<ul>
<li>PDF signatures are in a separate file</li>
<li>there does not seem to be a way to add a signature to an
existing signature file with Kleopatra</li>
</ul>
<p>Has there ever been an interest for the second point? If so,
here's how I see it:</p>
<p>If a signature file exists, Kleopatra would ask the user to add
the signature to the exisisting file OR replace it.</p>
<p>For most non-technical users, it's not an option to go to command
line and concatenate two or more signature files into one.</p>
<p>What do you think?</p>
<p>Cheers, Luc.<br>
</p>
<div class="moz-cite-prefix">On 2018-12-11 2:17 a.m., Andre Heinecke
wrote:<br>
</div>
<blockquote type="cite" cite="mid:1799843.AekaSueu3y@esus">
<pre class="moz-quote-pre" wrap="">Hi,
On Monday, December 10, 2018 4:29:03 PM CET Luc Lalonde wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">I tried to chat on the #gpg4win channel without success... I get an
error: cannot send to nick/channel.
It's been ages since I used IRC... So I hope that you'll excuse my
ignorance.
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
No problem, It was probably just that I wasn't anymore around. I should have
clarified that I'm mostly only there during German office hours.
I'm also available as <a class="moz-txt-link-rfc2396E" href="mailto:aheinecke@jabber.gnupg.org">"aheinecke@jabber.gnupg.org"</a> over federated jabber if
you prefer that.
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">What are the steps for a build setup on Linux or Windows... Is this
documented somewhere?
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
We only support a build setup on Linux for Windows and document test that only
for debian stable (which is currently debian stretch).
First fetch the source of our buildscripts:
git clone <a class="moz-txt-link-freetext" href="git://git.gnupg.org/gpg4win.git">git://git.gnupg.org/gpg4win.git</a>
The build is then documented in the README in that directory:
<a class="moz-txt-link-freetext" href="https://dev.gnupg.org/source/gpg4win/browse/master/README">https://dev.gnupg.org/source/gpg4win/browse/master/README</a>
I personally develop Kleopatra mostly for Linux and only afterwards check that
my new developments also work for windows.
There is some more documentation about developing Kleopatra here:
<a class="moz-txt-link-freetext" href="https://wiki.gnupg.org/DevelopingKleopatra">https://wiki.gnupg.org/DevelopingKleopatra</a>
For Linux development there is documentation here:
<a class="moz-txt-link-freetext" href="https://wiki.gnupg.org/BuildingFromGIT/Kleopatra">https://wiki.gnupg.org/BuildingFromGIT/Kleopatra</a>
Please take all documentation with a grain of salt it tends to become outdated
until a new person tries it out and updates it. :-)
Best Regards,
Andre
</pre>
</blockquote>
<pre class="moz-signature" cols="72">--
Luc Lalonde, analyste
-----------------------------
Département de génie informatique:
École polytechnique de MTL
(514) 340-4711 x5049
<a class="moz-txt-link-abbreviated" href="mailto:Luc.Lalonde@polymtl.ca">Luc.Lalonde@polymtl.ca</a>
-----------------------------</pre>
</body>
</html>