Hopefully my problem is obvious, but I seem to have run into a
wall configuring cosign for my site.
I don't know if this -12281 error is a Mozilla error code,
something apache understands, or something specific to cosign.
IE doesn't bother giving me an error code at all (in fact, I get the
page that looks like DNS problems from IE). Mozilla (well, firefox)
reports that "weblogin.reed.edu has sent an incorrect or unexpect
message" and then presents me with this error code.
As best I can tell, I've followed the cosign installation
I tried running cosignd in debug mode:
Something similar is shown on stdout whenever I try to access a cosign
protected page (and I get this -12281 error as well).
My apache 2 access_log looks like the following:
220.127.116.11 - - [17/Mar/2004:14:30:20 -0800] "GET /test/test.html
HTTP/1.1" 302 403
18.104.22.168 - - [17/Mar/2004:14:30:20 -0800] "GET
HTTP/1.1" 302 227
22.214.171.124 - - [17/Mar/2004:14:30:21 -0800] "\x80g\x01\x03" 200 4779
The error log doesn't seem to say a whole lot -- although once in a
[Wed Mar 17 14:27:37 2004] [error] [client 126.96.36.199] net_check: 3:
534 CHECK: Who me? Dunno.
These errors don't typically correspond to the major error I receive
whenever I try to look at a cosign protected page.
strace'ing the cosign daemon doesn't reveal any smoking guns.
I use the following in my httpd.conf:
CosignCrypto /var/cosign/certs/key.pem /var/cosign/certs/cert.pem
And my (self-signed) ssl certs check out okay.
Is there anything else I can/should take a look at to diagnose