https://bugs.winehq.org/show_bug.cgi?id=50471
Bug ID: 50471 Summary: Kindle for PC 1.16.0 can't connect Product: Wine Version: 6.0-rc6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: ameniutaeba1978@gmail.com Distribution: ---
Created attachment 69103 --> https://bugs.winehq.org/attachment.cgi?id=69103 Kindle error
I installed Kindle for PC ver 1.16.0 from winetricks on my Manjaro Linux. When I start Kindle, Kindle says "Unable to connect. Please check your network setting and proxy configuration. Network settings can be found under Tools > Options > Network"
I tested on wine-5.22 and wine-6.0-rc6 on Manajaro Linux but same result. I also tested wine-5.0 on Feren OS but the problem didn't occurred.
So the problem is on wine 5.22 or later, or on Manjaro Linux. I've also posted the problem on Manjaro Forum but no good reply. https://forum.manjaro.org/t/is-there-anyone-who-use-amazon-kindle-for-pc-via...
I attach the STDOUT and STDERR.
Thanks in advance.
https://bugs.winehq.org/show_bug.cgi?id=50471
--- Comment #1 from ameniutaeba1978@gmail.com --- I've also tested wine-6.0-rc6 on Ubuntu 20.10, but the same network message have displayed.
https://bugs.winehq.org/show_bug.cgi?id=50471
Alan aversa@email.arizona.edu changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |aversa@email.arizona.edu
--- Comment #2 from Alan aversa@email.arizona.edu --- Created attachment 69128 --> https://bugs.winehq.org/attachment.cgi?id=69128 Kindle.exe stdout
https://bugs.winehq.org/show_bug.cgi?id=50471
--- Comment #3 from Alan aversa@email.arizona.edu --- Same Kindle 1.16.0 network connectivity issue for me with wine-5.22, wine-6.0-rc5, and wine-6.0-rc6 on Slackware (-current), 32-bit WINEPREFIX. Stdout attached.
I also get network connectivity issues with Adobe Digital Editions, too, which doesn't even run without segfaulting anymore now that I upgraded from wine-6.0-rc5 to wine-6.0-rc6.
https://bugs.winehq.org/show_bug.cgi?id=50471
--- Comment #4 from Alan aversa@email.arizona.edu --- (In reply to ameniutaeba1978 from comment #0)
So the problem is on wine 5.22 or later
I get the same issue with Wine 5.21 (using an old, backed-up prefix). In this case it does prompt me to upgrade to Kindle 1.30, but when I try, the download hangs (as if network connectivity gets cut off at a certain point). I'm wondering if it's really the Amazon server that's causing issues.
https://bugs.winehq.org/show_bug.cgi?id=50471
--- Comment #5 from Alan aversa@email.arizona.edu --- I confirm this issue on wine-6.0.
https://bugs.winehq.org/show_bug.cgi?id=50471
--- Comment #6 from Alan aversa@email.arizona.edu --- using a local http proxy (squid), I see that Kindle.exe does connect to the Amazon.com server:
www.amazon.com:443 - HIER_DIRECT/184.24.124.204 www.amazon.com:443 - HIER_DIRECT/23.211.66.236 www.amazon.com:443 - HIER_DIRECT/96.17.76.102
https://bugs.winehq.org/show_bug.cgi?id=50471
--- Comment #7 from ameniutaeba1978@gmail.com --- I've upgraded wine to 6.0 and setup proxy(Squid), but still have the problem.
https://bugs.winehq.org/show_bug.cgi?id=50471
Marcelo Santana marcelo@msantana.eng.br changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |marcelo@msantana.eng.br
https://bugs.winehq.org/show_bug.cgi?id=50471
--- Comment #8 from Marcelo Santana marcelo@msantana.eng.br --- I've been having the same issue with Kindle for PC 1.17.44183 in Debian bullseye (testing), either using the Debian repository version 5.0.3, or from the WineHQ repository (versions 5.5, 6.0, and 6.1).
I tried to use it with the "winhttp" and "wininet" installed via winetricks but I still got the same issue.
https://bugs.winehq.org/show_bug.cgi?id=50471
Infidelus winehq20@melsplace.co.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |winehq20@melsplace.co.uk
https://bugs.winehq.org/show_bug.cgi?id=50471
--- Comment #9 from ameniutaeba1978@gmail.com --- Now I can connect kindle for PC to amazon with Kindle version 1.30.0. What I did are following. 1. uninstall old kindle with command "wine64 uninstaller" 2. mkdir -p ${WINEPREFIX:-$HOME/.wine}/drive_c/users/$USER/AppData/Local/Amazon/Kindle 3. install Kindle for PC version 1.30.0.
https://bugs.winehq.org/show_bug.cgi?id=50471
eris23 jdkatz23@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jdkatz23@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=50471
Alojzij Blatnik lojze.blatnik@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |lojze.blatnik@gmail.com
--- Comment #10 from Alojzij Blatnik lojze.blatnik@gmail.com --- My friend figured out that when installer doesn't work, you can do the following:
mkdir -p /home/user/.wine/drive_c/users/user/AppData/Local/Amazon/Kindle cd /home/user/.wine/drive_c/users/user/AppData/Local/Amazon/Kindle 7z -y x /tmp/KindleForPC-installer-1.31.60170.exe wine Kindle.exe
It also works with KindleForPC-installer-1.17.44170.exe
I tried to make it work in Docker container, but apparently there's more than that (there's connection error for version 1.17 and unstable browser when I tried to login in version 1.31).
Br
https://bugs.winehq.org/show_bug.cgi?id=50471
--- Comment #11 from Infidelus winehq20@melsplace.co.uk --- There's a thread on the Linux Mint forums that addresses this issue as well which mentions the issues is actually related to an untrusted Symantec certificate:
https://forums.linuxmint.com/viewtopic.php?f=47&t=342186&uid=248652
https://bugs.winehq.org/show_bug.cgi?id=50471
gunny gunny33@byom.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |gunny33@byom.de
--- Comment #12 from gunny gunny33@byom.de --- kindle4pc 1.16 / 1.17 in Linux
You can run it in Knoppix and Debian stable (buster), in Debian Testing (bullseye) you get "unable to connect".
There is an commented out certificate in /etc/ca-certificates.conf: !mozilla/VeriSign_Class_3_Public_Primary_Certification_Authority_-_G5.crt
You can leave this alone and fix it for wine/mono access only with creating
/var/certmgr/web/user_trusted/b204d74a.0
with content:
-----BEGIN CERTIFICATE----- MIIE0zCCA7ugAwIBAgIQGNrRniZ96LtKIVjNzGs7SjANBgkqhkiG9w0BAQUFADCB yjELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQL ExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTowOAYDVQQLEzEoYykgMjAwNiBWZXJp U2lnbiwgSW5jLiAtIEZvciBhdXRob3JpemVkIHVzZSBvbmx5MUUwQwYDVQQDEzxW ZXJpU2lnbiBDbGFzcyAzIFB1YmxpYyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0 aG9yaXR5IC0gRzUwHhcNMDYxMTA4MDAwMDAwWhcNMzYwNzE2MjM1OTU5WjCByjEL MAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZW ZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTowOAYDVQQLEzEoYykgMjAwNiBWZXJpU2ln biwgSW5jLiAtIEZvciBhdXRob3JpemVkIHVzZSBvbmx5MUUwQwYDVQQDEzxWZXJp U2lnbiBDbGFzcyAzIFB1YmxpYyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9y aXR5IC0gRzUwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCvJAgIKXo1 nmAMqudLO07cfLw8RRy7K+D+KQL5VwijZIUVJ/XxrcgxiV0i6CqqpkKzj/i5Vbex t0uz/o9+B1fs70PbZmIVYc9gDaTY3vjgw2IIPVQT60nKWVSFJuUrjxuf6/WhkcIz SdhDY2pSS9KP6HBRTdGJaXvHcPaz3BJ023tdS1bTlr8Vd6Gw9KIl8q8ckmcY5fQG BO+QueQA5N06tRn/Arr0PO7gi+s3i+z016zy9vA9r911kTMZHRxAy3QkGSGT2RT+ rCpSx4/VBEnkjWNHiDxpg8v+R70rfk/Fla4OndTRQ8Bnc+MUCH7lP59zuDMKz10/ NIeWiu5T6CUVAgMBAAGjgbIwga8wDwYDVR0TAQH/BAUwAwEB/zAOBgNVHQ8BAf8E BAMCAQYwbQYIKwYBBQUHAQwEYTBfoV2gWzBZMFcwVRYJaW1hZ2UvZ2lmMCEwHzAH BgUrDgMCGgQUj+XTGoasjY5rw8+AatRIGCx7GS4wJRYjaHR0cDovL2xvZ28udmVy aXNpZ24uY29tL3ZzbG9nby5naWYwHQYDVR0OBBYEFH/TZafC3ey78DAJ80M5+gKv MzEzMA0GCSqGSIb3DQEBBQUAA4IBAQCTJEowX2LP2BqYLz3q3JktvXf2pXkiOOzE p6B4Eq1iDkVwZMXnl2YtmAl+X6/WzChl8gGqCBpH3vn5fJJaCGkgDdk+bW48DW7Y 5gaRQBi5+MHt39tBquCWIMnNZBU4gcmU7qKEKQsTb47bDN0lAtukixlE0kF6BWlK WE9gyn6CagsCqiUXObXbf+eEZSqVir2G3l6BFoMtEMze/aiCKm0oHw0LxOXnGiYZ 4fQRbxC1lfznQgUy286dUV4otp6F01vvpX1FQHKOtw5rDgb7MzVIcbidJ4vEZV8N hnacRHr2lVz2XTIIM6RUthg/aFzyQkqFOFSDX9HoLPKsEdao7WNq -----END CERTIFICATE-----
https://bugs.winehq.org/show_bug.cgi?id=50471
najjah winehq@najjah.33mail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |winehq@najjah.33mail.com
--- Comment #13 from najjah winehq@najjah.33mail.com --- @gunny can you share how you found the certificate path and a valid certificate?
I wanna do the same for v1.17. Moreover, knowing that will be very useful in the future.
https://bugs.winehq.org/show_bug.cgi?id=50471
Alban Browaeys prahal@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |prahal@yahoo.com
--- Comment #14 from Alban Browaeys prahal@yahoo.com --- I got it working with a slightly different fix: I copied https://android.googlesource.com/platform/system/ca-certificates/+/938033cd7... ie " -----BEGIN CERTIFICATE----- MIIE0zCCA7ugAwIBAgIQGNrRniZ96LtKIVjNzGs7SjANBgkqhkiG9w0BAQUFADCB yjELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQL ExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTowOAYDVQQLEzEoYykgMjAwNiBWZXJp U2lnbiwgSW5jLiAtIEZvciBhdXRob3JpemVkIHVzZSBvbmx5MUUwQwYDVQQDEzxW ZXJpU2lnbiBDbGFzcyAzIFB1YmxpYyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0 aG9yaXR5IC0gRzUwHhcNMDYxMTA4MDAwMDAwWhcNMzYwNzE2MjM1OTU5WjCByjEL MAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZW ZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTowOAYDVQQLEzEoYykgMjAwNiBWZXJpU2ln biwgSW5jLiAtIEZvciBhdXRob3JpemVkIHVzZSBvbmx5MUUwQwYDVQQDEzxWZXJp U2lnbiBDbGFzcyAzIFB1YmxpYyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9y aXR5IC0gRzUwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCvJAgIKXo1 nmAMqudLO07cfLw8RRy7K+D+KQL5VwijZIUVJ/XxrcgxiV0i6CqqpkKzj/i5Vbex t0uz/o9+B1fs70PbZmIVYc9gDaTY3vjgw2IIPVQT60nKWVSFJuUrjxuf6/WhkcIz SdhDY2pSS9KP6HBRTdGJaXvHcPaz3BJ023tdS1bTlr8Vd6Gw9KIl8q8ckmcY5fQG BO+QueQA5N06tRn/Arr0PO7gi+s3i+z016zy9vA9r911kTMZHRxAy3QkGSGT2RT+ rCpSx4/VBEnkjWNHiDxpg8v+R70rfk/Fla4OndTRQ8Bnc+MUCH7lP59zuDMKz10/ NIeWiu5T6CUVAgMBAAGjgbIwga8wDwYDVR0TAQH/BAUwAwEB/zAOBgNVHQ8BAf8E BAMCAQYwbQYIKwYBBQUHAQwEYTBfoV2gWzBZMFcwVRYJaW1hZ2UvZ2lmMCEwHzAH BgUrDgMCGgQUj+XTGoasjY5rw8+AatRIGCx7GS4wJRYjaHR0cDovL2xvZ28udmVy aXNpZ24uY29tL3ZzbG9nby5naWYwHQYDVR0OBBYEFH/TZafC3ey78DAJ80M5+gKv MzEzMA0GCSqGSIb3DQEBBQUAA4IBAQCTJEowX2LP2BqYLz3q3JktvXf2pXkiOOzE p6B4Eq1iDkVwZMXnl2YtmAl+X6/WzChl8gGqCBpH3vn5fJJaCGkgDdk+bW48DW7Y 5gaRQBi5+MHt39tBquCWIMnNZBU4gcmU7qKEKQsTb47bDN0lAtukixlE0kF6BWlK WE9gyn6CagsCqiUXObXbf+eEZSqVir2G3l6BFoMtEMze/aiCKm0oHw0LxOXnGiYZ 4fQRbxC1lfznQgUy286dUV4otp6F01vvpX1FQHKOtw5rDgb7MzVIcbidJ4vEZV8N hnacRHr2lVz2XTIIM6RUthg/aFzyQkqFOFSDX9HoLPKsEdao7WNq -----END CERTIFICATE----- Certificate: Data: Version: 3 (0x2) Serial Number: 18:da:d1:9e:26:7d:e8:bb:4a:21:58:cd:cc:6b:3b:4a Signature Algorithm: sha1WithRSAEncryption Issuer: C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=(c) 2006 VeriSign, Inc. - For authorized use only, CN=VeriSign Class 3 Public Primary Certification Authority - G5 Validity Not Before: Nov 8 00:00:00 2006 GMT Not After : Jul 16 23:59:59 2036 GMT Subject: C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=(c) 2006 VeriSign, Inc. - For authorized use only, CN=VeriSign Class 3 Public Primary Certification Authority - G5 Subject Public Key Info: Public Key Algorithm: rsaEncryption RSA Public-Key: (2048 bit) Modulus: 00:af:24:08:08:29:7a:35:9e:60:0c:aa:e7:4b:3b: 4e:dc:7c:bc:3c:45:1c:bb:2b:e0:fe:29:02:f9:57: 08:a3:64:85:15:27:f5:f1:ad:c8:31:89:5d:22:e8: 2a:aa:a6:42:b3:8f:f8:b9:55:b7:b1:b7:4b:b3:fe: 8f:7e:07:57:ec:ef:43:db:66:62:15:61:cf:60:0d: a4:d8:de:f8:e0:c3:62:08:3d:54:13:eb:49:ca:59: 54:85:26:e5:2b:8f:1b:9f:eb:f5:a1:91:c2:33:49: d8:43:63:6a:52:4b:d2:8f:e8:70:51:4d:d1:89:69: 7b:c7:70:f6:b3:dc:12:74:db:7b:5d:4b:56:d3:96: bf:15:77:a1:b0:f4:a2:25:f2:af:1c:92:67:18:e5: f4:06:04:ef:90:b9:e4:00:e4:dd:3a:b5:19:ff:02: ba:f4:3c:ee:e0:8b:eb:37:8b:ec:f4:d7:ac:f2:f6: f0:3d:af:dd:75:91:33:19:1d:1c:40:cb:74:24:19: 21:93:d9:14:fe:ac:2a:52:c7:8f:d5:04:49:e4:8d: 63:47:88:3c:69:83:cb:fe:47:bd:2b:7e:4f:c5:95: ae:0e:9d:d4:d1:43:c0:67:73:e3:14:08:7e:e5:3f: 9f:73:b8:33:0a:cf:5d:3f:34:87:96:8a:ee:53:e8: 25:15 Exponent: 65537 (0x10001) X509v3 extensions: X509v3 Basic Constraints: critical CA:TRUE X509v3 Key Usage: critical Certificate Sign, CRL Sign 1.3.6.1.5.5.7.1.12:
0_.].[0Y0W0U..image/gif0!0.0...+..............k...j.H.,{..0%.#http://logo.verisign.com/vslogo.gif X509v3 Subject Key Identifier: 7F:D3:65:A7:C2:DD:EC:BB:F0:30:09:F3:43:39:FA:02:AF:33:31:33 Signature Algorithm: sha1WithRSAEncryption 93:24:4a:30:5f:62:cf:d8:1a:98:2f:3d:ea:dc:99:2d:bd:77: f6:a5:79:22:38:ec:c4:a7:a0:78:12:ad:62:0e:45:70:64:c5: e7:97:66:2d:98:09:7e:5f:af:d6:cc:28:65:f2:01:aa:08:1a: 47:de:f9:f9:7c:92:5a:08:69:20:0d:d9:3e:6d:6e:3c:0d:6e: d8:e6:06:91:40:18:b9:f8:c1:ed:df:db:41:aa:e0:96:20:c9: cd:64:15:38:81:c9:94:ee:a2:84:29:0b:13:6f:8e:db:0c:dd: 25:02:db:a4:8b:19:44:d2:41:7a:05:69:4a:58:4f:60:ca:7e: 82:6a:0b:02:aa:25:17:39:b5:db:7f:e7:84:65:2a:95:8a:bd: 86:de:5e:81:16:83:2d:10:cc:de:fd:a8:82:2a:6d:28:1f:0d: 0b:c4:e5:e7:1a:26:19:e1:f4:11:6f:10:b5:95:fc:e7:42:05: 32:db:ce:9d:51:5e:28:b6:9e:85:d3:5b:ef:a5:7d:45:40:72: 8e:b7:0e:6b:0e:06:fb:33:35:48:71:b8:9d:27:8b:c4:65:5f: 0d:86:76:9c:44:7a:f6:95:5c:f6:5d:32:08:33:a4:54:b6:18: 3f:68:5c:f2:42:4a:85:38:54:83:5f:d1:e8:2c:f2:ac:11:d6: a8:ed:63:6a SHA1 Fingerprint=4E:B6:D5:78:49:9B:1C:CF:5F:58:1E:AD:56:BE:3D:9B:67:44:A5:E5 "
to /var/certmgr/web/user_trusted//facacbc6.0 (which is the file Amazon Kindle ws looking after in crossover wine file debug traces ie "+file,+ntdll,+tid" channels.
Now it works with Amazon Kindle "Windows 7" crossover install but not PlayOnLinux "Windows 200" one. Per PlaOnLinux had (or still is I have not checked) installed the amazon_kindle bottle as "Windows 2000".
As the PlayOnLinux "+file,+ntdll,+tid" debug traces showed in "Windows 2000" mode no certs path is looked after. I do not know how to fix it as is so I switched my PlayOnLinux amazon kindle setup to "Windows 7" and the issue also vanished from the Amazon Kindle PlayOnLinux bottle.
NB: per https://www.pcworld.com/article/418765/google-to-revoke-trust-in-a-symantec-... this certificate is a security hazard so currently best is to limit it to wine (seems /var/certmgr is). Maybe there is a mean to setup a store specific to a bottle instead of all wine prefixes wide. Might be with mono certmgr.
Update: certmgr with wine-mono seems to do nothing. I opened a cmd.com prompt inside the bottle, then pressed "y" on the prompt to install as CA "VeriSign Class 3 Public Primary Certification Authority - G5" certificate: " c:>c:\windows\mono\mono-2.0\lib\mono\4.5\certmgr -ssl https://www.amazon.com Mono Certificate Manager - version 6.13.0.0 Manage X.509 certificates and CRL from stores. Copyright 2002, 2003 Motus Technologies. Copyright 2004-2008 Novell. BSD license d.
X.509 Certificate v3 Issued from: C=US, O="VeriSign, Inc.", OU=VeriSign Trust Network, OU="(c) 200 6 VeriSign, Inc. - For authorized use only", CN=VeriSign Class 3 Public Primary Certification Authority - G5 Issued to: C=US, O=DigiCert Inc, OU=www.digicert.com, CN=DigiCert Global Ro ot G2 Valid from: 11/6/2017 12:00:00 AM Valid until: 11/5/2022 11:59:59 PM *** WARNING: Certificate signature is INVALID *** Import this certificate into the CA store ?y "
but then the certificate is not added: " Z:\usr\share\playonlinux\python>c:\windows\mono\mono-2.0\lib\mono\4.5\certmgr -l ist -c -m CA Mono Certificate Manager - version 6.13.0.0 Manage X.509 certificates and CRL from stores. Copyright 2002, 2003 Motus Technologies. Copyright 2004-2008 Novell. BSD license d.
Self-signed X.509 v3 Certificate Serial Number: 1B114ACBF3260D8700 Issuer Name: C=US, S=Some-State, O=Wine, CN=Invalid dummy certificate Subject Name: C=US, S=Some-State, O=Wine, CN=Invalid dummy certificate Valid From: 3/13/2016 2:13:31 AM Valid Until: 3/12/2016 2:13:31 AM Unique Hash: 9D2EBDA266A2D56BBFFBE93085648ABA39B590A57053D4B92CA6B53E161E40C 258A63072B07E4D23CCFC58889EDCC81FEC463233C8DA6772B8B25DFAF46789CC "
same when downloading the certificate and adding it: from host: curl https://android.googlesource.com/platform/system/ca-certificates/+/d473643ce... | base64 --decode > facacbc6.cer then in the bottle cmd: " Z:\usr\share\playonlinux\python>c:\windows\mono\mono-2.0\lib\mono\4.5\certmgr -a dd -c -m CA z:\home\prahal\Projects\WIP\totem-click-mouse\b\facacbc6.cer Mono Certificate Manager - version 6.13.0.0 Manage X.509 certificates and CRL from stores. Copyright 2002, 2003 Motus Technologies. Copyright 2004-2008 Novell. BSD license d.
Z:\usr\share\playonlinux\python>c:\windows\mono\mono-2.0\lib\mono\4.5\certmgr -l ist -c -m CA Mono Certificate Manager - version 6.13.0.0 Manage X.509 certificates and CRL from stores. Copyright 2002, 2003 Motus Technologies. Copyright 2004-2008 Novell. BSD license d.
Self-signed X.509 v3 Certificate Serial Number: 1B114ACBF3260D8700 Issuer Name: C=US, S=Some-State, O=Wine, CN=Invalid dummy certificate Subject Name: C=US, S=Some-State, O=Wine, CN=Invalid dummy certificate Valid From: 3/13/2016 2:13:31 AM Valid Until: 3/12/2016 2:13:31 AM Unique Hash: 9D2EBDA266A2D56BBFFBE93085648ABA39B590A57053D4B92CA6B53E161E40C 258A63072B07E4D23CCFC58889EDCC81FEC463233C8DA6772B8B25DFAF46789CC "
So it looks like the wine-mono in the bottle certificate store is just a placeholder.
https://bugs.winehq.org/show_bug.cgi?id=50471
--- Comment #15 from Alban Browaeys prahal@yahoo.com --- NB: my comment was tested on Amazon Kindle 1.17.
https://bugs.winehq.org/show_bug.cgi?id=50471
promeneur epistemepromeneur@free.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |epistemepromeneur@free.fr
--- Comment #16 from promeneur epistemepromeneur@free.fr --- Hello
I got the same connection problem.
I have used K4PC 1.17 without any problem since 2015
Suddenly, some days ago, refreshing the book list fails.
I unregistered my kindle for pc.
I tried to register my kindle for pc then I got messages saying the connection is not possible, check your network settings, or I got a blank registering screen.
Finally, after 3 days fighting, many thanks to you, I got the solution.
openSUSE Tumbleweed wine 5.0 kindle 1.17.44183
the procedure :
create the file b204d74a.0 with the certificate supplied by gunny
As administrator
put b204d74a.0 file in /usr/share/pki/trust/anchors/
run the command to add the certificate
update-ca-certificates
then the command to check the certificate is well added in the OS
trust list
the last certificate in the list is certificate b204d74a.0
pkcs11:id=%7F%D3%65%A7%C2%DD%EC%BB%F0%30%09%F3%43%39%FA%02%AF%33%31%33;type=cert type: certificate label: VeriSign Class 3 Public Primary Certification Authority - G5 trust: anchor category: authority
-
WineHQ Bugzilla