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: Dell EMC RecoverPoint Information Disclosure and Denial of Service Vulnerabilities

SecurityFocus Vulnerabilities/Bugtraq - Wed, 11/14/2018 - 08:00
Dell EMC RecoverPoint Information Disclosure and Denial of Service Vulnerabilities

Vuln: Dell OpenManage Network Manager CVE-2018-15768 Remote Privilege Escalation Vulnerability

SecurityFocus Vulnerabilities/Bugtraq - Wed, 11/14/2018 - 08:00
Dell OpenManage Network Manager CVE-2018-15768 Remote Privilege Escalation Vulnerability

Vuln: Apache Tomcat CVE-2018-1305 Security Bypass Vulnerability

SecurityFocus Vulnerabilities/Bugtraq - Wed, 11/14/2018 - 08:00
Apache Tomcat CVE-2018-1305 Security Bypass Vulnerability

Facebook Patches Vulnerability That Could Have Exposed User Data

Slashdot - Wed, 11/14/2018 - 07:30
Yet another vulnerability has been patched that could have exposed user data. According to security company Imperva, the bug "allowed websites to obtain private information about Facebook users and their friends through unauthorized access to a company API, playing off a specific behavior in the Chrome browser," reports The Verge. From the report: In technical terms, the attack is a cross-site request forgery, using a legitimate Facebook login in unauthorized ways. For the attack to work, a Facebook user must visit a malicious website with Chrome, and then click anywhere on the site while logged into Facebook. From there, attackers could open a new pop-up or tab to the Facebook search page and run any number of queries to extract personal information. Some examples Imperva gives are checking if a user has taken photos in a certain location or country, if the user has written any recent posts that contain specific text, or checking if a user's friends like a company's Facebook page. In essence, the vulnerability exposed the interests of a user and their friends even if privacy settings were set so interests were only visible to a user's friends. Imperva says the vulnerability was not a common technique and the issue has been resolved with Facebook. However, it does mention that these more sophisticated social engineering attacks could become more common in 2019. A Facebook representative told The Verge: "We appreciate this researcher's report to our bug bounty program. We've fixed the issue in our search page and haven't seen any abuse. As the underlying behavior is not specific to Facebook, we've made recommendations to browser makers and relevant web standards groups to encourage them to take steps to prevent this type of issue from occurring in other web applications."

Read more of this story at Slashdot.

Microsoft Releases November 2018 Security Updates

US-CERT - Wed, 11/14/2018 - 07:24
Original release date: November 13, 2018

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

NCCIC encourages users and administrators to review Microsoft’s November 2018 Security Update Summary and Deployment Information and apply the necessary updates.

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


Nigerian Firm Takes Blame For Routing Google Traffic Through China

Slashdot - Wed, 11/14/2018 - 06:50
Earlier today, it was reported that Google suffered a brief outage on Monday that pushed some of its traffic through networks in Russia, China, and Nigeria. Soon after Google said it would conduct an investigation, Nigeria's Main One Cable Company fessed up to the incident. According to Reuters, the company says it "accidentally caused the problem during a network upgrade." From the report: Main One said in an email that it had caused a 74-minute glitch by misconfiguring a border gateway protocol filter used to route traffic across the internet. That resulted in some Google traffic being sent through Main One partner China Telecom, the West African firm said. Even though Main One said it was to blame, some security experts said the incident highlighted concerns about the potential for hackers to conduct espionage or disrupt communications by exploiting known vulnerabilities in the way traffic is routed over the internet. Main One, which describes itself as a leading provider of telecom and network services for businesses in West Africa, said that it had investigated the matter and implemented new processes to prevent it from happening again.

Read more of this story at Slashdot.

Amazon Is Getting More Than $2 Billion For NYC, Virginia Expansions

Slashdot - Wed, 11/14/2018 - 06:10
An anonymous reader quotes a report from Ars Technica: Over the last year, Amazon has dangled in front of cities the possibility that they could host the company's "second headquarters" -- a massive $5 billion facility that would provide 50,000 white-collar jobs. On Tuesday, Amazon confirmed what had been widely reported: nobody would be getting this massive prize. Instead, the expansion would be split in half, with New York City and Arlington, Virginia, (just outside Washington, DC) each getting smaller facilities that will employ around 25,000 people each. Amazon's Seattle offices will continue to be the company's largest and will continue to be Amazon's headquarters by any reasonable definition. But pretending to have three "headquarters" undoubtedly makes it easier for Amazon to coax taxpayer dollars out of local governments. [...] The tactic seems to have worked, as governments in both locations have offered Amazon hundreds of millions of dollars in incentives to locate their new offices there. Virginia officials appear to have driven a harder bargain than their rivals in New York. Amazon says it's getting $1.5 billion in government incentives for its New York expansion, whereas Virginia is offering a comparatively modest $573 million in direct incentives.

Read more of this story at Slashdot.

Adobe Releases Security Updates

US-CERT - Wed, 11/14/2018 - 01:40
Original release date: November 13, 2018

Adobe has released security updates to address vulnerabilities in Flash Player, Adobe Acrobat and Reader, and Adobe Photoshop CC. An attacker could exploit these vulnerabilities to obtain access to sensitive information.

NCCIC encourages users and administrators to review Adobe Security Bulletins APSB18-39, APSB18-40, and APSB18-43 and apply the necessary updates.

 

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


Google Suffered a Brief Outage on Monday Which Pushed Some of Its Traffic Through Russia, China and Nigeria; Company Says It Will Do an Investigation

Slashdot - Tue, 11/13/2018 - 23:20
Google suffered a brief outage and slowdown Monday, with some of its traffic getting rerouted through networks in Russia, China and Nigeria. From a report: Incorrect routing instructions sent some of the search giant's traffic to Russian network operator TransTelekom, China Telecom (which, as you may recall, has been found of misdirecting internet traffic in recent months) and Nigerian provider MainOne between 1:00 p.m. and 2:23 p.m. PT, according to internet research group ThousandEyes. "This incident at a minimum caused a massive denial of service to G Suite and Google Search," wrote Ameet Naik, ThousandEyes' technical marketing manager, in a blog post. "However, this also put valuable Google traffic in the hands of ISPs in countries with a long history of Internet surveillance. Applications like Gmail and Google Drive don't appear to have been affected, but YouTube users experienced some slowdown. Google noted that the issue was resolved and said it would conduct an internal investigation.

Read more of this story at Slashdot.

Amazon Picks New York, Northern Virginia For HQ2 [Update: Confirmed]

Slashdot - Tue, 11/13/2018 - 23:10
The Washington Post is reporting that Amazon has picked New York's Long Island City and Arlington County's Crystal City neighborhoods as the company's second headquarters (Warning: source paywalled; alternative source). The two locations will split the duty and will reportedly bring the cities an infusion of jobs and tax revenue. From the report: Amazon will open major new outposts in Northern Virginia's Crystal City and New York City, splitting its much-sought investment of up to 50,000 jobs between the two East Coast sites. The choice of Crystal City in Arlington County as one of the winners would cement Northern Virginia's reputation as a magnet for business and potentially reshape the Washington region into an East Coast outpost of Silicon Valley over the next decade. It also represents a victory for New York Mayor Bill de Blasio (D) and Gov. Andrew M. Cuomo (D), who had joked that he would change his name to "Amazon Cuomo" if necessary to land the prize. Amazon's decision to split the project rather than open a second headquarters on par with its Seattle campus has angered some who said the company had ginned up competition among cities only to change the rules midstream. Some said it was unfair that the company seemed to be considering only sites in more affluent communities. Updated on November 13, 15:10 GMT: Amazon on Tuesday confirmed that it had selected New York City and Northern Virginia for new headquarters. In a statement, Jeff Bezos said, "We are excited to build new headquarters in New York City and Northern Virginia. These two locations will allow us to attract world-class talent that will help us to continue inventing for customers for years to come. The team did a great job selecting these sites, and we look forward to becoming an even bigger part of these communities."

Read more of this story at Slashdot.

Corporate America's Blockchain and Bitcoin Fever is Over

Slashdot - Tue, 11/13/2018 - 22:40
S&P 500 executives are dropping blockchain buzzwords less on earnings calls and during presentations to analysts and investors. Analysts are also asking about it less. From a report: The hype was just that. The odds of a company turning blockchain "headlines into reality" are slim, as Forrester Research predicts. The prospect of incorporating blockchain technology or cryptocurrency into businesses excited investors and drove up share prices temporarily -- just look at Kodak, beverage company Long Blockchain, or Hooters franchisee Chanticleer Holdings -- so it's no wonder executives wanted shareholders to know that they too might get in on the new technologies. At the peak earlier this year, "blockchain" was mentioned 173 times, according to an analysis of company transcripts by Axios. The number has since fallen as much as 80%.

Read more of this story at Slashdot.

A Look at How One of the Largest Record Companies in the World Once Owned Rockstar Games and Sold it For a Pittance

Slashdot - Tue, 11/13/2018 - 22:00
Question: what is entertainment's highest-grossing weekend debut of all time? Hint: It only took place two weeks ago. From a report: It was claimed by a Western-themed video game called Red Dead Redemption 2 -- the second in a series dubbed 'Grand Theft Auto on horseback' -- which generated over $725m in just three days. The wording above ('highest-grossing weekend debut') has been carefully chosen. Because the highest-grossing entertainment launch of all time actually kicked off on a Tuesday, in September, 2013. That launch was Grand Theft Auto V, another video game, which grossed more than $1bn during its opening 72 hours on sale. Both Red Dead Redemption and Grand Theft Auto are made by Rockstar Games -- a New York-HQ'd interactive entertainment company famed for its ability to bring filmic sophistication to the world of PlayStations and Xboxes, and for its ability to generate billions upon billions of dollars by doing so. Ready for this? The Grand Theft Auto franchise, and the core team behind Rockstar's success, were, unbelievably, both once part of the music business. They were allowed to leave 20 years ago. For an absolute pittance. Let's rewind. Back in 1990, London-born Sam Houser, aged 19, landed a dream first job -- working in the post-room at BMG's UK HQ. Houser then supplemented his university studies by continuing to work at BMG for the next four years, focusing on pop music videos and VHS releases. By 1994, he'd graduated, and took a full-time role within BMG's new interactive entertainment division. Houser, it turned out, had a natural talent for 'A&R'ing' video games -- spotting titles that would sell big and signing them up as a label would an artist -- and, by 1996, he was named Head of Development at BMG Interactive in the UK. Got your palm located somewhere roughly near your forehead? Good. Prepare for the two to forcibly meet. Interactive released Grand Theft Auto, a 2D action-adventure game, which saw players fulfilling the objectives of criminal overlords across three cities. The title was a commercial smash in the US and Europe -- yet it emerged amid serious corporate turbulence. In March 1998, convinced that its foray into video games had been a waste of time and money, BMG -- under the instruction of owner Bertelsmann -- agreed to sell off BMG Interactive. According to Sam Houser, BMG let the company go, to New York-based Take Two Interactive, for a total consideration of $9m. (For those who can see where this narrative is going: Red Dead Redemption 2 generated that $9m back within an hour of going on sale last month.) The story doesn't end there.

Read more of this story at Slashdot.

A 100,000-Router Botnet Is Feeding On a 5-Year-Old UPnP Bug In Broadcom Chips

Slashdot - Tue, 11/13/2018 - 21:00
An anonymous reader quotes a report from Ars Technica: A recently discovered botnet has taken control of an eye-popping 100,000 home and small-office routers made from a range of manufacturers, mainly by exploiting a critical vulnerability that has remained unaddressed on infected devices more than five years after it came to light. Researchers from Netlab 360, who reported the mass infection late last week, have dubbed the botnet BCMUPnP_Hunter. The name is a reference to a buggy implementation of the Universal Plug and Play protocol built into Broadcom chipsets used in vulnerable devices. An advisory released in January 2013 warned that the critical flaw affected routers from a raft of manufacturers, including Broadcom, Asus, Cisco, TP-Link, Zyxel, D-Link, Netgear, and US Robotics. The finding from Netlab 360 suggests that many vulnerable devices were allowed to run without ever being patched or locked down through other means. Last week's report documents 116 different types of devices that make up the botnet from a diverse group of manufacturers. Once under the attackers' control, the routers connect to a variety of well-known email services. This is a strong indication that the infected devices are being used to send spam or other types of malicious mail.

Read more of this story at Slashdot.

Douglas Rain, Voice of HAL 9000 In '2001: A Space Odyssey,' Dies At 90

Slashdot - Tue, 11/13/2018 - 18:00
schwit1 shares a report from The Hollywood Reporter: Douglas Rain, the veteran Canadian stage actor who provided the soft and gentle voice of the rogue HAL 9000 computer for Stanley Kubrick's classic 2001: A Space Odyssey and its sequel, has died. He was 90. The first drafts of the 2001 script had HAL being voiced by a woman and was called Athena; afterward, it was decided that the computer should sound more like a man. Nigel Davenport, Martin Balsam and others were tried out -- and ruled out -- before and during filming of the 1968 sci-fi thriller. "Well, we had some difficulty deciding exactly what HAL should sound like, and Marty just sounded a little bit too colloquially American, whereas Rain had the kind of bland mid-Atlantic accent we felt was right for the part,' Kubrick told Newsday film critic Joseph Gelmis in an interview for the 1970 book The Film Director as Superstar. Kubrick told Rain that he had made the computer "too emotional and too human." So, in late 1967, the actor flew to New York City and spent a day and a half -- about 9 1/2 hours in all -- to voice HAL. As reported on the blog 2010: The Year We Make Contact, Rain "did the recordings with his bare feet resting on a pillow, in order to maintain the required relaxed tone."

Read more of this story at Slashdot.

Israel Aims To Ban Gasoline, Diesel Vehicles By 2030

Slashdot - Tue, 11/13/2018 - 11:30
An anonymous reader quotes a report from CleanTechnica: 2030 seems like a long way off, but it's really just around the corner. And when the bell tolls at midnight on December 31, 2030, you may not be able to buy a gasoline- or diesel-powered vehicle in Israel. After that date, all passenger cars will be electric and all trucks will be powered by electricity or compressed natural gas, if a proposal currently under consideration gets approved by the government. A final decision is expected by the end of this year. Energy Minister Yuval Steinitz [told Reuters last month] the biggest challenge will be creating a "critical mass" of electric and CNG powered vehicles before the deadline arrives. "We are already encouraging [the transition] by funding ... more than 2,000 new charging stations around the country," he says. The plan was set in motion one day after the United Nations issued its latest climate assessment that finds nations must do far more than they are currently doing in order to stave off warmer global average temperatures that will put the environment at risk. In order to reach the goal, the Israeli government will "reduce taxation on electric cars to almost zero, so they are going to be much cheaper," Energy Minister Yuval Steinitz said. He expects there will be about 177,000 electric cars on Israeli roads around 2025. By 2030, the expectation is that there will be nearly 1.5 million EVs in the country. The country has a ways to go though, as there are less than 100 electric cars on the roads today.

Read more of this story at Slashdot.

Facebook To Let French Regulators Investigate On Moderation Processes

Slashdot - Tue, 11/13/2018 - 10:05
Facebook and the French government are working together to look at the social media company's efforts to moderate content on its site. "At the start of 2019, French regulators will launch an informal investigation on algorithm-powered and human moderation," reports TechCrunch. "Facebook is willing to cooperate and give unprecedented access to its internal processes." From the report: Regulators will look at multiple steps: how flagging works, how Facebook identifies problematic content, how Facebook decides if it's problematic or not and what happens when Facebook takes down a post, a video or an image. This type of investigation is reminiscent of banking and nuclear regulation. It involves deep cooperation so that regulators can certify that a company is doing everything right. It's still unclear who's going to be in charge of this investigation. There could be regulators from France's telecom regulator (ARCEP), from the government's tech team (DINSIC), from the TV and radio regulator (CSA)... There's one thing for sure, the French government wants to focus on hate speech for now, so don't expect anyone from the privacy regulator (CNIL). The investigation isn't going to be limited to talking with the moderation teams and looking at their guidelines. The French government wants to find algorithmic bias and test data sets against Facebook's automated moderation tools.

Read more of this story at Slashdot.

Should Comcast Be Investigated For Antitrust Violations?

Slashdot - Tue, 11/13/2018 - 09:25
The American Cable Association (ACA), an industry group that represents over 700 small and medium-sized cable operators, wants antitrust regulators to investigate whether Comcast-NBCUniversal is abusing its power to hurt smaller television and internet service providers. The group has "asked U.S. Assistant Attorney General Makan Delrahim to 'immediately' open an investigation into Comcast's practices," reports The Verge. Comcast is denying the claims, and while the Justice Department hasn't publicly responded, that may change soon. President Donald Trump tweeted about the ACA's claims earlier this afternoon. From the report: The ACA claims Comcast has a uniquely powerful hold on the U.S. cable industry because it controls a large chunk of "must have" programming like NBC's regional sports channels. The group argues that the Comcast "has shown a willingness to harm rivals" in the past, even while bound by a 2011 consent decree that expired earlier this year. The letter is dated November 6th but was published today, after Fox Business Networks reported on its existence last week. Contra Trump's description, the letter doesn't seem to describe "routine" violations of antitrust law. It's primarily arguing that there's a huge risk of Comcast abusing its market position, while explaining just how much damage could result if Comcast did so. The ACA has put forward more concrete claims in the past, though -- like a 2017 complaint that Comcast was forcing smaller cable providers to bundle unwanted NBC-owned channels into TV packages, driving up their costs. The ACA's letter also raises concerns involving Hulu, suggesting that Comcast could effectively hold the service hostage. "We have heard from ACA members that they fear that ComcastNBCU may restrict, if it is not already restricting, their ability to access Hulu and make it available to their customers as an alternative to their cable offerings," reads the letter.

Read more of this story at Slashdot.

The Next Version of HTTP Won't Be Using TCP

Slashdot - Tue, 11/13/2018 - 08:45
"The HTTP-over-QUIC experimental protocol will be renamed to HTTP/3 and is expected to become the third official version of the HTTP protocol, officials at the Internet Engineering Task Force (IETF) have revealed," writes Catalin Cimpanu via ZDNet. "This will become the second Google-developed experimental technology to become an official HTTP protocol upgrade after Google's SPDY technology became the base of HTTP/2." From the report: HTTP-over-QUIC is a rewrite of the HTTP protocol that uses Google's QUIC instead of TCP (Transmission Control Protocol) as its base technology. QUIC stands for "Quick UDP Internet Connections" and is, itself, Google's attempt at rewriting the TCP protocol as an improved technology that combines HTTP/2, TCP, UDP, and TLS (for encryption), among many other things. Google wants QUIC to slowly replace both TCP and UDP as the new protocol of choice for moving binary data across the Internet, and for good reasons, as test have proven that QUIC is both faster and more secure because of its encrypted-by-default implementation (current HTTP-over-QUIC protocol draft uses the newly released TLS 1.3 protocol). In a mailing list discussion last month, Mark Nottingham, Chair of the IETF HTTP and QUIC Working Group, made the official request to rename HTTP-over-QUIC as HTTP/3, and pass it's development from the QUIC Working Group to the HTTP Working Group. In the subsequent discussions that followed and stretched over several days, Nottingham's proposal was accepted by fellow IETF members, who gave their official seal of approval that HTTP-over-QUIC become HTTP/3, the next major iteration of the HTTP protocol, the technology that underpins today's World Wide Web.

Read more of this story at Slashdot.

The Real Reason Palmer Luckey Was Fired From Facebook

Slashdot - Tue, 11/13/2018 - 08:03
ZDNet's Steven J. Vaughan-Nichols argues that the founder of Oculus, Palmer Luckey, wasn't fired because of his political views, as a recently-published Wall Street Journal article suggests, but because the virtual-reality company lost a $500 million intellectual property theft case to game maker ZeniMax. An anonymous reader shares the report: According to The Wall Street Journal, Palmer Luckey, the founder of Oculus, a virtual reality company, was fired by Facebook because "he donated $10,000 to an anti-Hillary Clinton group" during the 2016 U.S. Presidential campaign. But the article fails to mention a simple little fact: On Feb. 1, 2017, Oculus lost an intellectual property (IP) theft case against game maker ZeniMax, to the tune of $500 million. So, if one of your employees just cost your company a cool half-billion bucks for doing wrong what would you do? Well, Facebook isn't saying, even now, but on March 30, 2017, it let Luckey go. Yes, Luckey also lied about his political moves, which went well beyond donating to an anti-Hillary billboard campaign. But let's look at the record. Everyone knew he'd lied by Feb. 22, 2016. Was he fired then? No. Was he fired after being found guilty of stealing ZeniMax's trade secrets? Yes. Officially, Facebook stated: "All details associated with specific personnel matters are kept strictly confidential. This is our policy for all employees, no matter their seniority. But we can say unequivocally that Palmer's departure was not due to his political views." Let me spell it out for you: He made some political waves. Nothing happened. He cost Facebook $500 million. He was fired. Can anyone here seriously not draw the lines between the dots?

Read more of this story at Slashdot.

Vuln: SAP NetWeaver Knowledge Management CVE-2018-2477 XML External Entity Injection Vulnerability

SecurityFocus Vulnerabilities/Bugtraq - Tue, 11/13/2018 - 08:00
SAP NetWeaver Knowledge Management CVE-2018-2477 XML External Entity Injection Vulnerability
Syndicate content