image search by URL: you could let the client download the image and then upload it to the search engine, but especially with asymmetric down/up link speeds on customer internet connections, that might be much slower
so an internal service would be considered public if it's reachable over https (which should ideally be the case) and the service has a valid cert for some name in public DNS that points at it? overloading TLS cert meaning with "I trust the owners of these domains"?
-
-
how do you pick the trusted public-DNS resolver you need for this?
-
We operate such a service today. Idea is we resolve these request's host *only* via that path, and cert must line up with resolved IP. Can make it configurable as a (new) group policy (and disableable) for the paranoid. I'm sure there's a hole in this...



- 9 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
