Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add HTTPS as the default way to run OpenRegistry #83

Open
jay-dee7 opened this issue Dec 6, 2021 · 0 comments
Open

Add HTTPS as the default way to run OpenRegistry #83

jay-dee7 opened this issue Dec 6, 2021 · 0 comments
Assignees
Labels
Chore For work that isn't directly related to the product needs-triage This label refers to a non-final decision on implementation, when an important feature/bug is added P3 P3 labels are used for issues which are not very pressing and we'd love community to work on

Comments

@jay-dee7
Copy link
Member

jay-dee7 commented Dec 6, 2021

HTTPS wil enable us to use HTTP/2 which brings in tons of improvements in performance. We can use openssl to generate self-signed ssl keys and run locally with these certificates and of course production instances can have ssl certs from lets encrypt.

Links for References:

guacamole added a commit that referenced this issue Mar 1, 2022
@jay-dee7 jay-dee7 added P3 P3 labels are used for issues which are not very pressing and we'd love community to work on needs-triage This label refers to a non-final decision on implementation, when an important feature/bug is added Chore For work that isn't directly related to the product labels Oct 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Chore For work that isn't directly related to the product needs-triage This label refers to a non-final decision on implementation, when an important feature/bug is added P3 P3 labels are used for issues which are not very pressing and we'd love community to work on
Projects
Status: Todo
Development

No branches or pull requests

2 participants