keybase / keybase/client

HTTP proof from redirected domain

Open
#10,063 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
9.2k
Forks
1.3k
Avg merge
12h 58m
Merged PRs (30d)
56

Description

Hi I am [jaredhk](https://keybase.io/jaredhk) on Keybase.

My website is [jaredhk.com](http://jaredhk.com) but that redirects to [jaredhk.me](http://jaredhk.me). The proof is located at [jaredhk.me/keybase.txt](http://jaredhk.me/keybase.txt) and that is verified. However, my preferred domain to show up is [jaredhk.com](http://jaredhk.com) for a few reasons. I can't ever verify that with Keybase, though, since it redirects. Is there a way around this? Can we make a way around it?

Someone sort of brought this up in #9674 but it was never responded to

Contributor guide

No contributing guide indexed for this repository

Research direction

Review issue #9674 and the current handling of HTTP proofs for redirected domains. Reproduce the redirect from jaredhk.com to jaredhk.me and compare it with the verified keybase.txt proof. Done means the preferred redirected domain can be verified or the supported limitation is clearly established.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
authentication, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.