Jeff Howard is the quintessential work-from-home entrepreneur: He runs four of his own travel websites, he labors over details of each at his standing desk while taking care of his nearly 2-year-old son Liam.
And he depends on search engines to capture an audience.
When he received an email from Google earlier this month that told him one of his websites — http://hotelsneardcmetro.com, a travel service that connects people with hotels close to Washington, D.C., metro stations — did not meet the Chrome web browser’s revised standards for security, he was puzzled.
“Is this a mistake? Is this coming from the right source?” Mr. Howard said he thought at the time. “I did double check that,” he said, noting that none of his sites covering Washington, D.C., New York City, Boston or San Francisco collect explicit personal data.
Mr. Howard, 33, of Gibsonia, is just one of countless website administrators that have received the warning recently.
As part of a move to migrate all web addresses to a fully encrypted status, Google Chrome will begin labeling “HTTP” websites as “not secure” in October, favoring those adopting the “HTTPS” standard.
Read More
In response to a request for comment on Mr. Howard’s concerns, a Google spokesperson provided a link to a September 2016 blog post on the subject.
“Chrome currently indicates HTTP connections with a neutral indicator. This doesn’t reflect the true lack of security for HTTP connections,” Emily Schechter of the Chrome Security Team wrote in the blog post. “When you load a website over HTTP, someone else on the network can look at or modify the site before it gets to you.”

HTTP, or hypertext transfer protocol, was first introduced in the early 1990s, according to a 2014 study, “The Cost of the ‘S’ in HTTPS,” by Carnegie Mellon University researchers. HTTPS is an internet communication protocol that ensures data is transmitted confidentially, end-to-end; it’s the secure version of hypertext transfer protocol that fully encrypts a website.
Since the 1990s, the internet has changed drastically, and HTTPS is no longer only used in banking or e-commerce: it accounts for 50 percent of all connections. “The increasing personalization of the web” has forced the internet to change its basic infrastructure, according to the CMU study.
Google is looking to become a forerunner in that innovation and argues that such transmissions provide three layers of protection: encryption, or converting data into non-readable code; data integrity, which keeps information from being tampered with or modified without detection; and authentication, which builds user trust (think of the green padlock at the left of your address bar).
Mr. Howard thinks the behemoth California technology company should dish out some form of subsidy when websites change to HTTPS protocol at Google’s urging.
“If they really believed this was an altruistic thing for everyone to do ... they could offer $100 in advertising to your website,” he said.
While there are a myriad of security benefits in switching, Mr. Howard still feels the “Not secure” label is equivocal.
He thinks websites that don’t use consumer-facing logins, credit cards or collect important personal information would be unfairly called out by the use of the term “not secure.” He thinks it would be more accurate for the search engine giant to assess the site by saying ‘This website is not transmitted with encryption.’
He expects a “not secure” label would hurt businesses like his.

Some industry experts support the move toward HTTPS.
“Imagine if all the mail you sent and received didn’t have envelopes,” said Josh Aas, executive director of the Internet Security Research Group, a public benefit corporation in San Francisco. “Even junk mail can contain information that you really don’t want floating around out there,” he continued.
The internet research group runs Let’s Encrypt, a free certificate authority that helps people obtain digital certifications to enable HTTPS on their website. Let’s Encrypt employs 11 remote workers full-time and collectively, they’re responsible for 50 million certifications on any given day. The organization began issuing certificates in December 2015.
Mr. Aas, a proponent of HTTPS certification, said it’s relatively uncommon to see websites that don’t contain any sensitive information at all.
“You, as a business owner, might have a view of what is sensitive information, but your visitors have a perspective, too,” he said. “If you were, for example, to look at what pages people are looking at on a news website, you may get a good idea of their political affiliation.”

Plus, ad networks are constantly collecting information on website visitors.
“The web is complex enough that it’s very hard to sit there and decide what is confidential and what is not,” Mr. Aas said. “In the face of that complexity, we need to assume that everything is sensitive. It’s the only safe way to go.”
This time last year, Mr. Howard and his wife watched as revenue for their bootstrapped travel websites grew. Running the sites, which are monetized through referral commissions from users clicking on hotels, became more lucrative than full-time work. In the spring, it became Mr. Howard’s full-time job.
Still, he’s not a coder, software developer or website designer and he has no illusions about that. He admits there are a lot of instances where something could go wrong with his website during the transition process to an HTTPS.
“Every link or reference to an image would contain an HTTP and we have to switch it over to an HTTPS,” he explained. “It sounds simple, but I don’t know how to write a script that does that automatically. If we hire someone, we have to be careful a lot of things don’t break on the site.”

Some of the widgets on Mr. Howard’s site are also run with information from third-party websites, like HotelsCombined, a Sydney, Australia-based hotel search company. He fears that if websites hosting information in his widgets don’t move to HTTPS compliance, they will no longer function on his site.
He estimates he will spend at least $600 and three or four days ensuring each site runs on HTTPS.
In spite of all these issues, Mr. Howard expressed gratitude for the search engine giant, without which, he said, he could not have made a living from running a website.
“It’s a delicate balance in our relationship with Google ... we definitely like a lot of things about the company.”
On Thursday afternoon, Mr. Howard said he had moved one of his smaller websites, covering Boston, to an HTTPS. He used an outside vendor, based in Poland, called WPKraken to complete the job for $150.
“The name of the game now is to watch my rankings and see if they slide, improve or don't change at all.”
Courtney Linder: clinder@post-gazette.com or 412-263-1707. Twitter: @LinderPG.





Comments
Welcome to Post-Gazette subscriber-only commenting community. Please review our community guidelines.