Re: nytimes pages that fail in iceweasel [SOLVED]
On Mon, 22 Feb 2016 10:10:06 +1100 Andrew McGlashan wrote: > > > On 22/02/2016 2:02 AM, Adam Wilson wrote: > > On Sat, 20 Feb 2016 22:59:26 + Lisi Reisz > > wrote: > > And how is password-protection incompatible with free software > > principles anyway? > > It's not /really/ free if it needs me to login to access the > resources. > > A. > Hence rms' early anti-password campaign.
Re: nytimes pages that fail in iceweasel [SOLVED]
On 22/02/2016 2:02 AM, Adam Wilson wrote: > On Sat, 20 Feb 2016 22:59:26 + Lisi Reisz > wrote: > And how is password-protection incompatible with free software > principles anyway? It's not /really/ free if it needs me to login to access the resources. A.
Re: nytimes pages that fail in iceweasel
On Sun, 21 Feb 2016, Steve Kleene wrote: > On Sat, 20 Feb 2016 19:12:15 -0800, Patrick Bartek wrote: > > > What I'd like to know is how iceweasel broke on the OP's system in > > the first place. I did a standard install of the browser on my > > 64-bit Wheezy system years ago, installed Flash, etc., and it > > works. Maybe, it's because I don't use or have installed any > > desktop. Just use a window manager, Openbox. > > I'm the OP. I don't know when the feature got turned off, but I also > use just a windowing system (fvwm). I also wasn't using Tor. Just an isolated event then. No one else seems to have it. Guess we'll never really know the cause. At least, iceweasel is working correctly now. B
Re: nytimes pages that fail in iceweasel [SOLVED]
On Sat, 20 Feb 2016 22:59:26 + Lisi Reisz
wrote:
> On Saturday 20 February 2016 16:17:22 Andrew McGlashan wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA256
> >
> > Hi,
> >
> > On 21/02/2016 2:12 AM, Steve Kleene wrote:
> > > user_pref("dom.indexedDB.enabled", false);
> > >
> > > When I changed this to "true" in my original prefs.js, the web
> > > pages worked properly.
> > >
> > > The newly enabled function, IndexedDB, apparently has some
> > > security shortcomings:
> > >
> > > https://www.researchgate.net/publication/281066023_Some_Potential_Issu
> >
> > es_with_the_Security_of_HTML5_IndexedDB
> >
> > Please
> >
> > provide a link that is consistent with FOSS principles; no
> > login requirement.
>
> I didn't have to log in.
>
> Lisi
And how is password-protection incompatible with free software
principles anyway?
nytimes pages that fail in iceweasel
On Sat, 20 Feb 2016 19:12:15 -0800, Patrick Bartek wrote: > What I'd like to know is how iceweasel broke on the OP's system in the > first place. I did a standard install of the browser on my 64-bit Wheezy > system years ago, installed Flash, etc., and it works. Maybe, it's > because I don't use or have installed any desktop. Just use a window > manager, Openbox. I'm the OP. I don't know when the feature got turned off, but I also use just a windowing system (fvwm). I also wasn't using Tor.
Re: nytimes pages that fail in iceweasel [SOLVED]
On Sun, 21 Feb 2016, Andrew McGlashan wrote: > > On 21/02/2016 3:47 AM, Reco wrote: > > https://www.researchgate.net/profile/Stefan_Kimak/publication/281066023_Some_Potential_Issues_with_the_Security_of_HTML5_IndexedDB/links/55d3438208ae0b8f3ef92886.pdf?inViewer=0&pdfJsDownload=0&origin=publication_detail This displays perfectly both in Chrome and Iceweasel. No login required. > Okay, thanks, a reload of the page yeilded the /right/ result. What I'd like to know is how iceweasel broke on the OP's system in the first place. I did a standard install of the browser on my 64-bit Wheezy system years ago, installed Flash, etc., and it works. Maybe, it's because I don't use or have installed any desktop. Just use a window manager, Openbox. > Also using Tor I'm not. B
Re: nytimes pages that fail in iceweasel [SOLVED]
On Saturday 20 February 2016 16:17:22 Andrew McGlashan wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Hi,
>
> On 21/02/2016 2:12 AM, Steve Kleene wrote:
> > user_pref("dom.indexedDB.enabled", false);
> >
> > When I changed this to "true" in my original prefs.js, the web
> > pages worked properly.
> >
> > The newly enabled function, IndexedDB, apparently has some
> > security shortcomings:
> >
> > https://www.researchgate.net/publication/281066023_Some_Potential_Issu
>
> es_with_the_Security_of_HTML5_IndexedDB
>
> Please
>
> provide a link that is consistent with FOSS principles; no
> login requirement.
I didn't have to log in.
Lisi
>
> > The databases that various servers create are stored in the sqlite
> > files under my iceweasel profile. I may clear those out from time
> > to time.
> >
> > Thanks to everyone who responded.
>
> Thanks
> AndrewM
> -BEGIN PGP SIGNATURE-
>
> iF4EAREIAAYFAlbIkZEACgkQqBZry7fv4vunswD/X6OGwZV3b6rmr54jTVh/fdf1
> 0TFb+moN8EMNC31Rb4QBAL+ykW5QJFI4JDx8Ud9GZUeObMnfDPt8R7oGbCpg+AAW
> =nCnj
> -END PGP SIGNATURE-
Re: nytimes pages that fail in iceweasel [SOLVED]
On 21/02/2016 3:47 AM, Reco wrote: > https://www.researchgate.net/profile/Stefan_Kimak/publication/281066023_Some_Potential_Issues_with_the_Security_of_HTML5_IndexedDB/links/55d3438208ae0b8f3ef92886.pdf?inViewer=0&pdfJsDownload=0&origin=publication_detail Okay, thanks, a reload of the page yeilded the /right/ result. Also using Tor Cheers AndrewM
Re: nytimes pages that fail in iceweasel [SOLVED]
Hi.
On Sun, 21 Feb 2016 03:17:22 +1100
Andrew McGlashan wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Hi,
>
> On 21/02/2016 2:12 AM, Steve Kleene wrote:
> > user_pref("dom.indexedDB.enabled", false);
> >
> > When I changed this to "true" in my original prefs.js, the web
> > pages worked properly.
> >
> > The newly enabled function, IndexedDB, apparently has some
> > security shortcomings:
> >
> > https://www.researchgate.net/publication/281066023_Some_Potential_Issu
> es_with_the_Security_of_HTML5_IndexedDB
>
> Please
> >
> provide a link that is consistent with FOSS principles; no
> login requirement.
That link works for me without any authentication if I use Tor.
The link to PDF download with "full text" (whatever they mean by it) is:
https://www.researchgate.net/profile/Stefan_Kimak/publication/281066023_Some_Potential_Issues_with_the_Security_of_HTML5_IndexedDB/links/55d3438208ae0b8f3ef92886.pdf?inViewer=0&pdfJsDownload=0&origin=publication_detail
An interesting read btw. Thanks, Steve.
Reco
Re: nytimes pages that fail in iceweasel [SOLVED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
On 21/02/2016 2:12 AM, Steve Kleene wrote:
> user_pref("dom.indexedDB.enabled", false);
>
> When I changed this to "true" in my original prefs.js, the web
> pages worked properly.
>
> The newly enabled function, IndexedDB, apparently has some
> security shortcomings:
>
> https://www.researchgate.net/publication/281066023_Some_Potential_Issu
es_with_the_Security_of_HTML5_IndexedDB
Please
>
provide a link that is consistent with FOSS principles; no
login requirement.
> The databases that various servers create are stored in the sqlite
> files under my iceweasel profile. I may clear those out from time
> to time.
>
> Thanks to everyone who responded.
Thanks
AndrewM
-BEGIN PGP SIGNATURE-
iF4EAREIAAYFAlbIkZEACgkQqBZry7fv4vunswD/X6OGwZV3b6rmr54jTVh/fdf1
0TFb+moN8EMNC31Rb4QBAL+ykW5QJFI4JDx8Ud9GZUeObMnfDPt8R7oGbCpg+AAW
=nCnj
-END PGP SIGNATURE-
Re: nytimes pages that fail in iceweasel [SOLVED]
On Fri, 19 Feb 2016 21:13:26 -0500, I wrote:
>> A lot of sites on nytimes.com don't work correctly in my iceweasel, e.g.
>>
>> http://www.nytimes.com/interactive/2016/us/elections/fact-check.html#/factcheck-109
>>
>> If I click on any of the many "Read more" links, I get nothing. I don't
>> guess this is flash. Lots of flash sites work for me, and they ask if I want
>> to allow flash. The nytimes pages do not. Other examples:
>>
>> http://www.nytimes.com/interactive/2016/02/17/upshot/scalia-supreme-court-senate-nomination.html#g-detailed-responses
>> http://www.nytimes.com/interactive/2016/01/02/opinion/collins-our-new-year-quiz.html
>>
>> I am running iceweasel 38.6.1 under Wheezy. Any ideas what format these
>> pages
>> use or why they are failing?
On Sat, 20 Feb 2016 09:04:18 +0100, Sven Arvidsson replied:
> You could try starting Iceweasel with -P and create a new profile. If
> it works there, something is wrong in your normal profile.
I moved my ~/.mozilla directory away, called mozilla, and got a new, very
simple profile. Its prefs.js file was much shorter. By brute force, I
edited out lines that were only in my old prefs.js file until I found the
responsible line:
user_pref("dom.indexedDB.enabled", false);
When I changed this to "true" in my original prefs.js, the web pages worked
properly.
The newly enabled function, IndexedDB, apparently has some security
shortcomings:
https://www.researchgate.net/publication/281066023_Some_Potential_Issues_with_the_Security_of_HTML5_IndexedDB
The databases that various servers create are stored in the sqlite files
under my iceweasel profile. I may clear those out from time to time.
Thanks to everyone who responded.
Re: nytimes pages that fail in iceweasel
On Fri, 2016-02-19 at 21:13 -0500, Steve Kleene wrote: > A lot of sites on nytimes.com don't work correctly in my iceweasel, > e.g. > > http://www.nytimes.com/interactive/2016/us/elections/fact-check.html# > /factcheck-109 > > If I click on any of the many "Read more" links, I get nothing. I > don't > guess this is flash. Lots of flash sites work for me, and they ask > if I want > to allow flash. The nytimes pages do not. Other examples: You could try starting Iceweasel with -P and create a new profile. If it works there, something is wrong in your normal profile. -- Cheers, Sven Arvidsson http://www.whiz.se PGP Key ID 6FAB5CD5 signature.asc Description: This is a digitally signed message part
Re: nytimes pages that fail in iceweasel
On Fri, Feb 19, 2016 at 09:13:26PM -0500, Steve Kleene wrote: > A lot of sites on nytimes.com don't work correctly in my iceweasel, e.g. > > http://www.nytimes.com/interactive/2016/us/elections/fact-check.html#/factcheck-109 > > If I click on any of the many "Read more" links, I get nothing. I don't > guess this is flash. Lots of flash sites work for me, and they ask if I want > to allow flash. The nytimes pages do not. Other examples: > > http://www.nytimes.com/interactive/2016/02/17/upshot/scalia-supreme-court-senate-nomination.html#g-detailed-responses > http://www.nytimes.com/interactive/2016/01/02/opinion/collins-our-new-year-quiz.html > > I am running iceweasel 38.6.1 under Wheezy. Any ideas what format these pages > use or why they are failing? 38.6.1 (under jessie tho, not wheezy), everything works fine. Maybe you have javascript disabled?
Re: nytimes pages that fail in iceweasel
On Fri, 19 Feb 2016, Steve Kleene wrote: > A lot of sites on nytimes.com don't work correctly in my iceweasel, > e.g. > > http://www.nytimes.com/interactive/2016/us/elections/fact-check.html#/factcheck-109 > > If I click on any of the many "Read more" links, I get nothing. I > don't guess this is flash. Lots of flash sites work for me, and they > ask if I want to allow flash. The nytimes pages do not. Other > examples: Loads just fine here. "Read More" works, too. > http://www.nytimes.com/interactive/2016/02/17/upshot/scalia-supreme-court-senate-nomination.html#g-detailed-responses > http://www.nytimes.com/interactive/2016/01/02/opinion/collins-our-new-year-quiz.html Both links works. Loads the pages. No anomalies notes. > I am running iceweasel 38.6.1 under Wheezy. Any ideas what format > these pages use or why they are failing? My version, too, 64-bit. Ditto Wheezy. However, I'm only running a window manager -- Openbox. Don't have any desktops installed. B
nytimes pages that fail in iceweasel
A lot of sites on nytimes.com don't work correctly in my iceweasel, e.g. http://www.nytimes.com/interactive/2016/us/elections/fact-check.html#/factcheck-109 If I click on any of the many "Read more" links, I get nothing. I don't guess this is flash. Lots of flash sites work for me, and they ask if I want to allow flash. The nytimes pages do not. Other examples: http://www.nytimes.com/interactive/2016/02/17/upshot/scalia-supreme-court-senate-nomination.html#g-detailed-responses http://www.nytimes.com/interactive/2016/01/02/opinion/collins-our-new-year-quiz.html I am running iceweasel 38.6.1 under Wheezy. Any ideas what format these pages use or why they are failing? Thanks.
