IT guy just pop into the office to make a test. They deployed Chrome on a network not connected to the Internet to access some webapp and want to find why it is so low to start.

I said, it is most likely trying to update itself but get firewalled by a badly written rule that drop the packet instead of rejecting it, so it waits and timeout.

I suggested Chromium as possible solution.

The guy replied : "Chromium is open source, too much open, every one can read the code and hack it, very unsecure."

I died inside.

Add Comment