We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
reject_remote_clients Configuration corruption
tokio
1.10.1
>=1.18.4, <1.19.0,>=1.20.3, <1.21.0,>=1.23.1
<1.7.0
On Windows, configuring a named pipe server with pipe_mode will force ServerOptions::reject_remote_clients as false.
false
This drops any intended explicit configuration for the reject_remote_clients that may have been set as true previously.
true
The default setting of reject_remote_clients is normally true meaning the default is also overridden as false.
Ensure that pipe_mode is set first after initializing a ServerOptions. For example:
let mut opts = ServerOptions::new(); opts.pipe_mode(PipeMode::Message); opts.reject_remote_clients(true);
See advisory page for additional details.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
tokio
1.10.1
>=1.18.4, <1.19.0,>=1.20.3, <1.21.0,>=1.23.1
<1.7.0
On Windows, configuring a named pipe server with pipe_mode will force ServerOptions::reject_remote_clients as
false
.This drops any intended explicit configuration for the reject_remote_clients that may have been set as
true
previously.The default setting of reject_remote_clients is normally
true
meaning the default is also overridden asfalse
.Workarounds
Ensure that pipe_mode is set first after initializing a ServerOptions. For example:
See advisory page for additional details.
The text was updated successfully, but these errors were encountered: