In an extremely contrived scenario where the security boundary involves running untrusted Go code.
Whoa! Actual memory safety exploit for #golang using data race to break safety of interface object (races are the only escape hatch for memory/type safety in Go).
You are testing your Go code with the race detector (-race), right?https://twitter.com/NetanelBenSimon/status/1192077412579860480 …
-
-
-
People did that all the time with JavaScript and PHP and Java, all of which are "safe" (for non malicious programmers) then people invented applets and PHP hosting etc. Given that the Go's playground already runs untrusted code, it's certainly plausible others will as well.
- Još 2 druga odgovora
Novi razgovor -
-
-
Technically also "unsafe" is an escape hatch. I know it's obvious, but just a reminder to whoever is reading this.
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.