You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Windows 10.
Running v0.0.25
API setup for 2 accounts in the same house.
All of a sudden today it stopped making JSONs and even logging combat.
Funny thing is the proxy still allows playing and general internet connectivity, but nothing is logged and no JSONs are created.
Attempted troubleshooting by clearing appdata and upgrading to v0.0.26.
Power cycled. Checked firewall and antivirus.
Tried with disabled AV and firewall.
I have the exact same problem.
Tried changing port, disabling firewall, different devices, trying older versions but I'm still not getting the JSONs. But the proxy is working as I'm able to play the game normally :/.
sockjs? No, thats for websockets.
We will be investigating options, but there are no guaranteed solutions so don't keep your hopes up. There is one thing we can try and that's it. No ETA either.
Yeah. SWEX only works because it's unencrypted traffic. If they use https or ANY kind of encryption we're boned.
This is common to stop packet injection hacks.
But SWEX only LOOKS at the data. It doesn't manipulate it at all.
Unless SW embeds their own certificates in the app, it's at least theoretically possible to:
Create a "private" certificate authority (i.e. CA)
Add the certificate authority to your phone (trust the CA's public cert)
Create an SSL certificate for the SW domain using the CA
Configure the proxy to issue the "known" SSL certificate to the SW app on your phone, decrypt the traffic from your phone, and then re-encrypt traffic using the public SSL cert for SW
(I'm pretty sure corporations do something similar to allow for deep traffic inspection so we might have a community member with some experience doing this).
Unfortunately, trusting a CA cert on your phone creates a backdoor so the workflow needs to emphasize security. Specifically, you'd want/need EACH USER to control their own CA. For example, we could create a small app (maybe even IOS/Android) that:
creates the CA cert
trusts it on the phone and
Signs the public SSL key (generated by the proxy) for (only) the SW domain
EDIT: my SSL workflow was rusty. The Exporter would create a private/public key and the CA would sign the public key. Just a process tweak... doesn't affect the security model.
Each user would create their own CA and enter their own SSL certificate (for the SW domain) in the SW Exporter. Fortunately, this workflow also works for the SW Proxy website... with the added proviso that the website needs to know which user is connecting so it can present the correct SSL cert. You'd (probably) want/need separate sub-domains per-user (e.g. <user>.swproxy.com) to simplify this association.
Because the exporter doesn't have have access to the CA cert, it can't spoof other domain names. This is +1000 for SW Proxy website since, otherwise, it could spoof any domain name (including banks, etc.). Even if Xzandro had benign intentions, it would create a tempting target for a hacker.
No. Thats the issue. Im not even sure if this is an Android problem, problem with the lib or other things. Would be interesting to test this with iOS. Sadly I dont own one.
I started a PR to simplify code-level discussion. But you will need to test with IOS. Unless your android is <Nougat (or rooted), it won't work. Maybe Nox would let you put the CA cert in the right place at least for testing purposes.
Activity
donQ18 commentedon Aug 7, 2019
I have the exact same problem.
Tried changing port, disabling firewall, different devices, trying older versions but I'm still not getting the JSONs. But the proxy is working as I'm able to play the game normally :/.
comattose commentedon Aug 7, 2019
Same here. One second logging all my runes. I relogged and the exporter no longer creating the .json file.
pmsharp2 commentedon Aug 7, 2019
I noticed the same behavior starting today. Tested on both 0.0.23 and 0.0.26
HunBirdie commentedon Aug 7, 2019
Same here. Don't export the json file, nor the runs. Proxy is still working but the Exporter don't log anything.
Tested on 0.0.26 and 0.0.24.
Spkch commentedon Aug 7, 2019
Having the same problem. Tried on 3 different Wifis, it just opens, starts proxy and doesn't log anything after, no Jsons created. Using v0.0.26.
ErikAWSDev commentedon Aug 7, 2019
Having the same issue. The proxy aspect works fine as if I stop the app the game stops working.
Xzandro commentedon Aug 7, 2019
Summoners War is using https now. No idea if this is even fixable.
HunBirdie commentedon Aug 7, 2019
:-/
Zaringers commentedon Aug 7, 2019
Same problem.. So many players are using this tool, I don't think Com2us will make impossible to fix... I hope at least
QuatZo commentedon Aug 7, 2019
Maybe it'll work: https://github.com/sockjs
Spkch commentedon Aug 7, 2019
Well this is just terrible news :(
Xzandro commentedon Aug 7, 2019
sockjs? No, thats for websockets.
We will be investigating options, but there are no guaranteed solutions so don't keep your hopes up. There is one thing we can try and that's it. No ETA either.
Aregee33 commentedon Aug 7, 2019
So this doesn't work anymore? is that whats happened?
TheCloudCrafter commentedon Aug 7, 2019
Yeah. SWEX only works because it's unencrypted traffic. If they use https or ANY kind of encryption we're boned.
This is common to stop packet injection hacks.
But SWEX only LOOKS at the data. It doesn't manipulate it at all.
claytondaley commentedon Aug 7, 2019
Unless SW embeds their own certificates in the app, it's at least theoretically possible to:
(I'm pretty sure corporations do something similar to allow for deep traffic inspection so we might have a community member with some experience doing this).
Unfortunately, trusting a CA cert on your phone creates a backdoor so the workflow needs to emphasize security. Specifically, you'd want/need EACH USER to control their own CA. For example, we could create a small app (maybe even IOS/Android) that:
Each user would create their own CA and enter their own SSL certificate (for the SW domain) in the SW Exporter. Fortunately, this workflow also works for the SW Proxy website... with the added proviso that the website needs to know which user is connecting so it can present the correct SSL cert. You'd (probably) want/need separate sub-domains per-user (e.g.
<user>.swproxy.com) to simplify this association.Because the exporter doesn't have have access to the CA cert, it can't spoof other domain names. This is +1000 for SW Proxy website since, otherwise, it could spoof any domain name (including banks, etc.). Even if Xzandro had benign intentions, it would create a tempting target for a hacker.
14 remaining items
Xzandro commentedon Aug 8, 2019
As I said above. Code 22 error on login.
davidcl4196 commentedon Aug 8, 2019
Just for clarification, does the JSON capture happen before the code 22 error?
Xzandro commentedon Aug 8, 2019
No. Thats the issue. Im not even sure if this is an Android problem, problem with the lib or other things. Would be interesting to test this with iOS. Sadly I dont own one.
claytondaley commentedon Aug 8, 2019
I started a PR to simplify code-level discussion. But you will need to test with IOS. Unless your android is <Nougat (or rooted), it won't work. Maybe Nox would let you put the CA cert in the right place at least for testing purposes.
Xzandro commentedon Aug 8, 2019
Thats the thing. Nox runs on Android 5 so in theory it should work, which it doesn't.
claytondaley commentedon Aug 8, 2019
Did you see my note in the PR about the
listencommand?Xzandro commentedon Aug 8, 2019
Answered.
athena613b commentedon Aug 8, 2019
I have iOS if you need help testing.
swproxy commentedon Aug 9, 2019
Well I haven't seen code 22 error in my test
Capabilities to intercept HTTPS requests (#237)
Release 0.0.27 (#239)
Xzandro commentedon Aug 9, 2019
I released a first version. You can read more about this here: https://www.reddit.com/r/summonerswar/comments/cnwaq5/swex_0027_attempt_to_restore_export_functionality/
Lots of improvements to make still, but its something.
densaface commentedon Aug 9, 2019
Many thanks, works on memu3.5+android 4
Xzandro commentedon Aug 9, 2019
com2us reverted the https changes. Released v0.0.28 as a rerelease of 0.0.26. So I will close this for now.