Risk
10/14/2013
09:33 AM
Connect Directly
RSS
E-Mail
50%
50%
Repost This

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
Cartoon
Current Issue
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2012-0360
Published: 2014-04-23
Memory leak in Cisco IOS before 15.1(1)SY, when IKEv2 debugging is enabled, allows remote attackers to cause a denial of service (memory consumption) via crafted packets, aka Bug ID CSCtn22376.

CVE-2012-1317
Published: 2014-04-23
The multicast implementation in Cisco IOS before 15.1(1)SY allows remote attackers to cause a denial of service (Route Processor crash) by sending packets at a high rate, aka Bug ID CSCts37717.

CVE-2012-1366
Published: 2014-04-23
Cisco IOS before 15.1(1)SY on ASR 1000 devices, when Multicast Listener Discovery (MLD) tracking is enabled for IPv6, allows remote attackers to cause a denial of service (device reload) via crafted MLD packets, aka Bug ID CSCtz28544.

CVE-2012-3062
Published: 2014-04-23
Cisco IOS before 15.1(1)SY, when Multicast Listener Discovery (MLD) snooping is enabled, allows remote attackers to cause a denial of service (CPU consumption or device crash) via MLD packets on a network that contains many IPv6 hosts, aka Bug ID CSCtr88193.

CVE-2012-3918
Published: 2014-04-23
Cisco IOS before 15.3(1)T on Cisco 2900 devices, when a VWIC2-2MFT-T1/E1 card is configured for TDM/HDLC mode, allows remote attackers to cause a denial of service (serial-interface outage) via certain Frame Relay traffic, aka Bug ID CSCub13317.

Best of the Web