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.

Project Fi Creates Its Own Version of An Unlimited Plan

Slashdot - Thu, 01/18/2018 - 06:50
Google's Project Fi mobile virtual network operator (MVNO) has launched a new feature called Bill Protection that will cap your $10 per GB data bill at $60 a month, while still allowing you to use as much data as you want, essentially creating its own version of an unlimited data plan. The Verge reports: Prior to today, Project Fi users were charged $10 per GB no matter how much data they used, which could become quite costly for heavy users. Bill Protection should help alleviate those worries for most users. Google says those who use up to 15GB of data in a month won't experience any throttling, but if they cross that threshold -- Google says less than 1 percent of its users pass that mark -- they will "experience slower data" with speeds going down to 256kbps. If you don't want to be throttled when you pass 15GB in a month, Google says you can pay the usual $10 per GB to opt out of the slower speeds. It also noted that Bill Protection for Project Fi users on group plans will kick in at different usage levels, depending on the size of your group.

Read more of this story at Slashdot.

Meteor Lights Up Southern Michigan

Slashdot - Thu, 01/18/2018 - 06:10
New submitter Foundryman writes: Amidst fake missile reports in Hawaii and Japan, Michigan gets hit by something real. From a report via Ars Technica: "Early last night local time, a meteor rocketed through the skies of southern Michigan, giving local residents a dramatic (if brief) light show. It also generated an imperceptible thump, as the U.S. Geological Survey confirmed that there was a coincident magnitude 2.0 earthquake. The American Meteor Society has collected more than 350 eyewitness accounts, which ranged from western Pennsylvania out to Illinois and Wisconsin. They were heavily concentrated over southern Michigan, notably around the Detroit area. A number of people have also posted videos of the fireball online. The American Meteor Society estimates that the rock was relatively slow-moving at a sedate 45,000km an hour. Combined with its production of a large fireball, the researchers conclude it was probably a big rock. NASA's meteorwatch Facebook page largely agrees and suggests that this probably means that pieces of the rock made it to Earth. If you were on the flight path, you might want to check your yard.

Read more of this story at Slashdot.

A Photo Accidentally Revealed a Password For Hawaii's Emergency Agency

Slashdot - Thu, 01/18/2018 - 05:30
An anonymous reader quotes a report from Quartz: In the aftermath of an erroneous missile warning that terrified Hawaiians on Saturday (Jan. 13), the state's emergency management agency has come under increased scrutiny, from the poor design of the software that enables alerts to a particularly slapdash security measure by one of its employees. Old photos from the Associated Press inside the agency's office appear to show an unspecified password on a yellow Post-It note, stuck to a computer monitor. The image, which shows operations manger Jeffrey Wong standing in front of the computer, was taken in July and appeared in articles published at the time about the agency's preparedness in the face of a nuclear threat. The agency verified that the password is indeed real but wouldn't go into specifics on what program the password was supposed to be used for.

Read more of this story at Slashdot.

The World's Top-Selling Video Game Has a Cheating Problem

Slashdot - Thu, 01/18/2018 - 04:50
China's Tencent Holdings is going after the cheaters and hackers that infest PlayerUnknown's Battlegrounds as it prepares to bring the world's top-selling game to its home turf. From a report: Ahead of its official debut this year, the biggest gaming company on the planet has enlisted Chinese police to root out the underground rings that make and sell cheat software. It's helped law enforcement agents uncover at least 30 cases and arrest 120 people suspected of designing programs that confer unfair advantages from X-Ray vision (see-through walls) to auto-targeting (uncannily accurate snipers). Those convicted in the past have done jail time. Tencent and game developer Bluehole have a lot riding on cleaning things up for China, which accounted for more than half the game's 27 million users, according to online tracker Steam Spy. It's also the biggest source of cheat software, undermining a Battle Royale-style phenom that shattered gaming records in 2017 and surpassed best-sellers like Grand Theft Auto V. The proliferation of shenanigans threatens to drive away first-time users vital to its longer-term growth.

Read more of this story at Slashdot.

Cisco Releases Security Updates

US-CERT - Thu, 01/18/2018 - 02:52
Original release date: January 17, 2018

Cisco has released security updates to address vulnerabilities affecting multiple products. An attacker could exploit one of these vulnerabilities to take control of an affected system.

NCCIC/US-CERT encourages users and administrators to review the following Cisco Security Advisories and apply the necessary updates:

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


Bugtraq: [SECURITY] [DSA 4089-1] bind9 security update

SecurityFocus Vulnerabilities/Bugtraq - Thu, 01/18/2018 - 00:00
[SECURITY] [DSA 4089-1] bind9 security update

Bugtraq: ADVISORY - LiveZilla - Cross-site scripting (XSS) vulnerability in knowledgebase.php - CVE-2017-15869

SecurityFocus Vulnerabilities/Bugtraq - Thu, 01/18/2018 - 00:00
ADVISORY - LiveZilla - Cross-site scripting (XSS) vulnerability in knowledgebase.php - CVE-2017-15869

Bugtraq: Zenario v7.6 CMS - SQL Injection Web Vulnerability

SecurityFocus Vulnerabilities/Bugtraq - Thu, 01/18/2018 - 00:00
Zenario v7.6 CMS - SQL Injection Web Vulnerability

Bugtraq: MagicSpam 2.0.13 - Insecure File Permission Vulnerability

SecurityFocus Vulnerabilities/Bugtraq - Thu, 01/18/2018 - 00:00
MagicSpam 2.0.13 - Insecure File Permission Vulnerability

Within Next Five Years Your Pizzas Will Probably Be Delivered by Autonomous Cars, Domino's Pizza CEO Says

Slashdot - Wed, 01/17/2018 - 23:34
In an interview with The Street, Domino's Pizza outgoing CEO Patrick Doyle said in three to five years at the earliest he expects driverless cars and voice orders to shift the way the world orders pizza. From the report: "We have been investing in natural voice for ordering for a few years. We rolled that out in our own apps before Amazon launched Alexa and Alphabet launched Google Home...[and] we are making investments...to understand how consumers will want to interact with autonomous vehicles and pizza delivery," Doyle said.

Read more of this story at Slashdot.

Days After Hawaii's False Missile Alarm, a New One in Japan

Slashdot - Wed, 01/17/2018 - 22:50
An anonymous reader shares a report: Japan's public broadcaster on Tuesday accidentally sent news alerts that North Korea had launched a missile and that citizens should take shelter -- just days after the government of Hawaii had sent a similar warning to its citizens. The broadcaster, NHK, corrected itself five minutes later and apologized for the error on its evening news (Editor's note: the link may be paywalled; alternative source). The initial texts cited J-Alert, a system used by the government to issue warnings to its citizens about missiles, tsunamis and other natural disasters. But NHK later said that the system was not to blame for the false alarm. Makoto Sasaki, a spokesman for NHK, apologized, saying that "staff had mistakenly operated the equipment to deliver news alerts over the internet."

Read more of this story at Slashdot.

Philippine Lawmakers Worry China Telecom May Be a 'Trojan horse'

Slashdot - Wed, 01/17/2018 - 22:08
An anonymous reader shares a report: Opposition members of the Philippine Congress raised concern on Wednesday that China Telecom Corp, which may enter the Philippine industry, could be a "Trojan horse" aimed at giving China access to state secrets. The Southeast Asian country aims to name a third telecom operator within the first quarter that will break the duopoly of PLDT and Globe Telecom State-run China Telecom has been named as a possible investor in that third entity. President Rodrigo Duterte, who has warned both PLDT and Globe to shape up or face competition, has welcomed Chinese entities specifically to become the third telecoms operator. Beijing has selected China Telecom to invest in the Philippines, according to Philippine officials, but it would need to partner with a local company as it cannot operate alone under the law. China Telecom's presence in the Philippines, however, does not sit well with some lawmakers, given China's telecommunications expertise and sophisticated technology.

Read more of this story at Slashdot.

Salmonella Probably Killed the Aztecs

Slashdot - Wed, 01/17/2018 - 21:00
An anonymous reader quotes a report from The Guardian: In 1545 disaster struck Mexico's Aztec nation when people started coming down with high fevers, headaches and bleeding from the eyes, mouth and nose. Death generally followed in three or four days. Within five years as many as 15 million people -- an estimated 80% of the population -- were wiped out in an epidemic the locals named "cocoliztli." The word means pestilence in the Aztec Nahuatl language. Its cause, however, has been questioned for nearly 500 years. On Monday scientists swept aside smallpox, measles, mumps, and influenza as likely suspects, identifying a typhoid-like "enteric fever" for which they found DNA evidence on the teeth of long-dead victims. Scientists now say they have probably unmasked the culprit. Analysing DNA extracted from 29 skeletons buried in a cocoliztli cemetery, they found traces of the salmonella enterica bacterium, of the Paratyphi C variety. It is known to cause enteric fever, of which typhoid is an example. The Mexican subtype rarely causes human infection today. Many salmonella strains spread via infected food or water, and may have travelled to Mexico with domesticated animals brought by the Spanish, the research team said. The study has been published in the journal Nature Ecology and Evolution.

Read more of this story at Slashdot.

America's Fastest Spy Plane May Be Back -- And Hypersonic

Slashdot - Wed, 01/17/2018 - 18:00
A Lockheed Skunk Works executive implied last week at an aerospace conference that the successor to one of the fastest aircraft the world has seen, the SR-71 Blackbird, might already exist. Previously, Lockheed officials have said the successor, the SR-72, could fly by 2030. Bloomberg reports: Referring to detailed specifics of company design and manufacturing, Jack O'Banion, a Lockheed vice president, said a "digital transformation" arising from recent computing capabilities and design tools had made hypersonic development possible. Then -- assuming O'Banion chose his verb tense purposely -- came the surprise. "Without the digital transformation, the aircraft you see there could not have been made," O'Banion said, standing by an artist's rendering of the hypersonic aircraft. "In fact, five years ago, it could not have been made." Hypersonic applies to speeds above Mach 5, or five times the speed of sound. The SR-71 cruised at Mach 3.2, more than 2,000 mph, around 85,000 feet. "We couldn't have made the engine itself -- it would have melted down into slag if we had tried to produce it five years ago," O'Banion said. "But now we can digitally print that engine with an incredibly sophisticated cooling system integral into the material of the engine itself and have that engine survive for multiple firings for routine operation." The aircraft is also agile at hypersonic speeds, with reliable engine starts, he said. A half-decade before, he added, developers "could not have even built it even if we conceived of it."

Read more of this story at Slashdot.

Hackers Seem Close To Publicly Unlocking the Nintendo Switch

Slashdot - Wed, 01/17/2018 - 15:00
Ars Technica reports that "hackers have been finding partial vulnerabilities in early versions of the [Nintendo] Switch firmware throughout 2017." They have discovered a Webkit flaw that allows for basic "user level" access to some portions of the underlying system and a service-level initialization flaw that gives hackers slightly more control over the Switch OS. "But the potential for running arbitary homebrew code on the Switch really started looking promising late last month, with a talk at the 34th Chaos Communication Congress (34C3) in Leipzig Germany," reports Ars. "In that talk, hackers Plutoo, Derrek, and Naehrwert outlined an intricate method for gaining kernel-level access and nearly full control of the Switch hardware." From the report: The full 45-minute talk is worth a watch for the technically inclined, it describes using the basic exploits discussed above as a wedge to dig deep into how the Switch works at the most basic level. At one point, the hackers sniff data coming through the Switch's memory bus to figure out the timing for an important security check. At another, they solder an FPGA onto the Switch's ARM chip and bit-bang their way to decoding the secret key that unlocks all of the Switch's encrypted system binaries. The team of Switch hackers even got an unexpected assist in its hacking efforts from chipmaker Nvidia. The "custom chip" inside the Switch is apparently so similar to an off-the-shelf Nvidia Tegra X1 that a $700 Jetson TX1 development kit let the hackers get significant insight into the Switch's innards. More than that, amid the thousand of pages of Nvidia's public documentation for the X1 is a section on how to "bypass the SMMU" (the System Memory Management Unit), which gave the hackers a viable method to copy and write a modified kernel to the Switch's system RAM. As Plutoo put it in the talk, "Nvidia backdoored themselves."

Read more of this story at Slashdot.

Lawsuit Filed By 22 State Attorneys General Seeks To Block Net Neutrality Repeal

Slashdot - Wed, 01/17/2018 - 11:30
An anonymous reader quotes a report from TechCrunch: A lawsuit filed today by the attorneys general of 22 states seeks to block the Federal Communications Commission's recent controversial vote to repeal Obama era Net Neutrality regulations. The filing is led by New York State Attorney General Schneiderman, who called rollback a potential "disaster for New York consumers and businesses, and for everyone who cares about a free and open internet." The letter, which was filed in the United States District Court of Appeals in Washington, is cosigned by AGs from California, Connecticut, Delaware, Hawaii, Illinois, Iowa, Kentucky, Maine, Maryland, Massachusetts, Minnesota, Mississippi, New Mexico, North Carolina, Oregon, Pennsylvania, Rhode Island, Vermont, Virginia, Washington and Washington DC. "An open internet -- and the free exchange of ideas it allows -- is critical to our democratic process," Schneiderman added in an accompanying statement. "The repeal of net neutrality would turn internet service providers into gatekeepers -- allowing them to put profits over consumers while controlling what we see, what we do, and what we say online."

Read more of this story at Slashdot.

New Study Claims That the 'Black Death' Was Spread By Humans, Not Rats

Slashdot - Wed, 01/17/2018 - 09:45
dryriver shares a report from BBC: Rats were not to blame for the spread of plague during the Black Death, according to a study. The rodents and their fleas were thought to have spread a series of outbreaks in 14th-19th Century Europe. But a team from the universities of Oslo and Ferrara now says the first, the Black Death, can be "largely ascribed to human fleas and body lice." The study, in the Proceedings of the National Academy of Science, uses records of its pattern and scale. The Black Death claimed an estimated 25 million lives, more than a third of Europe's population, between 1347 and 1351. "We have good mortality data from outbreaks in nine cities in Europe," Prof Nils Stenseth, from the University of Oslo, told BBC News. "So we could construct models of the disease dynamics [there]." He and his colleagues then simulated disease outbreaks in each of these cities, creating three models where the disease was spread by: rats, airborne transmission, and fleas and lice that live on humans and their clothes. In seven out of the nine cities studied, the "human parasite model" was a much better match for the pattern of the outbreak. It mirrored how quickly it spread and how many people it affected. "The conclusion was very clear," said Prof Stenseth. "The lice model fits best. It would be unlikely to spread as fast as it did if it was transmitted by rats. It would have to go through this extra loop of the rats, rather than being spread from person to person." Plague is still endemic in some countries of Asia, Africa and the Americas, where it persists in "reservoirs" of infected rodents. According to the World Health Organization, from 2010 to 2015 there were 3,248 cases reported worldwide, including 584 deaths. And, in 2001, a study that decoded the plague genome used a bacterium that had come from a vet in the U.S. who had died in 1992 after a plague-infested cat sneezed on him as he had been trying to rescue it from underneath a house.

Read more of this story at Slashdot.

Many Enterprise Mobile Devices Will Never Be Patched Against Meltdown, Spectre

Slashdot - Wed, 01/17/2018 - 08:50
Mark Wilson shares a report from BetaNews: The Meltdown and Spectre bugs have been in the headlines for a couple of weeks now, but it seems the patches are not being installed on handsets. Analysis of more than 100,000 enterprise mobile devices shows that just a tiny percentage of them have been protected against the vulnerabilities -- and some simply may never be protected. Security firm Bridgeway found that just 4 percent of corporate phones and tablets in the UK have been patched against Spectre and Meltdown. Perhaps more worryingly, however, its research also found that nearly a quarter of enterprise mobile devices will never receive a patch because of their age. Organizations are advised to check for the availability of patches for their devices, and to install them as soon as possible. Older devices that will never be patched -- older than Marshmallow, for example -- should be replaced to ensure security, says Bridgeway.

Read more of this story at Slashdot.

Google Home and Chromecast Could Be Overloading Your Home Wi-Fi

Slashdot - Wed, 01/17/2018 - 08:10
Google Cast products could be to blame for your wonky internet connection. According to TP-Link, "The Cast feature normally sends packets of information at regular intervals to keep a live connection with products like Google Home," reports The Verge. "However, if the device is awakened from a 'sleep' mode, it will sometimes send a burst of information at once, which can overwhelm a router. The longer a Cast device has been in 'sleep' mode, the more information it might send at once." The engineer says that could exceed over 100,000 packets, an amount that "may eventually cause some of [the] router's primary features to shut down -- including wireless connectivity." TP-Link has reportedly fixed the issue in its C1200 router, but a broader fix from Google's end has not been found.

Read more of this story at Slashdot.

Vuln: Spring Framework CVE-2016-9878 Directory Traversal Vulnerability

SecurityFocus Vulnerabilities/Bugtraq - Wed, 01/17/2018 - 08:00
Spring Framework CVE-2016-9878 Directory Traversal Vulnerability
Syndicate content