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.

Internet Archive Launches a Commodore 64 Emulator

Slashdot - Wed, 10/10/2018 - 15:00
The Internet Archive has launched a free, browser-based Commodore 64 Emulator with over 10,500 programs that are "working and tested for at least booting properly." Interestingly, the emulator comes just before the launch of Commodore's own C64 Mini. "It's based off the VICE emulator version 3.2, which is a triumph of engineering," adds HardOCP.

Read more of this story at Slashdot.

'Why I Bid $700 For a Stolen PSN Account'

Slashdot - Wed, 10/10/2018 - 11:30
Patrick Klepek tells the story of a PlayStation Network user who had their 13-year-old account stolen via what appears to be a social engineering scheme against Sony. Klepek managed to track it down and start negotiating for its release. An anonymous Slashdot reader shares an excerpt from the report: 1,200. That's how much someone is asking for a PlayStation Network account I've been investigating for the past few weeks. "Secure," the person calls it, claiming the account will "never be touched" by the original owner again. "He won't be getting it back," they claim. More than a thousand dollars? That's a little rich for my blood, and so I counteroffer: $700. "Btc?" they respond, accepting my bid. (BTC refers to bitcoin. The majority of transactions like this take place using cryptocurrency; it's generally harder, but not impossible, to trace.) I didn't purchase the account, of course. But I could -- anyone could, if they only knew where to look. This account wasn't on a shady market because someone was clumsy with their digital security. They had a strong password and two-factor authentication. When they were notified about problems with their account, they called Sony and asked for help. Despite all this, despite proving their identity over and over, they lost access to their PSN account, including any trophies earned or any games purchased. It was gone...well, sort of. The original owner no longer had access, but this person -- the individual asking for $1,200 but who quickly and without hesitation dropped to $700 -- did.[...]More than likely, Sony itself is a victim of a clever social engineering scheme, in which a user, or series of users, repeatedly spammed their representatives, until it found someone willing to accept the limited information they did have, and calculated the system would eventually lock the account in their favor. Even a "failed" social engineering attempt can be a success, if the person calling comes away with new information about the account. Every company in the world can fall victim to social engineering, as there are no true fail safes. But Sony's setup seems especially ripe for it. Why didn't the system get flagged as "sensitive" sooner? Why can a user flip off two-factor authentication over the phone? How can an account get abandoned, when it's still active? There are ways Sony could have prevented this from happening. In the end, the original account owner was magically handed the account. "Sony promised that they were going to set it up so no reps could make any changes," the account owner said, "but they are still investigating how this happened."

Read more of this story at Slashdot.

The End of Coal Could Be Closer Than It Looks

Slashdot - Wed, 10/10/2018 - 10:50
The Intergovernmental Panel on Climate Change released a report on Monday saying that the world's electrical utilities need to reduce coal consumption by at least 60 percent over the next two decades through 2030 to avoid the worst effects of climate change that could occur with more than 1.5 degrees Celsius of warming. While that reduction seems out of reach, Bloomberg crunched some numbers and found that "it's possible to meet consumption-cut targets on the current path." From the report: The conventional wisdom is that this isn't possible, as rising demand from emerging economies, led by China and India, overwhelms the switch from fossil fuels in richer countries. That may underestimate the changing economics of energy generation, though. For one thing, it assumes that Asian countries will continue to build new coal-fired plants at a rapid rate, even though renewables are already the cheaper option in India and heading that way in China and Southeast Asia. For another, the falling cost and rising penetration of wind and solar is so recent that we're only just starting to see how they damage the business models of conventional generators. Thanks to the deflation of recent years, renewables already produce energy at a lower cost than thermal power plants. That causes the overall price of wholesale electricity to fall, reducing a conventional plant's revenue per megawatt-hour. When this drops below the generator's operating costs, the only away to avoid losing money is to switch off altogether. As a result, capacity factors -- the share of time when the plant is on and producing electricity -- decline as well, further undermining returns. The shift from an always-on "baseload" demand profile to a peaks-and-troughs one like this carries its own problems. The act of ramping up and down consumes fuel and causes the physical plant to wear out faster. Absent expensive refurbishments, that could take a decade off the 40- to 50-year life of a coal plant -- and banks will get progressively less likely to fund long-term refurbs as wind and solar further damage the economics of fossil power. Researchers at the Australian National University this year modeled the effect of this sort of scenario on that country's generation mix. Assuming that the cost of renewables continues to evolve in line with current trends, they found the average retirement age of coal plants falls to 30 years from 50 years. As a result, coal-powered generation drops by about 70 percent between 2020 and 2030. "Let's assume the addition of net new generation stops in 2020; that plant life reduces to 30 years from 40 years; and that capacity factors gradually fall from the current 50 percent to 35 percent, still well above the levels of the U.K.'s coal generators in recent years," the report says in closing. "The effect of those operating changes alone reduces coal-fired electricity output in 2030 by about 40 percent relative to the higher scenario. [...] Factor in a price on carbon or other robust government intervention and the decline would be much faster."

Read more of this story at Slashdot.

Walmart Patents Cart That Reads Your Pulse, Temperature

Slashdot - Wed, 10/10/2018 - 10:10
Walmart recently applied to patent biometric shopping handles that would track a shopper's heart rate, palm temperature, grip force, and walking speed. "The patent, titled 'System And Method For A Biometric Feedback Cart Handle' and published August 23, outlines a system where sensors in the cart send data to a server," reports Motherboard. "That server then notifies a store employee to check on individual customers." From the report: Over time, the server can build a database of data compared against store location and stress response, the patent says -- potentially valuable information for store planning. Other uses outlined in the patent include a pulse oximeter, for detecting when a customer's about to pass out, and a weight-triggered assisted push feature for propelling the cart itself. CBInsights suggests that these alerts could warn associates when several shoppers need help at the same time, or anticipate when arguments are about to break out.

Read more of this story at Slashdot.

Google To Launch Censored Search In China Despite Denials

Slashdot - Wed, 10/10/2018 - 09:30
Google intends to launch a censored version of its Search app for China sometime in the next six to nine months, according to a leaked transcript from a private employee meeting held last month. The Intercept's Ryan Gallagher today reported the company's Search engine chief, Ben Gomes, held a meeting to congratulate a room full of employees working on the platform, dubbed Project Dragonfly. From a report: According to The Intercept, Gomes talked about the launch timeline: "While we are saying it's going to be six and nine months [to launch], the world is a very dynamic place." He goes on to point out that the current political climate makes it difficult to pinpoint a definite timeline, but indicates employees should be ready to launch whenever a "window opens." These comments come in stark contrast to public statements given recently by both Gomes and Google's chief privacy officer, Kieth Enright. Speaking to members of Congress last month, Enright tried to skirt the issue of the Dragonfly project by playing dumb. According to Wired he didn't quite deny involvement, and in fact admitted the company had explored the idea, but simply stated Google wasn't "close to launching" the censored Search engine and that he was "not clear on the contours of what is in scope or out of scope for that project." Gomes took the soft-denial a step further when he told the BBC "Right now all we've done is some exploration, but since we don't have any plans to launch something there's nothing much I can say about it."

Read more of this story at Slashdot.

Pentagon's New Next-Gen Weapons Systems Are Laughably Easy To Hack

Slashdot - Wed, 10/10/2018 - 08:50
An anonymous reader quotes a report from ZDNet: New computerized weapons systems currently under development by the U.S. Department of Defense (DOD) can be easily hacked, according to a new report published today. The report was put together by the U.S. Government Accountability Office (GAO), an agency that provides auditing, evaluation, and investigative services for Congress. The report detailed some of the most eye-catching hacks GAO testers performed during their analysis: "In one case, it took a two-person test team just one hour to gain initial access to a weapon system and one day to gain full control of the system they were testing. Some programs fared better than others. For example, one assessment found that the weapon system satisfactorily prevented unauthorized access by remote users, but not insiders and near-siders. Once they gained initial access, test teams were often able to move throughout a system, escalating their privileges until they had taken full or partial control of a system. In one case, the test team took control of the operators' terminals. They could see, in real-time, what the operators were seeing on their screens and could manipulate the system. They were able to disrupt the system and observe how the operators responded. Another test team reported that they caused a pop-up message to appear on users' terminals instructing them to insert two quarters to continue operating. Multiple test teams reported that they were able to copy, change, or delete system data including one team that downloaded 100 gigabytes, approximately 142 compact discs, of data." The report claims the DOD documented many of these "mission-critical cyber vulnerabilities," but Pentagon officials who met with GAO testers claimed their systems were secure, and "discounted some test results as unrealistic." GAO said all tests were performed on computerized weapons systems that are still under development. GAO officials highlighted that hackers can't yet take control over current weapons systems and turn them against the U.S. But if these new weapons systems go live, the threat is more than real, GAO said.

Read more of this story at Slashdot.

Google's Human-Sounding Phone Bot Is Coming To the Pixel Next Month

Slashdot - Wed, 10/10/2018 - 08:10
Google's human-sounding AI software that makes calls for you is coming to Pixel smartphones next month in select markets, like New York, Atlanta, Phoenix, and the San Francisco Bay Area. Google Duplex, as it is called, will be a feature of Google Assistant and, for now, will only be able to call restaurants without online booking systems, which are already supported by the assistant. Wired reports: A Google spokesperson told WIRED that the company now has a policy to always have the bot disclose its true nature when making calls. Duplex still retains the human-like voice and "ums," "ahs," and "umm-hmms" that struck some as spooky, though. Nick Fox, the executive who leads product and design for Google search and the company's assistant, says those interjections are necessary to make Duplex calls shorter and smoother. "The person on the other end shouldn't be thinking about how do I adjust my behavior, I should be able to do what I normally do and the system adapts to that," he says. Fox, the Google exec leading the project, pitches Duplex as a win-win. Google users will be freed from having to make phone calls to plan their outings; restaurants without online booking systems will gain new customers. "Those businesses lose out because people say 'Unless I can book this online I'm not going to book,'" he says. Some people closer to the restaurant business worry that Duplex might make calling restaurants too easy for Google users. Gwyneth Borden, executive director of the Golden Gate Restaurant Association, a trade group for Bay Area restaurants, says people may use the technology to book multiple reservations and then flake out, or call restaurants over and over. Restaurants can opt out of receiving Duplex calls by speaking up during a call from Duplex, or through the website where businesses can manage listing information shown in Google's search and maps services. When calls go awry -- Fox says the "overwhelming majority" work out fine -- the software will alert an operator in a Google call center who takes over.

Read more of this story at Slashdot.

Vuln: wolfSSL CVE-2017-13099 Information Disclosure Vulnerability

SecurityFocus Vulnerabilities/Bugtraq - Wed, 10/10/2018 - 08:00
wolfSSL CVE-2017-13099 Information Disclosure Vulnerability

Vuln: IBM General Parallel File System CVE-2016-0263 Unspecified Local Privilege Escalation Vulnerability

SecurityFocus Vulnerabilities/Bugtraq - Wed, 10/10/2018 - 08:00
IBM General Parallel File System CVE-2016-0263 Unspecified Local Privilege Escalation Vulnerability

Vuln: Samba CVE-2016-2114 Remote Security Bypass Vulnerability

SecurityFocus Vulnerabilities/Bugtraq - Wed, 10/10/2018 - 08:00
Samba CVE-2016-2114 Remote Security Bypass Vulnerability

Vuln: Samba CVE-2016-2118 Man in the Middle Security Bypass Vulnerability

SecurityFocus Vulnerabilities/Bugtraq - Wed, 10/10/2018 - 08:00
Samba CVE-2016-2118 Man in the Middle Security Bypass Vulnerability

KDE Plasma 5.14 Released

Slashdot - Wed, 10/10/2018 - 07:30
jrepin writes: KDE has released Plasma 5.14 desktop. Among many other things, Plasma 5.14 simplifies managing multiple displays thanks to its new Display Configuration widget; Global Menus a la macOS now work also with GTK applications like GIMP; a new safeguard feature warns you if other users are logged in when you log out; and Discover now lets you install Snaps from all available channels (not just the default), orders software by release date, and shows package dependencies. Downloads can be found here.

Read more of this story at Slashdot.

Google Announces 'Home Hub' Smart Display With 7-Inch Screen, No Camera

Slashdot - Wed, 10/10/2018 - 06:50
At its Pixel 3 launch event, Google announced a smart speaker called the Google Home Hub, featuring a 7-inch display to give you visual information, making it easier to control smart home devices and view photos and the weather. Interestingly, Google decided not to include a camera in this device for privacy reasons, as they want you to feel comfortable placing it in an intimate location, such as a bedroom. PhoneDog reports: Google explains that Home Hub will be able to recognize who is speaking to it using Voice Match to provide info for that specific person, which should help to make the device more useful in homes with multiple people. And when you're not using Home Hub, a feature called Live Albums will let you select certain people and have Google Photos create albums with images of these people. Another feature of Google's Home Hub is the Home View. With it, you can easily see and control your smart home devices. And then there's Ambient EQ, which uses a sensor that'll adjust the color and brightness of the Home Hub screen based on the ambient lighting. That includes dimming the screen at night when it's time for bed. Google Home Hub will be available for $149 in four colors -- Chalk, Charcoal, Aqua, and Sand. It will launch on October 22nd and each purchase will come with six months of YouTube Premium.

Read more of this story at Slashdot.

Fully Self-Driving Cars May Hit US Roads in Pilot Program: NHTSA

Slashdot - Wed, 10/10/2018 - 06:12
Fully self-driving cars may be on the fast lane to U.S. roads under a pilot program the Trump administration said on Tuesday it was considering, which would allow real-world road testing for a limited number of the vehicles. Reuters: Self-driving cars used in the program would potentially need to have technology disabling the vehicle if a sensor fails or barring vehicles from traveling above safe speeds, the National Highway Traffic Safety Administration (NHTSA) said in a document made public Tuesday. NHTSA said it was considering whether it would have to be notified of any accident within 24 hours and was seeking public input on what other data should be disclosed including near misses. The U.S. House of Representatives passed legislation in 2017 to speed the adoption of self-driving cars, but the Senate has not approved it. Several safety groups oppose the bill, which is backed by carmakers. It has only a slender chance of being approved in 2018, congressional aides said.

Read more of this story at Slashdot.

VMware Releases Security Advisory

US-CERT - Wed, 10/10/2018 - 05:39
Original release date: October 09, 2018

VMware has released a security advisory to address a vulnerability in ESXi, Workstation, and Fusion. An attacker could exploit this vulnerability to cause a denial-of-service condition.

NCCIC encourages users and administrators to review VMware Security Advisory VMSA-2018-0025 and apply the necessary workarounds.

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


Microsoft Releases October 2018 Security Updates

US-CERT - Wed, 10/10/2018 - 04:35
Original release date: October 09, 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 October 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.


Adobe Releases Security Updates

US-CERT - Wed, 10/10/2018 - 00:13
Original release date: October 09, 2018

Adobe has released security updates to address vulnerabilities in Adobe Digital Editions, Framemaker, and Technical Communications Suite. An attacker could exploit these vulnerabilities to take control of an affected system.

NCCIC encourages users and administrators to review Adobe Security Bulletins APSB18-27, APSB18-37, and APSB18-38 and apply the necessary updates.

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


National Cybersecurity Awareness Month: Careers in Cybersecurity

US-CERT - Tue, 10/09/2018 - 19:06
Original release date: October 09, 2018

October is National Cybersecurity Awareness Month, an annual campaign to raise awareness about cybersecurity. The month’s themes educate students and professionals about cybersecurity attack methods, best practices, and preventive measures and are geared toward informing the next generation of cybersecurity professionals. It is critical that today’s students graduate ready to enter the workforce and are open to learning more about the growing field of cybersecurity.

NCCIC encourages interested candidates to review the following resources for information on cybersecurity employment opportunities:

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


Chrome 70's Upcoming Security Change Will Break Hundreds of Sites

Slashdot - Tue, 10/09/2018 - 10:05
When Chrome 70 arrives on October 16th, it will drop trust for a major HTTPS certificate provider, putting hundreds of popular websites at risk of breaking. "Chrome 70 is expected to be released on or around October 16, when the browser will start blocking sites that run older Symantec certificates issued before June 2016, including legacy branded Thawte, VeriSign, Equifax, GeoTrust and RapidSSL certificates," reports TechCrunch. From the report: [D]espite more than a year to prepare, many popular sites are not ready. Security researcher Scott Helme found 1,139 sites in the top one million sites ranked by Alexa, including Citrus, SSRN, the Federal Bank of India, Pantone, the Tel-Aviv city government, Squatty Potty and Penn State Federal to name just a few. Ferrari, One Identity and Solidworks were named on the list but recently switched to new certificates, escaping any future outages. HTTPS certificates encrypt the data between your computer and the website or app you're using, making it near-impossible for anyone -- even on your public Wi-Fi hotspot -- to intercept your data. Not only that, HTTPS certificates prove the integrity of the the site you're visiting by ensuring the pages haven't been modified in some way by an attacker. Most websites obtain their HTTPS certificates from a certificate authority, which abide by certain rules and procedures that over time become trusted by web browsers. If you screw that up and lose their trust, the browsers can pull the plug on all of the certificates from that authority. For these reasons, Google stopped supporting Symantec certificates last year after it was found to be issuing misleading and wrong certificates, as well as allowing non-trusted organizations to issue certificates without the proper oversight.

Read more of this story at Slashdot.

UK High Court Blocks Billion-Dollar Privacy Lawsuit Against Google

Slashdot - Tue, 10/09/2018 - 09:25
An anonymous reader quotes a report from the BBC: The High Court has blocked a bid to sue Google for allegedly unlawfully taking data from 4.4 million UK iPhone users. The legal case was mounted by a group called Google You Owe Us, led by former Which director Richard Lloyd. It sought compensation for people whose handsets were tracked by Google for several months in 2011 and 2012. Mr Lloyd said he was "disappointed" by the ruling and his group would appeal, but Google said it was "pleased" and thought the case was "without merit." Mr Justice Warby who oversaw the case explained that it was blocked because the claims that people suffered damage were not supported by the facts advanced by the campaign group. Another reason for blocking it, he said, was the impossibility of reliably calculating the number of iPhone users affected by the alleged privacy breach. The complaint made by Google You Owe Us alleged that the cookies were used by Google to track people and get around settings on Apple's Safari browser that blocked such monitoring. Ads were sold on the basis of the personal information gathered by Google's cookies. The Safari workaround was used by Google on lots of different devices but the UK case centered on iPhone users. The group hoped to win $1.3 billion in compensation for affected users.

Read more of this story at Slashdot.

Syndicate content