fluencelabs/rust-libp2p
1
0
Fork 0
mirror of https://github.com/fluencelabs/rust-libp2p synced 2025-05-28 10:11:19 +00:00
Code Issues Projects Releases Wiki Activity
rust-libp2p/core/CHANGELOG.md

70 lines
3.3 KiB
Markdown
Raw Normal View History

Remove temporary peer ID compatibility mode. (#1608) * Remove temporary peer ID compatibility. This removes the temporary compatibility mode between peer IDs using identity hashing and sha256, thus being the last step in the context of https://github.com/libp2p/rust-libp2p/issues/555. * Check digest length in PeerId::from_multihash for Identity hash. * Update core/src/peer_id.rs Co-authored-by: Toralf Wittner <tw@dtex.org> * Update core changelog. * Update core changelog. Co-authored-by: Toralf Wittner <tw@dtex.org>
2020-08-26 13:03:35 +02:00
# 0.22.0 [unreleased]
Update core changelog.
2020-09-03 11:29:52 +02:00
- Allow any closure to be passed as an executor.
[PR 1686](https://github.com/libp2p/rust-libp2p/pull/1686)
Remove temporary peer ID compatibility mode. (#1608) * Remove temporary peer ID compatibility. This removes the temporary compatibility mode between peer IDs using identity hashing and sha256, thus being the last step in the context of https://github.com/libp2p/rust-libp2p/issues/555. * Check digest length in PeerId::from_multihash for Identity hash. * Update core/src/peer_id.rs Co-authored-by: Toralf Wittner <tw@dtex.org> * Update core changelog. * Update core changelog. Co-authored-by: Toralf Wittner <tw@dtex.org>
2020-08-26 13:03:35 +02:00
- Remove `PeerId` compatibility mode for "identity" and SHA2 hashes.
Historically, before 0.12, `PeerId`s were incorrectly always hashed with SHA2.
Starting from version 0.13, rust-libp2p accepted both hashed and non-hashed keys as
input. Starting from version 0.16 rust-libp2p compared `PeerId`s of "identity" and
SHA2 hashes equal, which made it possible to connect through secio or noise to nodes
with an identity hash for the same peer ID. Starting from version 0.17, rust-libp2p
switched to not hashing the key (i.e. the correct behaviour) while retaining
equality between peer IDs using the "identity" hash and SHA2. Finally, with
this release, that will no longer be the case and it is assumed that peer IDs
whose length is less or equal to 42 bytes always use the "identity" hash so
two peer IDs are equal if and only if they use the same hash algorithm and
have the same hash digest. [PR 1608](https://github.com/libp2p/rust-libp2p/pull/1608).
core/transport/memory: Return dialer address in Upgrade event (#1724) Previously a `Listener` would return its own address as the `remote_addr` in the `ListenerEvent::Upgrade` event. With this commit a `Listener` returns the dialer address as the `remote_addr` in the `ListenerEvent::Upgrade` event. To do so a `DialFuture` registers a port with the global `HUB` at construction which is later on unregistered in the `Drop` implementation of the dialer's `Chan`. The sending side of the `mpsc::channel` registered in the `HUB` is dropped at `DialFuture` construction, thus one can not dial the dialer port. This mimics the TCP transport behaviour preventing both dialing and listening on the same TCP port.
2020-09-08 12:07:15 +02:00
- Return dialer address instead of listener address as `remote_addr` in
`MemoryTransport` `Listener` `ListenerEvent::Upgrade`
[PR 1724](https://github.com/libp2p/rust-libp2p/pull/1724).
*: Prepare v0.24.0 release (#1713) * */CHANGELOG: Update dates * Cargo.toml: Update to 0.24.0
2020-08-18 17:04:34 +02:00
# 0.21.0 [2020-08-18]
[core/swarm] Emit events for active connection close and fix `disconnect()`. (#1619) * Emit events for active connection close and fix `disconnect()`. The `Network` does currently not emit events for actively closed connections, e.g. via `EstablishedConnection::close` or `ConnectedPeer::disconnect()`. As a result, when actively closing connections, there will be `ConnectionEstablished` events emitted without eventually a matching `ConnectionClosed` event. This seems undesirable and has the consequence that the `Swarm::ban_peer_id` feature in `libp2p-swarm` does not result in appropriate calls to `NetworkBehaviour::inject_connection_closed` and `NetworkBehaviour::inject_disconnected`. Furthermore, the `disconnect()` functionality in `libp2p-core` is currently broken as it leaves the `Pool` in an inconsistent state. This commit does the following: 1. When connection background tasks are dropped (i.e. removed from the `Manager`), they always terminate immediately, without attempting an orderly close of the connection. 2. An orderly close is sent to the background task of a connection as a regular command. The background task emits a `Closed` event before terminating. 3. `Pool::disconnect()` removes all connection tasks for the affected peer from the `Manager`, i.e. without an orderly close, thereby also fixing the discovered state inconsistency due to not removing the corresponding entries in the `Pool` itself after removing them from the `Manager`. 4. A new test is added to `libp2p-swarm` that exercises the ban/unban functionality and places assertions on the number and order of calls to the `NetworkBehaviour`. In that context some new testing utilities have been added to `libp2p-swarm`. This addresses https://github.com/libp2p/rust-libp2p/issues/1584. * Update swarm/src/lib.rs Co-authored-by: Toralf Wittner <tw@dtex.org> * Incorporate some review feedback. * Adapt to changes in master. * More verbose panic messages. * Simplify There is no need for a `StartClose` future. * Fix doc links. * Further small cleanup. * Update CHANGELOGs and versions. Co-authored-by: Toralf Wittner <tw@dtex.org>
2020-08-04 11:30:09 +02:00
Update core changelog.
2020-08-24 10:48:36 +02:00
- Remove duplicates when performing address translation
[PR 1697](https://github.com/libp2p/rust-libp2p/pull/1697).
Changelog updates.
2020-08-17 10:14:44 +02:00
- Add `transport::Builder::multiplex_ext` for further customisation during
`StreamMuxer` creation. [PR 1691](https://github.com/libp2p/rust-libp2p/pull/1691).
[core/swarm] Emit events for active connection close and fix `disconnect()`. (#1619) * Emit events for active connection close and fix `disconnect()`. The `Network` does currently not emit events for actively closed connections, e.g. via `EstablishedConnection::close` or `ConnectedPeer::disconnect()`. As a result, when actively closing connections, there will be `ConnectionEstablished` events emitted without eventually a matching `ConnectionClosed` event. This seems undesirable and has the consequence that the `Swarm::ban_peer_id` feature in `libp2p-swarm` does not result in appropriate calls to `NetworkBehaviour::inject_connection_closed` and `NetworkBehaviour::inject_disconnected`. Furthermore, the `disconnect()` functionality in `libp2p-core` is currently broken as it leaves the `Pool` in an inconsistent state. This commit does the following: 1. When connection background tasks are dropped (i.e. removed from the `Manager`), they always terminate immediately, without attempting an orderly close of the connection. 2. An orderly close is sent to the background task of a connection as a regular command. The background task emits a `Closed` event before terminating. 3. `Pool::disconnect()` removes all connection tasks for the affected peer from the `Manager`, i.e. without an orderly close, thereby also fixing the discovered state inconsistency due to not removing the corresponding entries in the `Pool` itself after removing them from the `Manager`. 4. A new test is added to `libp2p-swarm` that exercises the ban/unban functionality and places assertions on the number and order of calls to the `NetworkBehaviour`. In that context some new testing utilities have been added to `libp2p-swarm`. This addresses https://github.com/libp2p/rust-libp2p/issues/1584. * Update swarm/src/lib.rs Co-authored-by: Toralf Wittner <tw@dtex.org> * Incorporate some review feedback. * Adapt to changes in master. * More verbose panic messages. * Simplify There is no need for a `StartClose` future. * Fix doc links. * Further small cleanup. * Update CHANGELOGs and versions. Co-authored-by: Toralf Wittner <tw@dtex.org>
2020-08-04 11:30:09 +02:00
- Refactoring of connection close and disconnect behaviour. In particular, the former
`NetworkEvent::ConnectionError` is now `NetworkEvent::ConnectionClosed` with the `error`
field being an `Option` and `None` indicating an active (but not necessarily orderly) close.
This guarantees that `ConnectionEstablished` events are always eventually paired
with `ConnectionClosed` events, regardless of how connections are closed.
Correspondingly, `EstablishedConnection::close` is now `EstablishedConnection::start_close`
to reflect that an orderly close completes asynchronously in the background, with the
outcome observed by continued polling of the `Network`. In contrast, `disconnect`ing
a peer takes effect immediately without an orderly connection shutdown.
See [PR 1619](https://github.com/libp2p/rust-libp2p/pull/1619) for further details.
protocols/kad: Implement NetworkBehaviour::inject_address_change (#1649) With 826f513 a `StreamMuxer` can notify that the address of a remote peer changed. This is needed to support the transport protocol QUIC as remotes can change their IP addresses within the lifetime of a single connection. This commit implements the `NetworkBehaviour::inject_address_change` handler to update the Kademlia routing table accordingly.
2020-08-06 15:35:24 +02:00
- Add `ConnectedPoint::get_remote_address`
([PR 1649](https://github.com/libp2p/rust-libp2p/pull/1649)).
[core]: fix typo in CHANGELOG.md (#1688)
2020-08-04 23:13:38 +02:00
# 0.20.1 [2020-07-17]
Upgrade ed25519-dalek to pre.4 (#1665) * Upgrade ed25519-dalek to pre.4 * Update core/src/identity/ed25519.rs Co-authored-by: Pierre Krieger <pierre.krieger1708@gmail.com> Co-authored-by: Pierre Krieger <pierre.krieger1708@gmail.com>
2020-07-17 12:01:49 +02:00
- Update ed25519-dalek dependency.
Prepare releases. (#1640) * Prepare releases. * Re-export libp2p-request-response from libp2p crate. * Clean up changelogs. * Restore upper bounds. * Version 0.21 for the root crate. * Stricter lower bound in libp2p-websocket version in root crate. * Update misc/peer-id-generator/Cargo.toml Co-authored-by: Toralf Wittner <tw@dtex.org> * Update release date. * Update misc/peer-id-generator/Cargo.toml Co-authored-by: Toralf Wittner <tw@dtex.org> Co-authored-by: Toralf Wittner <tw@dtex.org>
2020-07-01 15:36:20 +02:00
# 0.20.0 [2020-07-01]
- Conditional compilation fixes for the `wasm32-wasi` target
([PR 1633](https://github.com/libp2p/rust-libp2p/pull/1633)).
Allow StreamMuxer to notify changes in the address (#1621) * Allow StreamMuxer to notify changes in the address * Fix doc link * Revert accidental rename * Other accidental rename Co-authored-by: Roman Borschel <romanb@users.noreply.github.com>
2020-06-30 17:10:53 +02:00
- Rename `StreamMuxer::poll_inbound` to `poll_event` and change the
return value to `StreamMuxerEvent`. This new `StreamMuxerEvent` makes
it possible for the multiplexing layer to notify the upper layers of
a change in the address of the underlying connection.
- Add `ConnectionHandler::inject_address_change`.
Prepare release. (#1620)
2020-06-22 11:41:28 +02:00
# 0.19.2 [2020-06-22]
- Add PartialOrd and Ord for PeerId
([PR 1594](https://github.com/libp2p/rust-libp2p/pull/1594)).
- Updated dependencies.
- Deprecate `StreamMuxer::is_remote_acknowledged`
([PR 1616](https://github.com/libp2p/rust-libp2p/pull/1616)).
Reference in New Issue Copy Permalink