[Bug 48254] Steam + Skyrim Special Edition: fails to connect to api.bethesda.net

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=48254

Olivier F. R. Dierick <o.dierick at piezo-forte.be> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Steam + Skyrim Special      |Steam + Skyrim Special
                   |Edition: unimplemented      |Edition: fails to connect
                   |option 84                   |to api.bethesda.net
                 CC|                            |o.dierick at piezo-forte.be

--- Comment #12 from Olivier F. R. Dierick <o.dierick at piezo-forte.be> ---
Hello,

(In reply to Shumkar from comment #11)
> 
> How to make this bug referenced to Skyrim SE App?

I submitted the bug to the AppDB entry:
https://appdb.winehq.org/objectManager.php?sClass=version&iId=34366

There may be a delay for the AppDB maintainers to review and accept it.
When they do the game will appear in the list of apps affected by this bug.

(In reply to Shumkar from comment #8)
> How can I debug it further? Which components are being used in this process?
> Steam, my system libs?
> 
> I would appreciate the help.

You could try with wine-devel/wine-staging 4.21.
wine-stable 4.0.2 doesn't include the most recent development changes.

--- quote from terminal log ---
0299:err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated.
Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in
the winbind package of your distribution.
--- end of quote ---

Probably not related, but you could fix this by installing the winbind package
from your distribution (Remember to install the 32-bit package too on 64-bit
system).

--- quote from terminal log ---
0131:trace:winhttp:netconn_verify_cert verifying L"api.bethesda.net"
0131:trace:winhttp:netconn_verify_cert returning 00002f7d
0131:warn:winhttp:netconn_secure_connect cert verify failed: 12157
0131:warn:winhttp:netconn_secure_connect Failed to initialize security context
failed: 00000000
--- end of quote ---

It could be a cryptographic component issue.

May be a WINEDEBUG=warn+all trace could reveal something?

(In reply to Hans Leidekker from comment #6)
> I mean WINHTTP_OPTION_SECURE_PROTOCOLS. I wrote a test for this case and it
> fails on Windows with ERROR_WINHTTP_INCORRECT_HANDLE_TYPE. That means Wine
> behaves correctly here and the problem must be somewhere else.

If unimplemented option 84 is not the problem, may be the summary should
reflect that? I'll go ahead and change it. Please, correct me if my
understanding is wrong.

Regards.

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.