Support client certificates #46
Labels
No labels
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: mia/0x0#46
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
When a client presents a certificate, they should be able to manage their files. Additionally, all files uploaded using a specific certificate should be listed under a hard-to-guess URL, thus creating “folders”. Files uploaded this way should expire with the certificate if the certificate expires first, thus allowing users to set earlier expiration dates via their certificates.
Not sure what I was thinking. Who the hell wants to deal with X.509??
Tbh for a cURL-based program I would have loved to see this honestly
There are three problems to solve here:
I don’t think any of this needs X.509, especially for a mere temp file host.