4 ms·
I adore Go, but it seems to be impacted too: https://groups.google.com/g/golang-announce/c/dRtDK7WS78g https://groups.google.com/g/golang-announce/c/dRtDK7WS78g
by timdoug 4y ago
I adore Go, but it seems to be impacted too: https://groups.google.com/g/golang-announce/c/dRtDK7WS78g https://groups.google.com/g/golang-announce/c/dRtDK7WS78g
- woodruffw 4y agoThis is almost certainly a different bug. I don't believe Go's standard library uses OpenSSL.
- timdoug 4y agoYou’re right re: implementation —- I’m drawing a conclusion solely from the coordinated disclosure that it’s a similar crypto/TLS issue. If the Go issues were distinct I’d imagine they’d choose a different day to disclose/release?
- woodruffw 4y ago> If the Go issues were distinct I’d imagine they’d choose a different day to disclose/release? I think it's just a funny coincidence. That's going based on what I know about the OpenSSL one; I don't know anything about the Go one. We'll find out!
- komuW 4y agoit's unrelated; https://news.ycombinator.com/item?id=33382369 https://news.ycombinator.com/item?id=33382369
- deleted 4y ago[deleted]
- speedgoose 4y agoIndeed, it doesn’t sound like a coincidence.
- komuW 4y agoFilippo Valsorda(FiloSottile), who is the maintainer of Go's cryptography libraries said on Go's slack channel that the patch is unrelated. See screenshot of the slack conversation: https://paste.pics/f5622033ae711b36e0bbcda393a67866 https://paste.pics/f5622033ae711b36e0bbcda393a67866