The Wikimedia Foundation announced on Friday that it’s in the process of implementing HTTPS by default in an effort to encrypt all traffic on Wikipedia and other websites operated by the organization.
By deploying HTTPS for all traffic, the Wikimedia Foundation wants to ensure that users can surf its websites without sacrificing safety and privacy. HTTPS creates an encrypted connection between the user’s computer and the website to protect data against snooping governments and other third parties that might be monitoring traffic. In this case, the secure protocol also makes it more difficult for ISPs to censor access to certain Wikipedia articles.
In addition to rolling out HTTPS, a process that is expected to be completed within a couple of weeks, Wikimedia also announced the use of HTTP Strict Transport Security (HSTS) to provide protection against attempts to break HTTPS and intercept traffic.
Wikimedia has been working on the implementation of HTTPS for Wikipedia and its other websites since 2011. However, this is not an easy task and there are several challenges that must be overcome, especially in the case of a massively popular website such as Wikipedia.
Throughout the transition process, Wikimedia’s engineering team has had to improve the organization’s infrastructure and code based to ensure that the implementation of HTTPS will not have a negative impact on users.
“We’ve been carefully calibrating our HTTPS configuration to minimize negative impacts related to latency, page load times, and user experience. This was an iterative process that relied on industry standards, a large amount of testing, and our own experience running the Wikimedia sites,” Wikimedia said in a blog post.
Encrypting traffic has been a priority for many organizations following revelations about government surveillance. However, governments have also come to realize the importance of HTTPS.
The White House’s Office of Management and Budget (OMB) announced earlier this month the finalization of a HTTPS-Only Standard for all federal websites and web services. Agencies must ensure that all their publicly accessible resources are migrated to HTTPS-only with HSTS by December 31, 2016.
Eduard Kovacs (@EduardKovacs) is a managing editor at SecurityWeek. He worked as a high school IT teacher for two years before starting a career in journalism as Softpedia’s security news reporter. Eduard holds a bachelor’s degree in industrial informatics and a master’s degree in computer techniques applied in electrical engineering.
More from Eduard Kovacs
- China’s Offensive Cyber Operations in Africa Support Soft Power Efforts
- SANS Survey Shows Drop in 2023 ICS/OT Security Budgets
- Apple Patches 3 Zero-Days Likely Exploited by Spyware Vendor to Hack iPhones
- Cisco to Acquire Splunk for $28 Billion
- Car Cybersecurity Study Shows Drop in Critical Vulnerabilities Over Past Decade
- Omron Patches PLC, Engineering Software Flaws Discovered During ICS Malware Analysis
- Intel Launches New Attestation Service as Part of Trust Authority Portfolio
- Atos Unify Vulnerabilities Could Allow Hackers to Backdoor Systems
Latest News
- Researchers Discover Attempt to Infect Leading Egyptian Opposition Politician With Predator Spyware
- In Other News: New Analysis of Snowden Files, Yubico Goes Public, Election Hacking
- China’s Offensive Cyber Operations in Africa Support Soft Power Efforts
- Air Canada Says Employee Information Accessed in Cyberattack
- BIND Updates Patch Two High-Severity DoS Vulnerabilities
- Faster Patching Pace Validates CISA’s KEV Catalog Initiative
- SANS Survey Shows Drop in 2023 ICS/OT Security Budgets
- Apple Patches 3 Zero-Days Likely Exploited by Spyware Vendor to Hack iPhones
