|
Just a follow-up.
Our tests run OK - so may be browser related on the users end.
Sigh …. why does this type of thing always happen when we open the Summit
registration !!
Jon Paris
www.partner400.com
www.SystemiDeveloper.com
On Dec 10, 2014, at 9:58 AM, Jon Paris <jon.paris@xxxxxxxxxxxxxx> wrote:
I’ve just been told that we have a problem with the credit card gatewaythat only started after we made the poodle changes.
headaches
No idea why - just starting to test.
Jon Paris
www.partner400.com
www.SystemiDeveloper.com
On Dec 9, 2014, at 8:31 PM, rob@xxxxxxxxx wrote:
Apparently the 'lack' of patching is causing us grief. Customers are
updating their web browsers and are unable to attach to our website.
Hoping this is the cure:
http://www-01.ibm.com/support/docview.wss?uid=swg21657963
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From: rob@xxxxxxxxx
To: midrange-l@xxxxxxxxxxxx
Date: 12/09/2014 07:15 AM
Subject: Poodle patches really "breaking" anything?
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
Not to feed the "if it ain't broke don't fix it" crowd but are poodle
patches really causing headaches?
http://www.itjungle.com/fhs/fhs120914-story01.html
Granted, it was already broke due to the lax security, but what
howhave been caused by the patches, if any? Any horror stories? If so,
listdid you resolve it? For example:
- I'm running encrypted telnet and it all broke, and what you did to get
around it.
- I'm running Domino x.y.z and I had to ...
- I'm running WAS e.f.g and I had to ...
- I'm running sftp from Acme Coyote and I had to ...
and more of that genre.
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
listTo post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
