Re: userChrome.css will not be supported indefinitely

[WaltS48 <WaltS48@xxxxxxxxxxxxxxxxx>]

On 1/31/18 9:53 AM, Ed Mullen wrote:
> On 1/30/2018 at 2:30 PM, WaltS48 created this epitome of digital genius:
> > On 1/30/18 2:22 PM, Ed Mullen wrote:
> > > On 1/30/2018 at 2:17 PM, WaltS48 created this epitome of digital 
> > > genius:
> > > > On 1/30/18 2:01 PM, Wolf K wrote:
> > > > > On 2018-01-30 13:06, Ed Mullen wrote:
> > > > > > On 1/30/2018 at 1:01 PM, Caver1 created this epitome of digital 
> > > > > > genius:
> > > > > > > "The functionality of userChrome.css will not be supported, for 
> > > > > > > the same reasons that we removed support for legacy themes."
> > > > > > > https://bugzilla.mozilla.org/show_bug.cgi?id=1431962
> > > > > >
> > > > > > I just uttered language I cannot post here.
> > > > >
> > > > > I bet I had the same thoughts.
> > > > So, you all want somebody to hack into your userContent.css, or 
> > > > userChrome.ccs files and hijack your Firefox.
> > > >
> > > > Okay.
> > >
> > > Oh, c'mon!  Just how are they going to do that?
> >
> > The same way they could with Complete Themes I guess.
> >
> > Hack into your computer, edit the files and save them. Or maybe 
> > completely replace them.
> >
> > The next time you open Firefox, it doesn't look like you last used it.
>
> "Hack into your computer ..." is the key to why there is little to 
> worry about concerning this. How's someone going to hack into my PC by 
> my visiting a web site?  Pure FUD.

Really?

https://www.bleepingcomputer.com/news/security/mozilla-fixes-severe-flaw-in-firefox-ui-that-leads-to-remote-code-execution/

"Mozilla has released Firefox 58.0.1 to fix a security issue that was 
hiding in the browser's UI code and would have allowed an attacker to 
run code on the user's computer, allowing a quick and easy path to 
delivering malware or even taking over the entire PC."

_______________________________________________
general mailing list
general@xxxxxxxxxxxxxxxxx
https://lists.mozilla.org/listinfo/general