Title search: ✖
Show All (599)
All About GreenRope (168)
Content Marketing (66)
Customer Experience (79)
Digital Transformation (7)
Email Marketing (3)
Event Recaps (2)
Everything Small Business (46)
In the Clearing with Lars (25)
Marketing Automation (56)
Monthly Updates (22)
Social Media (20)
Tidbits for You (117)
Websites & SEO (4)
Weekly Roundup (16)
10 Surprising Things You Didn't know about Client Services & Search Marketing Manager, Lisa Frampton
Disqualifying Leads Without Alienating Them as Future Customers - Part 2: Cultivating Non-Leads with Automated Marketing
4 Ways to Get Your Email Marketing in Front of the Right Audience Through Personalization & Segmentation
Total Cost of Ownership: What does it mean and how can you avoid costly, unsuccessful implementations.
Everything You Need to Know about PPC: Interview with Spectrum Search Marketing Founder, Bryan Larkin
Important Changes for our API Users!
When someone connects to GreenRope's API, they transmit passwords and other data, and we transmit contact and other data back to them. It's important that this traffic back and forth be encrypted, so we require SSL for all API connections. Unfortunately, as technology improves, it becomes easier and easier to break encryption, so new methodologies have to be created every time, and old ones have to be deprecated, and the world has to stop using them, because they becomes susceptible to attacks.
Up until very recently we supported TLS 1.0, 1.1, and 1.2. But recently the PCI Security Standards Council has determined that TLS 1.0 is no longer secure, and it should no longer be used. Most browsers will prefer 1.2, and in some cases 1.1, and avoid 1.0 as much as possible, and PCI themselves have indicated that it should no longer be used after June 30th, 2016.
PCI and other security companies run PCI compliance scans, and one of those, run on behalf of a customer that uses forms for financial and other sensitive information, flagged us for failure because we still supported 1.0. In order for that customer's PCI compliance to come up clean, we had to turn TLS 1.0 off.
Any of our partners and customers that use our API can no longer use TLS 1.0 to connect to us. They should upgrade their tools as quickly as possible. TLS 1.1 and TLS 1.2 support exists for almost all of the languages and systems that can be used to connect with us, so it's just a matter of finding the right parameters, or upgrading the right libraries, to make this change.
Please Contact Us for more information!