Re: SwCpoker.eu | No Banking, Only Bitcoin | Bitcoin Poker 2.0 LIVE NOW!

Quote from: nomnomnom on August 21, 2015, 11:31:40 AM

Quote from: NLNico on August 20, 2015, 06:38:12 AM

Anyone managed to run SWC on Wine yet?

It opens for me, "just" doesn't connect (SSL problem or something?) I am getting errors that seem pretty common according to Google. But I don't have the knowledge nor time to try to fix them.

Same here, then I noticed the server it connects to has an expired certificate, maybe
windows just connects despite this and wine is more strict? I emailed them about it some time ago,
but seems they haven't found the time to replace it with a correct cert.

Quote

% openssl s_client -connect 95.xxx.xx.xxx:989
CONNECTED(00000003)
depth=3 C = SE, O = AddTrust AB, OU = AddTrust External TTP Network, CN = AddTrust External CA Root
verify return:1
depth=2 C = GB, ST = Greater Manchester, L = Salford, O = COMODO CA Limited, CN = COMODO RSA Certification Authority
verify return:1
depth=1 C = GB, ST = Greater Manchester, L = Salford, O = COMODO CA Limited, CN = COMODO RSA Domain Validation Secure Server CA
verify return:1
depth=0 OU = Domain Control Validated, OU = Free SSL, CN = www.swcpoker.eu
verify error:num=10:certificate has expired
notAfter=Jun 1 23:59:59 2015 GMT
verify return:1
depth=0 OU = Domain Control Validated, OU = Free SSL, CN = www.swcpoker.eu
notAfter=Jun 1 23:59:59 2015 GMT
verify return:1

I actually get a different message :p Seems like I can connect but do get error/warning:

Code:

Verify return code: 19 (self signed certificate in certificate chain)

Quote from: tspacepilot on August 22, 2015, 08:52:59 PM

Quote from: NLNico on August 20, 2015, 06:38:12 AM

Maybe post the actual errors. I quit using wine a few years ago because it was too much of a hassle. However, if you post the errors here, you might have some success solving them as getting seals to work on wine would be really useful for a large number of people, I think.

There are actually a lot of "fixme" errros, but I *think* these are the only relevant ones (because the client loads fine, just no connection):

Code:

p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: wrong ELF class: ELFCLASS64

...

reading ssl handshake packet
reading ssl handshake packet: read 1460 bytes
ProcessSSLHandshakeReceive (1460 )
reading ssl handshake packet
reading ssl handshake packet: read 674 bytes
ProcessSSLHandshakeReceive (674 )
reading ssl handshake packet
reading ssl handshake packet: read 0 bytes
error reading ssl handshake packet

...

GnuTLS error: An unexpected TLS packet was received.
err:secur32:schan_DecryptMessage Returning 80090304
DecryptMessage: Error
ReadSSL: problem
fixme:secur32:schannel_get_kx_algid unknown algorithm 0

The p11-kit error was different, but I did some extra install (gnome-keyring, libp11-kit-gnome-keyring, etc) and copy file for that already. Seems I still have the wrong "gnome-keyring-pkcs11.so" file though. But most Google results of that error dates from 2011/2012 and generally they say it should be fixed in latest wine versions Sad

(I am running 2-day old wine 1.7.50) Also I think -that- is not the crucial error, but something with the actual SSL messages. If I debug secur32 I obviously get much more details, but not a clear point where it failed... just "trace:secur32:schan_InitializeSecurityContextW Expected at least .. bytes, but buffer only contains .. bytes."

Would be awesome if we can get it fixed. IMHO I think SWC could even considering putting a bounty for it up. If someone makes an easy clear guide to get it working on Linux/Wine, it must have some value for SWC too. (or clear explanation why SWC needs to make some changes, idk)