https://bugs.winehq.org/show_bug.cgi?id=47542
Bug ID: 47542 Summary: .NET Framework NetNamedPipe with transport security throws System.ComponentModel.Win32Exception: Unknown error (0x80090304) Product: Wine Version: 4.12.1 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: failedshack@gmail.com Distribution: ---
Hello,
I use WCF on a .NET application of mine and found it crashed under Wine due to a "System.Security.Authentication.AuthenticationException", itself caused by "System.ComponentModel.Win32Exception: Unknown error (0x80090304)". WCF is commonly used to call remote procedures from different processes in the same machine or over the network.
After some investigation I found that this is caused by using a named pipe with transport security enabled (which is the default behavior for WCF). You can disable the transport security, which will make it work but such is not always possible, for example I use FiddlerCore, an HTTP proxy and it suffers from the same problem when SSL decryption is turned on. Meaning you can only intercept HTTP traffic.
I'll attach a minimal example program that can be used to reproduce this issue, along with the stacktrace produced and a screenshot.
Transport security can be disabled by replacing the default binding for this:
var binding = new NetNamedPipeBinding { Security = new NetNamedPipeSecurity { Mode = NetNamedPipeSecurityMode.None, Transport = new NamedPipeTransportSecurity() { ProtectionLevel = ProtectionLevel.None } } };
This bug looks similar to this one but the error code is different, so I'm not entirely sure: https://bugs.winehq.org/show_bug.cgi?id=46671
I hope this helps.
Regards
https://bugs.winehq.org/show_bug.cgi?id=47542
--- Comment #1 from failedshack@gmail.com --- Created attachment 64933 --> https://bugs.winehq.org/attachment.cgi?id=64933 Short example program that causes the issue.
https://bugs.winehq.org/show_bug.cgi?id=47542
--- Comment #2 from failedshack@gmail.com --- Created attachment 64934 --> https://bugs.winehq.org/attachment.cgi?id=64934 Screenshot of the example program running in Windows vs in Debian
https://bugs.winehq.org/show_bug.cgi?id=47542
--- Comment #3 from failedshack@gmail.com --- Created attachment 64935 --> https://bugs.winehq.org/attachment.cgi?id=64935 Stacktrace produced by the example program under Wine
https://bugs.winehq.org/show_bug.cgi?id=47542
--- Comment #4 from failedshack@gmail.com --- Oh and I'm using Winetricks and .NET Framework 4.8.
https://bugs.winehq.org/show_bug.cgi?id=47542
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dark.shadow4@web.de
--- Comment #5 from Fabian Maurer dark.shadow4@web.de --- Created attachment 64952 --> https://bugs.winehq.org/attachment.cgi?id=64952 Test Binary
For simplicity, attaching compiled binary from the source you provided.
Also confirming, this issue only happens with native .NET though - with wine-mono it crashes earlier.
https://bugs.winehq.org/show_bug.cgi?id=47542
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Keywords| |download
--- Comment #6 from Fabian Maurer dark.shadow4@web.de --- Confirming.
https://bugs.winehq.org/show_bug.cgi?id=47542
--- Comment #7 from Fabian Maurer dark.shadow4@web.de --- Sorry for the spam, but I just noticed I get a different error code(0x8009030e). How exactly did you setup your WINEPREFIX?
https://bugs.winehq.org/show_bug.cgi?id=47542
--- Comment #8 from failedshack@gmail.com --- (In reply to Fabian Maurer from comment #7)
Sorry for the spam, but I just noticed I get a different error code(0x8009030e). How exactly did you setup your WINEPREFIX?
I set up Wine on a fresh Debian 10 guest in VirtualBox and left the default settings. Then installed dotnet48 with Winetricks with WINEARCH=win32 set.
Not sure why I get a different error code. Interestingly though, yours appears to be the same code reported in the issue I mentioned could be similar.