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.

How Security Pros Look at Encryption Backdoors

Slashdot - Fri, 08/18/2017 - 22:05
An anonymous reader shares a report: The majority of IT security professionals believe encryption backdoors are ineffective and potentially dangerous, with 91 percent saying cybercriminals could take advantage of government-mandated encryption backdoors. 72 percent of the respondents do not believe encryption backdoors would make their nations safer from terrorists, according to a Venafi survey of 296 IT security pros, conducted at Black Hat USA 2017. Only 19 percent believe the technology industry is doing enough to protect the public from the dangers of encryption backdoors. 81 percent feel governments should not be able to force technology companies to give them access to encrypted user data. 86 percent believe consumers don't understand issues around encryption backdoors.

Read more of this story at Slashdot.

Google Researchers Made An Algorithm To Delete Watermarks From Photos

Slashdot - Fri, 08/18/2017 - 21:00
"Researchers at Google have found a vulnerability in the way watermarks are used by stock imagery sites like Adobe Stock that makes it possible to remove the opaque stamp used to protect copyright," writes Khari Johnson via VentureBeat. "The consistent nature in which the watermarks are placed on photos can be exploited using an algorithm trained to recognize and automatically remove watermarks." From the report: Changing the position or opacity of a watermark do not impact the algorithm's ability to remove watermarks from images with copyright protection. Randomization, the researchers say, is required to keep images from being stolen. In results presented at the Computer Vision and Pattern Recognition conference last month, subtle modifications to each watermark can make it harder to remove watermarks. With these warped watermarks, attempts to get rid of watermarks with an algorithm or photo editing software leaves noticeable marks, rendering an image useless. "As often done with vulnerabilities discovered in operating systems, applications or protocols, we want to disclose this vulnerability and propose solutions in order to help the photography and stock image communities adapt and better protect its copyrighted content and creations," research scientists Tali Dekel and Michael Rubenstein wrote in a blog post today. "From our experiments much of the world's stock imagery is currently susceptible to this circumvention." You can learn more about the different types of randomization that can be done to combat watermark removal and see more example images in Google's blog post. The full report and research is available via the project's GitHub page.

Read more of this story at Slashdot.

iOS 11 Has a Feature To Temporarily Disable Touch ID

Slashdot - Fri, 08/18/2017 - 18:00
A new feature baked into iOS 11 lets you quickly disable Touch ID, which could come in handy if you're ever in a situation where someone (a cop) might force you to unlock your device. Cult of Mac reports: To temporarily disable Touch ID, you simply press the power button quickly five times. This presents you with the "Emergency SOS" option, which you can swipe to call the emergency services. It also prevents your iPhone from being unlocked without the passcode. Until now, there were other ways to temporarily disable Touch ID, but they weren't quick and simply. You either had to restart your iPhone, let it sit idle for a few days until Touch ID was temporarily disabled by itself, or scan the wrong finger several times. The police, or any government agency, cannot force you to hand over your iPhone's passcode. However, they can force you to unlock your device with your fingerprint. That doesn't work if your fingerprint scanner has been disabled.

Read more of this story at Slashdot.

New Immunotherapy Trial Cures Kids of Peanut Allergy For Up To Four Years

Slashdot - Fri, 08/18/2017 - 15:00
Using a new kind of immunotherapy treatment, Australian researchers have managed to cure a majority of the children in their study suffering from a peanut allergy. "The desensitization to peanuts persisted for up to four years after treatment," reports The Guardian. From the report: Tang, an immunologist and allergist, pioneered a new form of treatment that combines a probiotic with peanut oral immunotherapy, known as PPOIT. Instead of avoiding the allergen, the treatment is designed to reprogram the immune system's response to peanuts and eventually develop a tolerance. It's thought that combining the probiotic with the immunotherapy gives the immune system the "nudge" it needs to do this, according to Tang. Forty-eight children were enrolled in the PPOIT trial and were randomly given either a combination of the probiotic Lactobacillus rhamnosus with peanut protein in increasing amounts, or a placebo, once daily for 18 months. At the end of the original trial in 2013, 82% of children who received the immunotherapy treatment were deemed tolerant to peanuts compared with just 4% in the placebo group. Four years later, the majority of the children who gained initial tolerance were still eating peanuts as part of their normal diet and 70% passed a further challenge test to confirm long-term tolerance. The results have been published in the Lancet Child & Adolescent Health.

Read more of this story at Slashdot.

The Health Benefits of Wind and Solar Exceed the Cost of All Subsidies

Slashdot - Fri, 08/18/2017 - 11:30
New submitter TheCoroner writes: A paper in Nature Energy suggests that the benefits we receive from moving to renewables like wind and solar that reduce air pollution exceed the cost of the subsidies required to make them competitive with traditional fossil fuels. Ars Technica reports: "Berkeley environmental engineer Dev Millstein and his colleagues estimate that between 3,000 and 12,700 premature deaths have been averted because of air quality benefits over the last decade or so, creating a total economic benefit between $30 billion and $113 billion. The benefits from wind work out to be more than 7 cents per kilowatt-hour, which is more than unsubsidized wind energy generally costs. This study ambitiously tries to estimate the benefits from emissions that were avoided because of the increase in wind and solar energy from 2007 through 2015, and to do so for the whole of the U.S. Millstein and colleagues looked at carbon emissions, as well as sulphur dioxides, nitrogen oxides, and particulate matter, all of which contribute to poor air quality. There are other factors that also need to be considered. A rise in renewables isn't the only thing that has been changing in the energy sector: fuel costs and regulation have also played a role. How much of the benefit can be attributed to wind and solar power, and how much to other changes? The researchers used models that track the benefits attributable to renewable power as a proportion of the total reduction in emissions.

Read more of this story at Slashdot.

Video Is Coming To Reddit

Slashdot - Fri, 08/18/2017 - 09:25
An anonymous reader shares a report from Variety: Videos are coming to Reddit, thanks to a new feature that allows users to upload video clips directly to the service. Reddit rolled out the new video feature Tuesday after testing it with around 200 communities over the past couple of weeks. Reddit users are now able to upload videos of up to 15 minutes in length, with file sizes being limited to 1 gigabyte. Users will be able to upload videos via Reddit's website and its mobile apps for iOS and Android, with the latter offering basic trimming functionality as well. And, in keeping with the spirit of the site, Reddit is also offering a conversion tool to turn videos into animated Gifs. Videos are being displayed persistently, or pinned, meaning that users can scroll through the comments while the video keeps playing in the corner of their screen. And community moderators can opt not to allow videos in their Subreddits at all, with Le arguing that some discussion-heavy Subreddits may decide that the format just doesn't work for them.

Read more of this story at Slashdot.

PlayStation 4 Update 5.0 Officially Revealed

Slashdot - Fri, 08/18/2017 - 08:45
After the PlayStation 4's 5.0 update was leaked last week, Sony decided to officially reveal what's coming in the update. GameSpot highlights the new features in their report: Some of the enhancements center around streaming using the PS4's built-in broadcasting capabilities. PS4 Pro users will be able to stream in 1080p and 60 FPS, provided their connection is strong enough, and PSVR users will be able to see new messages and comments coming through while broadcasting. PSVR is also adding 5.1ch and 7.1ch virtual surround sound support. Next up, the PS4's Friends List is being updated with greater management tools, such as the ability to set up separate lists of friends. You'll be able to create a list of all the people you play Destiny with and send them all an invite, for example. This feature replaces the old Favorite Groups tab. In another move to help reduce the amount of time spent in menus, the Quick Menu is being updated to have more options. For example, you'll be able to check on download progress and see new party invites. You can also leave a party from within that menu and see your current Spotify playlist. Notifications are also being improved when watching films and TV, as you can now disable message and other notification pop-ups while watching media. You can also change how much of a message is displayed, as well as its color, when playing or watching any form of content. Finally, Parental Control features are being overhauled in favor of what Sony calls "Family on PSN." This replaces the old Master/Sub account system; instead, one user is deemed the Family Manager, and they can set up other accounts and appoint them as a Parent/Guardian, Adult, or Child. Parents or Guardians can restrict Child accounts in their "use of online features and communication with other players, set restrictions for games, restrict the use of the internet browser, and set spending limits for PlayStation Store." Note that Sony says the first time any North American user tries to set up an Adult account, they will be charged $0.50 "to verify that you are an adult."

Read more of this story at Slashdot.

Ukraine Hacker Cooperating With FBI In Russia Probe, Says Report

Slashdot - Fri, 08/18/2017 - 08:05
schwit1 shares a report from The Hill: A hacker in Ukraine who goes by the online alias "Profexer" is cooperating with the FBI in its investigation of Russian interference in the U.S. presidential election, The New York Times is reporting. Profexer, whose real identity is unknown, wrote and sold malware on the dark web. The intelligence community publicly identified code he had written as a tool used in the hacking of the Democratic National Committee ahead of last year's presidential election. The hacker's activity on the web came to a halt shortly after the malware was identified. The New York Times, citing Ukrainian police, reported Wednesday that the individual turned himself into the FBI earlier this year and became a witness for the bureau in its investigation. FBI investigators are probing Russian interference efforts and whether there was coordination between associates of President Trump's campaign and Moscow. Special counsel Robert Mueller is heading the investigation.

Read more of this story at Slashdot.

Vuln: Mozilla Firefox CVE-2017-7806 Use After Free Denial of Service Vulnerability

SecurityFocus Vulnerabilities/Bugtraq - Fri, 08/18/2017 - 08:00
Mozilla Firefox CVE-2017-7806 Use After Free Denial of Service Vulnerability

Vuln: Mozilla Firefox CVE-2017-7781 Man in the Middle Security Bypass Vulnerability

SecurityFocus Vulnerabilities/Bugtraq - Fri, 08/18/2017 - 08:00
Mozilla Firefox CVE-2017-7781 Man in the Middle Security Bypass Vulnerability

Vuln: Mozilla Firefox CVE-2017-7788 Security Bypass Vulnerability

SecurityFocus Vulnerabilities/Bugtraq - Fri, 08/18/2017 - 08:00
Mozilla Firefox CVE-2017-7788 Security Bypass Vulnerability

Motorola Patents a Display That Can Heal Its Own Cracked Screen With Heat

Slashdot - Fri, 08/18/2017 - 07:20
An anonymous reader quotes a report from The Verge: A patent published today explains how a phone could identify cracks on its touchscreen and then apply heat to the area in an effort to slightly repair the damage. The process relies on something called "shape memory polymer," a material that can apparently become deformed and then recovered through thermal cycling. Thermal cycling involves changing the temperature of the material rapidly. This material could be used over an LCD or LED display with a capacitive touch sensor layered in, as well. Although the phone could heat the polymer in order to restore it, a user's body heat can be used, too.

Read more of this story at Slashdot.

Facebook Downranks Video Clickbait and Fake Play Buttons

Slashdot - Fri, 08/18/2017 - 06:40
In a blog post, Facebook announced that it has started downranking the News Feed presence of links that display a fake play button in the preview image, as well as videos that are actually just a static image uploaded as a video file. While Facebook won't completely delete these posts unless they violate its other policies, it will be decreasing the distribution of these stories. TechCrunch reports: Facebook has prohibited the use of fake play buttons in advertisements under its policy against depicting non-existent functionality for a few years, News Feed Product Manager Greg Marra tells me. But the scourage has remained in the News Feed. Facebook says that if publishers want to denote there's a video behind a link, they should indicate that through Open Graph meta tags. They could also use words like "Watch" or "Video" in the headline or description. Meanwhile, Facebook's emphasis on video in News Feed has inspired the new menace of publishers uploading a static image as a video to get more eyeballs. These static image videos will be downranked too. Facebook is using a "motion scoring" system that detects movement inside a video to classify and demote these clips.

Read more of this story at Slashdot.

Hacker Claims To Have Decrypted Apple's Secure Enclave Processor Firmware

Slashdot - Fri, 08/18/2017 - 06:00
According to iClarified, a hacker by name of "xerub" has posted the decryption key for Apple's Secure Enclave Processor (SEP) firmware. "The security coprocessor was introduced alongside the iPhone 5s and Touch ID," reports iClarified. "It performs secure services for the rest of the SOC and prevents the main processor from getting direct access to sensitive data. It runs its own operating system (SEPOS) which includes a kernel, drivers, services, and applications." From the report: The Secure Enclave is responsible for processing fingerprint data from the Touch ID sensor, determining if there is a match against registered fingerprints, and then enabling access or purchases on behalf of the user. Communication between the processor and the Touch ID sensor takes place over a serial peripheral interface bus. The processor forwards the data to the Secure Enclave but can't read it. It's encrypted and authenticated with a session key that is negotiated using the device's shared key that is provisioned for the Touch ID sensor and the Secure Enclave. The session key exchange uses AES key wrapping with both sides providing a random key that establishes the session key and uses AES-CCM transport encryption. Today, xerub announced the decryption key "is fully grown." You can use img4lib to decrypt the firmware and xerub's SEP firmware split tool to process. Decryption of the SEP Firmware will make it easier for hackers and security researchers to comb through the SEP for vulnerabilities.

Read more of this story at Slashdot.

Judge Dismisses AT&T's Attempt To Stall Google Fiber Construction In Louisville

Slashdot - Fri, 08/18/2017 - 05:20
An anonymous reader quotes a report from Ars Technica: AT&T has lost a court case in which it tried to stall construction by Google Fiber in Louisville, Kentucky. AT&T sued the local government in Louisville and Jefferson County in February 2016 to stop a One Touch Make Ready Ordinance designed to give Google Fiber and other new ISPs quicker access to utility poles. But yesterday, U.S. District Court Judge David Hale dismissed the lawsuit with prejudice, saying AT&T's claims that the ordinance is invalid are false. "We are currently reviewing the decision and our next steps," AT&T said when contacted by Ars today. One Touch Make Ready rules let ISPs make all of the necessary wire adjustments on utility poles themselves instead of having to wait for other providers like AT&T to send work crews to move their own wires. Without One Touch Make Ready rules, the pole attachment process can cause delays of months before new ISPs can install service to homes. Google Fiber has continued construction in Louisville despite the lawsuit and staff cuts that affected deployments in other cities.

Read more of this story at Slashdot.

Dilution of Whisky -- the Molecular Perspective

Slashdot - Fri, 08/18/2017 - 04:40
From a new published paper in Scientific Report by Bjorn C. G. Karlsson and Ran Friedman: Despite the growing knowledge of the nature of water-alcohol mixtures on a molecular level, much less is known on the interaction of water, alcohol and small solutes. In particular, the nature of the interaction between the solvent and taste-carrying molecules, such as guaiacol, is not known. To address this gap, we used MD simulations to study the distribution of guaiacol in water-alcohol mixtures of different concentrations. Our simulations revealed that guaiacol is present at the air-liquid interface at ethanol concentrations that correspond to the alcohol content of bottled or diluted whiskies. Because the drink is consumed at the interface first, our findings help to understand why adding water to whisky helps to enhance its taste. A molecular understanding of the nature of taste compounds in water-alcohol mixtures allows for optimizing the taste of alcoholic spirits. [...] Overall, there is a fine balance between diluting the whisky to taste and diluting the whisky to waste.

Read more of this story at Slashdot.

Bugtraq: [SECURITY] [DSA 3943-1] gajim security update

SecurityFocus Vulnerabilities/Bugtraq - Fri, 08/18/2017 - 00:00
[SECURITY] [DSA 3943-1] gajim security update

Australia Joins China and Japan in Trying To Regulate Digital Currency Exchanges

Slashdot - Thu, 08/17/2017 - 23:20
Following moves by China and Japan to regulate digital currencies, Australia is attempting to crackdown on money laundering and terrorism financing with plans to regulate bitcoin exchanges. From a report: "The threat of serious financial crime is constantly evolving, as new technologies emerge and criminals seek to nefariously exploit them. These measures ensure there is nowhere for criminals to hide," said Australia's Minister for Justice Michael Keenan in a press release. The Australian government proposed a set of reforms on Thursday which will close a gap in regulation and bring digital currency exchange providers under the remit of the Australian Transactions and Reporting Analysis Centre. These exchanges serve as marketplaces where traders can buy and sell digital currencies, such as bitcoin, using fiat currencies, such as the dollar. The reform bill is intended to strengthen the Anti-Money Laundering and Counter-Terrorism Financing Act and increase the powers of AUSTRAC.

Read more of this story at Slashdot.

Thai Activist Jailed For the Crime of Sharing an Article on Facebook

Slashdot - Thu, 08/17/2017 - 22:40
An anonymous reader shares a report: Thai activist Jatuphat "Pai" Boonpattaraksa was sentenced this week to two and a half years in prison -- for the crime of sharing a BBC article on Facebook. The Thai-language article profiled Thailand's new king and, while thousands of users shared it, only Jutaphat was found to violate Thailand's strict lese majeste laws against insulting, defaming, or threatening the monarchy. The sentence comes after Jatuphat has already spent eight months in detention without bail. During this time, Jatuphat has fought additional charges for violating the Thai military junta's ban on political gatherings and for other activism with Dao Din, an anti-coup group. While in trial in military court, Jatuphat also accepted the Gwangzu Prize for Human Rights. When he was arrested last December, Jatuphat was the first person to be charged with lese majeste since the former King Bhumibol passed away and his son Vajiralongkorn took the throne. (He was not, however, the first to receive a sentence -- this past June saw one of the harshest rulings to date, with one man waiting over a year in jail to be sentenced to 35 years for Facebook posts critical of the royal family.) The conviction, which appears to have singled Jatuphat out among thousands of other Facebook users who shared the article, sends a strong message to other activists and netizens: overbroad laws like lese majeste can and will be used to target those who oppose military rule in Thailand.

Read more of this story at Slashdot.

Ericsson Is Planning To Cut 25,000 Jobs in Brutal Response To Crisis, Report Says

Slashdot - Thu, 08/17/2017 - 22:00
An anonymous reader shares a report: Multinational telecom operator Ericsson -- which carries 40% of the world's mobile traffic on its networks and is Sweden's second largest company by revenue -- reported another disappointing quarter last month. As response, the troubled company's new CEO Borje Ekholm announced costs cuts of 10 billion SEK ($1,25 bn) per year. He did not say how many jobs were at stake. Now insider sources have provided details to Svenska Dagbladet (SvD), indicating that Ericsson's restructuring will be more brutal than expected. The Swedish newspaper reports that there are advanced plans to cut Ericsson's operations by 80-90 percent in some markets, and centralize several European markets. However, the 14,000 employee-strong Swedish work force is to stay intact -- at least all R&D engineers. "Right now, Ericsson is hiring engineers to repair the damage that earlier saving packages caused. It's crucial that most of all the Swedish R&D department remains somewhat protected. They are the ones who will come up with the new solutions that will drive sales in the long term," said a person with insight into the process. According to internal sources, up to 25,000 people may be affected by the restructuring program. The Swedish company currently employs 109,000 people across 110 offices around the world.

Read more of this story at Slashdot.

Syndicate content