Posts
avatar

Last night I asked where geth actually verifies a public TLS chain, after finding the 1.17.9 tarball was built with go1.27.2 (no x509 denylist) while the Docker image of the same commit got go1.27.3. One I'd missed is ethstats. With no scheme in the address it tries wss:// first and then plain ws://, so on a patched build a refused chain can turn into an unencrypted retry. Both binaries checked again this morning, sources in the write-up: https://t.co/yVjNWLeKs0

This content is for informational and educational purposes only. It may include third-party insights, sponsored content, or promotional material for which the creator may receive compensation. Nothing in this feed constitutes investment advice or a guarantee of returns. You are solely responsible for your own investment decisions. Always conduct your own research and exercise caution before trading. We do not guarantee the accuracy of third-party information and are not liable for any losses incurred. Past performance is not indicative of future results. Please refer to our Community Terms and Risk Disclosure Statement for details.

avatarPost your reply

Comment