Open source Google product breaks other open source Google product when used with third open source Google product
-
To encounter this bug, you need:
a go.net/websocket server
running on go's net/http server
wrapped by go's crypto/tls
viewed by Google Chrome.Remove or change any of those things and you no longer have the bug.
The bug is: when Google Chrome opens a secure websocket connection, it closes it before starting the handshake.
but only if it's a go server.
-
TRWTF is their logo. I mean, nobody is taking Go seriously but that logo does not help.
-
So even Google is smart enough not to talk to a Go server...
-
@Ben L. said:
when Google Chrome opens a secure websocket connection, it closes it before starting the handshake.
but only if it's a go server.HELLO SERVER I NEED A SECU--- A GO SERVER? *CLICK*
-
It's a race!
-
@dhromed said:
@Ben L. said:
when Google Chrome opens a secure websocket connection, it closes it before starting the handshake.
but only if it's a go server.HELLO SERVER I NEED A SECU--- A GO SERVER? CLICK
HELLO SERVER I NEED A SECU-- A GO SERVER? WELL WHY DON'T YOU GO FUCK YOURSELF?
-
-
-
-
@dhromed said:
@Ben L. said:
I love it, but they're gophers, not gerbils.
Fine, changed it.
Go-go gadget gophers!
-
I'm considering putting some of our beloved forum member avatrs on the gopher's faces.
Also, variabe speed, i.e. some implementation of the concept of "fitness" or "stamina".
And someting special that happens when one gopher wins.
-
Needs more HTML5.
-
Why is Go trying to use ECDSA with RSA certificates? Obviously that doesn't stand a snowball's chance in hell of working...
-
@TwelveBaud said:
Why is Go
trying to use ECDSA with RSA certificatesreimplementing all the crypto algorithms/protocols? Obviously thatdoesn't stand a snowball's chance in hell of workingis going to be rife with subtle bugs and security holes...
FTFY
-
@joe.edwards said:
@TwelveBaud said:
You're spot on there. Security code is genuinely hard, largely because it tends to fail in ways that are very hard to detect and diagnose. Sane people try to avoid writing security code, and even most insane people try to minimize.Why is Go
FTFYtrying to use ECDSA with RSA certificatesreimplementing all the crypto algorithms/protocols? Obviously thatdoesn't stand a snowball's chance in hell of workingis going to be rife with subtle bugs and security holes...
-
But what do you want them to do? Include C code in their libraries? Everybody knows that's impossible!
-
@dhromed said:
I'm considering putting some of our beloved forum member avatrs on the gopher's faces.
Also, variabe speed, i.e. some implementation of the concept of "fitness" or "stamina".
And someting special that happens when one gopher wins.
[code]if ( (_rightpos > trackLength / 2) && !gophers[i].secondwind )[/code]
That makes me disproportionately amused.
-
@mikeTheLiar said:
@dhromed said:
I'm considering putting some of our beloved forum member avatrs on the gopher's faces.
Also, variabe speed, i.e. some implementation of the concept of "fitness" or "stamina".
And someting special that happens when one gopher wins.
<font face="Lucida Console" size="2">if ( (_rightpos > trackLength / 2) && !gophers[i].secondwind )</font>
That makes me disproportionately amused.
After reaching the midpoint, the 6th and final gopher began to move backwards at a rate of one pixel per minute.
-
@Ben L. said:
the 6th and final gopher began to move backwards
Sometimes I tweak a thing and forget to test and odd things happen. I had a few shooting backwards once.
This only happens on hobby projects.
*cough*
obviously
@Ben L. said:
at a rate of one pixel per minute.
Per minute? Wow. @Ben L. said:
I did have a chuckle.
good
-
@mikeTheLiar said:
That makes me disproportionately amused.
I should probably not optimize game code for a living.