Hello, maybe this is related to Them changing the Terms of use wrt privacy and surfing behavior. https://mobile.twitter.com/phlsa/status/754337623964053504 Best regards, Thomas
So the implication then is that this was broken on Google's end rather than some issue with the crux build? Not sure why they wouldn't just harvest my info on crux just as easily as on other platforms. Is anyone running into this on non-crux builds of chromium? On Tue, Jul 19, 2016, 10:31 PM Thomas Penteker <tek@serverop.de> wrote:
Hello,
maybe this is related to Them changing the Terms of use wrt privacy and surfing behavior.
https://mobile.twitter.com/phlsa/status/754337623964053504
Best regards, Thomas
Actually, the chrome 'sync services' aren't available because the Pkgfile in opt/chromium doesn't build with api keys. You can generate/build with these keys using the following instructions[1]. I believe there's also an option to provide the keys at runtime. That should fix your problems with syncing. Here's my Pkgfile[2] for chromium. It's heavily based on the arch PKGBUILD, but uses my own api keys and enables some other things widevine and flash. BTW, the readme of opt/chromium also has warnings about the lack of features due to Google API access in the NOTES section. 1 http://www.chromium.org/developers/how-tos/api-keys 2 https://github.com/maraku/crux-ports/tree/master/chromium On Wed, Jul 20, 2016 at 05:47:18AM +0000, Alex Matviychuk wrote:
So the implication then is that this was broken on Google's end rather than some issue with the crux build?
Not sure why they wouldn't just harvest my info on crux just as easily as on other platforms. Is anyone running into this on non-crux builds of chromium?
On Tue, Jul 19, 2016, 10:31 PM Thomas Penteker <tek@serverop.de> wrote:
Hello,
maybe this is related to Them changing the Terms of use wrt privacy and surfing behavior.
https://mobile.twitter.com/phlsa/status/754337623964053504
Best regards, Thomas
_______________________________________________ CRUX mailing list CRUX@lists.crux.nu https://lists.crux.nu/mailman/listinfo/crux
Hi, On 21/07/16 06:57, manu wrote:
Actually, the chrome 'sync services' aren't available because the Pkgfile in opt/chromium doesn't build with api keys. You can generate/build with these keys using the following instructions[1]. I believe there's also an option to provide the keys at runtime. That should fix your problems with syncing.
[...]
As I note in the README, for versions greather than 23.x.x.x they restricted or removed support for unkeyed requests, so unless you have set up your API keys some of the functionality of Chromium (e.g. “Sign into Chromium …”) may stop working altogether
On Wed, Jul 20, 2016 at 05:47:18AM +0000, Alex Matviychuk wrote:
So the implication then is that this was broken on Google's end rather than some issue with the crux build?
Not sure why they wouldn't just harvest my info on crux just as easily as on other platforms. Is anyone running into this on non-crux builds of chromium?
I never believed it necessary to hardcode API keys in the port since CRUX is not a binary distribution and this can be done without problems in runtime by environment variables. The easiest way is to create your own API keys following the notes[1] in the README and add them for example to your ~/.bashrc $ cat >> ~/.bashrc << __EOF__ GOOGLE_API_KEY=your_api_key GOOGLE_DEFAULT_CLIENT_ID=your_client_id GOOGLE_DEFAULT_CLIENT_SECRET=your_client_secret __EOF__ In any case, today I will update the port again. ATM I'm building Chromium 52.0.2743.82 which includes 48 security fixes. Regards,
I followed the API tutorial and created my keys. Sync is working for me now with the latest build by passing my API info at runtime as noted in the README. Another question I have now is why aren't we building native client into chromium? If some folks don't want it, is there a way to package it separately? Thanks, Alex On Tue, Jul 26, 2016 at 3:08 AM Jose Vicente Beneyto <sepen@crux-arm.nu> wrote:
Hi,
On 21/07/16 06:57, manu wrote:
Actually, the chrome 'sync services' aren't available because the Pkgfile in opt/chromium doesn't build with api keys. You can generate/build with these keys using the following instructions[1]. I believe there's also an option to provide the keys at runtime. That should fix your problems with syncing.
[...]
As I note in the README, for versions greather than 23.x.x.x they restricted or removed support for unkeyed requests, so unless you have set up your API keys some of the functionality of Chromium (e.g. “Sign into Chromium …”) may stop working altogether
On Wed, Jul 20, 2016 at 05:47:18AM +0000, Alex Matviychuk wrote:
So the implication then is that this was broken on Google's end rather than some issue with the crux build?
Not sure why they wouldn't just harvest my info on crux just as easily as on other platforms. Is anyone running into this on non-crux builds of chromium?
I never believed it necessary to hardcode API keys in the port since CRUX is not a binary distribution and this can be done without problems in runtime by environment variables.
The easiest way is to create your own API keys following the notes[1] in the README and add them for example to your ~/.bashrc
$ cat >> ~/.bashrc << __EOF__ GOOGLE_API_KEY=your_api_key GOOGLE_DEFAULT_CLIENT_ID=your_client_id GOOGLE_DEFAULT_CLIENT_SECRET=your_client_secret __EOF__
In any case, today I will update the port again. ATM I'm building Chromium 52.0.2743.82 which includes 48 security fixes.
Regards,
_______________________________________________ CRUX mailing list CRUX@lists.crux.nu https://lists.crux.nu/mailman/listinfo/crux
participants (4)
-
Alex Matviychuk -
Jose Vicente Beneyto -
manu -
Thomas Penteker