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: GNU Debugger (GDB) CVE-2017-9778 Denial of Service Vulnerability

SecurityFocus Vulnerabilities/Bugtraq - Fri, 06/23/2017 - 08:00
GNU Debugger (GDB) CVE-2017-9778 Denial of Service Vulnerability

Wireless and Drone Execs Praised President Trump as He Pledged To Cut Down Regulations

Slashdot - Fri, 06/23/2017 - 07:20
U.S. President Donald Trump offered support for emerging technologies including unmanned aerial vehicles and next-generation wireless networks in a meeting on Thursday with the chiefs of AT&T and General Electric and other business leaders. From a report: For the likes of AT&T CEO Randall Stephenson, the public audience with Trump offered an opportunity to continue nudging the U.S. government -- including in a scheduled, private session with the leader of the Federal Communications Commission earlier Thursday -- to cut back on restrictions that make it difficult for AT&T and other telecom giants to grow their footprint and deploy the new technologies, such as 5G wireless. Speaking with Recode later Thursday, Marcelo Claure, the chief executive of Sprint, said that he and others in his industry had emphasized to Trump that the government must help them deploy new tools like small cells -- essentially, mini cell towers that improve wireless connectivity. Trump, for his part, promised Thursday to cut down on "too many years of excessive government regulation" to enable innovators and investments to offer new cutting-edge tools in health care, science, medicine and communication. "We have had regulation that's been so bad, so out of line that it's really hurt our country," he said.

Read more of this story at Slashdot.

FCC Proposes $120 Million Fine On Florida Robocall Scammer

Slashdot - Fri, 06/23/2017 - 06:40
The FCC on Thursday proposed a $120 million fine on a Florida resident alleged to have made almost 100 million spoofed robocalls to trick consumers with "exclusive" vacation deals from well-known travel and hospitality companies. Reuters reports: The man, identified as Adrian Abramovich, allegedly made 96 million robocalls during a three-month period by falsifying caller identification information that matched the local area code and the first three digits of recipient's phone number, the FCC said. The calls, which were in violation of the U.S. telecommunications laws, offered vacation deals from companies such as Marriott International Inc, Expedia Inc, Hilton Inc and TripAdvisor Inc. Consumers who answered the calls were transferred to foreign call centers that tried to sell vacation packages, often involving timeshares. These call centers were not related to the companies, the FCC said.

Read more of this story at Slashdot.

Alphabet Says Uber Knew About Stolen Self-Driving Car Files

Slashdot - Fri, 06/23/2017 - 06:00
In a Wednesday filing with a California court, Alphabet said a former self-driving executive Anthony Levandowski hatched a plan with Uber to steal more than 14,000 proprietary documents, including designs for the sensors that help the car see its surroundings. CNET reports: Alphabet says Uber's former CEO, Travis Kalanick, knew about the files but told Levandowski to destroy them. Uber has argued that it did not encourage or condone Levandowski taking any files from Waymo or bringing them to Uber, and has noted that his employment agreement affirmed he wouldn't do that. The litigation between Alphabet and Uber has been reported as a primary reason Kalanick was forced to resign as Uber's CEO Tuesday.

Read more of this story at Slashdot.

Lawsuit Accuses Comcast of Cutting Competitor's Wires To Put It Out of Business

Slashdot - Fri, 06/23/2017 - 05:20
An anonymous reader quotes a report from Ars Technica: A tiny Internet service provider has sued Comcast, alleging that the cable giant and its hired contractors cut the smaller company's wires in order to take over its customer base. Telecom Cable LLC had "229 satisfied customers" in Weston Lakes and Corrigan, Texas when Comcast and its contractors sabotaged its network, the lawsuit filed last week in Harris County District Court said. Comcast had tried to buy Telecom Cable's Weston Lakes operations in 2013 "but refused to pay what they were worth," the complaint says. Starting in June 2015, Comcast and two contractors it hired "systematically destroyed Telecom's business by cutting its lines and running off its customers," the lawsuit says. Comcast destroyed or damaged the lines serving all Telecom Cable customers in Weston Lakes and never repaired them, the lawsuit claims. Telecom Cable owner Anthony Luna estimated the value of his business at about $1.8 million, which he is seeking to recover. He is also seeking other damages from Comcast and its contractors, including exemplary damages that under state statute could "amount to a maximum of twice the amount of economic damages, plus up to $750,000 of non-economic damages," the complaint says. CourtHouse News Service has a story about the lawsuit, and it posted a copy of the complaint.

Read more of this story at Slashdot.

'Coal King' Is Suing John Oliver, Time Warner, and HBO

Slashdot - Thu, 06/22/2017 - 23:20
Reader Daetrin writes: Robert E. Murray, CEO of one of the largest coal mining companies in the US, is suing John Oliver, HBO, and Time Warner for defamation (alternative source) over a comedic report on the status of the coal industry in John Oliver's "Last Week Tonight". The report began with the decline of the coal mining industry, Trump's promises to revive it, and the plight of the workers involved, but was also highly critical of the business practices and safety record of Murray Energy Corporation and Robert Murray's leadership of the company. When the company was contacted about the piece before airing they responded with a cease and desist letter and threatened to sue. John Oliver continued with the segment anyway, saying "I didn't really plan for so much of this piece to be about you, but you kinda forced my hand on that one."

Read more of this story at Slashdot.

AMD Looks To 'Crush' Intel's Xeon With New Epyc Server Chips

Slashdot - Thu, 06/22/2017 - 22:40
AMD has unveiled the first generation of Epyc, its new range of server processors built around its Zen architecture. Processors will range from the Epyc 7251 -- an eight-core, 16-thread chip running at 2.1 to 2.9GHz in a 120W power envelope -- up to the Epyc 7601: a 32-core, 64-thread monster running at 2.2 to 3.2GHz, with a 180W design power. From a report: These chips are built on the same fundamental architecture as the company's Ryzen CPU cores, and they're aimed at the incredibly powerful data center market. AMD's 32-core / 64-thread Epyc CPUs combine four eight-core dies, each connected to the other via the company's Infinity Fabric. According to AMD, this approach is significantly cheaper than trying to pack 32 cores into a single monolithic die -- that approach would leave the company potentially throwing away huge amounts of silicon during its production ramp. The Infinity Fabric is deliberately over-provisioned to minimize any problems with non-NUMA aware software, according to Anandtech. Each 32-core Epyc CPU will support eight memory channels and two DIMMs per channel, for a total maximum memory capacity of 2TB per socket, or 4TB of RAM in a two-socket system. Each CPU will also offer 128 lanes of PCI Express 3.0 support -- enough to connect up to six GPUs at x16 each with room left over for I/O support. That's in a one-socket system, mind you. In a two-socket system, the total number of available PCI Express 3.0 lanes is unchanged, at 128 (64 PCIe 3.0 lanes are used to handle CPU -- CPU communication). Anandtech has a longer writeup with more details on the CPUs power efficiency and TDP scaling. Further reading: ZDNet, press release.

Read more of this story at Slashdot.

With Her Blog Post About Toxic Bro-Culture at Uber, Susan Fowler Proved That One Person Can Make a Difference

Slashdot - Thu, 06/22/2017 - 22:01
Kara Swisher, writing for Recode: It was Lao Tzu who said that "the journey of a thousand miles begins with a single step." In the case of complete and utter change reeling through Uber right now -- culminating in the resignation of its once untouchable CEO Travis Kalanick -- it turns out that it began with one of the most epic blog posts to be written about what happens when a hot company becomes hostage to its increasingly dysfunctional and toxic behaviors. It was clear from the moment you read the 3,000-word post by former engineer Susan Fowler about her time at the car-hailing company that nothing was going to be the same. Titled simply, "Reflecting on one very, very strange year at Uber," the essay deftly and surgically laid out the map that the media and others would use to prove to its out-to-lunch board and waffling investors that Uber CEO Travis Kalanick had to go. In her account, Fowler was neither mean nor self-righteous, although in reading the story that she laid out about her horrible time there, it would have been completely fair for her to have taken that tone.

Read more of this story at Slashdot.

Verizon Is Killing Tumblr's Fight For Net Neutrality

Slashdot - Thu, 06/22/2017 - 21:00
An anonymous reader quotes a report from The Verge: In 2014, Tumblr was on the front lines of the battle for net neutrality. The company stood alongside Amazon, Kickstarter, Etsy, Vimeo, Reddit, and Netflix during Battle for the Net's day of action. Tumblr CEO David Karp was also part of a group of New York tech CEOs that met with then-FCC chairman Tom Wheeler in Brooklyn that summer, while the FCC was fielding public comment on new Title II rules. President Obama invited Karp to the White House to discuss various issues around public education, and in February 2015 The Wall Street Journal reported that it was the influence of Karp and a small group of liberal tech CEOs that swayed Obama toward a philosophy of internet as public utility. But three years later, as the battle for net neutrality heats up once again, Tumblr has been uncharacteristically silent. The last mention of net neutrality on Tumblr's staff blog -- which frequently posts about political issues from civil rights to climate change to gun control to student loan debt -- was in June 2016. And Tumblr is not listed as a participating tech company for Battle for the Net's next day of action, coming up in three weeks. One reason for Karp and Tumblr's silence? Last week Verizon completed its acquisition of Tumblr parent company Yahoo, kicking off the subsequent merger of Yahoo and AOL to create a new company called Oath. As one of the world's largest ISPs, Verizon is notorious for challenging the principles of net neutrality -- it sued the FCC in an effort to overturn net neutrality rules in 2011, and its general counsel Kathy Grillo published a note this April complimenting new FCC chairman Ajit Pai's plan to weaken telecommunication regulations.

Read more of this story at Slashdot.

Domestic Appliances Guzzle Far More Energy Than Advertised, Says EU Survey

Slashdot - Thu, 06/22/2017 - 18:00
Chrisq writes: An EU study has found that many electronic devices and appliances use more energy in real-world conditions than in the standard EU tests. Often the real world figures are double those in the ratings. Sometimes this is achieved by having various optional features switched off during the test. For example, switching on modern TV features such as "ultra-high definition" and "high-dynamic range" in real-world test cycles boosted energy use in four out of seven televisions surveyed -- one by more than 100%. However some appliances appear to have "defeat devices" built in, with some Samsung TVs appearing to recognize the standard testing clip: "The Swedish Energy Agency's Testlab has come across televisions that clearly recognize the standard film (IEC) used for testing," says the letter, which the Guardian has seen. "These displays immediately lower their energy use by adjusting the brightness of the display when the standard film is being run. This is a way of avoiding the market surveillance authorities and should be addressed by the commission."

Read more of this story at Slashdot.

Curiosity Rover Decides, By Itself, What To Investigate On Mars

Slashdot - Thu, 06/22/2017 - 15:00
sciencehabit writes: NASA's Curiosity rover landed on Mars in 2012, in part to analyze rocks to see whether the Red Planet was ever habitable (or inhabited). But now the robot has gone off script, picking out its own targets for analysis -- precisely as planned. Last year, NASA scientists uploaded a piece of software called Autonomous Exploration for Gathering Increased Science (AEGIS) adapted from the older Opportunity rover. Curiosity can now scan each new location and use artificial intelligence to find promising targets for its ChemCam. Compared with the estimated 24% success rate of random aiming at picking out outcrops -- a prime target for investigation -- the current version of AEGIS lets the rover find them 94% of the time, researchers report.

Read more of this story at Slashdot.

Microsoft Admits Disabling Anti-Virus Software For Windows 10 Users

Slashdot - Thu, 06/22/2017 - 11:30
An anonymous reader quotes a report from the BBC: Microsoft has admitted that it does temporarily disable anti-virus software on Windows PCs, following an competition complaint to the European Commission by a security company. In early June, Kaspersky Lab filed the complaint against Microsoft. The security company claims the software giant is abusing its market dominance by steering users to its own anti-virus software. Microsoft says it implemented defenses to keep Windows 10 users secure. In an extensive blog post that does not directly address Kaspersky or its claims, Microsoft says it bundles the Windows Defender Antivirus with Windows 10 to ensure that every single device is protected from viruses and malware. To combat the 300,000 new malware samples being created and spread every day, Microsoft says that it works together with external anti-virus partners. The technology giant estimates that about 95% of Windows 10 PCs were using anti-virus software that was already compatible with the latest Windows 10 Creators Update. For the applications that were not compatible, Microsoft built a feature that lets users update their PCs and then reinstall a new version of the anti-virus software. "To do this, we first temporarily disabled some parts of the AV software when the update began. We did this work in partnership with the AV partner to specify which versions of their software are compatible and where to direct customers after updating," writes Rob Lefferts, a partner director of the Windows and Devices group in enterprise and security at Microsoft.

Read more of this story at Slashdot.

Remember When You Called Someone and Heard a Song?

Slashdot - Thu, 06/22/2017 - 10:05
An anonymous reader shares a Motherboard article: If you were youngish in the early 2000s, you probably remember this phenomenon -- calling a friend's cell phone, and instead of hearing the the standard ring, you heard a pop song. Called ringback tones, this digital music fad allowed cell phone owners to subject callers to their own musical preference. Ringback tones were incredibly trendy in the early and mid-2000's, but have since tapered off nearly to oblivion. Though almost nobody is buying ringbacks anymore, plenty of people still have them from back in the day. [...] In the process of writing this story, I heard from several people that they or someone they knew still had a ringback tone, in large part because they have had it for years, and don't know how to get rid of it.

Read more of this story at Slashdot.

eBay Will Now Price Match Amazon, Walmart and Others On Over 50,000 Items

Slashdot - Thu, 06/22/2017 - 09:25
eBay announced today a new Price Match Guarantee for over 50,000 items across its site -- promising that it will have the best deal online, or it will match the lowest price of a competitor. While only select items are available for this offer, "the move is a significant effort on eBay's part to ensure that it doesn't lose customers to Amazon, Walmart and other online stores as the market consolidates behind the industry's major players," reports TechCrunch. From the report: In order to qualify, the item must be one of the new, unopened items sold daily through eBay Deals, for starters. Deals are eBay's selection of "trending" inventory across all its categories -- like consumer electronics, home & garden, and fashion. The deals are also generally offered at 20 percent to 90 percent off, and are sourced from over 900 of eBay's trusted sellers. These sellers include both smaller merchants looking to grow their customer base as well as major consumer brands. At any time, eBay says there are "tens of thousands" of items offered through the Deals site, with featured deals updating at least once per day, beginning at 8 AM PT.

Read more of this story at Slashdot.

NSA Opens GitHub Account, Lists 32 Projects Developed By the Agency

Slashdot - Thu, 06/22/2017 - 08:45
An anonymous reader quotes a report from The Hacker News: The National Security Agency (NSA) -- the United States intelligence agency which is known for its secrecy and working in the dark -- has finally joined GitHub and launched an official GitHub page. GitHub is an online service designed for sharing code amongst programmers and open source community, and so far, the NSA is sharing 32 different projects as part of the NSA Technology Transfer Program (TTP), while some of these are "coming soon." "The NSA Technology Transfer Program (TTP) works with agency innovators who wish to use this collaborative model for transferring their technology to the commercial marketplace," the agency wrote on the program's page. "OSS invites the cooperative development of technology, encouraging broad use and adoption. The public benefits by adopting, enhancing, adapting, or commercializing the software. The government benefits from the open source community's enhancements to the technology." Many of the projects the agency listed are years old that have been available on the Internet for some time. For example, SELinux (Security-Enhanced Linux) has been part of the Linux kernel for years.

Read more of this story at Slashdot.

Ask Slashdot: Best Way To Isolate a Network And Allow Data Transfer?

Slashdot - Thu, 06/22/2017 - 08:05
Futurepower(R) writes: What is the best way to isolate a network from the internet and prevent intrusion of malware, while allowing carefully examined data transfer from internet-facing computers? An example of complete network isolation could be that each user would have two computers with a KVM switch and a monitor and keyboard, or two monitors and two keyboards. An internet-facing computer could run a very secure version of Linux. Any data to be transferred to that user's computer on the network would perhaps go through several Raspberry Pi computers running Linux; the computers could each use a different method of checking for malware. Windows computers on the isolated network could be updated using Autopatcher, so that there would never be a direct connection with the internet. Why not use virtualization? Virtualization does not provide enough separation; there is the possibility of vulnerabilities. Do you have any ideas about improving the example above?

Read more of this story at Slashdot.

Vuln: Drupal Core CVE-2017-6920 Remote Code Execution Vulnerability

SecurityFocus Vulnerabilities/Bugtraq - Thu, 06/22/2017 - 08:00
Drupal Core CVE-2017-6920 Remote Code Execution Vulnerability

Vuln: JasPer 'jp2_dec.c' Remote Heap Buffer Overflow Vulnerability

SecurityFocus Vulnerabilities/Bugtraq - Thu, 06/22/2017 - 08:00
JasPer 'jp2_dec.c' Remote Heap Buffer Overflow Vulnerability

Vuln: Cisco Prime Infrastructure and Evolved Programmable Network Manager SQL Injection Vulnerability

SecurityFocus Vulnerabilities/Bugtraq - Thu, 06/22/2017 - 08:00
Cisco Prime Infrastructure and Evolved Programmable Network Manager SQL Injection Vulnerability

South Korea Signs On To Build Full-Scale Hyperloop System

Slashdot - Thu, 06/22/2017 - 07:25
Hyperloop Transportation Technologies (HTT) has partnered with the South Korean government and local universities to build the world's first full-scale Hyperloop system. "The agreement was actually signed back in January but only revealed this week, and sees HTT team up with the South Korean government's department of technological innovation and infrastructure, along with the Korea Institute of Civil Engineering and Building (KICT) and Hanyang University," reports New Atlas. From the report: It involves the construction of a full-scale testbed, licensing of HTT's vacuum tube, levitation, propulsion and battery technologies along with the co-development of safety standards and regulations. The agreement is a multi-year partnership intended to build a new transportation system for South Korea, one which will be known as the HyperTube Express and carry passengers between Seoul and Busan in under 20 minutes, compared to the current three-hour drive. HTT may be setting out to build the world's first Hyperloop but it is no guarantee, with fellow startups Arrivo and Hyperloop One also moving full-steam ahead with their plans. The latter in particular seems to be making solid progress, recently showing off a full-scale test track in Nevada and forming agreements with Russia, Finland and Dubai to explore the feasibility of a Hyperloop in those countries. It's too early to tell who will be first out of the gate, but the competition is certainly heating up.

Read more of this story at Slashdot.

Syndicate content