https://bugs.winehq.org/show_bug.cgi?id=45768
Bug ID: 45768 Summary: PES 2019 demo launchs correctly fails upon connecting server (GnuTLS does not support algorithm 11..) Product: Wine Version: 3.15 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: bcrypt Assignee: wine-bugs@winehq.org Reporter: rtfss1@gmail.com Distribution: ---
Created attachment 62224 --> https://bugs.winehq.org/attachment.cgi?id=62224 some log
Hi, installed PES 2019 demo with Steam Proton.. and game launches correctly.. you accept some EULAS.. and then just before menu appears in what appears server connecting crashes.. from command line log from which steam was launched nothing interesting it shows DXVK being used (and I tested DXVK renders correctly the game on Windows by copying DLLS manually so clearly not a graphics issue).. I enabled proton game log file and from steam-886680.log I see lots of fixmes like:
GnuTLS does not support algorithm 10 with hash len 32 GnuTLS does not support algorithm 11 with hash len 32 GnuTLS does not support algorithm 11 with hash len 48
more log attached..
https://bugs.winehq.org/show_bug.cgi?id=45768
--- Comment #1 from oscarbg rtfss1@gmail.com --- just pointed these fixme's occur are the last errors in log just before crash..
https://bugs.winehq.org/show_bug.cgi?id=45768
--- Comment #2 from Hans Leidekker hans@meelstraat.net --- (In reply to oscarbg from comment #0)
GnuTLS does not support algorithm 10 with hash len 32 GnuTLS does not support algorithm 11 with hash len 32 GnuTLS does not support algorithm 11 with hash len 48
That's ALG_ID_ECDSA_P256 and ALG_ID_ECDSA_P384, which should be supported by recent GnuTLS. What version of GnuTLS do you have?
https://bugs.winehq.org/show_bug.cgi?id=45768
Alistair Leslie-Hughes leslie_alistair@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |leslie_alistair@hotmail.com
--- Comment #3 from Alistair Leslie-Hughes leslie_alistair@hotmail.com --- (In reply to Hans Leidekker from comment #2)
(In reply to oscarbg from comment #0)
GnuTLS does not support algorithm 10 with hash len 32 GnuTLS does not support algorithm 11 with hash len 32 GnuTLS does not support algorithm 11 with hash len 48
That's ALG_ID_ECDSA_P256 and ALG_ID_ECDSA_P384, which should be supported by recent GnuTLS. What version of GnuTLS do you have?
Patch one in patchset might help here https://github.com/wine-staging/wine-staging/tree/master/patches/bcrypt-BCry...
https://bugs.winehq.org/show_bug.cgi?id=45768
Luke A. Guest laguest@archeia.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |laguest@archeia.com
--- Comment #4 from Luke A. Guest laguest@archeia.com --- Confirm this, Rocksmith 2014:
2074018.970:0024:0025:trace:bcrypt:BCryptCloseAlgorithmProvider 0x1d86e8, 00000000 2074018.970:0024:0025:trace:bcrypt:BCryptOpenAlgorithmProvider 0x32a818, L"ECDSA_P384", (null), 00000000 2074018.970:0024:0025:trace:bcrypt:BCryptImportKeyPair 0x1d86e8, (nil), L"ECCPUBLICBLOB", 0x32a80c, 0x1d8738, 104, 00000000 2074018.970:0024:0025:trace:bcrypt:BCryptCloseAlgorithmProvider 0x1d86e8, 00000000 2074018.970:0024:0025:trace:bcrypt:BCryptVerifySignature 0x1d87a8, (nil), 0x1d8700, 48, 0x1ce4c0, 96, 00000000 2074018.970:0024:0025:fixme:bcrypt:key_asymmetric_verify GnuTLS does not support algorithm 11 with hash len 48 2074018.970:0024:0025:trace:bcrypt:BCryptDestroyKey 0x1d87a8
https://bugs.winehq.org/show_bug.cgi?id=45768
--- Comment #5 from Luke A. Guest laguest@archeia.com --- and alg 10:
2074019.183:0024:0025:trace:bcrypt:BCryptOpenAlgorithmProvider 0x32a818, L"ECDSA_P256", (null), 00000000 2074019.183:0024:0025:trace:bcrypt:BCryptImportKeyPair 0x1d86e8, (nil), L"ECCPUBLICBLOB", 0x32a80c, 0x208420, 72, 00000000 2074019.183:0024:0025:trace:bcrypt:BCryptCloseAlgorithmProvider 0x1d86e8, 00000000 2074019.183:0024:0025:trace:bcrypt:BCryptVerifySignature 0x55f9bc0, (nil), 0x204830, 32, 0x55fa100, 64, 00000000 2074019.183:0024:0025:fixme:bcrypt:key_asymmetric_verify GnuTLS does not support algorithm 10 with hash len 32 2074019.183:0024:0025:trace:bcrypt:BCryptDestroyKey 0x55f9bc0 2074019.183:0024:0025:fixme:crypt:verify_signature_bcrypt Failed to verify signature: c0000002
https://bugs.winehq.org/show_bug.cgi?id=45768
--- Comment #6 from Hans Leidekker hans@meelstraat.net --- (In reply to Alistair Leslie-Hughes from comment #3)
(In reply to Hans Leidekker from comment #2)
(In reply to oscarbg from comment #0)
GnuTLS does not support algorithm 10 with hash len 32 GnuTLS does not support algorithm 11 with hash len 32 GnuTLS does not support algorithm 11 with hash len 48
That's ALG_ID_ECDSA_P256 and ALG_ID_ECDSA_P384, which should be supported by recent GnuTLS. What version of GnuTLS do you have?
Patch one in patchset might help here https://github.com/wine-staging/wine-staging/tree/master/patches/bcrypt- BCryptGenerateKeyPair
That patch adds ALG_ID_ECDH_P256. This bug is about ALG_ID_ECDSA_P256 (and ALG_ID_ECDSA_P384).
Reporter, what version of GnuTLS do you have installed?
https://bugs.winehq.org/show_bug.cgi?id=45768
zzzzzyzz@hacari.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |zzzzzyzz@hacari.org
https://bugs.winehq.org/show_bug.cgi?id=45768
--- Comment #7 from oscarbg rtfss1@gmail.com --- Ok I sended response by mail few days ago and I got: "Do not mail wine-bugs directly. Please post in Bugzilla at http://bugs.winehq.org/."
I have Ubuntu 18.04 but maybe don't installed system updates in a few months..
In Synaptic I see: libgnutls30 installed version: 3.5.18-1ubuntu1
makes sense?
https://bugs.winehq.org/show_bug.cgi?id=45768
Vijay Kamuju infyquest@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |73b695f059740715ebd3ea0ce3c | |e88477977e628 Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED CC| |infyquest@gmail.com
--- Comment #8 from Vijay Kamuju infyquest@gmail.com --- This should be fixed by commit 73b695f059740715ebd3ea0ce3ce88477977e628
https://bugs.winehq.org/show_bug.cgi?id=45768
Hans Leidekker hans@meelstraat.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |--- Status|RESOLVED |REOPENED Ever confirmed|0 |1
--- Comment #9 from Hans Leidekker hans@meelstraat.net --- No, as explained in comment 6, this app wants ALG_ID_ECDSA_P256 (and ALG_ID_ECDSA_P384). That commit adds support for ALG_ID_ECDH_P256.
Support for the former has been in Wine while for while, but it depends on having recent GnuTLS libraries installed.
https://bugs.winehq.org/show_bug.cgi?id=45768
--- Comment #10 from Gijs Vermeulen gijsvrm@gmail.com --- Can you retest with wine-5.5?
This might have been influenced by https://source.winehq.org/git/wine.git/commit/741f76fc2c9203105ca7f87c0014bb... (Hans, are you able to confirm?)
https://bugs.winehq.org/show_bug.cgi?id=45768
--- Comment #11 from Hans Leidekker hans@meelstraat.net --- (In reply to Gijs Vermeulen from comment #10)
Can you retest with wine-5.5?
This might have been influenced by https://source.winehq.org/git/wine.git/commit/ 741f76fc2c9203105ca7f87c0014bb5a9da4d936 (Hans, are you able to confirm?)
That patch is about signing with ALG_ID_ECDSA_P256 and ALG_ID_ECDSA_P384. This bug is about verifying with these algorithms, which was supported before that patch, but it depends on recent GnuTLS.
https://bugs.winehq.org/show_bug.cgi?id=45768
Hans Leidekker hans@meelstraat.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID Status|REOPENED |RESOLVED
--- Comment #12 from Hans Leidekker hans@meelstraat.net --- Assuming old GnuTLS (steam runtime).
https://bugs.winehq.org/show_bug.cgi?id=45768
--- Comment #13 from Austin English austinenglish@gmail.com --- Closing.
https://bugs.winehq.org/show_bug.cgi?id=45768
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #14 from Austin English austinenglish@gmail.com --- Closing.