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: libgcrypt CVE-2017-0379 Information Disclosure Vulnerability

SecurityFocus Vulnerabilities/Bugtraq - Thu, 07/19/2018 - 08:00
libgcrypt CVE-2017-0379 Information Disclosure Vulnerability

Vuln: Oracle MySQL CVE-2018-2767 Incomplete Fix SSL Certificate Validation Security Bypass Vulnerability

SecurityFocus Vulnerabilities/Bugtraq - Thu, 07/19/2018 - 08:00
Oracle MySQL CVE-2018-2767 Incomplete Fix SSL Certificate Validation Security Bypass Vulnerability

Vuln: OpenSSL CVE-2017-3736 Information Disclosure Vulnerability

SecurityFocus Vulnerabilities/Bugtraq - Thu, 07/19/2018 - 08:00
OpenSSL CVE-2017-3736 Information Disclosure Vulnerability

IBM Wants $167 Million From Groupon Over Alleged Patent Infringement

Slashdot - Thu, 07/19/2018 - 07:30
On Monday, IBM asked a jury to award the company $167 million in a lawsuit against deals site Groupon for using patented technology without authorization. The patents involve e-commerce technology that had already been licensed to Amazon, Facebook, and Alphabet for between $20 million and $50 million per company. "Most big companies have taken licenses to these patents," IBM's lawyer, John Desmarais, said. "Groupon has not. The new kid on the block refuses to take responsibility for using these inventions." Reuters reports: Groupon lawyer J. David Hadden argued that IBM was overreading the scope of its patents and claiming ownership of building blocks of the internet. "A key question for you in this case is whether these patents cover the world wide web," Hadden told jurors. "They do not and that is because IBM did not invent the world wide web." An IBM executive is expected to testify during the two-week trial about licensing deals with technology companies like Amazon and Google, providing a rare glimpse into IBM's efforts to derive revenue from its large patent portfolio. The Armonk, New York-based company invests heavily in research and development and has secured more U.S. patents than any other company for the past 25 years.

Read more of this story at Slashdot.

Hackers Account For 90 Percent of Login Attempts At Online Retailers

Slashdot - Thu, 07/19/2018 - 06:50
Hackers account for 90% of of e-commerce sites' global login traffic, according to a report by cyber security firm Shape Security. They reportedly use programs to apply stolen data acquired on the dark web -- all in an effort to login to websites and grab something of value like cash, airline points, or merchandise. Quartz reports: These attacks are successful as often as 3% of the time, and the costs quickly add up for businesses, Shape says. This type of fraud costs the e-commerce sector about $6 billion a year, while the consumer banking industry loses out on about $1.7 billion annually. The hotel and airline businesses are also major targets -- the theft of loyalty points is a thing -- costing a combined $700 million every year. The process starts when hackers break into databases and steal login information. Some of the best known "data spills" took place at Equifax and Yahoo, but they happen fairly regularly -- there were 51 reported breaches last year, compromising 2.3 billion credentials, according to Shape. Taking over bank accounts is one way to monetize stolen login information -- in the US, community banks are attacked far more than any other industry group. According to Shape's data, that sector is attacked more than 200 million times each day. Shape says the number of reported credential breaches was roughly stable at 51 last year, compared with 52 in 2016. The best way consumers can minimize these attacks is by changing their passwords.

Read more of this story at Slashdot.

Zuckerberg: If Someone Gets Fired For Data Abuse 'It Should Be Me'

Slashdot - Thu, 07/19/2018 - 06:10
Mark Zuckerberg isn't planning to fire himself. At least, not at the moment. From a report: During an interview with Recode's Kara Swisher published Wednesday, the Facebook CEO touched on Russians interfering with US elections, misinformation, data breaches, the company's business model and more. When asked by Swisher who's to blame for the Cambridge Analytica scandal and related data misuse, Zuckerberg said he "designed the platform, so if someone's going to get fired for this, it should be me." Swisher followed up by asking if he was going to fire himself. "Not on this podcast right now," he said. Zuckerberg also defended the social media platform's decision not to kick off conspiracy theory-peddling websites like the far-right InfoWars. From a report: Zuckerberg said that instead of banning websites outright, the company removes individual posts that violate Facebook's terms of service. Posts promoting violence are particularly likely to be taken down, he added. Zuckerberg, who is Jewish, said even Holocaust deniers have a place on the platform as long as they genuinely believe the content they share. "I find that deeply offensive," he said. "But at the end of the day, I don't believe that our platform should take that down because I think there are things that different people get wrong. I don't think that they're intentionally getting it wrong."

Read more of this story at Slashdot.

Google Warns Android Might Not Remain Free Because of EU Decision

Slashdot - Thu, 07/19/2018 - 05:30
An anonymous reader quotes a report from The Verge: The EU's decision to force Google to unbundle its Chrome and search apps from Android may have some implications for the future of Android's free business model. In a blog post defending Google's decision to bundle search and Chrome apps on Android, Google CEO Sundar Pichai outlines the company's response to the EU's $5 billion fine. Pichai highlights the fact a typical Android user will "install around 50 apps themselves" and can easily remove preinstalled apps. But if Google is prevented from bundling its own apps, that will upset the Android ecosystem. "If phone makers and mobile network operators couldn't include our apps on their wide range of devices, it would upset the balance of the Android ecosystem," explains Pichai, carefully avoiding the fact that phone makers will no longer be forced to bundle these apps but can still choose to do so. Pichai then hints that the free Android business model has relied on this app bundling. "So far, the Android business model has meant that we haven't had to charge phone makers for our technology, or depend on a tightly controlled distribution model," says Pichai. "But we are concerned that today's decision will upset the careful balance that we have struck with Android, and that it sends a troubling signal in favor of proprietary systems over open platforms." While it may be a bluff to court popular opinion, Google is threatening to license Android to phone makers. "[I]f phone makers can bundle their own browsers instead of Chrome and point search queries toward rivals, then that could have implications for Google's mobile ad revenue, which constitutes more than 50 percent of the company's net digital ad revenue," reports The Verge.

Read more of this story at Slashdot.

Cisco Releases Security Updates

US-CERT - Thu, 07/19/2018 - 02:03
Original release date: July 18, 2018

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

NCCIC encourages users and administrators to review the Cisco Security Advisories and Alerts website and apply the necessary updates.

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


Bugtraq: [SECURITY] [DSA 4250-1] wordpress security update

SecurityFocus Vulnerabilities/Bugtraq - Thu, 07/19/2018 - 00:00
[SECURITY] [DSA 4250-1] wordpress security update

Bugtraq: [slackware-security] mutt (SSA:2018-198-01)

SecurityFocus Vulnerabilities/Bugtraq - Thu, 07/19/2018 - 00:00
[slackware-security] mutt (SSA:2018-198-01)

Bugtraq: [SECURITY] [DSA 4249-1] ffmpeg security update

SecurityFocus Vulnerabilities/Bugtraq - Thu, 07/19/2018 - 00:00
[SECURITY] [DSA 4249-1] ffmpeg security update

Bugtraq: [SECURITY] [DSA 4248-1] blender security update

SecurityFocus Vulnerabilities/Bugtraq - Thu, 07/19/2018 - 00:00
[SECURITY] [DSA 4248-1] blender security update

Appeals Court Won't Take Up Copyright Decision That Raised Alarm About Embedding, Linking

Slashdot - Wed, 07/18/2018 - 23:20
The 2nd Circuit denies an immediate appeal in a case that challenges how news organizations used embedded photos of Tom Brady. The Hollywood Reporter: Back in February, a New York judge caused a bit of a freakout by issuing a copyright decision regarding the embedding of a copyrighted photo of NFL superstar Tom Brady. Now comes another surprise with potentially big ramifications to the future of embedding and in-line linking: The 2nd Circuit Court of Appeals has denied an interlocutory appeal. Justin Goldman is the plaintiff in the lawsuit after finding the photo of the New England Patriots quarterback he shot and uploaded to Snapchat go viral. Many news organizations embedded social media posts that took Goldman's photo in stories about whether the Boston Celtics would recruit NBA star Kevin Durant with Brady's assistance. Breitbart, Heavy, Time, Yahoo, Vox Media, Gannett Company, Herald Media, Boston Globe Media Partners and New England Sports Network were defendants in the lawsuit, but many of these companies have since settled. Heavy has not, and in February, U.S. District Court Judge Katherine Forrest shocked many legal observers with a decision that refused to apply the "Server Test," where the direct liability of a website publisher for copyright infringement turns on whether the image is hosted on the publisher's own server or is embedded or linked from a third-party server. Although the Server Test has been adopted in other jurisdictions, Forrest wrote, "The plain language of the Copyright Act, the legislative history undergirding its enactment, and subsequent Supreme Court jurisprudence provide no basis for a rule that allows the physical location or possession of an image to determine who may or may not have 'displayed' a work within the meaning of the Copyright Act." She added, "Nowhere does the Copyright Act suggest that possession of an image is necessary in order to display it. Indeed, the purpose and language of the Act support the opposite view."

Read more of this story at Slashdot.

Top Voting Machine Vendor Admits It Installed Remote-Access Software on Systems Sold to States

Slashdot - Wed, 07/18/2018 - 22:40
Kim Zetter, reporting for Motherboard: The nation's top voting machine maker has admitted in a letter to a federal lawmaker that the company installed remote-access software on election-management systems it sold over a period of six years, raising questions about the security of those systems and the integrity of elections that were conducted with them. In a letter sent to Sen. Ron Wyden (D-OR) in April and obtained recently by Motherboard, Election Systems and Software acknowledged that it had "provided pcAnywhere remote connection software ... to a small number of customers between 2000 and 2006," which was installed on the election-management system ES&S sold them. The statement contradicts what the company told me and fact checkers for a story I wrote for the New York Times in February. At that time, a spokesperson said ES&S had never installed pcAnywhere on any election system it sold. "None of the employees, ⦠including long-tenured employees, has any knowledge that our voting systems have ever been sold with remote-access software," the spokesperson said. ES&S did not respond on Monday to questions from Motherboard, and it's not clear why the company changed its response between February and April. Lawmakers, however, have subpoena powers that can compel a company to hand over documents or provide sworn testimony on a matter lawmakers are investigating, and a statement made to lawmakers that is later proven false can have greater consequence for a company than one made to reporters.

Read more of this story at Slashdot.

EU Regulators Fine Google Record $5 Billion in Android Case

Slashdot - Wed, 07/18/2018 - 22:00
The European Union hit Alphabet's Google with a record antitrust fine of $5.06 billion on Monday, a decision that could loosen the company's grip on its biggest growth engine: mobile phones. From a report:The European Commission ordered Google to end the illegal conduct within 90 days or face additional penalties of up to 5 percent of parent Alphabet's average daily worldwide turnover. The EU enforcer also dismissed Google's arguments citing Apple as a competitor to Android devices, saying the iPhone maker does not sufficiently constrain Google because of its higher prices and switching costs for users. The European Commission finding is the most consequential decision made in its eight-year antitrust battle with Google. The fine significantly outstrips the $2.8B charge Brussels imposed on the company last year for favoring its own site in comparison shopping searches. The decision takes aim at a core part of Google's business strategy over the past decade, outlawing restrictions on its Android operating system that allegedly entrenched Google's dominance in online search at a time when consumers were moving from desktop to mobile devices. Android is the operating system used in more than 80 per cent of the world's smartphones and is vital to the group's future revenues as more users rely on mobile gadgets for search services. Google has denied wrongdoing. The European Commission took issues with the following practices: In particular, Google: 1. has required manufacturers to pre-install the Google Search app and browser app (Chrome), as a condition for licensing Google's app store (the Play Store); 2. made payments to certain large manufacturers and mobile network operators on condition that they exclusively pre-installed the Google Search app on their devices; and 3. has prevented manufacturers wishing to pre-install Google apps from selling even a single smart mobile device running on alternative versions of Android that were not approved by Google (so-called "Android forks"). Update: Google has announced that it would be appealing against the record fine. In a statement, the company said, "Android has created more choice for everyone, not less. A vibrant ecosystem, rapid innovation and lower prices are classic hallmarks of robust competition. We will appeal the Commission's decision." Update 2: In a blog post, Sundar Pichai, CEO of Google, said, the European Commission's decision ignores and misses several facts. He wrote: Today, the European Commission issued a competition decision against Android, and its business model. The decision ignores the fact that Android phones compete with iOS phones, something that 89 percent of respondents to the Commission's own market survey confirmed. It also misses just how much choice Android provides to thousands of phone makers and mobile network operators who build and sell Android devices; to millions of app developers around the world who have built their businesses with Android; and billions of consumers who can now afford and use cutting-edge Android smartphones. Today, because of Android, there are more than 24,000 devices, at every price point, from more than 1,300 different brands, including Dutch, Finnish, French, German, Hungarian, Italian, Latvian, Polish, Romanian, Spanish and Swedish phone makers. [...] The free distribution of the Android platform, and of Google's suite of applications, is not only efficient for phone makers and operators -- it's of huge benefit for developers and consumers. If phone makers and mobile network operators couldn't include our apps on their wide range of devices, it would upset the balance of the Android ecosystem. So far, the Android business model has meant that we haven't had to charge phone makers for our technology, or depend on a tightly controlled distribution model. [...] Rapid innovation, wide choice, and falling prices are classic hallmarks of robust competition and Android has enabled all of them. Today's decision rejects the business model that supports Android, which has created more choice for everyone, not less. We intend to appeal. Update 3: The French government said on Wednesday that it welcomes the record fine imposed on Google by European Union regulators, with a government spokesman describing it as an "excellent decision."

Read more of this story at Slashdot.

Secretive Startup Zoox Is Building a Bidirectional Autonomous Car From the Ground Up

Slashdot - Wed, 07/18/2018 - 21:00
A secretive Australian startup called Zoox (an abbreviation of zooxanthellae, the algae that helps fuel coral reef growth) is working on an autonomous vehicle that is unlike any other. Theirs is all-electric and bidirectional, meaning it can cruise into a parking spot traveling one way and cruise out the other. It can make noises to communicate with pedestrians. It even has displays on the windows for passengers to interact with. Bloomberg sheds some light on this company, reporting on their ambitions to build the safest and most inventive autonomous vehicle on the road: Zoox founders Tim Kentley-Klay and Jesse Levinson say everyone else involved in the race to build a self-driving car is doing it wrong. Both founders sound quite serious as they argue that Zoox is obvious, almost inevitable. The world will eventually move to perfectly engineered robotic vehicles, so why waste time trying to incorporate self-driving technology into yesteryear's cars? Levinson, whose father, Arthur, ran Genentech Inc., chairs Apple Inc., and mentored Steve Jobs, comes from Silicon Valley royalty. Together, they've raised an impressive pile of venture capital: about $800 million to date, including $500 million in early July at a valuation of $3.2 billion. Even with all that cash, Zoox will be lucky to make it to 2020, when it expects to put its first vehicles on the road.

Read more of this story at Slashdot.

Video Raises Concerns About Excessive Thermal Throttling On 2018 MacBook Pro With Intel Core i9

Slashdot - Wed, 07/18/2018 - 19:00
Last week, Apple announced new MacBook Pros, including a 15-inch model that supports Intel's 6-core 2.9GHz i9 processor. YouTube Dave Lee managed to get his hands on this top-of-the-line device early and run some tests, revealing that the laptop gets severely throttled due to thermal issues. 9to5Mac reports: Dave Lee this afternoon shared a new video on the Core i9 MacBook Pro he purchased, and according to his testing, the new machine is unable to maintain even its base clock speed after just a short time doing processor intensive work like video editing. "This CPU is an unlocked, overclockable chip but all of that CPU potential is wasted inside this chassis -- or more so the thermal solution that's inside here," says Lee. He goes on to share some Premiere Pro render times that suggest the new 2018 MacBook Pro with Core i9 chip underperforms compared to a 2017 model with a Core i7 chip. It took 39 minutes for the 2018 MacBook Pro to render a video that the older model was able to render in 35 minutes. Premiere Pro is not well-optimized for macOS, but the difference between the two MacBook Pro models is notable. Lee ran the same test again with the 2018 MacBook Pro in the freezer, and in cooler temperatures, the i9 chip was able to offer outstanding performance, cutting that render time down to 27 minutes and beating out the 2017 MacBook Pro.

Read more of this story at Slashdot.

System76 Linux Computer Maker Offers a Sneak Peek Into Its New Factory

Slashdot - Wed, 07/18/2018 - 15:00
BrianFagioli shares a report from BetaNews: System76 has long been a Linux computer seller, but recently, it has transitioned into a Linux computer maker. What's the difference, you ask? Well, currently, the company doesn't really make its own computers. System76's laptops, for instance, are made by other manufacturers, which it re-brands as its own. No, System76 doesn't just slap its name on other company's laptops and ship them out the door. Actually, it works closely with the manufacturers, tweaks firmware, and verifies that both Ubuntu and its Ubuntu-based Pop!_OS will work well on the hardware. System76 then offers top-notch support too. In other words, the company isn't just selling a computer, but an experience too. Unfortunately, when you rely on other computer manufacturers, you don't fully control the experience. Ultimately, System76 cannot achieve its true vision without building its own laptops. And so, that is exactly what it is going to do! Yes, System76 will be building and selling the computers right here in the USA (Denver, Colorado to be exact). I mean, when your company supports open source ideology and takes pride in being "Made in America," how can you go wrong? Many folks in the Linux community are excited to see the fruits of System76's labor, and today, we get a small peek. No, the company isn't sharing any of its computer designs, but it is showing off its new manufacturing facility. In a new blog post by System76 customer service all-star Emma, she shares several photos of the new factory. [T]he space is absolutely massive! It seems System76 has very lofty goals. Exactly when these new computers both designed and manufactured by System76 will become available for purchase is anyone's guess. Quite frankly, based on the System76's blog post, it seems they are still at very early stages. With that said, it will be interesting to see what is born inside that factory in Colorado. The Linux community is anxiously awaiting something special.

Read more of this story at Slashdot.

The SIM Hijackers

Slashdot - Wed, 07/18/2018 - 13:55
Lorenzo Franceschi-Bicchierai of Motherboard has a chilling story on how hackers flip seized Instagram handles and cryptocurrency in a shady, buzzing underground market for stolen accounts and usernames. Their victim's weakness? Phone numbers. He writes: First, criminals call a cell phone carrier's tech support number pretending to be their target. They explain to the company's employee that they "lost" their SIM card, requesting their phone number be transferred, or ported, to a new SIM card that the hackers themselves already own. With a bit of social engineering -- perhaps by providing the victim's Social Security Number or home address (which is often available from one of the many data breaches that have happened in the last few years) -- the criminals convince the employee that they really are who they claim to be, at which point the employee ports the phone number to the new SIM card. Game over.

Read more of this story at Slashdot.

Is the Earth's Mantle Full of Diamonds?

Slashdot - Wed, 07/18/2018 - 11:30
An anonymous reader quotes a report from Gizmodo: Scientists' models show that sound waves seem to travel too quickly through the old, stable cores of continents, called "cratons," which extend deep into the mantle at depths around 120 to 150 kilometers (75 to 93 miles). Through observations, experiments, and modeling, one team figured that a potential way to explain the sound speed anomaly would be the presence of a lot of diamonds, a medium that allows for a faster speed of sound than other crystals. Perhaps the Earth is as much as 2 percent diamonds by volume, they found. Scientists have modeled the rock beneath continents through tomography, which you can think of as like an x-ray image, but using sound waves. But sound-wave velocities of around 4.7 kilometers per second (about 10,513 mph) are faster than sound-wave velocities in other kinds of minerals beneath the crust, according to the paper in the journal Geochemistry, Geophysics, Geosystems. The researchers realized that if the regions had either 3 percent diamonds by volume or 50 percent of a rock formed at high pressure and temperature called eclogite, it would enable the sound speeds they observed. But both of those numbers seemed too high, based on observations of the minerals that end up on the Earth's surface: diamond-containing rocks called kimberlites. The researchers compromised and figured that 20 percent eclogite and 2 percent diamonds could explain the high velocities. The diamonds could be sprinkled as crystals found uniformly throughout the cratons.

Read more of this story at Slashdot.

Syndicate content