Issue 1647: Suggestions attempted for SSL sites http://code.google.com/p/chromium/issues/detail?id=1647
Comment #13 by den.molib: > And yes, https://<hostname>/ alone is already "leaked" by making a TCP connection to > the host, so we're not really exposing any data with that alone. It is only 'leaked' to the local DNS server and the routers in the path. Given an issue like the recent DNS vulnerability, the suggestion service can be an excelent entry point to gather information about which hosts to target next. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-bugs" group. To post to this group, send email to chromium-bugs@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-bugs?hl=en -~----------~----~----~----~------~----~------~--~---
