💾 Archived View for rawtext.club › ~sloum › geminilist › 002531.gmi captured on 2020-09-24 at 03:03:22. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2020-09-24)
-=-=-=-=-=-=-
Sean Conner sean at conman.org
Mon Aug 31 01:11:53 BST 2020
- - - - - - - - - - - - - - - - - - -
I just encounted this issue with my Gemini server (running GLV-1.12556)and caused it to stop receiving requests. Diagnosing the issue, I found itwas most likely caused by a request to an area requiring a clientcertificate, only the client certificate did NOT have a subject field. TheGemini protocol specification does NOT state what must be in a clientcertificate, and my server made the assumption that a client certificatewill always have one (and did not check to see if it was missing). It willnow return an error of '62' if the subject field is missing.
So that brings me to my question---what *IS* the minimum we can expect tobe in a client certificate? Is a client certificate without a subjectfield even legal? What about a missing issuer?
-spc