https://bugs.winehq.org/show_bug.cgi?id=49857
Bug ID: 49857 Summary: NCLauncher2: Crypto error on a successful login Product: Wine Version: 5.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: crypt32 Assignee: wine-bugs@winehq.org Reporter: yagocl@protonmail.ch Distribution: ---
I am attempting to run the NCSoft Launcher on Wine so that I may download and play the game Blade&Soul. The application is NCLauncher2.exe, you can grab it from here: https://launcher.patcher.ncsoft.com/NCLauncher2_Installer.exe or go the blade and soul website, register, and be sent to that download anyway.
Here's a sha256 checksum of what I downloaded: ba8e3f0272c103581eb05325384498a02c210f3df0ff78f399060aeb061b5d3e NCLauncher2_Installer.exe
The program runs fine, however if you get your credentials right and actually log in it will stop you with a crypto error. Here's the full message the launcher spits out in the UI:
Unfortunately there is no point to posting full terminal output since every message the program dumps into the terminal is obfuscated/encrypted. I tried running them through base64/32 -d to no avail. BUT, we can get wine to spit out what the program is doing in the crypto engine when the error happens with WINEDEBUG=+crypt trace file
This is what I get: 0009:fixme:crypt:PFXImportCertStore flags 00000021 not supported
I suppose it is trying to import a certificate in some way but cannot.
Here's some system info: Wine 5.17-staging 64 bit wineprefix Arch Linux with testing repos .NETs 4.5 all the way to 4.8 installed Intel CPU, Nvidia (+proprietary driver) GPU
https://bugs.winehq.org/show_bug.cgi?id=49857
yagocl@protonmail.ch changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |dotnet URL| |https://www.reddit.com/r/bl | |adeandsoul/comments/ivbmvk/ | |blade_and_soul_on_linux_wit | |h_dxvk/
https://bugs.winehq.org/show_bug.cgi?id=49857
--- Comment #1 from Hans Leidekker hans@meelstraat.net --- Created attachment 68228 --> https://bugs.winehq.org/attachment.cgi?id=68228 patch
Can you try this patch?
https://bugs.winehq.org/show_bug.cgi?id=49857
--- Comment #2 from yagocl@protonmail.ch --- Hi, I will try your patch on wine-staging git.
https://bugs.winehq.org/show_bug.cgi?id=49857
Hans Leidekker hans@meelstraat.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |547508e374b7e347488f8ce7a8f | |a40b333a79684 Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED
--- Comment #3 from Hans Leidekker hans@meelstraat.net --- Should be fixed by 547508e374b7e347488f8ce7a8fa40b333a79684.
https://bugs.winehq.org/show_bug.cgi?id=49857
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #4 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 5.19.
https://bugs.winehq.org/show_bug.cgi?id=49857
Fred dracoanarion@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dracoanarion@gmail.com
--- Comment #5 from Fred dracoanarion@gmail.com --- I'm actually wondering if this issue is really fixed.
After some difficulties, I could install the NCLauncher2, but there is still a failure during/after login, that seems to be related to certificates:
Note: The corean part should translate to "Certificate could not be found".
Tested with wine-5.19 (Staging). I created a new 64bit prefix, added winetricks dotnet462 corefonts d3dx9.
------------------------------
System.NullReferenceException 인증서를 찾을 수 없습니다. at A.c534e1664793830cb679d24d47d088810..ctor(String , String , Int32 , String , String , String , Int32 , String , Boolean , c58bd16845dd89cdccf2be96aac716727 ) at NCLauncherW.ViewModels.LauncherServiceLocator.c8f2ae7ac94891c9781b62fcc4e22d440() at NCLauncherW.ViewModels.LauncherServiceLocator.c84fc1a9632540e55b993d77c9da6a13f.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at (TaskAwaiter`1& ) at A.cc5578b8897930d10077f757bb1a294be.c47dc36c3ef840496a5f5c268b6bdd157(TaskAwaiter`1& ) at NCLauncherW.ViewModels.VerifyIpAuthCodeWindowViewModel.c315ce67b877818045ada406902533be7.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.AsyncMethodBuilderCore.<>c.<ThrowAsync>b__6_0(Object state) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
https://bugs.winehq.org/show_bug.cgi?id=49857
Olivier F. R. Dierick o.dierick@piezo-forte.be changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |o.dierick@piezo-forte.be
--- Comment #6 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- (In reply to Fred from comment #5)
I'm actually wondering if this issue is really fixed.
Hello,
Your issue looks different to me. Please, open a new bug.
Regards.
https://bugs.winehq.org/show_bug.cgi?id=49857
Michael Stefaniuc mstefani@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |5.0.x
https://bugs.winehq.org/show_bug.cgi?id=49857
Michael Stefaniuc mstefani@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|5.0.x |---
--- Comment #7 from Michael Stefaniuc mstefani@winehq.org --- Removing the 5.0.x milestone from bug fixes included in 5.0.4.
https://bugs.winehq.org/show_bug.cgi?id=49857
Steve Soule sts33nvyb@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |sts33nvyb@gmail.com
--- Comment #8 from Steve Soule sts33nvyb@gmail.com --- It looks like bug 50007 is the new bug reported by Fred.
-
WineHQ Bugzilla