Support client certificates #46

Closed
opened 2021-05-23 22:12:29 +02:00 by mia · 3 comments
Owner

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.

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.
Author
Owner

Not sure what I was thinking. Who the hell wants to deal with X.509??

Not sure what I was thinking. Who the hell wants to deal with X.509??
mia closed this issue 2022-08-01 18:05:04 +02:00
mia added the
wontfix
label 2022-08-01 18:05:09 +02:00

Tbh for a cURL-based program I would have loved to see this honestly

Tbh for a cURL-based program I would have loved to see this honestly
Author
Owner

There are three problems to solve here:

  • Allow custom expiry (see #33)
  • Hard-to-guess paths (#47)
  • Self-service file management

I don’t think any of this needs X.509, especially for a mere temp file host.

There are three problems to solve here: * Allow custom expiry (see #33) * Hard-to-guess paths (#47) * Self-service file management I don’t think any of this needs X.509, especially for a mere temp file host.
Sign in to join this conversation.
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: mia/0x0#46
No description provided.