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.

SpaceX's Reusable Rockets Win US Air Force General's Endorsement

Slashdot - Wed, 10/18/2017 - 15:00
As the military looks to drive down costs, the head of U.S. Air Force Space Command said he's "completely committed" to launching future missions with recycled rockets like those championed by SpaceX's Elon Musk. "It would be 'absolutely foolish' not to begin using pre-flown rockets, which brings such significant savings that they'll soon be commonplace for the entire industry, General John W. 'Jay' Raymond said," reports Bloomberg. From the report: "The market's going to go that way. We'd be dumb not to," he said. "What we have to do is make sure we do it smartly." The Air Force won't be able to use the recycled boosters until they're certified for military use, a process that Raymond suggested may already be in the works. "The folks out at Space and Missile Systems Center in Los Angeles that work for me would be in those dialogues," he said, declining to specify when certification could take place. "I don't know how far down the road we've gotten, but I am completely committed to launching on a reused rocket, a previously flown rocket, and making sure that we have the processes in place to be able to make sure that we can do that safely."

Read more of this story at Slashdot.

Peer Pressure Forced Whales and Dolphins To Evolve Big Brains Like Humans, Says Study

Slashdot - Wed, 10/18/2017 - 11:30
An anonymous reader quotes a report from Quartz: The human brain has evolved and expanded over millennia to accommodate our ever-more-complex needs and those of our societies. This process is known as "encephalization" and has given us the big brain we need to communicate, cooperate, reach consensus, empathize, and socialize. The same is true for cetaceans, like whales and dolphins, it seems. These sea creatures also grew big brains in order to better live in societies, according to a study published on Oct. 16 in Nature Ecology & Evolution. According to Michael Muthukrishna, an economic psychologist at the London School of Economics and co-author of the study, the researchers used two related theories, the Social-Brain Hypothesis and the Cultural-Brain Hypothesis, to make predictions about various relationships between brain size, societal organization, and the breadth of behaviors the cetaceans would display. Then they tested these predictions by creating and evaluating a comprehensive database of cetacean brain size, social structures, and cultural behaviors across species using data from prior studies on 90 types of whales and dolphins. The study found that cetaceans had complex alliances and communications, played and worked together for mutual benefit, and could even work with other species, like humans. Some also have individual signifiers, sounds that set them apart from others, and can mimic the sounds of others. In addition, it found that brain size predicted the breadth of social and cultural behaviors of these marine creatures (though ecological factors, like prey diversity and latitudinal range, also played a role). The researchers concluded there was a tie between cetacean encephalization, social structure, and group size.

Read more of this story at Slashdot.

Russian Troll Factory Paid US Activists To Fund Protests During Election

Slashdot - Wed, 10/18/2017 - 09:30
bestweasel writes: The Guardian reports on another story about Russian meddling, but interestingly, this one comes from a respected Russian news source, the RBC. From the report: "Russian trolls posing as Americans made payments to genuine activists in the U.S. to help fund protest movements on socially divisive issues. On Tuesday, the newspaper RBC published a major investigation into the work of a so-called Russian 'troll factory' since 2015, including during the period of the U.S. election campaign, disclosures that are likely to put further spotlight on alleged Russian meddling in the election. RBC said it had identified 118 accounts or groups in Facebook, Instagram and Twitter that were linked to the troll factory, all of which had been blocked in August and September this year as part of the U.S. investigation into Russian electoral meddling. Perhaps the most alarming element of the article was the claim that employees of the troll factory had contacted about 100 real U.S.-based activists to help with the organization of protests and events. RBC claimed the activists were contacted by Facebook group administrators hiding their Russian origin and were offered financial help to pay for transport or printing costs. About $80,000 was spent during a two-year period, according to the report."

Read more of this story at Slashdot.

EA Shuts Down Visceral Games, Shifting Development On Its Star Wars Game

Slashdot - Wed, 10/18/2017 - 08:50
Visceral Games, the studio behind games like Battlefield Hardline and Dead Space, is being shut down by EA. The Star Wars game in development at Visceral will be revamped and moved to a different studio. Kotaku reports: "Our Visceral studio has been developing an action-adventure title set in the Star Wars universe," EA's Patrick Soderlund said in a blog post. "In its current form, it was shaping up to be a story-based, linear adventure game. Throughout the development process, we have been testing the game concept with players, listening to the feedback about what and how they want to play, and closely tracking fundamental shifts in the marketplace. It has become clear that to deliver an experience that players will want to come back to and enjoy for a long time to come, we needed to pivot the design." Soderlund added that Visceral will be "ramping down and closing" and that "we're in the midst of shifting as many of the team as possible to other projects and teams at EA." "Lastly," he said, "while we had originally expected this game to launch late in our fiscal year 2019, we're now looking at a new timeframe that we will announce in the future."

Read more of this story at Slashdot.

Oracle Releases Security Bulletin

US-CERT - Wed, 10/18/2017 - 08:40
Original release date: October 17, 2017

Oracle has released its Critical Patch Update for October 2017 to address 252 vulnerabilities across multiple products. A remote attacker could exploit some of these vulnerabilities to take control of an affected system.

Users and administrators are encouraged to review the Oracle October 2017 Critical Patch Update and apply the necessary updates.

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


IC3 Issues Alert on DDoS Attacks

US-CERT - Wed, 10/18/2017 - 08:39
Original release date: October 17, 2017

The Internet Crime Complaint Center (IC3) has issued an alert on distributed denial-of-service (DDoS)-for-hire services advertised on criminal forums and marketplaces. Using DDoS attacks to prevent legitimate users from accessing websites or information can lead to serious consequences.

US-CERT encourages users and administrators to review the IC3 Alert for more information and US-CERT's Alert on Heightened DDoS Threat Posed by Mirai and Other Botnets.

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


ZTE Launches Axon M, a Foldable, Dual-Screened Smartphone

Slashdot - Wed, 10/18/2017 - 08:10
ZTE's new Axon M is a full-featured smartphone with a hinge that connects two full-size displays, making the Axon M a flip phone of sorts. "Its front screen is a 5.2-inch, 1080p panel, it has last year's Qualcomm Snapdragon 821 processor, 4GB of RAM, and a 20-megapixel camera," reports The Verge. "But flip the phone over and there's an identical 5.2-inch display on the back, making the Axon M anything but run-of-the-mill." From the report: The M's hinge allows the rear screen to flip forward and slot right next to the main display, creating an almost tablet sized canvas. You can stretch the home screen and apps across the two displays for a larger working area, or you can run two different apps at the same time, one on each screen. You can also "tent" the phone, and mirror the displays so two people can see the same content at the same time. ZTE says that it is utilizing Android's default split-screen features to enable many of the dual-screen functions, and it has made sure the "top 100" Android apps work on the phone. In the "extended" mode, which stretches a single app across both screens, the tablet version of the app is presented (provided there is one, which isn't always a guarantee with Android apps). It's even possible to stream video on both screens at the same time and switch the audio between them on the fly, which might be useful if you want to watch a sports game and YouTube at the same time, I guess.

Read more of this story at Slashdot.

Vuln: lcms2 CVE-2016-10165 Out-of-Bounds Read Denial of Service Vulnerability

SecurityFocus Vulnerabilities/Bugtraq - Wed, 10/18/2017 - 08:00
lcms2 CVE-2016-10165 Out-of-Bounds Read Denial of Service Vulnerability

Vuln: Apache Xalan-Java Library CVE-2014-0107 Security Bypass Vulnerability

SecurityFocus Vulnerabilities/Bugtraq - Wed, 10/18/2017 - 08:00
Apache Xalan-Java Library CVE-2014-0107 Security Bypass Vulnerability

Vuln: GNU glibc CVE-2015-0235 Remote Heap Buffer Overflow Vulnerability

SecurityFocus Vulnerabilities/Bugtraq - Wed, 10/18/2017 - 08:00
GNU glibc CVE-2015-0235 Remote Heap Buffer Overflow Vulnerability

Vuln: Apache Groovy CVE-2015-3253 Remote Code Execution Vulnerability

SecurityFocus Vulnerabilities/Bugtraq - Wed, 10/18/2017 - 08:00
Apache Groovy CVE-2015-3253 Remote Code Execution Vulnerability

'Significant' Number of Equifax Victims Already Had Info Stolen, Says IRS

Slashdot - Wed, 10/18/2017 - 07:30
An anonymous reader quotes a report from The Hill: The IRS does not expect the Equifax data breach to have a major effect on the upcoming tax filing season, Commissioner John Koskinen said Tuesday, adding that the agency believes a "significant" number of the victims already had their information stolen by cyber criminals. "We actually think that it won't make any significantly or noticeable difference," Koskinen told reporters during a briefing on the agency's data security efforts. "Our estimate is a significant percent of those taxpayers already had their information in the hands of criminals." The IRS estimates that more than 100 million Americans have had their personally identifiable information stolen by criminal hackers, he said. The Equifax breach disclosed in early September is estimated to have affected more than 145 million U.S. consumers. "It's an important reminder to the public that everyone can take any actions that they can ... to make sure we can do everything we can to protect personal information," Koskinen said of the breach on Tuesday, in response to a reporter's question. The IRS commissioner advised Americans to "assume" their data is already in the hands of criminals and "act accordingly."

Read more of this story at Slashdot.

IC3 Issues Alert on IoT Devices

US-CERT - Wed, 10/18/2017 - 06:56
Original release date: October 17, 2017

In conjunction with National Cyber Security Awareness Month, the Internet Crime Complaint Center (IC3) has issued an alert to individuals and businesses about the security risks involved with the Internet of Things (IoT). IoT refers to the emerging network of devices (e.g., smart TVs, home automation systems) that connect to one another via the Internet, often automatically sending and receiving data. IC3 warns that once a device is compromised, an attacker may take control of an affected system, obtain sensitive information, or cause a denial-of-service condition.

US-CERT encourages individuals and businesses to review the IC3 Alert for more information on IoT vulnerabilities and mitigation techniques.

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


Android Oreo Helps Google's Pixel 2 Smartphones Outperform Other Android Flagships

Slashdot - Wed, 10/18/2017 - 06:50
MojoKid highlights Hot Hardware's review of Google's new Pixel 2 and Pixel 2 XL smartphones: Google officially launched it's Pixel 2 phones today, taking the wraps off third-party reviews. Designed by Google but manufactured by HTC (Pixel 2) and LG (Pixel 2 XL), the two new handsets also boast Google's latest Android 8.0 operating system, aka Oreo, an exclusive to Google Pixel and certain Nexus devices currently. And in some ways, this is also a big advantage. Though they are based on the same Qualcomm Snapdragon 835 processor as many other Android devices, Google's new Pixel 2s manage to outpace similarly configured smartphones in certain benchmarks by significant margins (Basemark, PCMark and 3DMark). They also boot dramatically faster than any other Android handset on the market, in as little as 10 seconds. Camera performance is also excellent, with both the 5-inch Pixel 2 and 6-inch Pixel 2 XL sporting identical electronics, save for their displays and chassis sizes. Another notable feature built into Android Oreo is Google Now Playing, an always-listening, Shazam-like service (if you enable it) that displays song titles on the lock screen if it picks up on music playing in the room you're in. Processing is done right on the Pixel 2 and it doesn't need network connectivity. Another Pixel 2 Oreo-based trick is Google Lens, a machine vision system that Google notes "can recognize places like landmarks and buildings, artwork that you'd find in a museum, media covers such as books, movies, music albums, and video games..." The Google Pixel 2 and Pixel 2 XL are available now on Verizon or unlocked via the Google Store starting at $649 and $849 respectively for 64GB storage versions, with a $100 up-charge for 128GB variants.

Read more of this story at Slashdot.

Google Maps Ditches Walking Calorie Counter After Backlash

Slashdot - Wed, 10/18/2017 - 06:10
Following online backlash, Google is removing a planned feature in Maps that shows you how many calories you'd burn when in walking mode. Google's attempt to promote a healthy lifestyle caused a number of people to lambast the feature on Twitter, claiming it would "shame" and even "trigger" those with eating disorders. Engadget reports: Taking note of the negative reaction, Google is now dumping the experiment. It confirmed to Engadget that the update was briefly tested on iOS, and has been abandoned based on user feedback. As The Hill's Taylor Lorenz noted in her tweets, there was no way to turn off the feature. Lorenz also claimed that using pink cupcakes as the unit of measurement was "lowkey aimed at women." Others pointed out that Maps wasn't the appropriate place for the update. After all, there are plenty of fitness and calorie counting apps that keep track of your activity and consumption -- again emphasizing how misplaced the feature was.

Read more of this story at Slashdot.

Netflix, Amazon, Movie Studios Sue Over TickBox Streaming Device

Slashdot - Wed, 10/18/2017 - 05:30
Movies studios, Netflix, and Amazon have teamed up to file a lawsuit against a streaming media player called TickBox TV. The device in question runs Kodi on top of Android 6.0, and searches the internet for streams that it can make available to users without actually hosting any of the content itself. An anonymous reader quotes a report from Ars Technica: The complaint (PDF), filed Friday, says the TickBox devices are nothing more than "tool[s] for mass infringement," which operate by grabbing pirated video streams from the Internet. The lawsuit was filed by Amazon and Netflix Studios, along with six big movie studios that make up the Motion Picture Association of America: Universal, Columbia, Disney, Paramount, 20th Century Fox, and Warner Bros. "What TickBox actually sells is nothing less than illegal access to Plaintiffs' copyrighted content," write the plaintiffs' lawyers. "TickBox TV uses software to link TickBox's customers to infringing content on the Internet. When those customers use TickBox TV as Defendant intends and instructs, they have nearly instantaneous access to multiple sources that stream Plaintiffs' Copyrighted Works without authorization." The device's marketing materials let users know the box is meant to replace paid-for content, with "a wink and a nod," by predicting that prospective customers who currently pay for Amazon Video, Netflix, or Hulu will find that "you no longer need those subscriptions." The lawsuit shows that Amazon and Netflix, two Internet companies that are relatively new to the entertainment business, are more than willing to join together with movie studios to go after businesses that grab their content.

Read more of this story at Slashdot.

Intel Aims To Take on Nvidia With a Processor Specially Designed for AI

Slashdot - Wed, 10/18/2017 - 04:55
An anonymous reader shares a report: In what looks like a repeat of its loss to Qualcomm on smartphones, Intel has lagged graphics chip (GPU) maker Nvidia in the artificial intelligence revolution. Today Intel announced that its first AI chip, the Nervana Neural Network Processor, will roll out of factories by year's end. Originally called Lake Crest, the chip gets its name from Nervana, a company Intel purchased in August 2016, taking on the CEO, Naveen Rao, as Intel's AI guru. Nervana is designed from the ground up for machine learning, Rao tells me. You can't play Call of Duty with it. Rao claims that ditching the GPU heritage made room for optimizations like super-fast data interconnections allowing a bunch of Nervanas to act together like one giant chip. They also do away with the caches that hold data the processor might need to work on next. "In neural networks... you know ahead of time where the data's coming from, what operation you're going to apply to that data, and where the output is going to," says Rao.

Read more of this story at Slashdot.

Bugtraq: [security bulletin] MFSBGN03786 rev.1 - HPE Connected Backup, Local Escalation of Privilege

SecurityFocus Vulnerabilities/Bugtraq - Wed, 10/18/2017 - 00:00
[security bulletin] MFSBGN03786 rev.1 - HPE Connected Backup, Local Escalation of Privilege

Bugtraq: Advisory X41-2017-010: Command Execution in Shadowsocks-libev

SecurityFocus Vulnerabilities/Bugtraq - Wed, 10/18/2017 - 00:00
Advisory X41-2017-010: Command Execution in Shadowsocks-libev

Microsoft Responded Quietly After Detecting Secret Database Hack in 2013

Slashdot - Tue, 10/17/2017 - 23:20
Citing five former employees, Reuters reported on Tuesday that Microsoft's secret internal database for tracking bugs in its own software was broken into by a highly sophisticated hacking group more than four years ago. From the report: The company did not disclose the extent of the attack to the public or its customers after its discovery in 2013, but the five former employees described it to Reuters in separate interviews. Microsoft declined to discuss the incident. The database contained descriptions of critical and unfixed vulnerabilities in some of the most widely used software in the world, including the Windows operating system. Spies for governments around the globe and other hackers covet such information because it shows them how to create tools for electronic break-ins. The Microsoft flaws were fixed likely within months of the hack, according to the former employees. Yet speaking out for the first time, these former employees as well as U.S. officials informed of the breach by Reuters said it alarmed them because the hackers could have used the data at the time to mount attacks elsewhere, spreading their reach into government and corporate networks. "Bad guys with inside access to that information would literally have a 'skeleton key' for hundreds of millions of computers around the world," said Eric Rosenbach, who was U.S. deputy assistant secretary of defense for cyber at the time.

Read more of this story at Slashdot.

Syndicate content