As a user I would like to be able to send a client certificate when requested by gemini servers #42
Labels
No Label
blocked
bug
build
documentation
duplicate
enhancement
finger
gemini
gopher
help wanted
http
in progress
invalid
local
needs-info
non-code
non-functional
non-urgent
question
release
rendering
suggestion
telnet
terminal
urgent
wontfix
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: sloum/bombadillo#42
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Status code 6 is a request for a client certificate. I am inclined to set it up as follows:
Does this sound like a reasonable way to go? Or is generating certificates for a little used/new protocol too heavy a thing to be doing as part of the initialization? Should we just give users the option to point to a file in their config and call it a day?
This is closed by #44
Adds the ability for a client to add paths to their config for a key and cert. This will get sent automatically if the client requests a certificate. This behavior is not strictly in-line with the current spec and will need review as the spec matures and things are settled upon.