http://bugs.winehq.org/show_bug.cgi?id=34733
Bug #: 34733 Summary: Gnu TLS problem with UPlay 4.0 Product: Wine Version: 1.7.4 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: secur32 AssignedTo: wine-bugs@winehq.org ReportedBy: berillions@gmail.com Classification: Unclassified
Created attachment 46310 --> http://bugs.winehq.org/attachment.cgi?id=46310 Uplay 4 + secur32 log
Hi,
Today, there was an update for UPlay to pass to the version 4.0 Now, the automatic connection does not works correctly and i must to try more time to success.
In the output console, i have this message after every failure: "GnuTLS error: A TLS fatal alert has been received."
I attach the output console with +secur32 debug log. For example, i have this message in the log :
"[...] trace:secur32:schan_gnutls_log <4> REC[0x7d4948b8]: Expected Packet[1] Application Data(23) with length: 22 trace:secur32:schan_gnutls_log <4> REC[0x7d4948b8]: Received Packet[1] Alert(21) with length: 22 trace:secur32:schan_pull Pull 22 bytes trace:secur32:schan_get_buffer Using buffer 0: cbBuffer 27, BufferType 0x1, pvBuffer 0x5bee3b0 trace:secur32:schan_pull Read 22 bytes trace:secur32:schan_gnutls_log <4> REC[0x7d4948b8]: Decrypted Packet[1] Alert(21) with length: 2 trace:secur32:schan_gnutls_log <4> REC[0x7d4948b8]: Alert[2|20] - Bad record MAC - was received trace:secur32:schan_gnutls_log <2> ASSERT: gnutls_record.c:726 trace:secur32:schan_gnutls_log <2> ASSERT: gnutls_record.c:1122 GnuTLS error: A TLS fatal alert has been received. err:secur32:schan_DecryptMessage Returning 80090304 [...]"
http://bugs.winehq.org/show_bug.cgi?id=34733
--- Comment #1 from Berillions berillions@gmail.com 2013-10-15 13:30:25 CDT --- Forgot to mention that this problem appears when UPlay must to download/upload the savegame to the cloud.
http://bugs.winehq.org/show_bug.cgi?id=34733
--- Comment #2 from Juan Lang juan.lang@gmail.com 2013-10-17 11:39:31 CDT --- It looks like it it continues from the fatal alert? I'm not sure. There's also this, toward the end of your log: [1015/200823:WARNING:cert_verify_proc_win.cc(113)] Unknown error -2146885628 mapped to net::ERR_FAILED
Could you post a +chain log too?
http://bugs.winehq.org/show_bug.cgi?id=34733
--- Comment #3 from Berillions berillions@gmail.com 2013-10-17 12:36:29 CDT --- Created attachment 46335 --> http://bugs.winehq.org/attachment.cgi?id=46335 +secur32 log 2
(In reply to comment #2)
It looks like it it continues from the fatal alert? I'm not sure. There's also this, toward the end of your log: [1015/200823:WARNING:cert_verify_proc_win.cc(113)] Unknown error -2146885628 mapped to net::ERR_FAILED
Could you post a +chain log too?
I attached the new log (3 failures + 1 success at the end) but it seems that the +chain option for winedebug does not exist no ?
And in this new log, i don't have this error : [1015/200823:WARNING:cert_verify_proc_win.cc(113)] Unknown error -2146885628 mapped to net::ERR_FAILED
http://bugs.winehq.org/show_bug.cgi?id=34733
--- Comment #4 from Juan Lang juan.lang@gmail.com 2013-10-17 12:38:47 CDT --- Ok. I don't see any smoking guns here, because at the end of the log it appears that bytes are still streaming over the TLS connection. The last line from +secur32 is: trace:secur32:schan_DecryptMessage Received 646 bytes
http://bugs.winehq.org/show_bug.cgi?id=34733
--- Comment #5 from Berillions berillions@gmail.com 2013-10-17 12:51:38 CDT --- (In reply to comment #4)
Ok. I don't see any smoking guns here, because at the end of the log it appears that bytes are still streaming over the TLS connection. The last line from +secur32 is: trace:secur32:schan_DecryptMessage Received 646 bytes
At the end, it's the moment or i succeded to connect me into Uplay. Before, there was 3 connections failure.
And you think there is not wine bug with this connections problems ?
http://bugs.winehq.org/show_bug.cgi?id=34733
--- Comment #6 from Juan Lang juan.lang@gmail.com 2013-10-17 18:45:14 CDT --- No, I can't assert with confidence where the issue lies, that's all. I don't see anything that strongly suggests a secur32 bug.
http://bugs.winehq.org/show_bug.cgi?id=34733
--- Comment #7 from Berillions berillions@gmail.com 2013-10-19 07:47:40 CDT --- (In reply to comment #6)
No, I can't assert with confidence where the issue lies, that's all. I don't see anything that strongly suggests a secur32 bug.
Same problem on Archlinux but there is something that i understand here : [...] trace:secur32:schan_gnutls_log <4> REC[0x7dca80e8]: SSL 3.1 Alert packet received. Epoch 0, length: 22 trace:secur32:schan_gnutls_log <4> REC[0x7dca80e8]: Expected Packet Application Data(23) trace:secur32:schan_gnutls_log <4> REC[0x7dca80e8]: Received Packet Alert(21) with length: 22 trace:secur32:schan_pull Pull 22 bytes trace:secur32:schan_get_buffer Using buffer 0: cbBuffer 27, BufferType 0x1, pvBuffer 0x5bee3b0 trace:secur32:schan_pull Read 22 bytes trace:secur32:schan_gnutls_log <2> ASSERT: mac.c:253 trace:secur32:schan_gnutls_log <4> REC[0x7dca80e8]: Decrypted Packet[1] Alert(21) with length: 2 trace:secur32:schan_gnutls_log <4> REC[0x7dca80e8]: Alert[2|20] - Bad record MAC - was received trace:secur32:schan_gnutls_log <2> ASSERT: gnutls_record.c:794 trace:secur32:schan_gnutls_log <2> ASSERT: gnutls_record.c:800 trace:secur32:schan_gnutls_log <2> ASSERT: gnutls_record.c:1285 trace:secur32:schan_gnutls_log <2> ASSERT: gnutls_record.c:1388 GnuTLS error: A TLS fatal alert has been received. err:secur32:schan_DecryptMessage Returning 80090304 [...]
I have no knowledge about secur32/crypt functioning so i tried to search in Internet. I found that if ssl reveive an alert (like in my log), the connections is broken.
But : - SSL 3.1 exist and is implemented/known in Wine - Why the connection is broken ? This SSL bug appeared with UPlay 3.0 (only with the savegame) and since UPlay 4.x it's for the savegame/Uplay connection.
This bug does not exist on Windows so there is somewhere a problem in Wine which break the connection, no?
http://bugs.winehq.org/show_bug.cgi?id=34733
--- Comment #8 from Berillions berillions@gmail.com 2013-12-01 04:08:31 CST --- I remarked something when the synchronisation for the savegame does not works. In the output console, i have still these message for each failure: "GnuTLS error: A TLS fatal alert has been received. err:secur32:schan_DecryptMessage Returning 80090304"
And when i look into the "launcher_log.txt" (in Uplay folder), for earch sync failure, i have these message : [8]2013-12-01 10:56:31[157]ERROR XmlParser.cpp (49) Failed to parse XML. Error string="no element found". Line 1. Column 0. Byte index 4294967295. [8]2013-12-01 10:56:31[157]ERROR OrbitSavegameSynchronizer.cpp (981) failed to parse savegamelist: "" [8]2013-12-01 10:56:31[157]ERROR OrbitSavegameSynchronizer.cpp (585) Failed to download savegamelist [8]2013-12-01 10:56:31[157]ERROR SaveGameSyncJob.cpp (60) Save game sync connection failed. [8]2013-12-01 10:56:33[53]ERROR TCPSocketSelected.cpp (342) send failed, error=10054
For each Uplay's launch, i have in an other log file this error : [1201/105449:WARNING:cert_verify_proc_win.cc(113)] Unknown error -2146885628 mapped to net::ERR_FAILED
http://bugs.winehq.org/show_bug.cgi?id=34733
--- Comment #9 from Berillions berillions@gmail.com 2013-12-06 09:41:06 CST --- Created attachment 46757 --> http://bugs.winehq.org/attachment.cgi?id=46757 Network Infos for Wine
Now, the automatic connection to our account works but the sync savegame to UPlay could still failed.
In the Uplay/log folder, there is a file named "Network_info" which resume all network characteristics for Uplay in the OS.
I attached the first file which resume the information about Uplay and Wine.
Between these 2 files, we can see that Windows can use Installed providers and Wine nothing.
Same thing for the installed protocols, Wine use only 5 protocols and Wine 17 protocols.
I sent an email to Juan Lang about this log. For him, it's certainly possible that the sync problem is the consequence of this unavailability.
So Wine dev's, have you got an others ideas ?
http://bugs.winehq.org/show_bug.cgi?id=34733
Berillions berillions@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Gnu TLS problem with UPlay |Fail to sync to the Uplay |4.0 |Cloud
http://bugs.winehq.org/show_bug.cgi?id=34733
--- Comment #10 from Berillions berillions@gmail.com 2013-12-06 09:42:17 CST --- Created attachment 46758 --> http://bugs.winehq.org/attachment.cgi?id=46758 Network Infos for Seven
Same log from Windows Seven
http://bugs.winehq.org/show_bug.cgi?id=34733
--- Comment #11 from Berillions berillions@gmail.com --- Created attachment 47551 --> http://bugs.winehq.org/attachment.cgi?id=47551 +winsock,+secur32
New +secur32,+winsock log when i use UPlay with wine-1.7.12-141-gaa22a3c. I have always a gnutls error but this time, this appears when UPlay must to show my avatar. (I have the same errors lines for the Cloud)
Now, i have these lines in the log :
[...] trace:secur32:schan_gnutls_log <4> REC[0x7c66af28]: Expected Packet[1] Application Data(23) with length: 32 trace:secur32:schan_gnutls_log <4> REC[0x7c66af28]: Received Packet[1] Alert(21) with length: 32 trace:secur32:schan_pull Pull 32 bytes trace:secur32:schan_get_buffer Using buffer 0: cbBuffer 37, BufferType 0x1, pvBuffer 0x629e3a0 trace:secur32:schan_pull Read 32 bytes trace:secur32:schan_gnutls_log <4> REC[0x7c66af28]: Decrypted Packet[1] Alert(21) with length: 2 trace:secur32:schan_gnutls_log <4> REC[0x7c66af28]: Alert[2|40] - Handshake failed - was received trace:secur32:schan_gnutls_log <2> ASSERT: gnutls_record.c:726 trace:secur32:schan_gnutls_log <2> ASSERT: gnutls_record.c:1122 GnuTLS error: A TLS fatal alert has been received. err:secur32:schan_DecryptMessage Returning 80090304 trace:winsock:WS_select read 0x679e778, write (nil), excp 0x679e87c timeout 0x679e744 trace:winsock:WS_select read 0x679e778, write (nil), excp 0x679e87c timeout 0x679e744 trace:winsock:WS_select read 0x679e778, write (nil), excp 0x679e87c timeout 0x679e744 [...]
Someone has an idea about the "handshake failed" ?
http://bugs.winehq.org/show_bug.cgi?id=34733
hanska2@luukku.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |hanska2@luukku.com
--- Comment #12 from hanska2@luukku.com --- wine 1.7.23 has a fix for uplay not able to login. I don't know if this bug is related to it, but it's worth to try.
http://bugs.winehq.org/show_bug.cgi?id=34733
--- Comment #13 from Berillions berillions@gmail.com --- (In reply to hanska2 from comment #12)
wine 1.7.23 has a fix for uplay not able to login. I don't know if this bug is related to it, but it's worth to try.
Already tried. This bug still exist unfortunatly.
https://bugs.winehq.org/show_bug.cgi?id=34733
Adam Bolte abolte@systemsaviour.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |abolte@systemsaviour.com
--- Comment #14 from Adam Bolte abolte@systemsaviour.com --- Still exists in 1.7.33.
https://bugs.winehq.org/show_bug.cgi?id=34733
--- Comment #15 from Adam Bolte abolte@systemsaviour.com --- Created attachment 52625 --> https://bugs.winehq.org/attachment.cgi?id=52625 uplay_win81-launcher_log.txt
From Program Files (x86)/Ubisoft/Ubisoft Game Launcher/logs/launcher_log.txt on
a Windows 8.1 machine.
https://bugs.winehq.org/show_bug.cgi?id=34733
--- Comment #16 from Adam Bolte abolte@systemsaviour.com --- Created attachment 52626 --> https://bugs.winehq.org/attachment.cgi?id=52626 uplay_wine_1_7_53-launcher_log.txt
From From Program Files (x86)/Ubisoft/Ubisoft Game
Launcher/logs/launcher_log.txt in a clean UPlay + FarCry 4 Wine 1.7.53 prefix.
https://bugs.winehq.org/show_bug.cgi?id=34733
--- Comment #17 from Adam Bolte abolte@systemsaviour.com --- Created attachment 52627 --> https://bugs.winehq.org/attachment.cgi?id=52627 wine_1.7.53_winsock_secur32_console_output.log
Output of:
WINEDEBUG=+winsock,+secur32 wine Uplay.exe 2>&1 | grep -v 'trace:winsock:WS_select read 0x4fee774, write (nil), excp 0x4fee878 timeout 0x4fee73c'
I omitted that specific trace:winsock:WS_select... line because it was flooding the console.
We no longer have the "Handshake failed" message. Seems we are close.
https://bugs.winehq.org/show_bug.cgi?id=34733
AnAkkk anakin.cs@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |anakin.cs@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=34733
--- Comment #18 from Berillions berillions@gmail.com --- No news about this bug ? I have an old Uplay account for Wine's dev who want to try to resolv this bug.
https://bugs.winehq.org/show_bug.cgi?id=34733
--- Comment #19 from Adam Bolte abolte@systemsaviour.com --- Confirming this is still an issue with 1.9.4. Uplay continues to offer a "Skip" button on the error message, for now at least.
https://bugs.winehq.org/show_bug.cgi?id=34733
super_man@post.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |super_man@post.com
--- Comment #20 from super_man@post.com --- Is this still valid? While today I tested bug 40271 with the patch linked. I was able to see that uplay was synchronizing with the cloud and it didnt complain about it. I dont know if it needs the patch to get working.
https://bugs.winehq.org/show_bug.cgi?id=34733
--- Comment #21 from Berillions berillions@gmail.com --- Same thing for me. Don't know if the staging patch resolv this issue (impossible to confirm) but the cloud works. Tried with Valiant Heart.
https://bugs.winehq.org/show_bug.cgi?id=34733
mrdeathjr28@yahoo.es changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |mrdeathjr28@yahoo.es
https://bugs.winehq.org/show_bug.cgi?id=34733
--- Comment #22 from Adam Bolte abolte@systemsaviour.com --- To elaborate on what Berillions and super_man@post.com are saying:
Vanilla Wine 1.9.11, Uplay login doesn't work. If you have logged in before, you can click Settings (on the login pop-up) and click "always start in offline mode", and then you're in. So it doesn't seem possible to test cloud save without patches from staging right now.
It's easy to confirm this - just install Uplay into a clean prefix and try to log in. You'll get the message "A Ubisoft service is not available at the moment. You can try again later or switch to offline mode."
However Wine-Staging 1.9.10 patches (from bug 40271) do allow login to work without resorting to offline mode, and I can confirm that cloud-save does appear to work in the wine-staging environment.
All of the above described behavior was tested in a 32-bit Windows XP prefix with FarCry 3 installed without any DLL overrides.
A while back, Uplay used to open a pop-up that eventually stalled and indicated a cloud save failure, and asked (from memory) "Skip" or "Retry". That pop-up still exists, but then quickly disappears with Wine-Staging since saving appears to be working correctly with those patches. So I'm very eager to see patches for bug 40271 merged in, and for this bug to at least be marked as confirmed.
https://bugs.winehq.org/show_bug.cgi?id=34733
Bruno Jesus 00cpxxx@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |NEW URL| |https://uplay.ubi.com Keywords| |download
--- Comment #23 from Bruno Jesus 00cpxxx@gmail.com --- If the same patch from bug 40271 fixes this issue we can mark as duplicate, what do you think?
https://bugs.winehq.org/show_bug.cgi?id=34733
--- Comment #24 from Adam Bolte abolte@systemsaviour.com --- (In reply to Bruno Jesus from comment #23)
If the same patch from bug 40271 fixes this issue we can mark as duplicate, what do you think?
I just compiled https://raw.githubusercontent.com/wine-compholio/wine-staging/master/patches... (listed in bug 40271) into an otherwise clean 1.9.11, and logged out of Uplay for testing.
Confirming I didn't get stuck on either Uplay's login or cloud save functions. That patch fixes both issues, so this can be marked as a dup.
https://bugs.winehq.org/show_bug.cgi?id=34733
Bruno Jesus 00cpxxx@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |DUPLICATE
--- Comment #25 from Bruno Jesus 00cpxxx@gmail.com --- Thanks for the tests, this bug is older but since the patch is there and other people also confirmed it is fixed there I'm resolving as duplicate.
*** This bug has been marked as a duplicate of bug 40271 ***
https://bugs.winehq.org/show_bug.cgi?id=34733
Bruno Jesus 00cpxxx@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #26 from Bruno Jesus 00cpxxx@gmail.com --- Closing duplicate bugs.