Copiado do fórum de ajuda do Chrome :
For Chrome 6 stable, renegotiation checks are disabled if you have a proxy configured. We are working with several SSL MITM proxy vendors in the mean time to address this. One of the most common, Blue Coat, have (or will very soon) release an update to their products which includes the needed security fix. Applying this is by far the best solution.
If your proxy is rewriting the TCP streams themselves then there is no way to distinguish this from an attack. In this case, adding --allow-ssl-mitm-proxies to the command line will disable this check and all other additional security measures that we have roadmapped in this area.
Você precisa ativar essa opção iniciando o Chrome no Terminal e o comando deve ler open /Applications/Google Chrome.app/Contents/MacOS/Google Chrome --allow-ssl-mitm-proxies
(supondo que você tenha o Chrome na pasta / Applications .