Hi Rene,
Le 24/02/2016 23:41, Rene Engelhard a écrit :
On Wed, Feb 24, 2016 at 07:12:17PM +0100, Stéphane Aulery wrote:
This bug has been fixed in Ubuntu.
Maybe the patch is transferable?
No. (Well, maybe.)
Looking at what they did:
# Set up Google API keys, see
http://www.chromium.org/developers/how-tos/api-keys .
# Note: these are for Ubuntu use ONLY. For your own distribution,
# please get your own set of keys.
# Permission to add API keys, from Paweł Hajdan, To chad.mil...@canonical.com
# msgid: caadnaofsfoch68nm1sgpctrxqmspykqguputsf7sgrsrxih...@mail.gmail.com
# reused from chromium-browser 48.0.2564.82-0ubuntu1.1222
GOOGLEAPI_APIKEY_UBUNTU := <snipped, but is publically visible in debian/rules
>
GOOGLEAPI_CLIENTID_UBUNTU := <snipped, but is publically visible in
debian/rules >
GOOGLEAPI_CLIENTSECRET_UBUNTU := <snipped, but is publically visible in
debian/rules >
CONFIGURE_FLAGS += --with-gdrive-client-id=$(GOOGLEAPI_CLIENTID_UBUNTU)
--with-gdrive-client-secret=$(GOOGLEAPI_CLIENTSECRET_UBUNTU)
so no, we can't take that. Of course, we could get ours via the same way
- but then we also could post it somewhere on a public site, it's then no
secret anymore. It's as if we would put passwords publically visible.
Or I misunderstand the concept of a "secret" here, but I doubt that.
That said, I see that chromium-browser in Debian also has a debian/apikeys...
Ok, forget that. No way to spread this kind of thing!
Thanks Rene.
Regards,
--
Stéphane Aulery
