On 08/19/2017 03:26 AM, Andrew C Aitchison wrote:
> On Fri, 18 Aug 2017, ToddAndMargo wrote:
> 
>> On 08/17/2017 01:03 PM, David Sommerseth wrote:
>>> On 17/08/17 18:33, ToddAndMargo wrote:
>>>> On 08/17/2017 09:23 AM, ToddAndMargo wrote:
>>>>> Mozilla Firefox 55 source tarball

>> Yes I do.  All bugs and security flaws frozen in place for those
>> that don't like to upgrade their software and those that get
>> tired of having to respin an RPM every month or so due
>> to the rapid pace of Firefox's development.  EL Linux
>> is an anti-Kaisen OS and Red Hat gets CRABBY about having
>> to update things and often does not.
> 
> Red Hat are fairly quick at releasing the six-weekly updates to ESR - 
> IIRC 2 days after Mozilla for 52.3 (SL took almost a week after that).

I never meant to say they did not.  I meant to say they can be
crabby and drag their feet at times.  The few times I asked
them about this or that exploit they had not fixed, they
were a bit rude and refused.

> shouldn't you be paying Red Hat and keeping uptodate with their
> recommendations.

My office is not PCI compliant, as I do not take credit cards.
A check or cash will do fine.  In 22 years of ding this I have
only been asked to take a credit card three times.  One of
them solved the issue by writing me one of those weird credit
card checks that comes with your credit card statement.

The PCI compliant locations are at customer sites.  And they are
all Windows based.

Windows is a truly awful operating system, especially now
that Windows 10 has hit.  But since small business has
no access to business app on Linux (quick book, etc.),
they are stuck with Windows.

M$ has won the Applications War.  It doesn't matter how bad
an OS runs, if you can't run you apps on a better OS, you
are stuck with M$.  My opinion, the customer doesn't care
what his app run on .  They just have to run.

Point of Sale systems, especially those that take credit cards,
are really foolish to run on Windows, but there are no alternatives
for small business.  It is what it is.

I personally do not think PCI actually help all that much
with security.  It does a little; sometimes a lot when they
customer is really flaky.  It is mainly a paper chase to
keep the lawyers at bay.

I had a lady who was set up with a stand alone card reader
last week figure out how to get her non-PCI compliant
POS software on her non-PCI compliant computer on her
non-PCI compliant network to take credit cards.  It
was easier than using the compliant terminal.  When
her boss get back from vacation, we are going to have
"a talk".  (The software vendor said he could switch
the feature off if we wanted him to.)

> More significantly, perhaps you shouldn't run a browser (or a mail 
> reader) on the same machine as the credit-card handling ...

That would be wonderful.  But, since the customer has to
check all kinds of business posting on the eMail and social
media, as well as their cloud based time card ... I think
you get the idea.  They are pretty good about not doing
anything except business and I know this to be a fact as
my FIM (File Integrity Monitoring) software rats them out
if they do.  (And yes, their managers have had "stern"
conversation when they are caught playing video poker on
their machines.)

The solution would be to have an off POS (Point of Sale)
network leg computer for that kind of stuff, but the POS
software have to send eMail and its cost a second computer
and and and ...  (I try, but they don't listen.)

> 
>> Until I get this figured out, I have been using weird old Midori.
>> Maybe I will go to the dark side and install Chromium
>>
>> Do you know anyway to uninstall the recent updates that
>> caused this?
> 
> I'd try
>      yum downgrade firefox-52.2.0
> or
>      yum downgrade firefox-45.8.0

That would work for me.  But I am not on the RPM for
firefox.  The reason being that I support Firefox on
bazillions of customer over two counties.  I need to
see what they see.

I suppose I could temporarily run on the RPM and troubleshoot
the tar ball from its own directory until I get it fixed.
(You just untar it and run it directly from directory it creates.)

Thank you for the help!  Sorry for the rambling.
-T