-
Notifications
You must be signed in to change notification settings - Fork 0
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
Separate encrypted lookup path entirely #127
Comments
Does this only apply to the |
All queries. For HTTP delegated routing, the semantics are not finalised though close to be. |
gammazero
added a commit
that referenced
this issue
Aug 29, 2023
Do not rely on dbl-sha2-256 codec to determine if querying for encrypted or non-encrypted multihash. Use URL path instead. Fixes #127 Requires ipni/dhstore#84
gammazero
added a commit
that referenced
this issue
Sep 9, 2023
* Do not rely on dbl-sha2-256 codec to determine if querying for encrypted or non-encrypted multihash. Use URL path instead. Requires ipni/dhstore#84 Fixes #127
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The double hash multicodec code is not dedicated to encrypted records. Therefore we cannot implicitly assume that it represents one.
Separate encrypted lookup path by adding
/encrypted
prefix.Context:
The text was updated successfully, but these errors were encountered: