stillhq.com : Mikal, a geek from Canberra living in Silicon Valley (no blather posts) http://www.stillhq.com The life, times, travel and software of Michael Still (no blather posts) en Copyright (c) Michael Still 2000 - 2006 blosxom simplerss20 v20050208hh 180 http://blogs.law.harvard.edu/tech/rss GPG API Functionality /gpg Thu, 02 Nov 2000 04:00:00 GMT Here is my assignment work for Digital Communications Networks, Semester Two, 2000, which is relevant to GPG. <BR><BR><B><I> <CENTER>Demonstrated work inside the GPG 1.0.2 suite Items that are acceptable are interface design, bug detection and correction enhancements. What you deliver may consist of one or more of the following: <BR><BR> <LI>Properly Software Engineered additional code (your own, plus sections of GPG as necessary). <LI>Discussion of points of importance, illustrated by sections of your own and/or GPG code. </CENTER></b></i> <BR><BR> <hr> <BR><BR> <P> There has been much discussion recently on whether an API interface should be made available for GPG. Some of this has revolved around whether it is possible to easily implement such functionality. I have chosen to devote my DCN assignment two to this question. </P><P> The following documents constitute my submission: <UL> <LI><a href="/gpg/ass2/email.htm">A log of the GPG API related threads on the gpg-devel mailing list</a>, including comments from myself <LI>Some patches to the GPG source code to implement a proof of concept API function. I have chosen the decrypt function as it seems to be one of the more commonly used and therefore most useful functions. To make these changes I have had to modify some of the GPG source code, which is what the patches are. The patches are also available for easy download: <UL> <LI> <a href="/gpg/ass2/diff">The differences file</A> (<a href="/gpg/ass2/diff.sig">signed</a>) <LI> <a href="/gpg/ass2/api.c">api.c</a> (<a href="/gpg/ass2/api.c.sig">signed</a>) <LI> <a href="/gpg/ass2/api.h">api.h</a> (<a href="/gpg/ass2/api.h.sig">signed</a>) <LI> and <a href="/gpg/ass2/main.c">main.c</a> (<a href="/gpg/ass2/main.c.sig">signed</a>), which is added to the user interface code. This is needed so that main() is not imported into the C library that the API produces. </UL> <LI> <a href="/gpg/ass2/commentary/index.htm">A commentary on the GPG source code</a> that was developed while working on this API functionality. This is by no means complete, but it aids in comprehension of the GPG code somewhat. This has also been included the in patches above and the modified source code below to keep it all in one place. This link is merely to the commented files, to minimse the amount of digging around required to see what I have added. <LI> There is also a beautified version of the <a href="/gpg/source-1.0.3/index.htm"> original 1.0.3 code</a>, and the <a href="/gpg/source-modified-1.0.3/index.htm">modified 1.0.3 code</a>. <LI> And finally, here is some <a href="/cgi-bin/getpage?area=gpg&page=ass2/proof">documentation proving</a> that the proof of concept code works (and explaining how you can go about testing it yourself). </P> <br/><br/> <a href="http://www.stillhq.com/gpg/000002.commentform.html">Comment</a> http://www.stillhq.com/gpg/000002.html http://www.stillhq.com/gpg/000002.html Some observations on using GPG detached signatures /gpg Sun, 01 Oct 2000 05:00:00 GMT I have been having some trouble verifying the detached signatures on messages sent to me by others, so I thought that I might share <a href="/cgi-bin/getpage?area=gpg&page=detached-sig">what I have learnt from the whole thing</a>. <br/><br/> <a href="http://www.stillhq.com/gpg/000001.commentform.html">Comment</a> http://www.stillhq.com/gpg/000001.html http://www.stillhq.com/gpg/000001.html