Broken: Firefox 48 + Private Tab + Kerberos SSO

2016-08-23 Thread Dusty Mabe
I can't seem to get firefox-48.0-5.fc24.x86_64 to work with kerberos single sign on in a private window. It works fine when using a non-private window. Any ideas on why this would have broken? Anyone else seeing this? Dusty -- devel mailing list devel@lists.fedoraproject.org https://lists.fedor

Re: Broken: Firefox 48 + Private Tab + Kerberos SSO

2016-08-23 Thread Robert Marcano
On 08/23/2016 04:44 PM, Dusty Mabe wrote: I can't seem to get firefox-48.0-5.fc24.x86_64 to work with kerberos single sign on in a private window. It works fine when using a non-private window. Any ideas on why this would have broken? Anyone else seeing this? I just noticed it after reading y

Re: Broken: Firefox 48 + Private Tab + Kerberos SSO

2016-08-23 Thread Stephen John Smoogen
On Aug 23, 2016 16:46, "Dusty Mabe" wrote: > > > I can't seem to get firefox-48.0-5.fc24.x86_64 to work with kerberos > single sign on in a private window. It works fine when using a > non-private window. > > Any ideas on why this would have broken? Anyone else seeing this? > I would guess it is

Re: Broken: Firefox 48 + Private Tab + Kerberos SSO

2016-08-23 Thread Alexander Bokovoy
On Tue, 23 Aug 2016, Dusty Mabe wrote: I can't seem to get firefox-48.0-5.fc24.x86_64 to work with kerberos single sign on in a private window. It works fine when using a non-private window. Any ideas on why this would have broken? Anyone else seeing this? We fixed an information leak that was

Re: Broken: Firefox 48 + Private Tab + Kerberos SSO

2016-08-23 Thread Alexander Bokovoy
On Tue, 23 Aug 2016, Stephen John Smoogen wrote: On Aug 23, 2016 16:46, "Dusty Mabe" wrote: I can't seem to get firefox-48.0-5.fc24.x86_64 to work with kerberos single sign on in a private window. It works fine when using a non-private window. Any ideas on why this would have broken? Anyone

Re: Broken: Firefox 48 + Private Tab + Kerberos SSO

2016-08-24 Thread Robert Marcano
On 08/23/2016 05:06 PM, Robert Marcano wrote: On 08/23/2016 04:44 PM, Dusty Mabe wrote: I can't seem to get firefox-48.0-5.fc24.x86_64 to work with kerberos single sign on in a private window. It works fine when using a non-private window. Any ideas on why this would have broken? Anyone else s

Re: Broken: Firefox 48 + Private Tab + Kerberos SSO

2016-08-24 Thread Robert Marcano
On 08/24/2016 12:29 AM, Alexander Bokovoy wrote: On Tue, 23 Aug 2016, Dusty Mabe wrote: I can't seem to get firefox-48.0-5.fc24.x86_64 to work with kerberos single sign on in a private window. It works fine when using a non-private window. Any ideas on why this would have broken? Anyone else s

Re: Broken: Firefox 48 + Private Tab + Kerberos SSO

2016-08-24 Thread Robert Marcano
On 08/24/2016 08:41 AM, Robert Marcano wrote: On 08/24/2016 12:29 AM, Alexander Bokovoy wrote: On Tue, 23 Aug 2016, Dusty Mabe wrote: I can't seem to get firefox-48.0-5.fc24.x86_64 to work with kerberos single sign on in a private window. It works fine when using a non-private window. Any ide

Re: Broken: Firefox 48 + Private Tab + Kerberos SSO

2016-08-24 Thread Jason L Tibbitts III
> "RM" == Robert Marcano writes: RM> I wonder if the default setting for RM> network.negotiate-auth.trusted-uris=https:// is or isn't a leak. My understanding (from talking to npmccallum and ab/abbra at flock) is that the security and disclosure issues with that have been fixed to the satisf

Re: Broken: Firefox 48 + Private Tab + Kerberos SSO

2016-08-24 Thread Alexander Bokovoy
On Wed, 24 Aug 2016, Robert Marcano wrote: On 08/24/2016 12:29 AM, Alexander Bokovoy wrote: On Tue, 23 Aug 2016, Dusty Mabe wrote: I can't seem to get firefox-48.0-5.fc24.x86_64 to work with kerberos single sign on in a private window. It works fine when using a non-private window. Any ideas

Re: Broken: Firefox 48 + Private Tab + Kerberos SSO

2016-08-24 Thread Robert Marcano
On 08/24/2016 10:43 AM, Alexander Bokovoy wrote: On Wed, 24 Aug 2016, Robert Marcano wrote: ... I wonder if the default setting for network.negotiate-auth.trusted-uris=https:// is or isn't a leak. No, it is not, at least not to the remote server you are trying to visit. Kerberos flow is alwa