Feed aggregator

  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.

Vuln: Lenovo VIBE Mobile CVE-2017-3748 Local Privilege Escalation Vulnerability

Lenovo VIBE Mobile CVE-2017-3748 Local Privilege Escalation Vulnerability

Petya Ransomware Outbreak Originated In Ukraine Via Tainted Accounting Software

Slashdot - Wed, 06/28/2017 - 07:20
An anonymous reader quotes a report from Bleeping Computer: Today's massive ransomware outbreak was caused by a malicious software update for M.E.Doc, a popular accounting software used by Ukrainian companies. According to several researchers, such as Cisco Talos, ESET, MalwareHunter, Kaspersky Lab, and others, an unknown attacker was able to compromise the software update mechanism for M.E.Doc's servers, and deliver a malicious update to customers. When the update reached M.E.Doc's customers, the tainted software packaged delivered the Petya ransomware -- also referenced online as NotPetya, or Petna. The Ukrainian software vendor appears to have inadvertently confirmed that something was wrong when, this morning, issued a security advisory. Hours later, as the ransomware outbreak spread all over Ukraine and other countries across the globe causing huge damages, M.E.Doc denied on Facebook its servers ever served any malware. According to security researcher MalwareHunter, this is not the first time M.E.Doc has carried a malicious software update that delivered ransomware. Back in May, the company's software update mechanism also helped spread the XData ransomware.

Read more of this story at Slashdot.

Police Use Lyft As 'Trojan Horse' To Capture Suspect In Murder of Tech CEO

Slashdot - Wed, 06/28/2017 - 06:40
McGruber writes: On Friday, June 23, 2017, three men broke into the home of Albert Eugene DeMagnus, the CEO of Computer Management Services. The men stabbed DeMangus, who was pronounced dead after he had been taken to a hospital. Police officers chased two of the suspects as they fled in DeMangus' gray Lexus. The Lexus crashed and the two men ran away into the woods. Police then set up a perimeter with road checkpoints. Soon, a Lyft driver approached a checkpoint and told police she was picking up a passenger nearby. "This may be one of our suspects trying to leave the scene," Fayette County, Georgia Sheriff Barry Babb thought of the person being picked up. So Babb and three officers got into his car, which happened to be identical to the Lyft driver's. They got the location of the suspect from the Lyft driver and simply drove to the suspect, posing as his ride. "The subject walked all the way up, was about to open the door and get in our vehicle, when we exited and identified ourself," said Sheriff Babb. The suspect fled and got about 100 yards into the woods before being taken into custody. "That was something that was unique for us," Babb said, "a first time for us."

Read more of this story at Slashdot.

Multiple Petya Ransomware Infections Reported

US-CERT - Wed, 06/28/2017 - 00:56
Original release date: June 27, 2017

US-CERT has received multiple reports of Petya ransomware infections in many countries around the world. Ransomware is a type of malicious software that infects a computer and restricts users' access to the infected machine until a ransom is paid to unlock it. Individuals and organizations are discouraged from paying the ransom, as this does not guarantee that access will be restored. Using unpatched and unsupported software may increase the risk of proliferation of cybersecurity threats, such as ransomware.

Petya ransomware encrypts the master boot records of infected Windows computers, making affected machines unusable. Open-source reports indicate that the ransomware exploits vulnerabilities in Server Message Block (SMB). US-CERT encourages users and administrators to review the US-CERT article on the Microsoft SMBv1 Vulnerability and the Microsoft Security Bulletin MS17-010. For general advice on how to best protect against ransomware, review US-CERT Alert TA16-091A. Please report any ransomware incidents to the Internet Crime Complaint Center (IC3).

This product is provided subject to this Notification and this Privacy & Use policy.


Bugtraq: [CVE-2017-8831] Double-Fetch Vulnerability in Linux-4.10.1/drivers/media/pci/saa7164/saa7164-bus.c

SecurityFocus Vulnerabilities/Bugtraq - Wed, 06/28/2017 - 00:00
[CVE-2017-8831] Double-Fetch Vulnerability in Linux-4.10.1/drivers/media/pci/saa7164/saa7164-bus.c

Bugtraq: DefenseCode Security Advisory: IBM DB2 Command Line Processor Buffer Overflow

SecurityFocus Vulnerabilities/Bugtraq - Wed, 06/28/2017 - 00:00
DefenseCode Security Advisory: IBM DB2 Command Line Processor Buffer Overflow

The New iPad Pro Review

Slashdot - Tue, 06/27/2017 - 23:20
An anonymous reader writes: As tech reviewers across the United States and Europe sing praises of Apple's new iPad Pro, here's what Joshua Topolsky, former editor-in-chief of The Verge and Engadget (and now with The Outline) had to say: "It [10.5-inch iPad Pro] is inferior to a laptop in almost every way, unless you like to draw. If you think you can replace you laptop with this setup: you cannot. Imagine a computer, but everything works worse than you expect. That is the new iPad. Now, I know the software is in beta, but I also know how Apple betas work. They don't massively change. I have no doubt it's a very powerful piece of hardware, and the screen is gorgeous. Garageband is a lot of fun to play with. But this doesn't COME CLOSE to replacing your laptop, even for simple things you do, like email. AND one other thing. Apple's keyboard cover is a fucking atrocity. A terrible piece of hardware. Awkward to use, poor as a cover. Okay in a pinch if you need something LIKE a keyboard. Anyhow good to know there are still Apple fanboys who get mad if you insult their products. But I don't think it's a very good product. Finally, iOS 11 is definitely a STEP in the right direction. But guys the iPad has been around forever and it still feels half-assed. I think a lot of people are willing to contort themselves around a bad UX because marketing is powerful."

Read more of this story at Slashdot.

Ukrainian Banks, Electricity Firm Hit by Fresh Cyber Attack; Reports Claim the Ransomware Is Quickly Spreading Across the World

Slashdot - Tue, 06/27/2017 - 22:34
A massive cyber attack has disrupted businesses and services in Ukraine on Tuesday, bringing down the government's website and sparking officials to warn that airline flights to and from the country's capital city Kiev could face delays. Motherboard reports that the ransomware is quickly spreading across the world. From a report: A number of Ukrainian banks and companies, including the state power distributor, were hit by a cyber attack on Tuesday that disrupted some operations (a non-paywalled source), the Ukrainian central bank said. The latest disruptions follow a spate of hacking attempts on state websites in late-2016 and repeated attacks on Ukraine's power grid that prompted security chiefs to call for improved cyber defences. The central bank said an "unknown virus" was to blame for the latest attacks, but did not give further details or say which banks and firms had been affected. "As a result of these cyber attacks these banks are having difficulties with client services and carrying out banking operations," the central bank said in a statement. BBC reports that Ukraine's aircraft manufacturer Antonov, two postal services, Russian oil producer Rosneft and Danish shipping company Maersk are also facing "disruption, including its offices in the UK and Ireland." According to local media reports, the "unknown virus" cited above is a ransomware strain known as Petya.A. Here's how Petya encrypts files on a system (video). News outlet Motherboard reports that Petya has hit targets in Spain, France, Ukraine, Russia, and other countries as well. From the report: "We are seeing several thousands of infection attempts at the moment, comparable in size to Wannacry's first hours," Costin Raiu, a security researcher at Kaspersky Lab, told Motherboard in an online chat. Judging by photos posted to Twitter and images provided by sources, many of the alleged attacks involved a piece of ransomware that displays red text on a black background, and demands $300 worth of bitcoin. "If you see this text, then your files are no longer accessible, because they are encrypted," the text reads, according to one of the photos. "Perhaps you are busy looking for a way to recover your files, but don't waste your time. Nobody can recover your files without our decryption service."

Read more of this story at Slashdot.

Google Slapped With $2.7 Billion By EU For Skewing Searches

Slashdot - Tue, 06/27/2017 - 22:00
Google suffered a major regulatory blow on Tuesday after European antitrust officials fined the search giant 2.4 billion euros, or $2.7 billion, for unfairly favoring some of its own search services over those of rivals. The European Commission concluded that the search giant abused its near-monopoly in online search to "give illegal advantage" to its own Shopping service. Margrethe Vestager, the EU's competition commissioner, said Google "denied other companies the chance to compete" and left consumers without "genuine choice." The hefty fine marks the latest chapter in a lengthy standoff between Europe and Google, which also faces two separate charges under the region's competition rules related to Android, its popular mobile software, and to some of its advertising products. From a report: Google has 90 days to "stop its illegal conduct" and give equal treatment to rival price-comparison services, according to a binding order from the European Commission on Tuesday. It's up to Google to choose how it does this and it must tell the EU within 60 days of its plans. Failure to comply brings a risk of fines of up to 5 percent of its daily revenue. [...] "I expect the Commission now to swiftly conclude the other two ongoing investigations against Google," Markus Ferber, a member of the European Parliament from Germany. "Unfortunately, the Google case also illustrates that competition cases tend to drag on for far too long before they are eventually resolved. In a fast-moving digital economy this means often enough that market abuse actually pays off and the abuser succeeds in eliminating the competition." Google has been pushing its own comparison shopping service since 2008, systematically giving it prominent placement when people search for an item, the EU said. Rival comparison sites usually only appear on page four of search results, effectively denying them a massive audience as the first page attracts 95 percent of all clicks. In a blog post, Google said the EU has "underestimated" the value Google's services brings to the table. "We believe the European Commission's online shopping decision underestimates the value of those kinds of fast and easy connections. While some comparison shopping sites naturally want Google to show them more prominently, our data show that people usually prefer links that take them directly to the products they want, not to websites where they have to repeat their searches. We think our current shopping results are useful and are a much-improved version of the text-only ads we showed a decade ago. Showing ads that include pictures, ratings, and prices benefits us, our advertisers, and most of all, our users. And we show them only when your feedback tells us they are relevant. Thousands of European merchants use these ads to compete with larger companies like Amazon and eBay. [...] Given the evidence, we respectfully disagree with the conclusions announced today. We will review the Commission's decision in detail as we consider an appeal, and we look forward to continuing to make our case," wrote Kent Walker, SVP and General Counsel at Google.

Read more of this story at Slashdot.

Amazon Robots Poised To Revamp How Whole Foods Runs Warehouses

Slashdot - Tue, 06/27/2017 - 21:00
After Amazon announced it would buy Whole Foods Market for $13.7 billion earlier this month, John Mackey, Whole Foods' chief executive officer, rejoiced and reportedly gushed about Amazon's technological innovation. "We will be joining a company that's visionary," Mackey said. "I think we're gonna get a lot of those innovations in our stores. I think we're gonna see a lot of technology. I think you're gonna see Whole Foods Market evolve in leaps and bounds." Specifically, Mackey is talking about the thousands of delivery robots Amazon uses in its facilities. Bloomberg reports: In negotiations, Amazon spent a lot of time analyzing Whole Foods' distribution technology, pointing to a possible way in which the company sees the most immediate opportunities to reduce costs, said a person familiar with the matter who asked not to be identified because the issue was private. Experts say the most immediate changes would likely be in warehouses that customers never see. That suggests the jobs that could be affected the earliest would be in the warehouses, where products from suppliers await transport to store shelves, said Gary Hawkins, CEO of the Center for Advancing Retail and Technology, a Los Angeles nonprofit that helps retailers and brands innovate. As Amazon looks to automate distribution, cashiers will be safe -- for now. Amazon sees automation as a key strategic advantage in its overall grocery strategy, according to company documents reviewed by Bloomberg before the Whole Foods acquisition was announced. Whole Foods has 11 distribution centers specializing in perishable foods that serve its stores. It also has seafood processing plants, kitchens and bakeries that supply prepared food to each location. Those are the places where Amazon could initially focus, according to experts. While the company said it has no current plans to automate the jobs of cashiers in Whole Foods stores after it finishes acquiring the grocery chain, it's likely only a matter of time before cashier positions become automated. According to Bloomberg's report, Amazon may bring the robots to the stores after automating Whole Foods' warehouses. "The first ones will likely navigate aisles to check inventory and alert employees when items run low, said Austin Bohlig, an advisor at Loup Ventures, which invests in robotics startups," reports Bloomberg.

Read more of this story at Slashdot.

New Study Confirms the Oceans Are Warming Rapidly

Slashdot - Tue, 06/27/2017 - 18:00
An anonymous reader shares a report from The Guardian, written by John Abraham, who discusses the rising ocean temperatures and the important factors that affect ocean-temperature accuracy: The most important measurement of global warming is in the oceans. In fact, "global warming" is really "ocean warming." If you are going to measure the changing climate of the oceans, you need to have many sensors spread out across the globe that take measurements from the ocean surface to the very depths of the waters. Importantly, you need to have measurements that span decades so a long-term trend can be established. These difficulties are tackled by oceanographers, and a significant advancement was presented in a paper just published in the journal Climate Dynamics. That paper, which I was fortunate to be involved with, looked at three different ocean temperature measurements made by three different groups. We found that regardless of whose data was used or where the data was gathered, the oceans are warming. In the paper, we describe perhaps the three most important factors that affect ocean-temperature accuracy. First, sensors can have biases (they can be "hot" or "cold"), and these biases can change over time. Another source of uncertainty is related to the fact that we just don't have sensors at all ocean locations and at all times. Some sensors, which are dropped from cargo ships, are densely located along major shipping routes. Other sensors, dropped from research vessels, are also confined to specific locations across the globe. Finally, temperatures are usually referenced to a baseline "climatology." So, when we say temperatures have increased by 1 degree, it is important to say what the baseline climatology is. Have temperatures increased by 1 degree since the year 1990? Since the year 1970? Since 1900? The choice of baseline climatology really matters.

Read more of this story at Slashdot.

Physicists Have Created the Brightest Light Ever Recorded

Slashdot - Tue, 06/27/2017 - 15:00
Jason Koebler writes: A group of physicists at the University of Nebraska-Lincoln's Extreme Light Laboratory announced Monday that they have created the brightest light ever produced on Earth using Diocles, one of the most powerful lasers in the United States. When this high intensity laser pulse, which is one billion times brighter than the surface of the sun, strikes the electron, it causes it to behave differently. By firing this laser at individual electrons, the researchers found that past a certain threshold, the brightness of light will actually change an object's appearance rather than simply making it brighter. The x-rays that are produced in this fashion have an extremely high amount of energy, and Umstadter and his colleagues think this could end up being applied in a number of ways. For starters, it could allow doctors to produce x-ray medical images on the nanoscale, which would allow them to detect tumors and other anomalies that regular x-rays might have missed. Moreover, it could also be used for more sophisticated x-ray scanning at airports and other security checkpoints.

Read more of this story at Slashdot.

Social Media Giants Step Up Joint Fight Against Extremist Content

Slashdot - Tue, 06/27/2017 - 11:33
Social media giants Facebook, Google's YouTube, Twitter and Microsoft said on Monday they were forming a global working group to combine their efforts to remove terrorist content from their platforms. From a report: Responding to pressure from governments in Europe and the United States after a spate of militant attacks, the companies said they would share technical solutions for removing terrorist content, commission research to inform their counter-speech efforts and work more with counter-terrorism experts. The Global Internet Forum to Counter Terrorism "will formalize and structure existing and future areas of collaboration between our companies and foster cooperation with smaller tech companies, civil society groups and academics, governments and supra-national bodies such as the EU and the UN," the companies said in a statement.

Read more of this story at Slashdot.

NIST Releases New Digital Identity Guidelines

US-CERT - Tue, 06/27/2017 - 10:48
Original release date: June 26, 2017

The National Institute of Standards and Technology (NIST) has released the Digital Identity Guidelines document suite. The four-volume suite offers technical guidelines for organizations that use digital identity services.

US-CERT encourages information security practitioners in industry, government, and academic organizations to refer to the NIST blog post and SP 800-63 for more information.

This product is provided subject to this Notification and this Privacy & Use policy.


New Study Explains Why Trump's 'Sad' Tweets Are So Effective

Slashdot - Tue, 06/27/2017 - 10:05
An anonymous reader quotes a report from The Verge: During his campaign and presidency, Donald Trump has used Twitter to circumvent traditional media broadcasters and speak directly to the masses. He is particularly known for one specific tweet construction: he sets up a situation that he feels should inspire anger or outrage, then punctuates it with "Sad!" New research from New York University suggests a reason why this style is so effective: a tweet containing moral and emotional language spreads farther among people with similar political persuasion. The study offered up "duty" as an example of a purely moral word, "fear" as a purely emotional one, and "hate" as word that combined the two categories. The research found that the use of purely moral or purely emotional language had a limited impact on the spread of a tweet, but the "presence of moral-emotional words in messages increased their diffusion by a factor of 20% for each additional word." The impact of this language cut both ways. Tweets with moral-emotional words spread further among those with a similar political outlook, and they spread less with those who held opposing views, according to the research published in the journal PNAS. The study looked at 563,312 tweets on the topics of gun control, same-sex marriage, and climate change, and rated their impact by the number of retweets each one received.

Read more of this story at Slashdot.

Zillow Threatens To Sue Blogger For Using Its Photos For Parody

Slashdot - Tue, 06/27/2017 - 09:25
Kate Wagner is facing potential legal charges by real estate Zillow for allegedly violating the site's terms of service by reproducing images from their site on her blog. Wagner's blog is called McMansion Hell -- a Tumblr blog that "highlights the absurdity of giant real estate properties and the ridiculous staging and photography that are omnipresent in their sales listings," writes Natt Garun via The Verge. From the report: A typical McMansion Hell blog post will have a professional photo of a home and / or its interior, along with captions scattered throughout by Wagner. She also adds information about the history and characteristics of various architecture styles, and uses photos from the likes of Zillow and Redfin to illustrate how so many real estate listings inaccurately use the terms. Under each post, Wagner adds a disclaimer that credits the original source of the images and cites Fair Use for the parody, which allows for use of copyrighted material for "criticism, comment, news reporting, teaching, scholarship, and research." In a cease and desist letter to Wagner, Zillow claims Wagner's reproduction of these images do not apply under the Copyright Act. Additionally, the company claims McMansion Hell may "[interfere] with Zillow's business expectations and interests." As a result of the potential lawsuit, Wagner has temporarily taken McMansionHell.com down. In a statement to The Verge, Zillow said: "Zillow has a legal obligation to honor the agreements we make with our listing providers about how photos can be used. We are asking this blogger to take down the photos that are protected by copyright rules, but we did not demand she shut down her blog and hope she can find a way to continue her work."

Read more of this story at Slashdot.

China, Canada Vow Not To Conduct Cyberattacks On Private Sector

Slashdot - Tue, 06/27/2017 - 08:45
New submitter tychoS writes from a report via Reuters: China and Canada have signed an agreement vowing not to conduct state-sponsored cyberattacks against each other aimed at stealing trade secrets or other confidential business information. The new agreement was reached during talks between Canada's national security and intelligence adviser, Daniel Jean, and senior communist party official Wang Yongqing, a statement dated June 22 on the Canadian government's website showed. "This is something that three or four years ago (Beijing) would not even have entertained in the conversation," an unnamed Canadian government official told the Globe and Mail, which first reported the agreement. The new agreement only covers economic cyber-espionage, which includes hacking corporate secrets and proprietary technology, but does not deal with state-sponsored cyber spying for intelligence gathering.

Read more of this story at Slashdot.

'Infarm' Startup Wants To Put a Farm In Every Grocery Store

Slashdot - Tue, 06/27/2017 - 08:05
Infarm, a 40-plus person startup based in Berlin, imagines a future where every grocery store has its own farm packed with herbs, vegetables and fruit. "The plants themselves are being monitored by multiple sensors and fed by an internet-controlled irrigation and nutrition system," reports TechCrunch. "Growing out from the center, the basil is at ascending stages of its life, with the most outer positioned ready for you, the customer, to harvest." From the report: The concept might not be entirely new -- Japan has been an early pioneer in vertical farming, where the lack of space for farming and very high demand from a large population has encouraged innovation -- but what potentially sets Infarm apart, including from other startups, is the modular approach and go-to-market strategy it is taking. This means that the company can do vertical farming on a small but infinitely expandable scale, and is seeing Infarm place farms not in offsite warehouses but in customer-facing city locations, such as grocery stores, restaurants, shopping malls, and schools, enabling the end-customer to actually pick the produce themselves. In contrast, the Infarm system is chemical pesticide-free and can prioritize food grown for taste, color and nutritional value rather than shelf life or its ability to sustain mass production. Its indoor nature means it isn't restricted to seasonality either and by completely eliminating the distance between farmer and consumer, food doesn't get much fresher. When a new type of herb or plant is introduced, Infarm's plant experts and engineers create a recipe or algorithm for the produce type, factoring in nutrition, humidity, temperature, light intensity and spectrum, which is different from system to system depending on what is grown. The resulting combination of IoT, Big Data and cloud analytics is akin to "Farming-as-a-Service," whilst , space permitting, Infarm's modular approach affords the ability to keep adding more farming capacity in a not entirely dissimilar way to how cloud computing can be ramped up at the push of a button.

Read more of this story at Slashdot.

Vuln: IBM DB2 CVE-2017-1297 Local Buffer Overflow Vulnerability

SecurityFocus Vulnerabilities/Bugtraq - Tue, 06/27/2017 - 08:00
IBM DB2 CVE-2017-1297 Local Buffer Overflow Vulnerability

Vuln: Cisco AnyConnect Secure Mobility Client CVE-2017-6638 Local Privilege Escalation Vulnerability

SecurityFocus Vulnerabilities/Bugtraq - Tue, 06/27/2017 - 08:00
Cisco AnyConnect Secure Mobility Client CVE-2017-6638 Local Privilege Escalation Vulnerability
Syndicate content