metalshark Tracker

Re: When will Stadia Controllers support apostrophes in wireless PSKs?

metalshark — Sun, 29 Nov 2020 06:04:59 GMT

@tret think they’ve abandoned development/support here’s the latest I’ve heard from them.

Re: When will Stadia Controllers support apostrophes in wireless PSKs?

metalshark — Mon, 27 Jan 2020 09:30:34 GMT

It’s also worth remembering that this is all because of a bug Google tried to educate developers about 13 years ago (escaping and sanitising user input correctly): https://google-gruyere.appspot.com/part2#2__cross_site_scripting As a developer things like this (no escaping strings correctly) strikes as sloppiness and potential for vulnerabilities. There really is no excuse for this to have not been patched as soon as demonstrated.

Re: When will Stadia Controllers support apostrophes in wireless PSKs?

metalshark — Fri, 17 Jan 2020 04:58:47 GMT

Whichever mod thought that ignoring the bug was an acceptable solution, please consider actually getting the issue fixed instead.

Re: When will Stadia Controllers support apostrophes in wireless PSKs?

metalshark — Fri, 10 Jan 2020 08:29:35 GMT

No pixel phone (or Android to use the sigmaxpi app) and at home have a gaming PC.

Having special characters in your passphrase (as opposed to just alphanumerics) means that creating rainbow tables for your SSID takes a lot longer.

Hopefully Google actually take supporting the product seriously, not going to hold my breath though.

Re: When will Stadia Controllers support apostrophes in wireless PSKs?

metalshark — Sun, 05 Jan 2020 07:58:57 GMT

I’ve used the Feedback feature and communicated with them on Twitter (where they asked me to do all the fault finding for them!?!), as well as raising on the Discord. Due to the speed of creating an alphanumeric rainbow table for WPA2 PSKs, am not lowering my security so the controller can work when every other device in the house follows the spec. Plus this is a great indication of how much support to expect out of Google for Stadia going forward.

Here’s the conversation from over a month ago showing them asking me to do the fault finding for them. Now when asking for updates on them fixing it (remembering Chromebooks, Chromecasta, Nest devices, Android and Google Home devices do not have this issue) I just get two emojis. Someone writing and two hands together like a prayer.

When will Stadia Controllers support apostrophes in wireless PSKs?

metalshark — Thu, 02 Jan 2020 13:22:58 GMT

Worked with the Stadia Twitter account and determined/tested the reason the controller won’t connect to WiFi, but the Chromecast and every other device can is the use of apostrophes in the PSK. That was over 5 weeks ago. Still no update. Does anyone know when this will be remedied and how to pause your pro subscription as my Stadia account has been unused for 5 weeks as a result.

Re: Controller can't connect to Wi-Fi

metalshark — Sat, 07 Dec 2019 10:15:03 GMT

Google Stadia’s controller limited to alphanumeric only passwords apparently.
https://twitter.com/googlestadia/status/1202971650003615746?s=21

Re: Controller can't connect to Wi-Fi

metalshark — Tue, 03 Dec 2019 09:13:41 GMT

Worth noting that spaces in PSKs are also not an issue.

Re: Controller can't connect to Wi-Fi

metalshark — Tue, 03 Dec 2019 08:58:25 GMT

Support on Twitter are now responding. Did some diagnosis together. Length isn't an issue so: abcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyz1234567890 works. Full stops (periods) aren't an issue so: full.stop works. Apostrophes are an issue (at least with the iOS app) so: one'apostrophe does not work. It's reported - have asked for a public ticket number/bug report/road map, if I receive one I'll post it here. From doing all of these tests this morning, for me, multiple attempts make no difference neither does manually selecting WPA, WPA TKIP, WPA2, WPA2 TKIP or WPA3 (this is a WPA2/3 network, but was asked to try WPA TKIP by support).

Re: Controller can't connect to Wi-Fi

metalshark — Sun, 01 Dec 2019 06:16:19 GMT

Chromecast is fine works great. Controller though won’t connect to WiFi. Everything else is fine with WiFi. 63 character PSK with two apostrophes. Logs says the controller doesn’t authenticate properly (e.g. has a buggy supplicant). What we really want to know is how do we get actual support. Feedback on the app and this community site does not work and the Google Support line say to wait to hear for updates. How on earth do we get an update on a controller that won’t connect in the first place?

Re: Controller can't connect to Wi-Fi

metalshark — Thu, 21 Nov 2019 14:53:38 GMT

Same here.

Chromecast Ultra connects to WiFi fine, controller does not. Have WiFi 6 routers (AX, certified WiFi 6), logs show it authenticating with the wrong PSK. 100% using the right one. 63 character long PSK with two apostrophes in it. Where do I report the controller bug?