Ability to add vanity URLs #66

Open
opened 1 year ago by kevq · 3 comments
kevq commented 1 year ago

It would be great to have the ability to create something like a CNAME entry in our DNS host that gives us the ability to use a subdomain that links to a Keyoxide profile.

Let's be honest, no one is going to remember their fingerprint, so some kind of vanity URL would be helpful.

It would be great to have the ability to create something like a CNAME entry in our DNS host that gives us the ability to use a subdomain that links to a Keyoxide profile. Let's be honest, no one is going to remember their fingerprint, so some kind of vanity URL would be helpful.
Owner

Sounds great. So what is the issue here? Need for a guide? Because you already did this, I saw. My point being: what needs to happen to close this issue? Is Keyoxide currently impeding in any way?

no one is going to remember their fingerprint

I have remembered the first four characters, so yes, we can agree on that :)

Sounds great. So what is the issue here? Need for a guide? Because you already did this, I saw. My point being: what needs to happen to close this issue? Is Keyoxide currently impeding in any way? > no one is going to remember their fingerprint I have remembered the first four characters, so yes, we can agree on that :)
yarmo added the
question
label 1 year ago
kevq commented 1 year ago
Poster

Sorry I wasn't very clear in my original post (not like me, I know! 😄)

So, I've created a redirect to a sub-domain, yep that was fine. What I mean is a way of doing this from within Keyoxide. So the ability to add a CNAME in your host that points to the Keyoxide profile and KeyOxide issues a LE certificate against that sub-domain so it all works.

I'm thinking like how Netlify does it - the create <subdomain>.netlify.app for websites hosted with them, then you setup a CNAME that points to it. They issue the LE cert and the URL works.

Hope that makes sense?

Sorry I wasn't very clear in my original post (not like me, I know! 😄) So, I've created a redirect to a sub-domain, yep that was fine. What I mean is a way of doing this from within Keyoxide. So the ability to add a CNAME in your host that points to the Keyoxide profile and KeyOxide issues a LE certificate against that sub-domain so it all works. I'm thinking like how Netlify does it - the create `<subdomain>.netlify.app` for websites hosted with them, then you setup a CNAME that points to it. They issue the LE cert and the URL works. Hope that makes sense?

What @kevq suggests if what keys.openpgp.org does for WKD-as-a-Service.

But I've got a question: wouldn't a simple redirect from https://kevq.uk/key (just an example) to https://keyoxide.org/YOUR-KEY work? This is far simpler to do (it works now!) and no need for complicated let's encrypt issuance process.

What @kevq suggests if what keys.openpgp.org does for WKD-as-a-Service. But I've got a question: wouldn't a simple redirect from https://kevq.uk/key (just an example) to https://keyoxide.org/YOUR-KEY work? This is far simpler to do (it works now!) and no need for complicated let's encrypt issuance process.
Sign in to join this conversation.
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.