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.

Cisco Releases Security Updates

US-CERT - Thu, 01/10/2019 - 03:27
Original release date: January 09, 2019
Cisco has released security updates to address vulnerabilities in Cisco AsyncOS Software for Cisco Email Security Appliance. A remote attacker could exploit these vulnerabilities to cause a denial-of-service condition. The National Cybersecurity and Communications Integration Center (NCCIC), part of the Cybersecurity and Infrastructure Security Agency (CISA), 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.


Cancer in America Is Way Down, For the Wealthy Anyway

Slashdot - Wed, 01/09/2019 - 23:25
The good news is that cancer in America was beaten back over the 25 years ending 2016, with death rates plummeting, particularly when it comes to the four most common types of the dreaded affliction. From a report: There's a caveat, however. Those gains have been reaped mostly by the well-off. While racial disparities have begun to narrow, the impact of limited access to treatment for the poorest Americans has increased wealth-based inequality, according to the American Cancer Society's annual update on trends and statistics. "Any time you have a disease as serious as cancer, when you have a substantial reduction in deaths, that's a notable achievement," said Len Lichtenfeld, the interim chief medical officer for the American Cancer Society. "But there are still a lot of areas for improvement." Health insurance and access to care can be an issue in some poor and rural portions of the country, where there are higher death rates of colon, cervical and lung cancers, according to Cancer Statistics 2019. While poverty was actually associated with lower rates of cancer mortality prior to the 1980s, that trend has since reversed, due in part to changes in diet and smoking as well as screening and treatment rates, the health organization said.

Read more of this story at Slashdot.

Natural Gas is Now Getting in the Way; US Carbon Emissions Increase by 3.4%

Slashdot - Wed, 01/09/2019 - 22:45
AmiMoJo shares a report: "The US was already off track in meeting its Paris Agreement targets. The gap is even wider headed into 2019." That's the dire news from Rhodium Group, a research firm that released preliminary estimates of US carbon emissions in 2018. Though the Trump administration said it would exit the Paris Agreement in 2017, the US is still bound by the agreement to submit progress reports until 2020. But the administration has justified regulatory rollbacks since then, claiming that regulation from the US government is unnecessary because emissions were trending downward anyway. But it appears that emissions have increased 3.4 percent in 2018 across the US economy, the second-largest annual increase in 20 years, according to Rhodium Group's preliminary data. (2010, when the US started recovering from the recession, was the largest annual increase in the last two decades.) This reversal of course -- the first increase in emissions in three years -- came from a few sources. Carbon emissions from the US electricity sector increased by 1.9 percent, largely because the installation of new natural gas plants has outpaced coal retirements. Cheap natural gas has been credited with killing coal, which is a dirtier fossil fuel in terms of emissions. But natural gas is a fossil fuel, too, and burning more natural gas than is needed to simply replace coal will result in more carbon emissions. But electricity wasn't the main culprit. Transportation was.

Read more of this story at Slashdot.

Google Home Gets Real-Time Interpretations For 27 languages

Slashdot - Wed, 01/09/2019 - 22:01
Google Assistant has announced the introduction of real-time translations with Google Home speakers and third-party smart displays like those from JBL, Sony, and Lenovo. Interpretations will initially be available in 27 languages. From a report: Plans are to later bring real-time interpretations to mobile devices, but no date has been set, a company spokesperson told VentureBeat. Real-time interpretation with Google Assistant is the latest conversational AI milestone from Google, following the release of Duplex and Call Screen for Pixel phones in late 2018. But just like the first response to Duplex, you should taper your expectations. Initial demos by VentureBeat found Interpreter Mode to be quick in its response, but each exchange could last no more than 15 seconds, a limitation that makes Interpreter Mode helpful but not yet capable of handling the longer exchanges that often occur in a typical conversation.

Read more of this story at Slashdot.

Samsung Phone Users Perturbed To Find They Can't Delete Facebook

Slashdot - Wed, 01/09/2019 - 21:00
An anonymous reader quotes a report from Bloomberg: Nick Winke, a photographer in the Pacific northwest, was perusing internet forums when he came across a complaint that alarmed him: On certain Samsung Electronics Co. smartphones, users aren't allowed to delete the Facebook app. Winke bought his Samsung Galaxy S8, an Android-based device that comes with Facebook's social network already installed, when it was introduced in 2017. He has used the Facebook app to connect with old friends and to share pictures of natural landscapes and his Siamese cat -- but he didn't want to be stuck with it. He tried to remove the program from his phone, but the chatter proved true -- it was undeletable. He found only an option to "disable," and he wasn't sure what that meant. A Facebook spokesperson said the disabled version of the app acts like it's been deleted, so it doesn't continue collecting data or sending information back to Facebook. But there's rarely communication with the consumer about the process. The Menlo Park, California-based company said whether the app is deletable or not depends on various pre-install deals Facebook has made with phone manufacturers, operating systems and mobile operators around the world over the years, including Samsung. Facebook, the world's largest social network, wouldn't disclose the financial nature of the agreements, but said they're meant to give the consumer "the best" phone experience right after opening the box.

Read more of this story at Slashdot.

Mark Zuckerberg's Resolution Is To Talk About Tech's Place In Society

Slashdot - Wed, 01/09/2019 - 18:00
In the past, Facebook CEO Mark Zuckerberg challenged himself to create an AI assistant for his home and committed to learning Mandarin. This year he's planning to hold a number of public discussions about how technology plays a role in the future of society. Engadget reports: "I'm an engineer, and I used to just build out my ideas and hope they'd mostly speak for themselves," he wrote in a Facebook post. "But given the importance of what we do, that doesn't cut it anymore. So I'm going to put myself out there more than I've been comfortable with and engage more in some of these debates about the future, the tradeoffs we face, and where we want to go." Zuckerberg plans to hold talks with "leaders, experts, and people in our community from different fields" every few weeks. He'll make the discussions available on his Facebook and Instagram feeds or elsewhere. Engadget suggests Zuckerberg "might be best served to directly focus on restoring trust with Facebook's two billion users and fixing the vast array of problems with which his platform is struggling, including privacy screwups and a tanking stock."

Read more of this story at Slashdot.

Dell Alienware Area-51m Packs Desktop Hardware Into Powerful, Upgradeable Laptop

Slashdot - Wed, 01/09/2019 - 15:00
MojoKid writes: Dell just unveiled its latest desktop-replacement class notebook, the new Alienware Area-51m. Unlike most other notebooks, however, the Area-51m is actually packing an array of desktop-class hardware. Intel's Core i9-9900K is an available CPU option, for example, and NVIDIA's GeForce RTX 2080 will be offered in the machine as well. The Area-51m also supports up to 64GB of RAM via quad SO-DIMM slots, multiple NVMe M.2 solid state drives and a SATA drive can be installed, and numerous 17.3" display options will be available as well, including a 144Hz IPS G-SYNC model. The Alienware Area-51m is also upgradeable, thanks to the use of socketed desktop processors and a custom GPU module. The machine will be available starting January 29th in two color options, Lunar Light and Dark Side of the Moon.

Read more of this story at Slashdot.

AT&T Preps For New Layoffs Despite Billions In Tax Breaks and Regulatory Favors

Slashdot - Wed, 01/09/2019 - 11:30
An anonymous reader quotes a report from Motherboard: AT&T is preparing for yet another significant round of layoffs according to internal documents obtained by Motherboard. The staff reductions come despite billions in tax breaks and regulatory favors AT&T promised would dramatically boost both investment and job creation. A source at AT&T who asked to remain anonymous because they were not authorized to speak publicly told Motherboard that company leadership is planning what it's calling a "geographic rationalization" and employment "surplus" reduction that will consolidate some aspects of AT&T operations in 10 major operational hubs in New York, California, Texas, New Jersey, Washington State, Colorado, Georgia, Illinois, Missouri, and Washington, DC. A spokesperson for AT&T confirmed to Motherboard that it is planning to "adjust" its workforce. While AT&T has yet to come up with a final, formal internal tally for this new round of looming layoffs, AT&T employees worry the staff reductions could prove to be significant, especially outside of these core areas. Managers are being briefed on the plans now, though AT&T isn't expected to formally announce the specifics until they're finalized later this month. The staff reductions were first announced in an internal memo sent to managers last Friday by Jeff McElfresh, President, Technology & Operations at AT&T. This news comes in the wake of AT&T receiving a $20 billion windfall last quarter courtesy of the Trump administration tax breaks. That's in addition to the friendlier environment AT&T finds itself in as a result of the Trump administration's assault on consumer protections ranging from net neutrality to broadband privacy guidelines. "To win in this new world, we must continue to lower costs and keep getting faster, leaner, and more agile," McElfresh told employees. "This includes reductions in our organization, and others across the company, which will begin later this month and take place over several months."

Read more of this story at Slashdot.

Deep Pacific Waters Are Cooling Down Due To Centuries-Ago Little Ice Age, New Study Suggests

Slashdot - Wed, 01/09/2019 - 10:10
schwit1 quotes a report from The Inquisitr: Most of the world's waters may be warming as a result of climate change, but a new study shows that the deepest parts of the Pacific Ocean still appear to be cooling down hundreds of years after the period in history known as the "Little Ice Age." According to a report from Science Daily, a team of researchers from the Woods Hole Oceanographic Institute (WHOI) and Harvard University discovered that there has been a "lag" of a few centuries in terms of temperature change in the deep Pacific. This part of the ocean, the report stressed, is still seemingly cooling and adjusting to the temperature drops of the Little Ice Age while the rest of the Pacific gets warmer as a result of modern factors. "These waters are so old and haven't been near the surface in so long, they still 'remember' what was going on hundreds of years ago when Europe experienced some of its coldest winters in history," commented WHOI physical oceanographer Jake Gebbie, lead author of the new study. As documented in a paper that was published Friday in the journal Science, the researchers created a model simulating how the deep Pacific's temperature might react to changes in climate on the surface, then compared the data from the model against two historical sources. These sources included ocean temperature data taken in the 1870s by scientists aboard the HMS Challenger and temperatures gathered over a century later, through the World Ocean Circulation Experiment in the 1990s. Based on how these comparisons aligned, the researchers found that warming was present in most parts of the world's oceans and consistent with the current trend of climate change. The only exception was the deep Pacific, where temperatures were cooling at around 1.25 miles (two kilometers) deep. This suggested that long-ago changes in surface climate, such as those that took place during the Little Ice Age, could still have an influence on the effect of climate change in modern times.

Read more of this story at Slashdot.

Canada's Bell Telecommunications Company Wants Permission To Gather, Track Customer Data

Slashdot - Wed, 01/09/2019 - 09:30
Bell Canada is asking customers for permission to track everything they do with their home and mobile phones, internet, television, apps or any other services they get through Bell or its affiliates. "In return, Bell says it will provide advertising and promotions that are more 'tailored' to their needs and preferences," reports CBC.ca. From the report: "Tailored marketing means Bell will be able to customize advertising based on participant account information and service usage patterns, similar to the ways that companies like Google and others have been doing for some time," the company says in recent notices to customers. If given permission, Bell will collect information about its customers' age, gender, billing addresses, and the specific tablet, television or other devices used to access Bell services. It will also collect the "number of messages sent and received, voice minutes, user data consumption and type of connectivity when downloading or streaming." "Bell's marketing partners will not receive the personal information of program participants; we just deliver the offers relevant to the program participants on their behalf," the company assures customers. Teresa Scassa, who teaches law at the University of Ottawa and holds the Canada Research Chair in Information Law and Policy, says Bell customers who opt into Bell's new program could be giving away commercially valuable personal information with little to no compensation for increased risks to their privacy and security. "Here's a company that's taking every shred of personal information about me, from all kinds of activities that I engage in, and they're monetizing it. What do I get in return? Better ads? Really? That's it? What about better prices?" Toronto-based consultant Charlie Wilton, whose firm has advised Bell and Rogers in the past, says: "I mean, in a perfect world, they would give you discounts or they would give you points or things that consumers would more tangibly want, rather than just the elimination of a pain point -- which is what they're offering right now."

Read more of this story at Slashdot.

Software Developer Tops List of U.S. News & World Report's Annual Best Jobs Rankings

Slashdot - Wed, 01/09/2019 - 08:50
According to U.S. News and World Report's annual best jobs rankings, software developer is the top pick for the new year. "The publication's Best Jobs of 2019 list takes seven factors into account, including median salary, employment rate and stress level," reports USA Today. "The median salary for a software developer is $101,790, and the unemployment rate is 1.9 percent, according to the most recent data from the U.S. Bureau of Labor Statistics." From the report: Though software developers have neither the highest median salary nor lowest unemployment rate on the U.S. News Best Jobs of 2019 list, the position's projected increase in demand -- roughly 30 percent between 2016 and 2026 -- and average stress levels helped it land the top spot, said Rebecca Koenig, careers reporter at U.S. News and World Report. "Unlike some other jobs that do pretty well on the list, which are very demanding, software developer tends not to be a really stressful profession," Koenig said. Here are the Top 10, in order: 1. Software Developer 2. Statistician 3. Physician assistant 4. Dentist 5. (tie) Orthodontist 6. (tie) Nurse anesthetist 7. Nurse practitioner 8. Pediatrician 9. (tie) Obstetrician and gynecologist 9. (tie) Oral and maxillofacial surgeon 9. (tie) Prosthodontist 9. (tie) Physician

Read more of this story at Slashdot.

The Impossible Burger 2.0 Is a Plant-Based Beef Replacement That Uses Soy Instead Wheat Protein To Take On New Forms

Slashdot - Wed, 01/09/2019 - 08:10
An anonymous reader quotes a report from Popular Science: During a press event at the Consumer Electronics Show in Las Vegas, Impossible Foods showed off its new plant-based ground beef replacement by offering a selection of foods from traditional sliders to the ambitious tartare. Thanks to a change in formula, the new Impossible Burger 2.0 goes beyond simple patties and aims to take on ground beef with every recipe, from lasagna to tacos. The first tastes are very promising. Back in 2016, the original Impossible Burger debuted as a veggie burger that could almost pass as beef. Its meaty secret was a molecule called heme, which contains iron and is largely responsible for the flavors we associate with cooked flesh. But, according to Impossible CEO Pat Brown, it requires a protein to bind it. The original Impossible Burger used wheat protein, which worked, but had some drawbacks. First, it meant the Impossible Burger wasn't gluten-free, but it also put some limitations on the meat's form factor. The wheat worked for burger patties that stayed in a relatively static shape, but it couldn't crumble or take on other shapes -- like meatballs -- without losing its integrity. The solution was a switch to soy. The resulting Impossible Burger 2.0 product has 14 grams of fat and 240 calories in a single quarter-pound serving (whether it's a patty, ball, or glob of tartare). Impossible also claims that the Burger 2.0 has the same amount of bioavailable iron and protein as its cow-derived cousin. According to Brown, the levels of amino acids are "at least on-par" with typical ground beef and, in some cases, exceed what real meat can offer. As for taste, Popular Science's Stan Horaczek says "it works best as a burger with a thin patty so you don't get a whole mouthful of soy at once, but once you introduce a bun and some toppings, you might not even notice the differences with real beef." The Impossible Burger 2.0 will be served at a few restaurants starting this week, with a wider roll out starting on February 8 when it will be available to all U.S. restaurants through food distributors. It's also planning to have its products in some U.S. supermarkets by later this year.

Read more of this story at Slashdot.

Vuln: Cisco Firepower Management Center CVE-2018-15458 Denial of Service Vulnerability

SecurityFocus Vulnerabilities/Bugtraq - Wed, 01/09/2019 - 08:00
Cisco Firepower Management Center CVE-2018-15458 Denial of Service Vulnerability

Vuln: Cisco IP Phone 8800 Series CVE-2018-0461 Arbitrary Script Injection Vulnerability

SecurityFocus Vulnerabilities/Bugtraq - Wed, 01/09/2019 - 08:00
Cisco IP Phone 8800 Series CVE-2018-0461 Arbitrary Script Injection Vulnerability

Vuln: IBM API Connect CVE-2018-1932 Information Disclosure Vulnerability

SecurityFocus Vulnerabilities/Bugtraq - Wed, 01/09/2019 - 08:00
IBM API Connect CVE-2018-1932 Information Disclosure Vulnerability

Google Removes 85 Adware Apps That Were Installed By Millions of Users

Slashdot - Wed, 01/09/2019 - 07:30
Google has removed 85 Android apps from the official Play Store that security researchers from Trend Micro deemed to contain a common strain of adware. "The 85 apps had been downloaded over nine million times, and one app, in particular, named 'Easy Universal TV Remote,' was downloaded over five million times," reports ZDNet. From the report: While the apps were uploaded on the Play Store from different developer accounts and were signed by different digital certificates, they exhibited similar behaviors and shared the same code, researchers said in a report published today. But besides similarities in their source code, the apps were also visually identical, and were all of the same types, being either games or apps that let users play videos or control their TVs remotely. The first time users ran any of the apps, they would proceed to show fullscreen ads in different steps, asking and reasking users to press various buttons to continue. If the user was persistent and stayed with the app until it reached a menu page, every menu button push would trigger yet another fullscreen ad, over and over again until the app would suddenly crash, hiding its original app icon. But despite the crash, unbeknownst to the user, the app would continue to run in the phone's background, showing new fullscreen ads ever 15 or 30 minutes, generating profits for the fraudsters until users either removed the apps or reset devices to factory settings as a last resort. You can view a list of the 85 adware apps via this PDF file.

Read more of this story at Slashdot.

DARPA Wants To Build an AI To Find the Patterns Hidden in Global Chaos

Slashdot - Wed, 01/09/2019 - 06:51
A new program at DARPA is aimed at creating a machine learning system that can sift through the innumerable events and pieces of media generated every day and identify any threads of connection or narrative in them. It's called KAIROS: Knowledge-directed Artificial Intelligence Reasoning Over Schemas. From a report: "Schema" in this case has a very specific meaning. It's the idea of a basic process humans use to understand the world around them by creating little stories of interlinked events. For instance when you buy something at a store, you know that you generally walk into the store, select an item, bring it to the cashier, who scans it, then you pay in some way, and then leave the store. This "buying something" process is a schema we all recognize, and could of course have schemas within it (selecting a product; payment process) or be part of another schema (gift giving; home cooking). Although these are easily imagined inside our heads, they're surprisingly difficult to define formally in such a way that a computer system would be able to understand. They're familiar to us from long use and understanding, but they're not immediately obvious or rule-bound, like how an apple will fall downwards from a tree at a constant acceleration. And the more data there are, the more difficult it is to define. Buying something is comparatively simple, but how do you create a schema for recognizing a cold war, or a bear market? That's what DARPA wants to look into.

Read more of this story at Slashdot.

Verizon Says It Won't Launch Fake 5G Icons Like AT&T Did

Slashdot - Wed, 01/09/2019 - 06:10
Verizon and T-Mobile are calling out AT&T for starting a shady marketing tactic that labeled its 4G network as a 5G network. "In an open letter, in which AT&T is not named directly, Verizon says in part 'the potential to over-hype and under-deliver on the 5G promise is a temptation that the wireless industry must resist,'" reports TechCrunch. Meanwhile, T-Mobile directly called out AT&T, tweeting a short video of someone putting a sticky note reading "9G" on top of their iPhone's LTE icon. The Verge reports: The promise comes right as AT&T has started to roll out updates doing exactly that: changing the "LTE" icon in the corner of select phones into an icon reading "5G E." One might assume that a "5G E" connection is the same thing as a "5G" connection, but it's not. AT&T is just pretending that the faster portions of its LTE network are 5G and is trying to get a head start on the 5G marketing race by branding it "5G Evolution." T-Mobile isn't happy about the marketing nonsense either. Its CTO, Neville Ray, wrote that AT&T was "duping customers." Verizon says it's "calling on the broad wireless industry to commit to labeling something 5G only if new device hardware is connecting to the network using new radio technology to deliver new capabilities" (emphasis Verizon's). Kyle Malady, Verizon's chief technical officer, says Verizon will lead by example and that "a clear, consistent, and simple understanding of 5G" is needed so consumers don't have to "maneuver through marketing double-speak or technical specifications." Malady says Verizon will "not call our 4G network a 5G network if customers don't experience a performance or capability upgrade that only 5G can deliver." But that isn't the same thing as saying "we won't label our network 5G unless it's 5G." In fact, if you turn that sentence into a positive statement, it says "we will only call our 4G network a 5G network if it delivers a 5G-like experience." The Verge notes that Verizon "has also been misleading about its jump into 5G." Last year, Big Red bragged about launching the "world's first commercial 5G service," even though "it wasn't mobile; it was home internet service that just happened to be delivered wirelessly during the final stretch to a subscriber's home; and it didn't use the global 5G standard -- it used a rival 5G standard created by Verizon."

Read more of this story at Slashdot.

Huawei Has Suspected Ties To Front Companies In Iran and Syria, New Documents Reveal

Slashdot - Wed, 01/09/2019 - 05:30
An anonymous reader quotes a report from Reuters: The U.S. case against the chief financial officer of China's Huawei Technologies, who was arrested in Canada last month, centers on the company's suspected ties to two obscure companies. One is a telecom equipment seller that operated in Tehran; the other is that firm's owner, a holding company registered in Mauritius. U.S. authorities allege CFO Meng Wanzhou deceived international banks into clearing transactions with Iran by claiming the two companies were independent of Huawei, when in fact Huawei controlled them. Huawei has maintained the two are independent: equipment seller Skycom Tech Co Ltd and shell company Canicula Holdings Ltd. But corporate filings and other documents found by Reuters in Iran and Syria show that Huawei, the world's largest supplier of telecommunications network equipment, is more closely linked to both firms than previously known. The documents reveal that a high-level Huawei executive appears to have been appointed Skycom's Iran manager. They also show that at least three Chinese-named individuals had signing rights for both Huawei and Skycom bank accounts in Iran. Reuters also discovered that a Middle Eastern lawyer said Huawei conducted operations in Syria through Canicula. Huawei, U.S. authorities assert, retained control of Skycom, using it to sell telecom equipment to Iran and move money out via the international banking system. As a result of the deception, U.S. authorities say, banks unwittingly cleared hundreds of millions of dollars of transactions that potentially violated economic sanctions Washington had in place at the time against doing business with Iran.

Read more of this story at Slashdot.

Microsoft Releases January 2019 Security Updates

US-CERT - Wed, 01/09/2019 - 04:40
Original release date: January 08, 2019

Microsoft has released updates to address multiple vulnerabilities in Microsoft software. A remote attacker could exploit one of these vulnerabilities to take control of an affected system.

The National Cybersecurity and Communications Integration Center (NCCIC), part of the Cybersecurity and Infrastructure Security Agency (CISA), encourages users and administrators to review Microsoft’s January 2019 Security Update Summary and Deployment Information and apply the necessary updates.

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


Syndicate content