https://bugs.winehq.org/show_bug.cgi?id=50264
Bug ID: 50264 Summary: Application unable to communicate with server with tls Product: Wine Version: 6.0-rc1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: l12436@yahoo.com.tw Distribution: ---
Created attachment 68802 --> https://bugs.winehq.org/attachment.cgi?id=68802 console log with error
Console will show "GnuTLS error: Key usage violation in certificate has been detected." and tool will failed.
https://bugs.winehq.org/show_bug.cgi?id=50264
Olivier F. R. Dierick o.dierick@piezo-forte.be changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |o.dierick@piezo-forte.be
--- Comment #1 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- Hello,
What is the name of the application?
Please attach a 'WINEDEBUG=+wininet,+secur32,+crypt,+winsock' debug trace. Instructions to get a debug log can be found there: https://wiki.winehq.org/FAQ#get_log
Regards.
https://bugs.winehq.org/show_bug.cgi?id=50264
--- Comment #2 from TOM l12436@yahoo.com.tw --- Created attachment 68812 --> https://bugs.winehq.org/attachment.cgi?id=68812 here is the message
https://bugs.winehq.org/show_bug.cgi?id=50264
--- Comment #3 from TOM l12436@yahoo.com.tw --- it is an activation from FallDoll game
https://bugs.winehq.org/show_bug.cgi?id=50264
--- Comment #4 from TOM l12436@yahoo.com.tw --- sorry for the typo It's FallenDoll
https://bugs.winehq.org/show_bug.cgi?id=50264
Olivier F. R. Dierick o.dierick@piezo-forte.be changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|-unknown |crypt32 Summary|Application unable to |FallenDoll unable to |communicate with server |communicate with server |with tls |with tls
https://bugs.winehq.org/show_bug.cgi?id=50264
Hans Leidekker hans@meelstraat.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|crypt32 |-unknown
--- Comment #5 from Hans Leidekker hans@meelstraat.net --- 023c:trace:secur32:schan_gnutls_log <1> Peer's certificate does not allow digital signatures. Key usage violation detected.
The server certificate is invalid for other reasons too:
$ gnutls-cli -p 5535 163.172.39.69 Processed 126 CA certificate(s). Resolving '163.172.39.69:5535'... Connecting to '163.172.39.69:5535'... - Certificate type: X.509 - Got a certificate list of 1 certificates. - Certificate[0] info: - subject `CN=sd-96092', issuer `CN=sd-96092', serial 0x2614da94ca240a9b441e23edf289b4f6, RSA key 2048 bits, signed using RSA-SHA1 (broken!), activated `2019-11-07 13:01:52 UTC', expires `2020-11-07 00:00:00 UTC', pin-sha256="092jw+FdrUY1mE/f/PHYRfM/jIDXn6ofd0Ls0WTe7QA=" Public Key ID: sha1:9e0099b02b59c9220207e882af9e84096ba02488 sha256:d3dda3c3e15dad4635984fdffcf1d845f33f8c80d79faa1f7742ecd164deed00 Public Key PIN: pin-sha256:092jw+FdrUY1mE/f/PHYRfM/jIDXn6ofd0Ls0WTe7QA=
- Status: The certificate is NOT trusted. The certificate issuer is unknown. The certificate chain uses expired certificate. The name in the certificate does not match the expected. *** PKI verification of server certificate failed... *** Fatal error: Error in the certificate.
Does this work on Windows?
https://bugs.winehq.org/show_bug.cgi?id=50264
--- Comment #6 from TOM l12436@yahoo.com.tw --- (In reply to Hans Leidekker from comment #5)
023c:trace:secur32:schan_gnutls_log <1> Peer's certificate does not allow digital signatures. Key usage violation detected.
The server certificate is invalid for other reasons too:
$ gnutls-cli -p 5535 163.172.39.69 Processed 126 CA certificate(s). Resolving '163.172.39.69:5535'... Connecting to '163.172.39.69:5535'...
- Certificate type: X.509
- Got a certificate list of 1 certificates.
- Certificate[0] info:
- subject `CN=sd-96092', issuer `CN=sd-96092', serial
0x2614da94ca240a9b441e23edf289b4f6, RSA key 2048 bits, signed using RSA-SHA1 (broken!), activated `2019-11-07 13:01:52 UTC', expires `2020-11-07 00:00:00 UTC', pin-sha256="092jw+FdrUY1mE/f/PHYRfM/jIDXn6ofd0Ls0WTe7QA=" Public Key ID: sha1:9e0099b02b59c9220207e882af9e84096ba02488 sha256:d3dda3c3e15dad4635984fdffcf1d845f33f8c80d79faa1f7742ecd164deed00 Public Key PIN: pin-sha256:092jw+FdrUY1mE/f/PHYRfM/jIDXn6ofd0Ls0WTe7QA=
- Status: The certificate is NOT trusted. The certificate issuer is unknown.
The certificate chain uses expired certificate. The name in the certificate does not match the expected. *** PKI verification of server certificate failed... *** Fatal error: Error in the certificate.
Does this work on Windows?
yes, I also curious it will work or not, but it actually work on windows 7 64bit. App did not show tls error like wine
The certificate is actually invalid ?
https://bugs.winehq.org/show_bug.cgi?id=50264
--- Comment #7 from Hans Leidekker hans@meelstraat.net --- (In reply to TOM from comment #6)
(In reply to Hans Leidekker from comment #5)
Does this work on Windows?
yes, I also curious it will work or not, but it actually work on windows 7 64bit. App did not show tls error like wine
The certificate is actually invalid ?
Yes. Can you provide steps to reproduce?
https://bugs.winehq.org/show_bug.cgi?id=50264
--- Comment #8 from TOM l12436@yahoo.com.tw --- (In reply to Hans Leidekker from comment #7)
(In reply to TOM from comment #6)
(In reply to Hans Leidekker from comment #5)
Does this work on Windows?
yes, I also curious it will work or not, but it actually work on windows 7 64bit. App did not show tls error like wine
The certificate is actually invalid ?
Yes. Can you provide steps to reproduce?
you mean the program? that is belong to another author's product, I do not know I could send it or not. I just use its Application.
https://bugs.winehq.org/show_bug.cgi?id=50264
--- Comment #9 from TOM l12436@yahoo.com.tw --- This is its website. https://www.projecthelius.com/index.html#/index
https://bugs.winehq.org/show_bug.cgi?id=50264
--- Comment #10 from TOM l12436@yahoo.com.tw --- Created attachment 68948 --> https://bugs.winehq.org/attachment.cgi?id=68948 a log from procmon.exe may help