Feed aggregator

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

Vuln: Oracle Java SE CVE-2018-2602 Local Security Vulnerability

SecurityFocus Vulnerabilities/Bugtraq - Wed, 01/17/2018 - 08:00
Oracle Java SE CVE-2018-2602 Local Security Vulnerability

Vuln: Multiple CPU Hardwares CVE-2017-5754 Information Disclosure Vulnerability

SecurityFocus Vulnerabilities/Bugtraq - Wed, 01/17/2018 - 08:00
Multiple CPU Hardwares CVE-2017-5754 Information Disclosure Vulnerability

Vuln: Multiple CPU Hardwares CVE-2017-5715 Information Disclosure Vulnerability

SecurityFocus Vulnerabilities/Bugtraq - Wed, 01/17/2018 - 08:00
Multiple CPU Hardwares CVE-2017-5715 Information Disclosure Vulnerability

ISC Releases Security Advisories for DHCP, BIND

US-CERT - Wed, 01/17/2018 - 07:58
Original release date: January 16, 2018

The Internet Systems Consortium (ISC) has released updates or workarounds that address vulnerabilities in versions of ISC Dynamic Host Configuration Protocol (DHCP) and Berkeley Internet Name Domain (BIND). A remote attacker could exploit these vulnerabilities to cause a denial-of-service condition.

NCCIC/US-CERT encourages users and administrators to review ISC Knowledge Base Articles AA-01541 and AA-01542 and apply the necessary updates or workarounds.

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


Lyft Says Nearly 250K of Its Passengers Ditched a Personal Car In 2017

Slashdot - Wed, 01/17/2018 - 07:30
An anonymous reader quotes a report from TechCrunch: Lyft has a new report out detailing its "economic impact" for 2017, and the document includes a lot of stats on its performance throughout the year. The ride-hailing provider claims 375.5 million rides for the year, which is 130 percent growth measured year-over-year. It served 23 million different passengers, itself a 92 percent YoY increase, and had 1.4 million drivers on the platform -- 100 percent growth vs. its total for 2016. Lyft is making some especially strong claims regarding its impact on car ownership trends: In 2017 alone, it said that almost a quarter of a million passengers on its platform dropped owning a personal vehicle, due to the availability of ridesharing specifically. Fifty percent of its users also report driving their own car less because of Lyft's service, and a quarter of those on the platform say they don't feel personal vehicle ownership is that important anymore. The ride-hailing company also found attitudes generally favorable towards self-driving vehicles and their use: 83 percent of Lyft passengers surveyed by the company said they'd be open to hailing and riding in a self-driving vehicle once they're available.

Read more of this story at Slashdot.

China Builds 'World's Biggest Air Purifier' That Actually Works

Slashdot - Wed, 01/17/2018 - 06:50
The South China Morning Post shares an update on the status of an experimental tower in northern China, dubbed the world's biggest air purifier by its operators. According to the scientist leading the project, the tower -- which stands over 328 feet (100 meters) tall -- has brought a noticeable improvement in air quality. From the report: The head of the research, Cao Junji, said improvements in air quality had been observed over an area of 10 square kilometers (3.86 square miles) in the city over the past few months and the tower has managed to produce more than 10 million cubic meters (353 million cubic feet) of clean air a day since its launch. Cao added that on severely polluted days the tower was able to reduce smog close to moderate levels. The system works through greenhouses covering about half the size of a soccer field around the base of the tower. Polluted air is sucked into the glasshouses and heated up by solar energy. The hot air then rises through the tower and passes through multiple layers of cleaning filters. The average reduction in PM2.5 -- the fine particles in smog deemed most harmful to health -- fell 15 per cent during heavy pollution. Cao said the results were preliminary because the experiment is still ongoing. The team plans to release more detailed data in March with a full scientific assessment of the facility's overall performance.

Read more of this story at Slashdot.

Oracle Releases January 2018 Security Bulletin

US-CERT - Wed, 01/17/2018 - 06:31
Original release date: January 16, 2018

Oracle has released its Critical Patch Update for January 2018 to address 237 vulnerabilities across multiple products. A remote attacker could exploit some of these vulnerabilities to obtain access to sensitive information.

NCCIC/US-CERT encourages users and administrators to review the Oracle January 2018 Critical Patch Update and apply the necessary updates.

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


Bitcoin Plunges Below $12,000 To Six-Week Low Over Crackdown Fears

Slashdot - Wed, 01/17/2018 - 06:10
Bitcoin plunged to a six-week low Tuesday after comments from South Korea's finance minister renewed worries about a crackdown in one of the largest markets for digital currency trading. In a radio program interview, South Korean Finance Minister Kim Dong-yeon said that "the shutdown of virtual currency exchanges is still one of the options" the government has. CNBC reports: Bitcoin dropped more than 17 percent to a low of $11,182.71 on Tuesday, falling below $12,000 for the first time since December 5, according to CoinDesk. CoinDesk's bitcoin price index tracks prices from cryptocurrency exchanges Bitstamp, Coinbase, itBit and Bitfinex. As of 12:13 p.m. ET, bitcoin was trading more than 13 percent lower at $11,759.73 a coin, according to CoinDesk. Trading in South Korean won accounted for about 4 percent of bitcoin trading volume, according to CryptoCompare. U.S. dollar-bitcoin trading had the largest share at 40 percent, the website showed. Other major digital currencies including ethereum and ripple also fell significantly. According to CoinMarketCap data, ethereum was trading at $1,051.83, down more than 20 percent in the last 24 hours, before lifting slightly to $1,117.72. Ripple fell almost 27 percent to $1.33 a token before recovering slightly to $1.36.

Read more of this story at Slashdot.

Researchers Uncover Android Malware With Never-Before-Seen Spying Capabilities

Slashdot - Wed, 01/17/2018 - 05:30
An anonymous reader quotes a report from Ars Technica: According to a report published Tuesday by antivirus provider Kaspersky Lab, "Skygofree" is most likely an offensive security product sold by an Italy-based IT company that markets various surveillance wares. With 48 different commands in its latest version, the malware has undergone continuous development since its creation in late 2014. It relies on five separate exploits to gain privileged root access that allows it to bypass key Android security measures. Skygofree is capable of taking pictures, capturing video, and seizing call records, text messages, gelocation data, calendar events, and business-related information stored in device memory. Skygofree also includes the ability to automatically record conversations and noise when an infected device enters a location specified by the person operating the malware. Another never-before-seen feature is the ability to steal WhatsApp messages by abusing the Android Accessibility Service that's designed to help users who have disabilities or who may temporarily be unable to fully interact with a device. A third new feature: the ability to connect infected devices to Wi-Fi networks controlled by attackers. Skygofree also includes other advanced features, including a reverse shell that gives malware operators better remote control of infected devices. The malware also comes with a variety of Windows components that provide among other things a reverse shell, a keylogger, and a mechanism for recording Skype conversations.

Read more of this story at Slashdot.

France Says 'Au Revoir' to the Word 'Smartphone'

Slashdot - Wed, 01/17/2018 - 04:50
Hoping to prevent English tech vocabulary from entering the French language, officials have suggested 'mobile multifunction' as an alternative. An anonymous reader shares a report: The official journal of the French Republic, the Journal officiel, has suggested "internet clandestin" instead of dark net. It's dubbed a casual gamer "joueur occasionnel" for messieurs and "joueuse occasionnelle" for mesdames. To replace hashtag, it's selected "mot-diese." Now, as the Local reports, the latest word to get the official boot in France is smartphone. It's time to say bonjour to the "le mobile multifonction." The recommendation was put forth by the Commission d'enrichissement de la langue francaise, which works in conjunction with the Academie Francaise to preserve the French language. This isn't the first time that the commission has tried to encourage French citizens to switch over to a Franco-friendly word for "smartphone." Previous suggestions included "ordiphone" (from "ordinateur," the French word for computer) and "terminal de poche" (or pocket terminal). These, it seems, did not quite stick.

Read more of this story at Slashdot.

Bugtraq: [SECURITY] [DSA 4088-1] gdk-pixbuf security update

SecurityFocus Vulnerabilities/Bugtraq - Wed, 01/17/2018 - 00:00
[SECURITY] [DSA 4088-1] gdk-pixbuf security update

Bugtraq: [RT-SA-2017-013] Truncation of SAML Attributes in Shibboleth 2

SecurityFocus Vulnerabilities/Bugtraq - Wed, 01/17/2018 - 00:00
[RT-SA-2017-013] Truncation of SAML Attributes in Shibboleth 2

Google Starts Certificate Program To Fill Empty IT Jobs

Slashdot - Tue, 01/16/2018 - 23:26
An anonymous reader shares a report: There are 150,000 open IT jobs in the U.S., and Google wants to make it easier to fill them. Today the company is announcing a certificate program on the Coursera platform to help give people with no prior IT experience the basic skills they need to get an entry-level IT support job in 8 to 12 months. Why it matters: Entry-level IT jobs are are typically higher-paying than similar roles in other fields. But they're harder to fill because, while IT support roles don't require a college degree, they do require prior experience. The median annual wage for a computer network support specialist was $62,670 in May 2016 The median annual wage for a computer user support specialist was $52,160 in May 2016. The impetus: Natalie Van Kleef Conley, head recruiter of Google's tech support program, was having trouble finding IT support specialists so she helped spearhead the certificate program. It's also part of Google's initiative to help Americans get skills needed to get a new job in a changing economy, the company told us.

Read more of this story at Slashdot.

Now Hiring For a Fascinating New Kind of Job That Only a Human Can Do: Babysit a Robot

Slashdot - Tue, 01/16/2018 - 22:53
From a report: Book a night at LAX's Residence Inn and you may be fortunate enough to meet an employee named Wally. His gig is relatively pedestrian -- bring you room service, navigate around the hotel's clientele in the lobby and halls -- but Wally's life is far more difficult than it seems. If you put a tray out in front of your door, for instance, he can't get to you. If a cart is blocking the hall, he can't push it out of the way. But fortunately for Wally, whenever he gets into a spot of trouble, he can call out for help. See, Wally is a robot -- specifically, a Relay robot from a company called Savioke. And when the machine finds itself in a particularly tricky situation, it relies on human agents in a call center way across the country in Pennsylvania to bail it out. [...] The first companies to unleash robots into service sectors have been quietly opening call centers stocked with humans who monitor the machines and help them get out of jams. "It's something that's just starting to emerge, and it's not just robots," says David Poole, CEO and co-founder of Symphony Ventures, which consults companies on automation. "I think there is going to be a huge industry, probably mostly offshore, in the monitoring of devices in general, whether they're health devices that individuals wear or monitoring pacemakers or whatever it might be."

Read more of this story at Slashdot.

Twitter Hits Back Again at Claims That Its Employees Monitor Direct Messages

Slashdot - Tue, 01/16/2018 - 22:10
From a report on TechCrunch: Twitter is pushing back against claims made by conservative activist group Project Veritas that its employees monitor private user data, including direct messages. In a statement to BuzzFeed News, a Twitter representative said "we do not proactively review DMs. Period. A limited number of employees have access to such information, for legitimate work purposes, and we enforce strict access protocols for those employees." Last week, Project Veritas, which produces undercover sting operations that purportedly expose liberal biases at media companies and other organizations, posted footage that appeared to show Twitter engineers claiming that teams of employees look at users' private data. One engineer seemed to say that Twitter can hand over President Donald Trump's data, including deleted tweets and direct messages, to the Department of Justice.

Read more of this story at Slashdot.

Democrats Are Just One Vote Shy of Restoring Net Neutrality

Slashdot - Tue, 01/16/2018 - 21:00
An anonymous reader quotes a report from Engadget: Senate minority leader Chuck Schumer now says Democrats in the Senate are a single vote away from restoring net neutrality. According to the senator from New York, they now have a total of 50 votes for a Senate resolution of disapproval that would restore the Open Internet Order of 2015 and deliver a stiff rebuke to Ajit Pai and other Republican members of the FCC. It would also prevent the agency from passing a similar measure in the future, all but guaranteeing Net Neutrality is permanently preserved. Right now the resolution has the support of all 49 Democrats in the Senate and one Republican, Susan Collins of Maine. But Schumer and the rest of the caucus will have to win over one more Republican vote to prevent Vice President Mike Pence from breaking tie and allowing the repeal to stand. Under the Congressional Review Act, the Senate has 60 days to challenge a decision by an independent agency like the FCC. Democrats have less than 30 days to convince a "moderate" like John McCain or Lindsey Graham to buck their party. Further reading: The Washington Post (paywalled)

Read more of this story at Slashdot.

Is Pop Music Becoming Louder, Simpler and More Repetitive?

Slashdot - Tue, 01/16/2018 - 18:00
dryriver writes: The BBC has posted a very interesting article that investigates whether people claiming all over the internet that "pop music just isn't what it used to be" are simply growing old, or if there actually is objective science capable of backing up this claim of a "steady decline in music quality." The findings from five different studies are quoted; the findings from the fourth study is especially striking: 1. Pop music has become slower -- in tempo -- in recent years and also "sadder" and less "fun" to listen to. 2. Pop music has become melodically less complex, using fewer chord changes, and pop recordings are mastered to sound consistently louder (and therefore less dynamic) at a rate of around one decibel every eight years. 3. There has been a significant increase in the use of the first-person word "I" in pop song lyrics, and a decline in words that emphasize society or community. Lyrics also contain more words that can be associated with anger or anti-social sentiments. 4. 42% of people polled on which decade has produced the worst pop music since the 1970s voted for the 2010s. These people were not from a particular aging demographic at all -- all age groups polled, including 18-29 year olds, appear to feel unanimously that the 2010s are when pop music became worst. This may explain a rising trend of young millennials, for example, digging around for now 15-30 year-old music on YouTube frequently. It's not just the older people who listen to the 1980s and 1990s on YouTube and other streaming services it seems -- much younger people do it too. 5. A researcher put 15,000 Billboard Hot 100 song lyrics through the well-known Lev-Zimpel-Vogt (LZV1) data compression algorithm, which is good at finding repetitions in data. He found that songs have steadily become more repetitive over the years, and that song lyrics from today compress 22% better on average than less repetitive song lyrics from the 1960s. The most repetitive year in song lyrics was 2014 in this study. Conclusion: There is some scientific evidence backing the widely voiced complaint -- on the internet in particular -- that pop music is getting worse and worse in the 2000s and the 2010s. The music is slower, melodically simpler, louder, more repetitive, more "I" (first-person) focused, and more angry with anti-social sentiments. The 2010s got by far the most music quality down votes with 42% from people polled on which decade has produced the worst music since the 1970s.

Read more of this story at Slashdot.

The James Webb Space Telescope Has Emerged From the Freezer

Slashdot - Tue, 01/16/2018 - 15:00
The James Webb Space Telescope has emerged from a large vacuum chamber that was home to temperatures of just 20 degrees Celsius above absolute zero. Scientists have reviewed the data and given the instrument a clean bill of health. "We now have verified that NASA and its partners have an outstanding telescope and set of science instruments," said Bill Ochs, the Webb telescope project manager at NASA's Goddard Space Flight Center in Greenbelt, Maryland. "We are marching toward launch." Ars Technica reports: The $10 billion telescope underwent tests inside Chamber A at Johnson Space Center, which was built in 1965 to conduct thermal-vacuum testing on the Apollo command and service modules. Beginning in mid-July, after the telescope was cooled down to a temperature range of 20 to 40 Kelvin, engineers tested the alignment of Webb's 18 primary mirror segments to ensure they would act as a single, 6.5-meter telescope. (They did). Later, they assessed the fine guidance system of the telescope by simulating the light of a distant star. The Webb telescope was able to detect the light, and all of the optical systems were able to process it. Then, the telescope was able to track the "star" and its movement, giving scientists confidence that the Webb instrument will work once in space. Webb still has a ways to go before it launches. Now that project scientists know that the optic portion of the instrument can withstand the vacuum of space, and the low temperatures at the Earth-Sun L2 point it will orbit in deep space, they must perform additional testing before a probable launch next year.

Read more of this story at Slashdot.

Why You Shouldn't Stifle Your Sneeze

Slashdot - Tue, 01/16/2018 - 11:30
An anonymous reader quotes a report from The Guardian: In a season where colds are rife, holding your nose and closing your mouth might seem like a considerate alternative to an explosive "Achoo!" But doctors have warned of the dangers of such a move after a man was found to have ruptured the back of his throat when attempting to stifle a sneeze. Medics say the incident, which they detail in the British Medical Journal Case Reports, came to light when a 34-year old man arrived in A&E with a change to his voice, a swollen neck, pain when swallowing and a popping sensation in his neck after he pinched his nose to contain an expulsion. The team took scans of the man's neck to investigate and discovered bubbles of air in the tissues at the back of the throat, and in the neck from the base of the skull to halfway down the man's back. That, they say, suggested a tear had occurred at the back of the throat as a result of increased pressure from the stifled sneeze, leading to air collecting in his soft tissues. The authors warn that blocking the nostrils and mouth when sneezing is dangerous, noting that while tearing of the throat tissue is rare, it could result in a ruptured eardrum or even a brain aneurysm.

Read more of this story at Slashdot.

SpaceX and Boeing Slated For Manned Space Missions By Year's End

Slashdot - Tue, 01/16/2018 - 10:45
schwit1 shares a report from Fortune, covering NASA's announcement last week that it expects SpaceX to conduct a crewed test flight by the end of the year: SpaceX's crewed test flight is slated for December, after an uncrewed flight in August. Boeing will also be demonstrating its CST-100 Starliner capsule, with a crewed flight in November following an uncrewed flight in August. NASA's goal is to launch crews to the ISS from U.S. soil, a task that has fallen to Russia's space program since the retirement of the U.S. Space Shuttle program in 2011. NASA began looking for private launch companies to take over starting in 2010, and contracted both SpaceX and Boeing in 2014 to pursue crewed launches. The push to restore America's crewed spaceflight capacity has been delayed in part, according to a detailed survey by Ars Technica, by Congress redirecting funds in subsequent years. The test flights could determine whether Boeing or SpaceX conducts the first U.S. commercial space launch to the ISS. Whichever company gets that honor may also claim a symbolic U.S. flag stuck to a hatch on the space station. Sources speaking to Ars describe the race between the two companies as too close to call, and say that a push to early 2019 is entirely possible. But in an apparent vote of confidence, NASA has already begun naming astronauts to helm the flights.

Read more of this story at Slashdot.

Syndicate content