Tixy writes:
> On Fri, 2020-10-16 at 19:56 +0300, Georgi Naplatanov wrote:
> [...]
>> Debian Jessie is not supported even as LTS anymore. If I was you then I
>> would try to use FireFox binaries provided by mozilla.org.
>
> I would second that, or upgrade to a newer version of Debian.
> Personall
On Fri, 2020-10-16 at 19:56 +0300, Georgi Naplatanov wrote:
[...]
> Debian Jessie is not supported even as LTS anymore. If I was you then I
> would try to use FireFox binaries provided by mozilla.org.
I would second that, or upgrade to a newer version of Debian.
Personally I wouldn't go anywhere n
On 10/16/20 6:21 PM, Mick Ab wrote:
> Iceweasel has been running okay on a Debian Jessie desktop for a long time.
>
> Lately, it keeps hanging. It was noticed that the following message
> appeared in an xterm window :
>
> ###!!![Parent][DispatchAsyncMessage] Error:
> PLayerTransaction::Msg_Releas
I went to the message you linked and then the site mentioned and downloaded a
large /etc/hosts file that seems to send most of what was eating up cpu &
memory to the bit bucket. Huge difference in FF response time, no hard drive
grinding. Top now shows around 10% cpu usage and 80% memory.
Thank
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Nov 07, 2017 at 04:31:32PM -0800, cgi...@surfnaked.ca wrote:
[...]
> The Internet is like a big city - there are lots of bright lights
> and excitement, but also dark alleys down which the unwary get
> mugged.
with the difference that on the
Quoting deloptes :
RRRoy BBBean wrote:
Now, I have to temporarily enable between 20 and 200 domains every time
I do anything. I can't imagine what the www will be like in another 10
years...
indeed it changed negatively in the past 10-15y. it is now virtually
impossible to find useful inform
On 11/7/17, RRRoy BBBean wrote:
>> It has problems, especially with scripts. There are apparently simple
>> pages which will eat a third of a CPU, continuously.
>
> In the past, I have foolishly let my computer sit overnight, with FF
> open to a site which (it turned out, on later examination) con
RRRoy BBBean wrote:
> Now, I have to temporarily enable between 20 and 200 domains every time
> I do anything. I can't imagine what the www will be like in another 10
> years...
indeed it changed negatively in the past 10-15y. it is now virtually
impossible to find useful information - only thing
> It has problems, especially with scripts. There are apparently simple
> pages which will eat a third of a CPU, continuously.
In the past, I have foolishly let my computer sit overnight, with FF
open to a site which (it turned out, on later examination) continuously
cycled video ads. I noticed th
On Tue 07 Nov 2017 at 08:34:44 (-0800), Mike McClain wrote:
> I run an older PC, Pentium3 w/ 512M memory which does everything I
> need but Iceweasel is killing me since the last couple of upgrades.
>
> It's become such a memory hog that it ties up the system for minutes
> at a time.
>
> How can
On Tue, 7 Nov 2017 08:34:44 -0800
Mike McClain wrote:
> I run an older PC, Pentium3 w/ 512M memory which does everything I
> need but Iceweasel is killing me since the last couple of upgrades.
>
> It's become such a memory hog that it ties up the system for minutes
> at a time.
>
It has proble
On Tue, Nov 07, 2017 at 08:34:44AM -0800, Mike McClain wrote:
> I run an older PC, Pentium3 w/ 512M memory which does everything I
> need but Iceweasel is killing me since the last couple of upgrades.
>
> It's become such a memory hog that it ties up the system for minutes
> at a time.
>
> How ca
On Sat, Aug 06, 2016 at 11:37:00PM +0100, Lisi Reisz wrote:
> On Saturday 06 August 2016 23:23:22 Bob Holtzman wrote:
> > On Fri, Aug 05, 2016 at 12:24:43AM +0100, Lisi Reisz wrote:
> > > On Thursday 04 August 2016 20:48:41 afamilyofbetatesters hendersonpark
> wrote:
> > > > This may not even be p
I have added:
debhttp://mozilla.debian.net/ jessie-backports firefox-release
to my sources.list and installed firefox. Well and good. I have
version 47.0.1. I assume that we will catch up with Mozilla and get
48.0 soon.
My actual question, though, is this: Has anything been said about w
On Saturday 06 August 2016 23:23:22 Bob Holtzman wrote:
> On Fri, Aug 05, 2016 at 12:24:43AM +0100, Lisi Reisz wrote:
> > On Thursday 04 August 2016 20:48:41 afamilyofbetatesters hendersonpark
wrote:
> > > This may not even be possible, but how can I update the IceWeasel
> > > (Firefox) from 45 (o
On Fri, Aug 05, 2016 at 12:24:43AM +0100, Lisi Reisz wrote:
> On Thursday 04 August 2016 20:48:41 afamilyofbetatesters hendersonpark wrote:
> > This may not even be possible, but how can I update the IceWeasel (Firefox)
> > from 45 (old) to the current 47? I need it on 47 to be able to use a
> > pl
On 2016-08-04, afamilyofbetatesters hendersonpark
wrote:
>
> This may not even be possible, but how can I update the IceWeasel (Firefox)
> from 45 (old) to the current 47? I need it on 47 to be able to use a
> platform I use instead of skype :)
>
I don't believe Iceweasel gets updated to Firefox
Le 04/08/2016 à 21:48, afamilyofbetatesters hendersonpark a écrit :
> This may not even be possible, but how can I update the IceWeasel
> (Firefox) from 45 (old) to the current 47? I need it on 47 to be able to
> use a platform I use instead of skype :)
what you have and is available in Jessie is
On Thursday 04 August 2016 20:48:41 afamilyofbetatesters hendersonpark wrote:
> This may not even be possible, but how can I update the IceWeasel (Firefox)
> from 45 (old) to the current 47? I need it on 47 to be able to use a
> platform I use instead of skype :)
What version of Debian are you usi
On 2016-05-11 12:10:25 +0200, to...@tuxteam.de wrote:
> This is happening only on local files? Perhaps FF is expecting that
> brain damaged byte order mark to recognize the file as UTF-8?
I reported a bug about that in the past:
https://bugzilla.mozilla.org/show_bug.cgi?id=1071816
--
Vincent
On 2016-05-11 11:55:33 +0200, Frédéric Marchal wrote:
> On Wednesday 11 May 2016 11:23:56 err...@free.fr wrote:
> > Why unicode like utf-8 is not default value in iceweasel ?
> >
> > (it's time, we are in 2016 now)
>
> Unicode is the default in firefox/iceweasel.
No, the default is windows-1
Hi there
Michael Lange wrote:
On Wed, 11 May 2016 18:43:50 +0200
Michael Lange wrote:
According to this (yet probably dated ) page:
http://www-archive.mozilla.org/projects/intl/chardet.html
universal_charset_detector might help if it were enabled by default.
Just looked at the above p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, May 11, 2016 at 06:55:31PM +0200, Michael Lange wrote:
> On Wed, 11 May 2016 18:43:50 +0200
> Michael Lange wrote:
>
> > According to this (yet probably dated ) page:
> >http://www-archive.mozilla.org/projects/intl/chardet.html
> > univer
On Wed, 11 May 2016 18:43:50 +0200
Michael Lange wrote:
> According to this (yet probably dated ) page:
>http://www-archive.mozilla.org/projects/intl/chardet.html
> universal_charset_detector might help if it were enabled by default.
Just looked at the above page again, and noticed that the
On Wed, 11 May 2016 16:28:03 +0200
wrote:
> There's some hope. Have a look at the intl subcategory in about:config
> [1] (especially at intl.locale.matchOS and/or general.useragent.locale),
> but also intl.accept.charsets (it is a list, might be prioritized).
>
I never tested this before, but a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, May 11, 2016 at 03:14:39PM +0200, Rob van der Putten wrote:
> Hi there
>
>
> to...@tuxteam.de wrote:
>
> >On Wed, May 11, 2016 at 12:34:29PM +0200, Rob van der Putten wrote:
[...]
> >That's because it has been enshrined by the Unicode Cons
Hi there
to...@tuxteam.de wrote:
On Wed, May 11, 2016 at 12:34:29PM +0200, Rob van der Putten wrote:
I actually thought about this. But it just seems crude;
vim some.txt
^vufeff
:wq
It does work though.
But I want UTF-8 without a BOM. It is, after all, the default locale.
Everyone wan
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, May 11, 2016 at 12:34:29PM +0200, Rob van der Putten wrote:
> Hi there
>
>
> to...@tuxteam.de wrote:
[BOM BOM hurrah!]
> I actually thought about this. But it just seems crude;
>
> vim some.txt
> ^vufeff
> :wq
>
> It does work though.
> B
Hi there
to...@tuxteam.de wrote:
This is happening only on local files? Perhaps FF is expecting that brain
damaged byte order mark to recognize the file as UTF-8?
When the data come over HTTP there are other out-of-band hints to communicate
the encoding.
Try editing the file with some Micros
On 5/11/2016 4:58 AM, Rob van der Putten wrote:
Hi there
Michael Lange wrote:
you can try the following:
type "about:config" into iceweasel's address bar (without the
quotes of
course), then type "charset" into the config's search bar.
Several options
should appear. Look for the key "intl.ch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, May 11, 2016 at 11:58:31AM +0200, Rob van der Putten wrote:
> Hi there
>
>
> Michael Lange wrote:
>
> >you can try the following:
> >
> >type "about:config" into iceweasel's address bar (without the quotes of
> >course), then type "charset"
Hi there
Michael Lange wrote:
you can try the following:
type "about:config" into iceweasel's address bar (without the quotes of
course), then type "charset" into the config's search bar. Several options
should appear. Look for the key "intl.charset.default". Is the value
already set to "UTF-
On Wednesday 11 May 2016 11:23:56 err...@free.fr wrote:
> Why unicode like utf-8 is not default value in iceweasel ?
>
> (it's time, we are in 2016 now)
Unicode is the default in firefox/iceweasel. See
https://developer.mozilla.org/en-US/docs/Web/Guide/Localizations_and_character_encodings
Why unicode like utf-8 is not default value in iceweasel ?
(it's time, we are in 2016 now)
signature.asc
Description: OpenPGP digital signature
Hi,
On Wed, 11 May 2016 10:55:54 +0200
Rob van der Putten wrote:
> Hi there
>
>
> UTF-8 is my default locale. So obviously text files are UTF-8 as well.
> So why does iceweasel insist that these are windows-1252? How do I fix
> this?
you can try the following:
type "about:config" into icewea
On Wednesday 11 May 2016 10:55:54 Rob van der Putten wrote:
> Hi there
>
>
> UTF-8 is my default locale. So obviously text files are UTF-8 as well.
> So why does iceweasel insist that these are windows-1252? How do I fix this?
In about:config, have you changed any of intl.charset.detector or
in
On 04/12/2016 12:08 PM, The Wanderer wrote
The Firefox development process follows a type of cascading release:
http://www.askvg.com/mozilla-updates-firefox-update-channels-nightly-aurora-beta-and-release/
There are nightly builds, which are compiled every night from the public
source tree (ass
On 04/12/2016 12:16 PM, Lisi Reisz wrote:
Aurora is alpha and will be 47 - a long way from release-ready - and
beta is almost release-ready, so probably 46. If you had trouble with
esr45, why not try release? It should be up to date and stable. esr45
is supposed to be 45 long term support - but
On Tuesday 12 April 2016 17:08:10 The Wanderer wrote:
> On 2016-04-12 at 11:43, Harris Paltrowitz wrote:
> > On 04/12/2016 11:06 AM, Lisi Reisz wrote:
> >> On Tuesday 12 April 2016 15:14:08 Harris Paltrowitz wrote:
> >>> I tried Firefox 45 last week but as you may remember from my
> >>> recent emai
On Tuesday 12 April 2016 16:43:47 Harris Paltrowitz wrote:
> On 04/12/2016 11:06 AM, Lisi Reisz wrote:
> > On Tuesday 12 April 2016 15:14:08 Harris Paltrowitz wrote:
> >> I tried Firefox 45 last week but as you may remember from my recent
> >> emails, I experienced major issues with choppy videos i
On 2016-04-12 at 11:43, Harris Paltrowitz wrote:
> On 04/12/2016 11:06 AM, Lisi Reisz wrote:
>
>> On Tuesday 12 April 2016 15:14:08 Harris Paltrowitz wrote:
>>
>>> I tried Firefox 45 last week but as you may remember from my
>>> recent emails, I experienced major issues with choppy videos in
>>>
On 04/12/2016 11:06 AM, Lisi Reisz wrote:
On Tuesday 12 April 2016 15:14:08 Harris Paltrowitz wrote:
I tried Firefox 45 last week but as you may remember from my recent
emails, I experienced major issues with choppy videos in Youtube using
Firefox 45, but not with Iceweasel 38.7.1. I've since
On 2016-04-12 at 09:09, Harris Paltrowitz wrote:
> Hey all,
>
> Recently when I started using Debian I noticed that the version of
> Iceweasel that Jessie comes with is 38.7.1, whereas the latest
> Firefox is 45. I also noticed that when I visit www.citibank.com
> using Iceweasel 38.7.1 the Cit
On Tuesday 12 April 2016 15:14:08 Harris Paltrowitz wrote:
> On 04/12/2016 09:43 AM, Lisi Reisz wrote:
> > On Tuesday 12 April 2016 14:09:12 Harris Paltrowitz wrote:
> >> Hey all,
> >>
> >> Recently when I started using Debian I noticed that the version of
> >> Iceweasel that Jessie comes with is 3
> Recently when I started using Debian I noticed that the version of Iceweasel
> that Jessie comes with is 38.7.1, whereas the latest Firefox is 45. I also
> noticed that when I visit www.citibank.com using Iceweasel 38.7.1 the
> Citibank website tells me that my browser is out of date and not sup
On 04/12/2016 09:43 AM, Lisi Reisz wrote:
On Tuesday 12 April 2016 14:09:12 Harris Paltrowitz wrote:
Hey all,
Recently when I started using Debian I noticed that the version of
Iceweasel that Jessie comes with is 38.7.1, whereas the latest Firefox
is 45. I also noticed that when I visit www.ci
On Tuesday 12 April 2016 14:09:12 Harris Paltrowitz wrote:
> Hey all,
>
> Recently when I started using Debian I noticed that the version of
> Iceweasel that Jessie comes with is 38.7.1, whereas the latest Firefox
> is 45. I also noticed that when I visit www.citibank.com using
> Iceweasel 38.7.1
iceweasel 44.0.2
deb http://debian.salud.gob.sv/debian-mozilla/ wheezy-backports
iceweasel-release
http://wiki.salud.gob.sv/wiki/Actualizaciones_y_sources.list
On 17/03/2016 2:52 AM, Andrew McGlashan wrote:
> Latest case in point, Firefox 44.x would allow nice and easy copy of a
> section of a webpage (links, pictures, everything) -- ready to be pasted
> in to an email or a document of some type (fully formatted with relative
> link adjustments). It wo
Marc writes:
> I am perfectly happy to continue downloading from Mozilla if that will
> keep me current, and Debian's repo will not.
Why do you need to keep current? Just curious.
--
John Hasler
jhas...@newsguy.com
Elmwood, WI USA
On 16/03/2016 11:40 PM, John Hasler wrote:
> Marc writes:
>> I am perfectly happy to continue downloading from Mozilla if that will
>> keep me current, and Debian's repo will not.
>
> Why do you need to keep current? Just curious.
Well, security is a good reason to remain current; but those ES
On 16/03/2016 3:05 PM, Marc Shapiro wrote:
> What is the difference between firefox-esr and firefox-release? I have
> been downloading the tar file from mozilla since this whole thing
> started. How different is what Debian now has from the Mozilla tar
> file? Will Debian keep up with the Mozi
On 03/14/2016 02:59 PM, Liam O'Toole wrote:
On 2016-03-14, Laszlo T. wrote:
No more Iceweasel brand. The Debian can use the Firefox name. So change the
repository
deb http://mozilla.debian.net/ jessie-backports firefox-release
In the case of wheezy, that would be wheezy-backports. Also, note
On 2016-03-14, Laszlo T. wrote:
> No more Iceweasel brand. The Debian can use the Firefox name. So change the
> repository
>
> deb http://mozilla.debian.net/ jessie-backports firefox-release
In the case of wheezy, that would be wheezy-backports. Also, note that
firefox-esr is available as well as
No more Iceweasel brand. The Debian can use the Firefox name. So change the
repository
deb http://mozilla.debian.net/ jessie-backports firefox-release
remove Iceweasel, install Firefox and you will have fresh browser,
currently v45. It works fine for me.
On Mon, 14 Mar 2016 03:46:13 +0100
sp113438 wrote:
> On Sun, 13 Mar 2016 23:46:45 +
> Lisi Reisz wrote:
>
> > I just got the following error after an update:
> >
> > W: Failed to fetch
> > http://mozilla.debian.net/dists/wheezy-backports/Release: Unable to
> > find expected entry 'icewease
On Sun, 13 Mar 2016 23:46:45 +
Lisi Reisz wrote:
> I just got the following error after an update:
>
> W: Failed to fetch
> http://mozilla.debian.net/dists/wheezy-backports/Release: Unable to
> find expected entry 'iceweasel-release/binary-amd64/Packages' in
> Release file (Wrong sources.lis
On Sun, 13 Mar 2016 23:46:45 +
Lisi Reisz wrote:
> I just got the following error after an update:
>
> W: Failed to fetch
> http://mozilla.debian.net/dists/wheezy-backports/Release: Unable to
> find expected entry 'iceweasel-release/binary-amd64/Packages' in
> Release file (Wrong sources.lis
On Sun, 2016-03-13 at 19:53 +1000, Weaver wrote:
> There's much more than a symlink involved.
> The installation happened on two machines: on the laptop, it failed
> to
> find the main bookmark menu, and as that was the first update, that
> went
> west. I backed up the bookmarks file on the PC, b
On 2016-03-12 17:44, Sven Arvidsson wrote:
On Sat, 2016-03-12 at 00:37 -0500, Dale Harris wrote:
Huh, why is iceweasel installing firefox-esr now and not even putting
in a sym. link from iceweasel to firefox?
Iceweasel is no more, read the changelog.
Aside from an advisory a read in the gen
On Sat, 2016-03-12 at 10:11 +, Joe wrote:
> After a routine upgrade (which did *not* raise a changelog notice),
> any
> menu entries which reference iceweasel are now broken, with the user
> being left to fix them. I'd say that was a bug.
There was a NEWS file, so should have been picked up by
On 12/03/16 10:13, Joe wrote:
On Sat, 12 Mar 2016 21:04:52 +1100
Andrew McGlashan wrote:
On 12/03/2016 4:37 PM, Dale Harris wrote:
Huh, why is iceweasel installing firefox-esr now and not even
putting in a sym. link from iceweasel to firefox?
http://www.pcworld.com/article/3036509/linux/ice
On Sat, 12 Mar 2016 21:04:52 +1100
Andrew McGlashan wrote:
> On 12/03/2016 4:37 PM, Dale Harris wrote:
> > Huh, why is iceweasel installing firefox-esr now and not even
> > putting in a sym. link from iceweasel to firefox?
>
> http://www.pcworld.com/article/3036509/linux/iceweasel-will-be-rena
On Sat, 12 Mar 2016 08:44:43 +0100
Sven Arvidsson wrote:
> On Sat, 2016-03-12 at 00:37 -0500, Dale Harris wrote:
> > Huh, why is iceweasel installing firefox-esr now and not even
> > putting in a sym. link from iceweasel to firefox?
>
> Iceweasel is no more, read the changelog.
>
> If you th
On 12/03/2016 4:37 PM, Dale Harris wrote:
> Huh, why is iceweasel installing firefox-esr now and not even putting
> in a sym. link from iceweasel to firefox?
http://www.pcworld.com/article/3036509/linux/iceweasel-will-be-renamed-firefox-as-relations-between-debian-and-mozilla-thaw.html
On Sat, 2016-03-12 at 00:37 -0500, Dale Harris wrote:
> Huh, why is iceweasel installing firefox-esr now and not even putting
> in a sym. link from iceweasel to firefox?
Iceweasel is no more, read the changelog.
If you think it should install a symlink, file a bug.
--
Cheers,
Sven Arvidsson
ht
I believe that cached images will still load.
mrc
On Sat, Nov 14, 2015 at 5:47 PM, Safwat wrote:
> For those who say it's a css thing:
>
> 1. The DOM is definitely changing. I can see that through inspect element.
Can you tell if what you're looking at is before or after the stream
processing? I'm not familiar enough with firefox deugging to gue
> Wow. That means that they bypass NoScript. Through technical or human
> weakness, whatever.
You're reaching conclusions too fast. It's possible that this is simply
NoScript disabling Google's tracking by modifying the URLS.
signature.asc
Description: OpenPGP digital signature
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, Nov 14, 2015 at 10:47:13AM +0200, Safwat wrote:
> For those who say it's a css thing:
>
> 1. The DOM is definitely changing. I can see that through inspect element.
>
> 2. It doesn't happen when NoScript is off and Firefox's
> javascript_enab
For those who say it's a css thing:
1. The DOM is definitely changing. I can see that through inspect element.
2. It doesn't happen when NoScript is off and Firefox's
javascript_enabled is set to false.
On Sat, Nov 14, 2015 at 12:00 AM, Eduardo M KALINOWSKI
wrote:
> On Qui, 12 Nov 2015, Safwat wrote:
>>
>> I am running NoScript + Iceweasel, and I observed something weird.
>> Consider a Google search result which has this "a href" value:
>>
>>
>> https://www.google.com/url?q=https://en.wikipedia.o
>Could it be NoScript itself, or another extension, changing the link to
avoid Google tracking?
That's definitely possible. I'll check it out.
On Qui, 12 Nov 2015, Safwat wrote:
I am running NoScript + Iceweasel, and I observed something weird.
Consider a Google search result which has this "a href" value:
https://www.google.com/url?q=https://en.wikipedia.org/wiki/Hello_(Adele_song)&sa=U&ved=0CCsQFjAIahUKEwjPuq3H34vJAhWDWhQKHW7eCbA&usg
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Nov 12, 2015 at 10:46:23PM +0200, Safwat wrote:
> I am running NoScript + Iceweasel, and I observed something weird.
> Consider a Google search result which has this "a href" value:
>
> https://www.google.com/url?q=https://en.wikipedia.org/wik
On Wed 04 Nov 2015 at 14:59:23 +0100, Vincent Lefevre wrote:
> On 2015-11-03 13:59:12 +, Brian wrote:
> > The contention is that overriding a bank security decision and altering
> > the user-agent string is unwise and not to be recommended.
> >
> > Access to digital banking at RBS and Natwest
On 2015-11-03 13:59:12 +, Brian wrote:
> The contention is that overriding a bank security decision and altering
> the user-agent string is unwise and not to be recommended.
>
> Access to digital banking at RBS and Natwest in the UK is allowed only
> when the string "Firefox" is found. Many ye
On Tue 03 Nov 2015 at 23:07:56 (+1300), Chris Bannister wrote:
> On Tue, Nov 03, 2015 at 08:27:42AM +, Joe wrote:
> > On Mon, 2 Nov 2015 22:53:03 +
> > Brian wrote:
> > > An attacker must inject a payload into a web page that the user
> > > visits. When the page loads in the user’s browser
On Tue 03 Nov 2015 at 02:57:47 +0100, Vincent Lefevre wrote:
> On 2015-11-02 22:53:03 +, Brian wrote:
> > An attacker must inject a payload into a web page that the user visits.
> > When the page loads in the user’s browser the attacker’s payload will
> > be executed. A user would likely have
On Tue, Nov 03, 2015 at 08:27:42AM +, Joe wrote:
> On Mon, 2 Nov 2015 22:53:03 +
> Brian wrote:
>
>
> >
> > An attacker must inject a payload into a web page that the user
> > visits. When the page loads in the user’s browser the attacker’s
> > payload will be executed. A user would lik
On Mon, 2 Nov 2015 22:53:03 +
Brian wrote:
>
> An attacker must inject a payload into a web page that the user
> visits. When the page loads in the user’s browser the attacker’s
> payload will be executed. A user would likely have no knowledge of
> this, irrespective of whatever browser or
On Mon, Nov 02, 2015 at 04:13:44PM +0200, Alex Moonshine wrote:
>
>
> On 11/02/2015 03:22 PM, Vincent Lefevre wrote:
> >But some videos are not supported with official precompiled Firefox
> >versions due to obsolete gstreamer:
> >https://bugzilla.mozilla.org/show_bug.cgi?id=947287
>
> Oh, right.
On Mon, Nov 02, 2015 at 07:19:46AM -0500, Jack Dangler wrote:
> Got a msg this morning from online bank service that my browser
> (iceweasel) is no longer up to date (equates to ff31) and wants to
> 'either update your browser to a compatible version or install one of
> the following - [list of usu
On 2015-11-02 22:53:03 +, Brian wrote:
> An attacker must inject a payload into a web page that the user visits.
> When the page loads in the user’s browser the attacker’s payload will
> be executed. A user would likely have no knowledge of this, irrespective
> of whatever browser or user-agent
On Mon 02 Nov 2015 at 23:02:38 +0100, Vincent Lefevre wrote:
> On 2015-11-02 15:00:19 +, Brian wrote:
> > On Mon 02 Nov 2015 at 14:58:24 +0100, Vincent Lefevre wrote:
> >
> > > On 2015-11-02 13:47:41 +, Brian wrote:
> > > > On Mon 02 Nov 2015 at 14:17:39 +0100, Vincent Lefevre wrote:
> >
On 2015-11-02 15:00:19 +, Brian wrote:
> On Mon 02 Nov 2015 at 14:58:24 +0100, Vincent Lefevre wrote:
>
> > On 2015-11-02 13:47:41 +, Brian wrote:
> > > On Mon 02 Nov 2015 at 14:17:39 +0100, Vincent Lefevre wrote:
> > > > The user's browser cannot compromise the site itself. But a security
On Mon 02 Nov 2015 at 11:42:50 -0500, Jack Dangler wrote:
> On Mon, 2015-11-02 at 07:23 -0700, Charlie Kravetz wrote:
> > On Mon, 02 Nov 2015 08:00:59 -0600
> > John Hasler wrote:
> >
> > >Jack Dangler wrote:
> > >> The next version of iceweasel i found in deb packages is 41 (quite a
> > >> jump
On Mon, 2015-11-02 at 07:23 -0700, Charlie Kravetz wrote:
> On Mon, 02 Nov 2015 08:00:59 -0600
> John Hasler wrote:
>
> >Jack Dangler wrote:
> >> The next version of iceweasel i found in deb packages is 41 (quite a
> >> jump), but says it is likely buggy (i'm guessing its in experimental).
> >
On Monday 02 November 2015 14:34:49 Vincent Lefevre wrote:
> On 2015-11-02 07:23:07 -0700, Charlie Kravetz wrote:
> > On Mon, 02 Nov 2015 08:00:59 -0600
> >
> > John Hasler wrote:
> > >Jack Dangler wrote:
> > >> The next version of iceweasel i found in deb packages is 41 (quite a
> > >> jump), but
On Mon 02 Nov 2015 at 14:58:24 +0100, Vincent Lefevre wrote:
> On 2015-11-02 13:47:41 +, Brian wrote:
> > On Mon 02 Nov 2015 at 14:17:39 +0100, Vincent Lefevre wrote:
> > > The user's browser cannot compromise the site itself. But a security
> > > bug may permit an attacker to get the user's l
Am 02.11.2015 um 15:23 schrieb Charlie Kravetz:
> The stable release of Firefox is Version 41.0.2, released Oct 15.
> Doesn't that make 38 old?
No, it doesn't.
38.x is the currently stable extended support release (ESR) of Firefox.
--
Regards
mks
On 2015-11-02 07:23:07 -0700, Charlie Kravetz wrote:
> On Mon, 02 Nov 2015 08:00:59 -0600
> John Hasler wrote:
>
> >Jack Dangler wrote:
> >> The next version of iceweasel i found in deb packages is 41 (quite a
> >> jump), but says it is likely buggy (i'm guessing its in experimental).
> >
> >Un
On Mon, 02 Nov 2015 08:00:59 -0600
John Hasler wrote:
>Jack Dangler wrote:
>> The next version of iceweasel i found in deb packages is 41 (quite a
>> jump), but says it is likely buggy (i'm guessing its in experimental).
>
>Unstable has 38.3. Works fine.
The stable release of Firefox is Versi
On 11/02/2015 03:22 PM, Vincent Lefevre wrote:
But some videos are not supported with official precompiled Firefox
versions due to obsolete gstreamer:
https://bugzilla.mozilla.org/show_bug.cgi?id=947287
Oh, right. I use gstreamer from http://www.deb-multimedia.org/
Yes, I know I just said us
Jack Dangler wrote:
> The next version of iceweasel i found in deb packages is 41 (quite a
> jump), but says it is likely buggy (i'm guessing its in experimental).
Unstable has 38.3. Works fine.
--
John Hasler
jhas...@newsguy.com
Elmwood, WI USA
On 2015-11-02 13:47:41 +, Brian wrote:
> On Mon 02 Nov 2015 at 14:17:39 +0100, Vincent Lefevre wrote:
> > The user's browser cannot compromise the site itself. But a security
> > bug may permit an attacker to get the user's login and password, and
> > neither the bank nor the user would like th
On Mon 02 Nov 2015 at 14:17:39 +0100, Vincent Lefevre wrote:
> On 2015-11-02 13:03:14 +, Brian wrote:
> > The reason you advance is probably the one which bank's IT section would
> > give if you asked them. Quite how a user's browser can compromise the
> > security of the site itself is unlike
On Monday 02 November 2015 07:19:46 Jack Dangler wrote:
> Got a msg this morning from online bank service that my browser
> (iceweasel) is no longer up to date (equates to ff31) and wants to
> 'either update your browser to a compatible version or install one of
> the following - [list of usual su
On Mon 02 Nov 2015 at 15:10:55 +0200, Alex Moonshine wrote:
> Not really a solution to OPs problem, but I've decided that it's much
> easier to just use a stand-alone precompiled Firefox downloaded from
> Mozilla website, which happily updates itself. Debian's update policy
> for Iceweasel is far
1 - 100 of 1228 matches
Mail list logo
