Risk
10/14/2013
09:33 AM
Connect Directly
RSS
E-Mail
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
Register for Dark Reading Newsletters
White Papers
Flash Poll
Current Issue
Cartoon
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-0972
Published: 2014-08-01
The kgsl graphics driver for the Linux kernel 3.x, as used in Qualcomm Innovation Center (QuIC) Android contributions for MSM devices and other products, does not properly prevent write access to IOMMU context registers, which allows local users to select a custom page table, and consequently write ...

CVE-2014-2627
Published: 2014-08-01
Unspecified vulnerability in HP NonStop NetBatch G06.14 through G06.32.01, H06 through H06.28, and J06 through J06.17.01 allows remote authenticated users to gain privileges for NetBatch job execution via unknown vectors.

CVE-2014-3009
Published: 2014-08-01
The GDS component in IBM InfoSphere Master Data Management - Collaborative Edition 10.0 through 11.0 and InfoSphere Master Data Management Server for Product Information Management 9.0 and 9.1 does not properly handle FRAME elements, which makes it easier for remote authenticated users to conduct ph...

CVE-2014-3302
Published: 2014-08-01
user.php in Cisco WebEx Meetings Server 1.5(.1.131) and earlier does not properly implement the token timer for authenticated encryption, which allows remote attackers to obtain sensitive information via a crafted URL, aka Bug ID CSCuj81708.

CVE-2014-3534
Published: 2014-08-01
arch/s390/kernel/ptrace.c in the Linux kernel before 3.15.8 on the s390 platform does not properly restrict address-space control operations in PTRACE_POKEUSR_AREA requests, which allows local users to obtain read and write access to kernel memory locations, and consequently gain privileges, via a c...

Best of the Web
Dark Reading Radio