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.

Sign up for GitHub

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

Jump to bottom

Remove path gateway ipfs.io, use dweb.link everywhere #1165

Open
lidel opened this issue Feb 22, 2023 · 0 comments
Open

Remove path gateway ipfs.io, use dweb.link everywhere #1165

lidel opened this issue Feb 22, 2023 · 0 comments
Assignees
@whizzzkid
Labels
effort/days Estimated to take multiple days, but less than a week effort/hours Estimated to take one or several hours exp/intermediate Prior experience is likely helpful P1 High: Likely tackled by core team if no one steps up topic/security Work related to security

Comments

@lidel
Copy link
Member

lidel commented Feb 22, 2023 •
edited
Loading

Current state

We have:

  • "Default Public Gateway" set to ipfs.io
  • "Default Public Subdomain Gateway" set to dweb.link

Problem

We've introduced subdomain gateways to solve multiple issues in browser context, and are moving all web use cases towards that model. Soon, we will start locking down path gateways (ipfs/in-web-browsers#157) which means website/dapp links copied by users will stop working correctly if loaded via ipfs.io.

IPFS Companion should remove the footgun of path gateway by removing it from GUI.

Desired state

  • There should only be "Default Public Gateway" set to dweb.link.

Side-quest: migrate existing user settings

We need to write a migration that reads "Default Public Subdomain Gateway" and uses that (if it is other than dweb.link)

cc @darobin @autonome for sanity check
@whizzzkid @SgtPooki fysa this impacts end-user security, and should be prioritized
@lidel lidel added topic/security Work related to security exp/intermediate Prior experience is likely helpful P1 High: Likely tackled by core team if no one steps up effort/hours Estimated to take one or several hours effort/days Estimated to take multiple days, but less than a week labels Feb 22, 2023
@github-project-automation github-project-automation bot moved this to Needs Grooming in IPFS-GUI (PL EngRes) Feb 23, 2023
@SgtPooki SgtPooki moved this from Needs Grooming to Prioritized / Ready for Dev in IPFS-GUI (PL EngRes) Mar 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@whizzzkid whizzzkid

Labels
effort/days Estimated to take multiple days, but less than a week effort/hours Estimated to take one or several hours exp/intermediate Prior experience is likely helpful P1 High: Likely tackled by core team if no one steps up topic/security Work related to security
Projects
No open projects
IPFS-GUI (PL EngRes)
Status: Prioritized / Ready for Dev
Milestone
No milestone
Development

No branches or pull requests
2 participants
@lidel @whizzzkid