Risk

10/14/2013
09:33 AM
50%
50%

LinkedIn Preps 'Block User' Capability

Feature will help end online stalkers' pursuit of victims.

When Anna Rihtar began her campaign for LinkedIn to add a block user feature, she was at the beginning of her sales career -- and in the middle of an ongoing stalking nightmare. Sadly, she was far from alone.

Rihtar worked with Change.org to bolster her earlier efforts and began a LinkedIn Privacy/Blocking Petition group on the business-oriented social media site (membership required). When I first wrote about her efforts, many were surprised that LinkedIn didn't already include this capability, which is readily available on many other social networks. All that changed recently when LinkedIn finally agreed to begin working on a block user feature.

Writing in a forum on the LinkedIn privacy group, Paul Rockwell, the company's head of trust and safety, told members that LinkedIn is building a block user feature. Rockwell also pointed participants to the redesigned Safety Center and reminded them about flagging or reporting inappropriate or threatening behavior.

The feature is not out yet, and Rockwell didn't give an estimated timeframe. That left some skeptics among the group's approximately 80 members -- many of whom say they have been stalked online.

Bonny Folkestad, a consultant who has been stalked via LinkedIn, told me in an email:

I don't know if it will change anything, since a trust has been broken. I don't know if I can ever feel safe to be honest. It is a true love/hate relationship. I really think LinkedIn, Pinterest, FaceBook, etc., should all have staff that pay attention to and welcome emails regarding concerns that people might have, that they would take customer service to the virtual world and even investigate complaints. The front end is changing so fast that the back end has to catch up. These companies are making enough money that they can afford to have staffs to protect those that use their sites. They need the ethical hackers to protect us. Actually they can't afford not to.

Read the rest of this article on Internet Evolution.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Weaponizing IPv6 to Bypass IPv4 Security
John Anderson, Principal Security Consultant, Trustwave Spiderlabs,  6/12/2018
'Shift Left' & the Connected Car
Rohit Sethi, COO of Security Compass,  6/12/2018
Why CISOs Need a Security Reality Check
Joel Fulton, Chief Information Security Officer for Splunk,  6/13/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-1060
PUBLISHED: 2018-06-18
python before versions 2.7.15, 3.4.9, 3.5.6 and 3.7.0 is vulnerable to catastrophic backtracking in pop3lib's apop() method. An attacker could use this flaw to cause denial of service.
CVE-2018-1090
PUBLISHED: 2018-06-18
In Pulp before version 2.16.2, secrets are passed into override_config when triggering a task and then become readable to all users with read access on the distributor/importer. An attacker with API access can then view these secrets.
CVE-2018-1152
PUBLISHED: 2018-06-18
libjpeg-turbo 1.5.90 is vulnerable to a denial of service vulnerability caused by a divide by zero when processing a crafted BMP image.
CVE-2018-1153
PUBLISHED: 2018-06-18
Burp Suite Community Edition 1.7.32 and 1.7.33 fail to validate the server certificate in a couple of HTTPS requests which allows a man in the middle to modify or view traffic.
CVE-2018-12530
PUBLISHED: 2018-06-18
An issue was discovered in MetInfo 6.0.0. admin/app/batch/csvup.php allows remote attackers to delete arbitrary files via a flienamecsv=../ directory traversal. This can be exploited via CSRF.