Endpoint //

Privacy

4/30/2018
08:25 PM
50%
50%

WhatsApp Founder to Depart Facebook Amid Privacy, Encryption Dispute

Jan Koum also plans to step down from Facebook's board of directors.

Jan Koum, the founder of WhatsApp who sold his private messaging app to Facebook four years ago for $19 billion, reportedly plans to step down in the wake of increasing concerns over the parent company's intentions for its user data as well efforts to weaken its encryption.

The Washington Post today reported that Koum also will leave his post on Facebook's board of directors. Koum later wrote in a Facebook post that it "is time for me to move on," but did not provide a timeline for his departures or any details.

According to The Post, the recent news of Cambridge Analytica's abuse of Facebook users' data exacerbated Koum's discontent with how Facebook handles user data, given WhatsApp's promise to its users that it would continue to emphasize and protect their privacy and data in the aftermath of the acquisition by Facebook.

Read more here.

Dark Reading's Quick Hits delivers a brief synopsis and summary of the significance of breaking news events. For more information from the original source of the news item, please follow the link provided in this article. View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
4/30/2018 | 8:58:04 PM
Distancing
Not surprising, it seems like it would be prudent to distance yourself from this debacle if you want to look towards future endeavors from a business perspective.
Four Faces of Fraud: Identity, 'Fake' Identity, Ransomware & Digital
David Shefter, Chief Technology Officer at Ziften Technologies,  6/14/2018
Meet 'Bro': The Best-Kept Secret of Network Security
Greg Bell, CEO, Corelight,  6/14/2018
Containerized Apps: An 8-Point Security Checklist
Jai Vijayan, Freelance writer,  6/14/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Flash Poll
New Best Practices for Secure App Development
New Best Practices for Secure App Development
The transition from DevOps to SecDevOps is combining with the move toward cloud computing to create new challenges - and new opportunities - for the information security team. Download this report, to learn about the new best practices for secure application development.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-1120
PUBLISHED: 2018-06-20
A flaw was found affecting the Linux kernel before version 4.17. By mmap()ing a FUSE-backed file onto a process's memory containing command line arguments (or environment strings), an attacker can cause utilities from psutils or procps (such as ps, w) or any other program which makes a read() call t...
CVE-2018-1132
PUBLISHED: 2018-06-20
A flaw was found in Opendaylight's SDNInterfaceapp (SDNI). Attackers can SQL inject the component's database (SQLite) without authenticating to the controller or SDNInterfaceapp. SDNInterface has been deprecated in OpenDayLight since it was last used in the final Carbon series release. In addition t...
CVE-2018-12594
PUBLISHED: 2018-06-20
Reliable Controls MACH-ProWebCom 7.80 devices allow remote attackers to obtain sensitive information via a direct request for the data/fileinfo.xml or job/job.json file, as demonstrated the Master Password field.
CVE-2018-12445
PUBLISHED: 2018-06-20
** DISPUTED ** An issue was discovered in the com.dropbox.android application 98.2.2 for Android. The FingerprintManager class for Biometric validation allows authentication bypass through the callback method from onAuthenticationFailed to onAuthenticationSucceeded with null, because the fingerprint...
CVE-2018-12446
PUBLISHED: 2018-06-20
** DISPUTED ** An issue was discovered in the com.dropbox.android application 98.2.2 for Android. The Passcode feature allows authentication bypass via runtime manipulation that forces a certain method's return value to true. In other words, an attacker could authenticate with an arbitrary passcode....