Concerns with chromedriver hosting

1 view
Skip to first unread message

Daniel

unread,
1:53 PM (2 hours ago) 1:53 PM
to ChromeDriver Users
I have concerns with opening up my servers to access storage.googleapis.com. This is where chromedriver is hosted now as it has moved away from googlechromelabs.github.io. There are other complications that make allowing server access to   storage.googleapis.com problematic. I think it is fair to say that is   storage.googleapis.com can be abused or used for harm. Allowing only traffic to a full URL which is scoped down to chromedriver download pages also has problems as it requires initial communication to the point of the path being sent (only a few packets but cannot be blocked). Allowing only a few packets to anywhere (to then analyze the URL) does open up other issues.

Is there a trusted/controlled mirror available by chance?

How are others approaching this issue if they have concerns?

I do not find decryption of all traffic and signature analysis sufficient (So easy to create new signatures). I would also like to avoid  WAF style initial communication before decisions are made if possible.

Ideally I would like a known trustworthy tightly controlled FQDN without a fast flux style CDN behind it. Does this possibly exist? Please enlighten me.
Reply all
Reply to author
Forward
0 new messages