GNU bug report logs -
#18393
mm-view-pkcs7-verify ignores mml-smime-use
Previous Next
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 18393 in the body.
You can then email your comments to 18393 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bugs <at> gnus.org
:
bug#18393
; Package
gnus
.
(Wed, 03 Sep 2014 14:28:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Jens Lechtenboerger <lechten <at> wi.uni-muenster.de>
:
New bug report received and forwarded. Copy sent to
bugs <at> gnus.org
.
(Wed, 03 Sep 2014 14:28:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
Hi there,
I use mml-smime-use to prefer EPG over OpenSSL. However,
mm-view-pkcs7-verify ignores that variable and calls
smime-verify-region (which uses OpenSSL).
For signed e-mails with
Content-Type: application/pkcs7-mime; name="smime.p7m";
smime-type=signed-data
this results in the error message: "No CA configured"
(And the e-mail is displayed in base64 encoded form; the text is not
shown.)
In contrast, mm-view-pkcs7-decrypt does observe mml-smime-use to
choose between EPG and OpenSSL.
Best wishes
Jens
Ma Gnus v0.10
GNU Emacs 24.3.93.1 (i686-pc-linux-gnu, GTK+ Version 2.20.1)
of 2014-08-18 on pcwi7557
Information forwarded
to
bugs <at> gnus.org
:
bug#18393
; Package
gnus
.
(Wed, 25 Jan 2017 20:09:01 GMT)
Full text and
rfc822 format available.
Message #8 received at 18393 <at> debbugs.gnu.org (full text, mbox):
Jens Lechtenboerger <lechten <at> wi.uni-muenster.de> writes:
> I use mml-smime-use to prefer EPG over OpenSSL. However,
> mm-view-pkcs7-verify ignores that variable and calls
> smime-verify-region (which uses OpenSSL).
>
> For signed e-mails with
> Content-Type: application/pkcs7-mime; name="smime.p7m";
> smime-type=signed-data
> this results in the error message: "No CA configured"
> (And the e-mail is displayed in base64 encoded form; the text is not
> shown.)
>
> In contrast, mm-view-pkcs7-decrypt does observe mml-smime-use to
> choose between EPG and OpenSSL.
I'm very unfamiliar with the smime code. Could you take a stab at doing
this yourself? :-)
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
Information forwarded
to
bugs <at> gnus.org
:
bug#18393
; Package
gnus
.
(Thu, 26 Jan 2017 07:41:01 GMT)
Full text and
rfc822 format available.
Message #11 received at 18393 <at> debbugs.gnu.org (full text, mbox):
On 2017-01-25, Lars Ingebrigtsen wrote:
> I'm very unfamiliar with the smime code. Could you take a stab at doing
> this yourself? :-)
I had a look before reporting this but didn’t see a simple fix.
Currently, I don’t have enough time to work on this, but I’ll put it
on my long-term agenda.
Best wishes
Jens
bug reassigned from package 'gnus' to 'emacs,gnus'.
Request was from
Lars Ingebrigtsen <larsi <at> gnus.org>
to
control <at> debbugs.gnu.org
.
(Thu, 26 Jan 2017 14:58:02 GMT)
Full text and
rfc822 format available.
bug No longer marked as found in versions 5.13001.
Request was from
Lars Ingebrigtsen <larsi <at> gnus.org>
to
control <at> debbugs.gnu.org
.
(Thu, 26 Jan 2017 14:58:02 GMT)
Full text and
rfc822 format available.
Information forwarded
to
bug-gnu-emacs <at> gnu.org, bugs <at> gnus.org
:
bug#18393
; Package
emacs,gnus
.
(Mon, 23 Sep 2019 19:03:02 GMT)
Full text and
rfc822 format available.
Message #18 received at 18393 <at> debbugs.gnu.org (full text, mbox):
Jens Lechtenboerger <lechten <at> wi.uni-muenster.de> writes:
> I use mml-smime-use to prefer EPG over OpenSSL. However,
> mm-view-pkcs7-verify ignores that variable and calls
> smime-verify-region (which uses OpenSSL).
>
> For signed e-mails with
> Content-Type: application/pkcs7-mime; name="smime.p7m";
> smime-type=signed-data
> this results in the error message: "No CA configured"
> (And the e-mail is displayed in base64 encoded form; the text is not
> shown.)
Could you send such a message to enable us to debug this?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
Information forwarded
to
bug-gnu-emacs <at> gnu.org, bugs <at> gnus.org
:
bug#18393
; Package
emacs,gnus
.
(Tue, 24 Sep 2019 12:37:02 GMT)
Full text and
rfc822 format available.
Message #21 received at 18393 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
On 2019-09-23, Lars Ingebrigtsen wrote:
> Jens Lechtenboerger <lechten <at> wi.uni-muenster.de> writes:
>
>> I use mml-smime-use to prefer EPG over OpenSSL. However,
>> mm-view-pkcs7-verify ignores that variable and calls
>> smime-verify-region (which uses OpenSSL).
>>
>> For signed e-mails with
>> Content-Type: application/pkcs7-mime; name="smime.p7m";
>> smime-type=signed-data
>> this results in the error message: "No CA configured"
>> (And the e-mail is displayed in base64 encoded form; the text is not
>> shown.)
>
> Could you send such a message to enable us to debug this?
Attached you find the message from section 4.9 of RFC4134, with the
CA certificate. Verify with:
openssl smime -verify -CAfile carldssself.pem -in rfc4134-4.9.mail -signer signer.pem -out signedtext.txt
Best wishes
Jens
[rfc4134-4.9.mail (application/octet-stream, attachment)]
[carldssself.pem (application/octet-stream, attachment)]
Information forwarded
to
bug-gnu-emacs <at> gnu.org, bugs <at> gnus.org
:
bug#18393
; Package
emacs,gnus
.
(Wed, 25 Sep 2019 13:40:02 GMT)
Full text and
rfc822 format available.
Message #24 received at 18393 <at> debbugs.gnu.org (full text, mbox):
Jens Lechtenboerger <lechten <at> wi.uni-muenster.de> writes:
>>> I use mml-smime-use to prefer EPG over OpenSSL. However,
>>> mm-view-pkcs7-verify ignores that variable and calls
>>> smime-verify-region (which uses OpenSSL).
>>>
>>> For signed e-mails with
>>> Content-Type: application/pkcs7-mime; name="smime.p7m";
>>> smime-type=signed-data
>>> this results in the error message: "No CA configured"
>>> (And the e-mail is displayed in base64 encoded form; the text is not
>>> shown.)
>>
>> Could you send such a message to enable us to debug this?
>
> Attached you find the message from section 4.9 of RFC4134, with the
> CA certificate. Verify with:
>
> openssl smime -verify -CAfile carldssself.pem -in rfc4134-4.9.mail
> -signer signer.pem -out signedtext.txt
Yup, I get the same.
If I say:
(setq smime-CA-file "/tmp/carldssself.pem")
I get a blank article buffer.
I'm trying to follow the logic of the code here. One bug is what you
report, that mml-smime-use isn't heeded, and I'll fix that (it seems
pretty easy, I can just cargo-cult mm-view-pkcs7-decrypt, which starts:
(defun mm-view-pkcs7-decrypt (handle &optional from)
(insert-buffer-substring (mm-handle-buffer handle))
(goto-char (point-min))
(if (eq mml-smime-use 'epg)
...
But in this instance we don't get to that function. Instead we get to:
(defun mm-view-pkcs7 (handle &optional from)
(cl-case (mm-view-pkcs7-get-type handle)
(enveloped (mm-view-pkcs7-decrypt handle from))
(signed (mm-view-pkcs7-verify handle))
(otherwise (error "Unknown or unimplemented PKCS#7 type"))))
(defun mm-view-pkcs7-verify (handle)
...)
because this is "signed", not "enveloped". I'm not very familiar with
this stuff... but the mm-view-pkcs7-verify function just verifies the
data and doesn't return anything, which explains why I'm getting an
empty article buffer. But why is this ever useful? It seems odd,
doesn't it?
Is the -verify function also supposed to return the decoded text?
(Which is "This is some sample content.".)
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
Information forwarded
to
bug-gnu-emacs <at> gnu.org, bugs <at> gnus.org
:
bug#18393
; Package
emacs,gnus
.
(Thu, 26 Sep 2019 09:05:02 GMT)
Full text and
rfc822 format available.
Message #27 received at 18393 <at> debbugs.gnu.org (full text, mbox):
On 2019-09-25, Lars Ingebrigtsen wrote:
> (setq smime-CA-file "/tmp/carldssself.pem")
>
> I get a blank article buffer.
Same here.
> [...]
> (defun mm-view-pkcs7-verify (handle)
> ...)
>
> because this is "signed", not "enveloped". I'm not very familiar with
> this stuff... but the mm-view-pkcs7-verify function just verifies the
> data and doesn't return anything, which explains why I'm getting an
> empty article buffer. But why is this ever useful? It seems odd,
> doesn't it?
>
> Is the -verify function also supposed to return the decoded text?
> (Which is "This is some sample content.".)
Function mm-view-pkcs7-verify calls (mm-insert-part handle), which
somehow deals with the text for subsequent display. The search for
"Content-Type" suggests that this is only meant for multi-part
e-mails, for which it really works. In this case, however, it
inserts the text among binary data, which seems to fail subsequently.
Best wishes
Jens
Information forwarded
to
bug-gnu-emacs <at> gnu.org, bugs <at> gnus.org
:
bug#18393
; Package
emacs,gnus
.
(Thu, 26 Sep 2019 14:27:01 GMT)
Full text and
rfc822 format available.
Message #30 received at 18393 <at> debbugs.gnu.org (full text, mbox):
Jens Lechtenboerger <lechten <at> wi.uni-muenster.de> writes:
> On 2019-09-25, Lars Ingebrigtsen wrote:
>
>> (setq smime-CA-file "/tmp/carldssself.pem")
>>
>> I get a blank article buffer.
>
> Same here.
I've now fixed this on the trunk.
>> [...]
>> (defun mm-view-pkcs7-verify (handle)
>> ...)
>>
>> because this is "signed", not "enveloped". I'm not very familiar with
>> this stuff... but the mm-view-pkcs7-verify function just verifies the
>> data and doesn't return anything, which explains why I'm getting an
>> empty article buffer. But why is this ever useful? It seems odd,
>> doesn't it?
>>
>> Is the -verify function also supposed to return the decoded text?
>> (Which is "This is some sample content.".)
>
> Function mm-view-pkcs7-verify calls (mm-insert-part handle), which
> somehow deals with the text for subsequent display.
But that's just the raw data that's supposed to be verified. "openssl
smime" outputs the actual verified data, so I've adjusted the callers to
return that.
In addition, whatever that function inserted in that buffer was just
discarded.
*phew*
OK, so now it works for the case you weren't using, so now I can start
working on the actual bug report. :-)
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
Information forwarded
to
bug-gnu-emacs <at> gnu.org, bugs <at> gnus.org
:
bug#18393
; Package
emacs,gnus
.
(Thu, 26 Sep 2019 14:33:02 GMT)
Full text and
rfc822 format available.
Message #33 received at 18393 <at> debbugs.gnu.org (full text, mbox):
Lars Ingebrigtsen <larsi <at> gnus.org> writes:
> OK, so now it works for the case you weren't using, so now I can start
> working on the actual bug report. :-)
And that part was trivial. :-) Can you check whether this works for
you now with the test email?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
Information forwarded
to
bug-gnu-emacs <at> gnu.org, bugs <at> gnus.org
:
bug#18393
; Package
emacs,gnus
.
(Fri, 27 Sep 2019 06:10:02 GMT)
Full text and
rfc822 format available.
Message #36 received at 18393 <at> debbugs.gnu.org (full text, mbox):
On 2019-09-26, Lars Ingebrigtsen wrote:
> Lars Ingebrigtsen <larsi <at> gnus.org> writes:
>
>> OK, so now it works for the case you weren't using, so now I can start
>> working on the actual bug report. :-)
>
> And that part was trivial. :-) Can you check whether this works for
> you now with the test email?
Yes, many thanks for your efforts! This works for the test mail and
for multipart mails.
Best wishes
Jens
Information forwarded
to
bug-gnu-emacs <at> gnu.org, bugs <at> gnus.org
:
bug#18393
; Package
emacs,gnus
.
(Fri, 27 Sep 2019 06:34:02 GMT)
Full text and
rfc822 format available.
Message #39 received at 18393 <at> debbugs.gnu.org (full text, mbox):
On 2019-09-27, Jens Lechtenboerger wrote:
> On 2019-09-26, Lars Ingebrigtsen wrote:
>
>> Lars Ingebrigtsen <larsi <at> gnus.org> writes:
>>
>>> OK, so now it works for the case you weren't using, so now I can start
>>> working on the actual bug report. :-)
>>
>> And that part was trivial. :-) Can you check whether this works for
>> you now with the test email?
>
> Yes, many thanks for your efforts! This works for the test mail and
> for multipart mails.
One addition: If verification fails, just an empty buffer is shown,
without any indication what went wrong. An error message would be
nice, also an option to see the text anyways.
Best wishes
Jens
Information forwarded
to
bug-gnu-emacs <at> gnu.org, bugs <at> gnus.org
:
bug#18393
; Package
emacs,gnus
.
(Fri, 27 Sep 2019 13:56:02 GMT)
Full text and
rfc822 format available.
Message #42 received at 18393 <at> debbugs.gnu.org (full text, mbox):
Jens Lechtenboerger <lechten <at> wi.uni-muenster.de> writes:
>> Yes, many thanks for your efforts! This works for the test mail and
>> for multipart mails.
Thanks for checking.
> One addition: If verification fails, just an empty buffer is shown,
> without any indication what went wrong. An error message would be
> nice, also an option to see the text anyways.
Yes, that's true. Could you send me a couple of messages where
verification should fail for me so that I can test? Perhaps we should
start building a test suite...
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
Information forwarded
to
bug-gnu-emacs <at> gnu.org, bugs <at> gnus.org
:
bug#18393
; Package
emacs,gnus
.
(Fri, 27 Sep 2019 15:05:02 GMT)
Full text and
rfc822 format available.
Message #45 received at 18393 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
On 2019-09-27, Lars Ingebrigtsen wrote:
> Jens Lechtenboerger <lechten <at> wi.uni-muenster.de> writes:
>
>> One addition: If verification fails, just an empty buffer is shown,
>> without any indication what went wrong. An error message would be
>> nice, also an option to see the text anyways.
>
> Yes, that's true. Could you send me a couple of messages where
> verification should fail for me so that I can test? Perhaps we should
> start building a test suite...
Actually, I was too fast. I had a problem with my keyring, which
resulted in verification errors, which in turn resulted in empty
buffers. I’m not sure how to test this.
Attached you find an e-mail where I just changed some bytes in the
text, keeping the old signature. Verification fails, but the
messages is displayed without any indication of the verification
failure.
Best wishes
Jens
[rfc4134-invalid-sig.mail (application/octet-stream, attachment)]
Information forwarded
to
bug-gnu-emacs <at> gnu.org, bugs <at> gnus.org
:
bug#18393
; Package
emacs,gnus
.
(Fri, 27 Sep 2019 15:20:01 GMT)
Full text and
rfc822 format available.
Message #48 received at 18393 <at> debbugs.gnu.org (full text, mbox):
Jens Lechtenboerger <lechten <at> wi.uni-muenster.de> writes:
> Actually, I was too fast. I had a problem with my keyring, which
> resulted in verification errors, which in turn resulted in empty
> buffers. I’m not sure how to test this.
>
> Attached you find an e-mail where I just changed some bytes in the
> text, keeping the old signature. Verification fails, but the
> messages is displayed without any indication of the verification
> failure.
Thanks.
The more I dig into the entire framework for reporting errors in
encrypted/signed messages we have, the more inadequate it seems.
If you have a multipart/signed message, and you have
(setq gnus-buttonized-mime-types '("multipart/\\(signed\\|encrypted\\)"))
then the button (!) will tell you whether the verification of the
signature was successful or not. And the decryption/verification
functions alter the mm-security-handle bound by
mm-possibly-verify-or-decrypt to enable this... er... reporting.
If you don't have the button (and by default that variable is nil),
you'll get no feedback whatsoever.
In the case of the message you sent me, it's not a multipart message, so
no buttons are inserted anyway, so you never ever get any feedback.
This doesn't seem the right way to do security-related functionality.
I think the principle here should be, when displaying signed/encrypted
messages, that Gnus should, by default:
1) say that what you're viewing is signed/encrypted and
2) explicitly say whether the signature was verified or not, and if
there were any error messages, it should report them.
But 1) should not be done in an obnoxious way.
But I should be doing more testing before I start hacking away, and have
a bigger test corpus.
Does anybody know of one that's handy with different signing/encryption
methods?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
Information forwarded
to
bug-gnu-emacs <at> gnu.org, bugs <at> gnus.org
:
bug#18393
; Package
emacs,gnus
.
(Fri, 27 Sep 2019 18:17:01 GMT)
Full text and
rfc822 format available.
Message #51 received at 18393 <at> debbugs.gnu.org (full text, mbox):
On 2019-09-27, at 17:19, Lars Ingebrigtsen wrote:
> But I should be doing more testing before I start hacking away, and have
> a bigger test corpus.
>
> Does anybody know of one that's handy with different signing/encryption
> methods?
At the end of 2015, when gnus was still maintained in its own
repository (https://git.gnus.org/gnus.git) and had a "lisp/tests"
subdirectory, I refactored gnus code for OpenPGP and S/MIME and
added tests/gnustest-mml-sec.el with key material in
tests/mml-gpghome (with expired subkeys, disabled keys, revoked
uids). I don’t know whether that is still publicly accessible
anywhere but I’ve got a local copy with my merged branch if you are
interested.
I did not create S/MIME messages of the form of this bug report.
Best wishes
Jens
Information forwarded
to
bug-gnu-emacs <at> gnu.org, bugs <at> gnus.org
:
bug#18393
; Package
emacs,gnus
.
(Sat, 28 Sep 2019 17:56:02 GMT)
Full text and
rfc822 format available.
Message #54 received at 18393 <at> debbugs.gnu.org (full text, mbox):
Jens Lechtenboerger <lechten <at> wi.uni-muenster.de> writes:
> At the end of 2015, when gnus was still maintained in its own
> repository (https://git.gnus.org/gnus.git) and had a "lisp/tests"
> subdirectory, I refactored gnus code for OpenPGP and S/MIME and
> added tests/gnustest-mml-sec.el with key material in
> tests/mml-gpghome (with expired subkeys, disabled keys, revoked
> uids). I don’t know whether that is still publicly accessible
> anywhere but I’ve got a local copy with my merged branch if you are
> interested.
I do not seem to have a "mml-gpghome" directory on any of my machines.
Could you tar up and mail me the test data?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
Information forwarded
to
bug-gnu-emacs <at> gnu.org, bugs <at> gnus.org
:
bug#18393
; Package
emacs,gnus
.
(Sun, 29 Sep 2019 08:58:02 GMT)
Full text and
rfc822 format available.
Message #57 received at 18393 <at> debbugs.gnu.org (full text, mbox):
On 2019-09-28, at 19:55, Lars Ingebrigtsen wrote:
> Jens Lechtenboerger <lechten <at> wi.uni-muenster.de> writes:
>
>> At the end of 2015, when gnus was still maintained in its own
>> repository (https://git.gnus.org/gnus.git) and had a "lisp/tests"
>> subdirectory, I refactored gnus code for OpenPGP and S/MIME and
>> added tests/gnustest-mml-sec.el with key material in
>> tests/mml-gpghome (with expired subkeys, disabled keys, revoked
>> uids). I don’t know whether that is still publicly accessible
>> anywhere but I’ve got a local copy with my merged branch if you are
>> interested.
>
> I do not seem to have a "mml-gpghome" directory on any of my machines.
> Could you tar up and mail me the test data?
I uploaded a tar archive for the test directory here:
https://uni-muenster.sciebo.de/s/OIfu8cUSgqRfhVs
The file gnustest-mml-sec.README contains initial pointers.
Best wishes
Jens
Information forwarded
to
bug-gnu-emacs <at> gnu.org, bugs <at> gnus.org
:
bug#18393
; Package
emacs,gnus
.
(Sun, 29 Sep 2019 11:18:01 GMT)
Full text and
rfc822 format available.
Message #60 received at 18393 <at> debbugs.gnu.org (full text, mbox):
Jens Lechtenboerger <lechten <at> wi.uni-muenster.de> writes:
> I uploaded a tar archive for the test directory here:
> https://uni-muenster.sciebo.de/s/OIfu8cUSgqRfhVs
>
> The file gnustest-mml-sec.README contains initial pointers.
Thanks; I'll have a look and possibly put some of the tests into the
Emacs test directory.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
Information forwarded
to
bug-gnu-emacs <at> gnu.org, bugs <at> gnus.org
:
bug#18393
; Package
emacs,gnus
.
(Mon, 30 Sep 2019 06:44:01 GMT)
Full text and
rfc822 format available.
Message #63 received at 18393 <at> debbugs.gnu.org (full text, mbox):
I've now started the job of reporting reporting back
decryption/verification errors. The first bit is just a refactoring of
the code with some helper functions to make it really explicit when
things fail or not. There should be no functional change so far...
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
Information forwarded
to
bug-gnu-emacs <at> gnu.org, bugs <at> gnus.org
:
bug#18393
; Package
emacs,gnus
.
(Tue, 04 Aug 2020 17:31:01 GMT)
Full text and
rfc822 format available.
Message #66 received at 18393 <at> debbugs.gnu.org (full text, mbox):
Lars Ingebrigtsen <larsi <at> gnus.org> writes:
> Jens Lechtenboerger <lechten <at> wi.uni-muenster.de> writes:
>
>> I uploaded a tar archive for the test directory here:
>> https://uni-muenster.sciebo.de/s/OIfu8cUSgqRfhVs
>>
>> The file gnustest-mml-sec.README contains initial pointers.
>
> Thanks; I'll have a look and possibly put some of the tests into the
> Emacs test directory.
I've now added these tests to Emacs 28.
I think that covers all the specific bugs reported in this bug report,
so I'm closing it. If there are more bugs in this area (and I'm sure
there are), please open new reports.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
Added tag(s) fixed.
Request was from
Lars Ingebrigtsen <larsi <at> gnus.org>
to
control <at> debbugs.gnu.org
.
(Tue, 04 Aug 2020 17:31:02 GMT)
Full text and
rfc822 format available.
bug marked as fixed in version 28.1, send any further explanations to
18393 <at> debbugs.gnu.org and Jens Lechtenboerger <lechten <at> wi.uni-muenster.de>
Request was from
Lars Ingebrigtsen <larsi <at> gnus.org>
to
control <at> debbugs.gnu.org
.
(Tue, 04 Aug 2020 17:31:02 GMT)
Full text and
rfc822 format available.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Wed, 02 Sep 2020 11:24:13 GMT)
Full text and
rfc822 format available.
This bug report was last modified 5 years and 5 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.