Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Google TV Pairing Protocol -- SSL Handshake Error with Go (golang)

Tags:

go

google-tv

I'm writing a Go package for the Google TV Pairing Protocol. But I seem to be hitting a problem with the TLS handshake.

sock, err := tls.Dial("tcp", "10.8.0.1:9552", &tls.Config{InsecureSkipVerify: true})

That line gives me a handshake error. The exact error message is: remote error: handshake failure. If I try the same host/port via curl, it gives curl: (35) error:14094410:SSL routines:SSL3_READ_BYTES:sslv3 alert handshake failure as well.

Any ideas? Is the Google TV expecting a client cert maybe? I haven't seen any references to the need for a client cert anywhere.

If anyone wants to help figure it out, here's the code: https://github.com/dustywilson/go-polo

The README file has the easy code to check it out. You will have to know the IP address for your Google TV box since this doesn't use mDNS. If you (someone, anyone) run this and you get different results, let me know.

I've already gone through the Google TV Remote code at google-tv-remote. A more useful one is google-tv-pairing-protocol which is the equivalent Java/Android project to what I'm doing. Of course I've already poured over that code. I think it's a problem either with Go itself (unlikely), a problem with the Go TLS package not knowing how to read the Google TV's certificate (I know it was a problem a year ago), or a problem with my code (typically would be most likely, but I'm just not seeing it).

By the way, I'm testing this on a Logitech Revue and it has a self-signed SSL certificate. It's not rooted or modified in any way.

My resulting code will be open source, of course. Thanks for the assistance.

like image 456
Emmaly Avatar asked Nov 04 '22 10:11

Emmaly


1 Answers

Client certs are generated by the Java remote client at runtime, and stored for future use. Check out the code at:

http://code.google.com/p/google-tv-remote/source/browse/src/com/google/android/apps/tvremote/KeyStoreManager.java

You might be running into an invalid cert. According to the code, you need a specific CN.

/* Returns the name that should be used in a new certificate. * The format is: "CN=anymote/PRODUCT/DEVICE/MODEL/unique identifier" */

like image 80
saxman Avatar answered Nov 09 '22 02:11

saxman