[gentoo-user] OT: Noteworthy change in the way Chrome logs in

[gentoo-user] OT: Noteworthy change in the way Chrome logs in

[Adam Carter]

[-- Attachment #1: Type: text/plain, Size: 567 bytes --]

From:
https://blog.cryptographyengineering.com/2018/09/23/why-im-leaving-chrome/

"A few weeks ago Google shipped an update to Chrome that fundamentally
changes the sign-in experience. From now on, every time you log into a
Google property (for example, Gmail), Chrome will automatically *sign the
browser into your Google account* for you. It’ll do this without asking, or
even explicitly notifying you. (However, and this is important: Google
developers claim this will not actually start synchronizing your data to
Google — yet. See further below.)"

[-- Attachment #2: Type: text/html, Size: 805 bytes --]

Re: [gentoo-user] OT: Noteworthy change in the way Chrome logs in

[Andrew Udvare]

> On 2018-09-24, at 02:47, Adam Carter <adamcarter3@gmail.com> wrote:
> 
> From: https://blog.cryptographyengineering.com/2018/09/23/why-im-leaving-chrome/
> 
> "A few weeks ago Google shipped an update to Chrome that fundamentally changes the sign-in experience. From now on, every time you log into a Google property (for example, Gmail), Chrome will automatically sign the browser into your Google account for you. It’ll do this without asking, or even explicitly notifying you. (However, and this is important: Google developers claim this will not actually start synchronizing your data to Google — yet. See further below.)"

I use the Google features, with many Google accounts including ones I have no control of like work accounts. I have many Chrome profiles to avoid the confusion that Google is trying to solve with this feature. I wish they would solve it in a better way like allowing multiple user accounts open in one session complete with multi-account Gmail and others. I can understand that other users may not ever figure out to create separate profiles.

I can understand not wanting this feature but unfortunately Google does not believe in options when it comes to Chrome. They are always removing or obscuring them. They seem to have a feeling that if there are options (more than one good default setting), something is wrong.

-- 
Andrew Udvare

Re: [gentoo-user] OT: Noteworthy change in the way Chrome logs in

[Mick]

[-- Attachment #1: Type: text/plain, Size: 2019 bytes --]

On Monday, 24 September 2018 08:09:30 BST Andrew Udvare wrote:
> > On 2018-09-24, at 02:47, Adam Carter <adamcarter3@gmail.com> wrote:
> > 
> > From:
> > https://blog.cryptographyengineering.com/2018/09/23/why-im-leaving-chrome
> > /
> > 
> > "A few weeks ago Google shipped an update to Chrome that fundamentally
> > changes the sign-in experience. From now on, every time you log into a
> > Google property (for example, Gmail), Chrome will automatically sign the
> > browser into your Google account for you. It’ll do this without asking,
> > or even explicitly notifying you. (However, and this is important: Google
> > developers claim this will not actually start synchronizing your data to
> > Google — yet. See further below.)"
> I use the Google features, with many Google accounts including ones I have
> no control of like work accounts. I have many Chrome profiles to avoid the
> confusion that Google is trying to solve with this feature. I wish they
> would solve it in a better way like allowing multiple user accounts open in
> one session complete with multi-account Gmail and others. I can understand
> that other users may not ever figure out to create separate profiles.
> 
> I can understand not wanting this feature but unfortunately Google does not
> believe in options when it comes to Chrome. They are always removing or
> obscuring them. They seem to have a feeling that if there are options (more
> than one good default setting), something is wrong.

Unless I understood this wrong, 'Google Chrome' will not be able to perform 
this (dis)service, unless you have enabled the "Offer to save passwords" 
feature AND|OR you use Chrome to sign in to an Alphabet related website.

If you value your privacy you can leave the "Offer to save passwords" setting 
disabled, or can use a profile where this is not enabled and can also avoid 
ever using Chrome to sign in to any of Alphabet's creations.

Is Chromium also affected by this?


-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: [gentoo-user] OT: Noteworthy change in the way Chrome logs in

[Andrew Udvare]

> On 2018-09-24, at 06:29, Mick <michaelkintzios@gmail.com> wrote:
> 
> 
> Unless I understood this wrong, 'Google Chrome' will not be able to perform 
> this (dis)service, unless you have enabled the "Offer to save passwords" 
> feature AND|OR you use Chrome to sign in to an Alphabet related website.

This is not necessarily true because AFAIK it works by taking the session generated from within Google's main sign on page and applying that session to the browser.

> 
> Is Chromium also affected by this?

Yes.

-- 
Andrew Udvare

Re: [gentoo-user] OT: Noteworthy change in the way Chrome logs in

[Mick]

[-- Attachment #1: Type: text/plain, Size: 929 bytes --]

On Monday, 24 September 2018 13:47:05 BST Andrew Udvare wrote:
> > On 2018-09-24, at 06:29, Mick <michaelkintzios@gmail.com> wrote:
> > 
> > 
> > Unless I understood this wrong, 'Google Chrome' will not be able to
> > perform
> > this (dis)service, unless you have enabled the "Offer to save passwords"
> > feature AND|OR you use Chrome to sign in to an Alphabet related website.
> 
> This is not necessarily true because AFAIK it works by taking the session
> generated from within Google's main sign on page and applying that session
> to the browser.
> > Is Chromium also affected by this?
> 
> Yes.

:-(

This is worse than I expected.  OK, therefore never signing into Google's 
systems with Chromium is the only way to stop this invasion of privacy.  
Thankfully, we still have Firefox.  ;-)

I assume closing the browser terminates the session and login, both in the 
browser and in the Google websites.

-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[gentoo-user] Re: OT: Noteworthy change in the way Chrome logs in

[Nikos Chantziaras]

On 24/09/2018 10:09, Andrew Udvare wrote:
> I can understand not wanting this feature but unfortunately Google
> does not believe in options when it comes to Chrome. They are always
> removing or obscuring them. They seem to have a feeling that if there
> are options (more than one good default setting), something is
> wrong.

There is an option for this, actually. Go to:

   chrome://flags/#account-consistency

and set it to "Disabled."

Re: [gentoo-user] Re: OT: Noteworthy change in the way Chrome logs in

[Andrew Udvare]

> On Sep 24, 2018, at 10:20, Nikos Chantziaras <realnc@gmail.com> wrote:
> 
> There is an option for this, actually. Go to:
> 
>  chrome://flags/#account-consistency
> 
> and set it to "Disabled."
> 

Flags come and go and they are not intended for use by regular users. Based on the fact that the flag can be enabled automatically via random field testing, I assume the flag will disappear soon in the future, and the feature will be on. This is the price of using Chrome unfortunately.

Andrew

[gentoo-user] Re: OT: Noteworthy change in the way Chrome logs in

[Nikos Chantziaras]

On 25/09/2018 00:09, Andrew Udvare wrote:
> 
> 
>> On Sep 24, 2018, at 10:20, Nikos Chantziaras <realnc@gmail.com> wrote:
>>
>> There is an option for this, actually. Go to:
>>
>>   chrome://flags/#account-consistency
>>
>> and set it to "Disabled."
>>
> 
> Flags come and go and they are not intended for use by regular users. Based on the fact that the flag can be enabled automatically via random field testing, I assume the flag will disappear soon in the future, and the feature will be on. This is the price of using Chrome unfortunately.

It's not like there's a shortage of browsers. For now, the flags works 
perfectly. If it stops working, well, let's just say I'm not married to 
Google.

Re: [gentoo-user] OT: Noteworthy change in the way Chrome logs in

[Walter Dnes]

On Mon, Sep 24, 2018 at 02:59:17PM +0100, Mick wrote

> This is worse than I expected.  OK, therefore never signing into Google's 
> systems with Chromium is the only way to stop this invasion of privacy.  
> Thankfully, we still have Firefox.  ;-)

Ahemm... https://dustri.org/b/mozilla-is-still-screwing-around-with-privacy-in-firefox.html

-- 
Walter Dnes <waltdnes@waltdnes.org>
I don't run "desktop environments"; I run useful applications

Re: [gentoo-user] OT: Noteworthy change in the way Chrome logs in

[Mick]

[-- Attachment #1: Type: text/plain, Size: 791 bytes --]

On Tuesday, 25 September 2018 03:11:38 BST Walter Dnes wrote:
> On Mon, Sep 24, 2018 at 02:59:17PM +0100, Mick wrote
> 
> > This is worse than I expected.  OK, therefore never signing into Google's
> > systems with Chromium is the only way to stop this invasion of privacy.
> > Thankfully, we still have Firefox.  ;-)
> 
> Ahemm...
> https://dustri.org/b/mozilla-is-still-screwing-around-with-privacy-in-firef
> ox.html

Yes, there is this leaking agent running in FF, but I have (almost) disabled 
telemetry.  The problem is this pesky entry which is shown as "locked" and 
therefore unable to be disabled in about:config

Preference Name            Status  Type     Value
=========================  ======  =======  =====
toolkit.telemetry.enabled  locked  boolean  true

-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: [gentoo-user] OT: Noteworthy change in the way Chrome logs in

[Dale]

Mick wrote:
> On Tuesday, 25 September 2018 03:11:38 BST Walter Dnes wrote:
>> On Mon, Sep 24, 2018 at 02:59:17PM +0100, Mick wrote
>>
>>> This is worse than I expected.  OK, therefore never signing into Google's
>>> systems with Chromium is the only way to stop this invasion of privacy.
>>> Thankfully, we still have Firefox.  ;-)
>> Ahemm...
>> https://dustri.org/b/mozilla-is-still-screwing-around-with-privacy-in-firef
>> ox.html
> Yes, there is this leaking agent running in FF, but I have (almost) disabled 
> telemetry.  The problem is this pesky entry which is shown as "locked" and 
> therefore unable to be disabled in about:config
>
> Preference Name            Status  Type     Value
> =========================  ======  =======  =====
> toolkit.telemetry.enabled  locked  boolean  true
>


Just for giggles, I looked at my config and it shows a default status
and is set to false.  Maybe it is a difference in version or could it be
a USE flag makes a difference or something else???  I'm on Firefox
52.9.0.  Maybe you are using the latest version.  I'm stuck here due to
some add ons not ready for the newer versions. 

Dale

:-)  :-) 

Re: [gentoo-user] OT: Noteworthy change in the way Chrome logs in

[Mick]

[-- Attachment #1: Type: text/plain, Size: 1591 bytes --]

On Tuesday, 25 September 2018 12:02:48 BST Dale wrote:
> Mick wrote:
> > On Tuesday, 25 September 2018 03:11:38 BST Walter Dnes wrote:
> >> On Mon, Sep 24, 2018 at 02:59:17PM +0100, Mick wrote
> >> 
> >>> This is worse than I expected.  OK, therefore never signing into
> >>> Google's
> >>> systems with Chromium is the only way to stop this invasion of privacy.
> >>> Thankfully, we still have Firefox.  ;-)
> >> 
> >> Ahemm...
> >> https://dustri.org/b/mozilla-is-still-screwing-around-with-privacy-in-fir
> >> ef
> >> ox.html
> > 
> > Yes, there is this leaking agent running in FF, but I have (almost)
> > disabled telemetry.  The problem is this pesky entry which is shown as
> > "locked" and therefore unable to be disabled in about:config
> > 
> > Preference Name            Status  Type     Value
> > =========================  ======  =======  =====
> > toolkit.telemetry.enabled  locked  boolean  true
> 
> Just for giggles, I looked at my config and it shows a default status
> and is set to false.  Maybe it is a difference in version or could it be
> a USE flag makes a difference or something else???  I'm on Firefox
> 52.9.0.  Maybe you are using the latest version.  I'm stuck here due to
> some add ons not ready for the newer versions. 
> 
> Dale
> 
> :-)  :-) 

I'm on 60.2.0 and although other telemetry entries are modifiable, the one I 
mention above is shown as locked.  Apparently this is locked to 'true' for 
pre-release builds and 'false' for release builds:

https://medium.com/georg-fritzsche/data-preference-changes-in-firefox-58-2d5df9c428b5

-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: [gentoo-user] OT: Noteworthy change in the way Chrome logs in

[Dale]

Mick wrote:
> On Tuesday, 25 September 2018 12:02:48 BST Dale wrote:
>> Mick wrote:
>>> On Tuesday, 25 September 2018 03:11:38 BST Walter Dnes wrote:
>>>> On Mon, Sep 24, 2018 at 02:59:17PM +0100, Mick wrote
>>>>
>>>>> This is worse than I expected.  OK, therefore never signing into
>>>>> Google's
>>>>> systems with Chromium is the only way to stop this invasion of privacy.
>>>>> Thankfully, we still have Firefox.  ;-)
>>>> Ahemm...
>>>> https://dustri.org/b/mozilla-is-still-screwing-around-with-privacy-in-fir
>>>> ef
>>>> ox.html
>>> Yes, there is this leaking agent running in FF, but I have (almost)
>>> disabled telemetry.  The problem is this pesky entry which is shown as
>>> "locked" and therefore unable to be disabled in about:config
>>>
>>> Preference Name            Status  Type     Value
>>> =========================  ======  =======  =====
>>> toolkit.telemetry.enabled  locked  boolean  true
>> Just for giggles, I looked at my config and it shows a default status
>> and is set to false.  Maybe it is a difference in version or could it be
>> a USE flag makes a difference or something else???  I'm on Firefox
>> 52.9.0.  Maybe you are using the latest version.  I'm stuck here due to
>> some add ons not ready for the newer versions. 
>>
>> Dale
>>
>> :-)  :-) 
> I'm on 60.2.0 and although other telemetry entries are modifiable, the one I 
> mention above is shown as locked.  Apparently this is locked to 'true' for 
> pre-release builds and 'false' for release builds:
>
> https://medium.com/georg-fritzsche/data-preference-changes-in-firefox-58-2d5df9c428b5
>


Ahhh.  I was hoping that info might lead to a solution to it but I guess
not.  Better to mention and it not matter than to not mention and it
would have helped.  lol  Heck, I get help from this list but I also try
to help when I can.  All we can do is try. 

We tried.  ;-)

Dale

:-)  :-) 

Re: [gentoo-user] OT: Noteworthy change in the way Chrome logs in

[Mick]

[-- Attachment #1: Type: text/plain, Size: 2198 bytes --]

On Tuesday, 25 September 2018 13:29:14 BST Dale wrote:
> Mick wrote:
> > On Tuesday, 25 September 2018 12:02:48 BST Dale wrote:
> >> Mick wrote:
> >>> On Tuesday, 25 September 2018 03:11:38 BST Walter Dnes wrote:
> >>>> On Mon, Sep 24, 2018 at 02:59:17PM +0100, Mick wrote
> >>>> 
> >>>>> This is worse than I expected.  OK, therefore never signing into
> >>>>> Google's
> >>>>> systems with Chromium is the only way to stop this invasion of
> >>>>> privacy.
> >>>>> Thankfully, we still have Firefox.  ;-)
> >>>> 
> >>>> Ahemm...
> >>>> https://dustri.org/b/mozilla-is-still-screwing-around-with-privacy-in-f
> >>>> ir
> >>>> ef
> >>>> ox.html
> >>> 
> >>> Yes, there is this leaking agent running in FF, but I have (almost)
> >>> disabled telemetry.  The problem is this pesky entry which is shown as
> >>> "locked" and therefore unable to be disabled in about:config
> >>> 
> >>> Preference Name            Status  Type     Value
> >>> =========================  ======  =======  =====
> >>> toolkit.telemetry.enabled  locked  boolean  true
> >> 
> >> Just for giggles, I looked at my config and it shows a default status
> >> and is set to false.  Maybe it is a difference in version or could it be
> >> a USE flag makes a difference or something else???  I'm on Firefox
> >> 52.9.0.  Maybe you are using the latest version.  I'm stuck here due to
> >> some add ons not ready for the newer versions.
> >> 
> >> Dale
> >> 
> >> :-)  :-)
> > 
> > I'm on 60.2.0 and although other telemetry entries are modifiable, the one
> > I mention above is shown as locked.  Apparently this is locked to 'true'
> > for pre-release builds and 'false' for release builds:
> > 
> > https://medium.com/georg-fritzsche/data-preference-changes-in-firefox-58-2
> > d5df9c428b5
> Ahhh.  I was hoping that info might lead to a solution to it but I guess
> not.  Better to mention and it not matter than to not mention and it
> would have helped.  lol  Heck, I get help from this list but I also try
> to help when I can.  All we can do is try. 
> 
> We tried.  ;-)
> 
> Dale
> 
> :-)  :-) 

Yes, this one is hardcoded and there doesn't seem to be a workaround, other 
than modifying the source code.
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]