You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The "wamp-parser-rs" repository relies on the "websocket" crate, which in turn depends on an outdated and unmaintained version (v0.10) of the "hyper" crate. As of now, "hyper" has moved on to v1.0.0-rc.4, and the "websocket" crate remains on an old version.
Additionally, it's worth noting that the "websocket-rs" project, which provides the "websocket" crate, is also unmaintained, adding to the security concerns.
Impact
Using outdated and unmaintained dependencies poses significant security risks. Such dependencies may have unresolved vulnerabilities or lack essential updates and patches to address security issues.
Proposed Solution
Switch to an Alternative WebSocket Implementation: A preferred and effective solution is to migrate to a different WebSocket implementation, such as tokio-tungstenite. Tokio-tungstenite is an actively maintained WebSocket library designed to seamlessly integrate with the Tokio asynchronous runtime. By transitioning to this well-maintained library, you can ensure the long-term security and maintainability of the project while minimizing the effort required to address dependency-related issues.
Advantages of this Solution:
Utilizing a WebSocket library that is actively maintained.
Compatibility with modern Rust async/await patterns and Tokio.
Reduced long-term maintenance overhead.
Considerations:
Carefully plan the migration to ensure that existing code using the "websocket" crate is updated to use "tokio-tungstenite" as smoothly as possible.
Update project documentation and dependencies to reflect the switch to "tokio-tungstenite."
This solution prioritizes adopting a well-maintained WebSocket library to enhance the project's security and sustainability while avoiding the complexities of forking and maintaining an outdated crate.
For more context, please refer to the comment on the original issue highlighting the concerns related to the old dependency and the unmaintained status of the "websocket" crate.
The text was updated successfully, but these errors were encountered:
Websocket libraries can be entirely removed from this repo. Websocket functionality is being moved to the other library. Websocket library was available for message conversion from JSON String to Websocket message.
websocket crate and a few other crates were removed completely from the repo. We will not be using tungnstenite in this library, in favor of ezsockets in the Client side library found here.
Description
The "wamp-parser-rs" repository relies on the "websocket" crate, which in turn depends on an outdated and unmaintained version (v0.10) of the "hyper" crate. As of now, "hyper" has moved on to v1.0.0-rc.4, and the "websocket" crate remains on an old version.
Additionally, it's worth noting that the "websocket-rs" project, which provides the "websocket" crate, is also unmaintained, adding to the security concerns.
Impact
Using outdated and unmaintained dependencies poses significant security risks. Such dependencies may have unresolved vulnerabilities or lack essential updates and patches to address security issues.
Proposed Solution
Switch to an Alternative WebSocket Implementation: A preferred and effective solution is to migrate to a different WebSocket implementation, such as tokio-tungstenite. Tokio-tungstenite is an actively maintained WebSocket library designed to seamlessly integrate with the Tokio asynchronous runtime. By transitioning to this well-maintained library, you can ensure the long-term security and maintainability of the project while minimizing the effort required to address dependency-related issues.
Advantages of this Solution:
Considerations:
This solution prioritizes adopting a well-maintained WebSocket library to enhance the project's security and sustainability while avoiding the complexities of forking and maintaining an outdated crate.
For more context, please refer to the comment on the original issue highlighting the concerns related to the old dependency and the unmaintained status of the "websocket" crate.
The text was updated successfully, but these errors were encountered: