Moving the keys to a file on the installed system sounds like a goodidea. I would suggest compile-time and run-time options for this, as
well as checking paths in the user's home directory.
Paweł, could you explain the motivations and intentions of the
Chromium and Google API teams here?
The goal is to require keys for access, so that potential abuse of these APIs can be more
easily detected and addressed.
Debian cannot comply with the Google API terms, will Google therefore
revoke the API keys that we are using and block Debian users from
using Google APIs?
On behalf of Google Chrome Team I am providing you with:
Official permission to include Google API keys in your packages and to distribute these
packages. The remainder of the Terms of Service for each API applies, but at this time you
are not bound by the requirement to only access the APIs for personal and development use,
and Additional quota for each API in an effort to adequately support your users.