-
Notifications
You must be signed in to change notification settings - Fork 40
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
Exception at System.Runtime.Remoting.Channels.ChannelServices.RegisterChannel SingeInstanceIPCChannel is not securable while ensureSecurity is specified as true #64
Comments
Can you get a log with |
sure |
perhaps mono itself does not support such a function? |
The log shows that this is an IpcServerChannel, not TcpChannel, but it seems to be the same situation. I'm not sure what ISecurableChannel is supposed to do. MSDN just says "Gets or sets a Boolean value that indicates whether the current channel is secure." |
found some information here |
Do not decompile .NET Framework code. |
thanks for the safety. I suspect the whole thing is the default IChannel secure field for mono and net.framework |
This sounds like the same problem, posted way back in 2007: http://www.claassen.net/geek/blog/2007/06/isecurablechannel-in-tcpchannel-not.html |
The MSDN documentation for RegisterChannel offers this explanation:
I thought about adding a stub ISecurableChannel implementation to Mono's IpcServerChannel implementation and Mono's TcpChannel implementation, which would do no encryption even if the IsSecured property is set to true. However, I don't know how we would ensure that the fake implementation is only used for connections that stay on the local machine. If there's any chance that data sent to the channel could be sent over the internet unencrypted, that could be very bad. |
Is there a way to disable ensureSecurity? |
The application you're running would have to do that. There's no override option in Mono. |
Noting that the launcher for The Amazing Spider-Man hits this issue. |
is there any solution?
wine-5.13
whine-mono 5.1.0
The text was updated successfully, but these errors were encountered: