3 ms·
Good to know. I knew that I needed to do it, but I'll be sure to add support for this prior to Go 1.2. (The TLS stack doesn't support renegotiation at all, so
by agl 13y ago
Good to know. I knew that I needed to do it, but I'll be sure to add support for this prior to Go 1.2.
(The TLS stack doesn't support renegotiation at all, so it's not vulnerable, but a client can't know that unless it echos the extension in question.)
- agwa 13y agoAh, you're using the Go TLS package? That makes sense ;-). As it turns out the latest version of Firefox still connects to servers which don't indicate secure renegotiation; the parent poster caused the problem by mucking around with the TLS settings in about:config.
- nitrogen 13y agoWell, it looks like he wrote the Go TLS package.