-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
feat: support GetClosesPeers (IPIP-476) and ExposeRoutingAPI by default #10954
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
Changes from all commits
23f1b59
ea8682c
e55712a
0f41957
a109580
bb2c7d8
8e389e0
6f14b3b
e5978f9
a4ed175
14511d7
3d64d58
b7111b7
4e88fe9
267b42f
49a9cff
8b81a40
0b07da9
693f112
638be7b
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -168,6 +168,10 @@ The `go-ipfs` name was deprecated in 2022 and renamed to `kubo`. Starting with t | |
|
|
||
| All users should migrate to the `kubo` name in their scripts and configurations. | ||
|
|
||
| #### Routing V1 HTTP API now exposed by default | ||
|
|
||
| The [Routing V1 HTTP API](https://specs.ipfs.tech/routing/http-routing-v1/) is now exposed by default at `http://127.0.0.1:8080/routing/v1`. This allows light clients in browsers to use Kubo Gateway as a delegated routing backend instead of running a full DHT client. Support for [IPIP-476: Delegated Routing DHT Closest Peers API](https://github.com/ipfs/specs/pull/476) is included. Can be disabled via [`Gateway.ExposeRoutingAPI`](https://github.com/ipfs/kubo/blob/master/docs/config.md#gatewayexposeroutingapi). | ||
|
|
||
|
Comment on lines
+171
to
+174
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. You probably thought of this better, but, assuming someone has exposed the gateway listen address already (:8080), doesn't this inadvertently exposes the routing API to the world? And, if so, how does this interact with certain gateway options... for example NoFetch means the gateway will not trigger lookups nor fetch any content, but now this API would allow for such lookups to be performed, so it seems a door that was closed is being opened. There are also other gateway options that might make similar considerations. |
||
| ### 📦️ Important dependency updates | ||
|
|
||
| - update `go-libp2p` to [v0.45.0](https://github.com/libp2p/go-libp2p/releases/tag/v0.45.0) (incl. [v0.44.0](https://github.com/libp2p/go-libp2p/releases/tag/v0.44.0)) with self-healing UPnP port mappings and go-log/slog interop fixes | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.