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: Foreman CVE-2018-14664 Multiple HTML Injection Vulnerabilities

SecurityFocus Vulnerabilities/Bugtraq - Thu, 10/10/2019 - 08:00
Foreman CVE-2018-14664 Multiple HTML Injection Vulnerabilities

Bugtraq: [SECURITY] [DSA 4269-1] postgresql-9.6 security update

SecurityFocus Vulnerabilities/Bugtraq - Sat, 01/19/2019 - 00:00
[SECURITY] [DSA 4269-1] postgresql-9.6 security update

Bugtraq: [SECURITY] [DSA 4268-1] openjdk-8 security update

SecurityFocus Vulnerabilities/Bugtraq - Sat, 01/19/2019 - 00:00
[SECURITY] [DSA 4268-1] openjdk-8 security update

Bugtraq: [SECURITY] [DSA 4267-1] kamailio security update

SecurityFocus Vulnerabilities/Bugtraq - Sat, 01/19/2019 - 00:00
[SECURITY] [DSA 4267-1] kamailio security update

Bugtraq: [CVE-2018-12584] Heap overflow vulnerability in reSIProcate through 1.10.2

SecurityFocus Vulnerabilities/Bugtraq - Sat, 01/19/2019 - 00:00
[CVE-2018-12584] Heap overflow vulnerability in reSIProcate through 1.10.2

More rss feeds from SecurityFocus

SecurityFocus Vulnerabilities/Bugtraq - Sat, 01/19/2019 - 00:00
News, Infocus, Columns, Vulnerabilities, Bugtraq ...

Intel Core i9-9990XE: Up To 5.0 GHz, Auction Only

Slashdot - Fri, 01/18/2019 - 23:25
Ian Cutress, reporting for AnandTech: AnandTech has seen documents and supporting information from multiple sources that show that Intel is planning to release a new high-end desktop processor, the Core i9-9990XE. These documents show that the processors will not be sold at retail; rather they will only be sold to system integrators, and then only through a closed online auction. This new processor will be the highest numbered processor in Intel's high-end desktop line. The current top processor is the i9-9980XE, an 18 core part with a base frequency of 3.5 GHz and a turbo frequency of 4.0 GHz. The i9-9990XE, on the other hand, is not simply the 9980XE with an increase in frequency. The Core i9-9990XE will be a 14 core processor, but with a base frequency of 4.0 GHz and a turbo frequency of 5.0 GHz. This makes it a super-binned 9940X.

Read more of this story at Slashdot.

Have Aliens Found Us? A Harvard Astronomer on the Mysterious Interstellar Object 'Oumuamua

Slashdot - Fri, 01/18/2019 - 22:45
On October 19, 2017, astronomers at the University of Hawaii spotted a strange object travelling through our solar system, which they later described as "a red and extremely elongated asteroid." It was the first interstellar object to be detected within our solar system; the scientists named it 'Oumuamua, the Hawaiian word for a scout or messenger. The following October, Avi Loeb, the chair of Harvard's astronomy department, co-wrote a paper (with a Harvard postdoctoral fellow, Shmuel Bialy) that examined 'Oumuamua's "peculiar acceleration" and suggested that the object "may be a fully operational probe sent intentionally to Earth's vicinity by an alien civilization." Loeb has long been interested in the search for extraterrestrial life, and he recently made further headlines by suggesting that we might communicate with the civilization that sent the probe. Isaac Chotiner of The New Yorker has interviewed Loeb, who was frustrated that scientists saw 'Oumuamua too late in its journey to photograph the object. "My motivation for writing the paper is to alert the community to pay a lot more attention to the next visitor," he told Chotiner. An excerpt from the interview: The New Yorker: Your explanation of why 'Oumuamua might be an interstellar probe may be hard for laypeople to understand. Why might this be the case, beyond the fact that lots of things are possible? Loeb: There is a Scientific American article I wrote where I summarized six strange facts about 'Oumuamua. The first one is that we didn't expect this object to exist in the first place. We see the solar system and we can calculate at what rate it ejected rocks during its history. And if we assume all planetary systems around other stars are doing the same thing, we can figure out what the population of interstellar objects should be. That calculation results in a lot of possibilities, but the range is much less than needed to explain the discovery of 'Oumuamua. There is another peculiar fact about this object. When you look at all the stars in the vicinity of the sun, they move relative to the sun, the sun moves relative to them, but only one in five hundred stars in that frame is moving as slow as 'Oumuamua. You would expect that most rocks would move roughly at the speed of the star they came from. If this object came from another star, that star would have to be very special. [...]The New Yorker: Hold on. "'Not where is the lack of evidence so that I can fit in any hypothesis that I like?' " [Bailer-Jones, of the Max Planck Institute for Astronomy, in Heidelberg, Germany, has identified four possible home stars for 'Oumuamua, and was asked to respond to Loeb's light-sail theory by NBC.] Loeb: Well, it's exactly the approach that I took. I approached this with a scientific mind, like I approach any other problem in astronomy or science that I work on. The point is that we follow the evidence, and the evidence in this particular case is that there are six peculiar facts. And one of these facts is that it deviated from an orbit shaped by gravity while not showing any of the telltale signs of cometary outgassing activity. So we don't see the gas around it, we don't see the cometary tail. It has an extreme shape that we have never seen before in either asteroids or comets. We know that we couldn't detect any heat from it and that it's much more shiny, by a factor of ten, than a typical asteroid or comet. All of these are facts. I am following the facts. Last year, I wrote a paper about cosmology where there was an unusual result, which showed that perhaps the gas in the universe was much colder than we expected. And so we postulated that maybe dark matter has some property that makes the gas cooler. And nobody cares, nobody is worried about it, no one says it is not science. Everyone says that is mainstream -- to consider dark matter, a substance we have never seen. That's completely fine. It doesn't bother anyone. But when you mention the possibility that there could be equipment out there that is coming from another civilization -- which, to my mind, is much less speculative, because we have already sent things into space -- then that is regarded as unscientific. But we didn't just invent this thing out of thin air. The reason we were driven to put in that sentence was because of the evidence, because of the facts. If someone else has a better explanation, they should write a paper about it rather than just saying what you said.

Read more of this story at Slashdot.

That 773M Password 'Megabreach' is Years Old

Slashdot - Fri, 01/18/2019 - 22:06
Security reporter Brian Krebs writes: My inbox and Twitter messages positively lit up today with people forwarding stories from Wired and other publications about a supposedly new trove of nearly 773 million unique email addresses and 21 million unique passwords that were posted to a hacking forum. A story in The Guardian breathlessly dubbed it "the largest collection ever of breached data found." But in an interview with the apparent seller, KrebsOnSecurity learned that it is not even close to the largest gathering of stolen data, and that it is at least two to three years old. The dump, labeled "Collection #1" and approximately 87GB in size, was first detailed earlier today by Troy Hunt, who operates the HaveIBeenPwned breach notification service. Hunt said the data cache was likely "made up of many different individual data breaches from literally thousands of different sources." KrebsOnSecurity sought perspective on this discovery from Alex Holden, CTO of Hold Security, a company that specializes in trawling underground spaces for intelligence about malicious actors and their stolen data dumps. Holden said the data appears to have first been posted to underground forums in October 2018, and that it is just a subset of a much larger tranche of passwords being peddled by a shadowy seller online.

Read more of this story at Slashdot.

Google Play Malware Used Phones' Motion Sensors To Conceal Itself

Slashdot - Fri, 01/18/2019 - 21:00
An anonymous reader quotes a report from Ars Technica: Malicious apps hosted in the Google Play market are trying a clever trick to avoid detection -- they monitor the motion-sensor input of an infected device before installing a powerful banking trojan to make sure it doesn't load on emulators researchers use to detect attacks. The thinking behind the monitoring is that sensors in real end-user devices will record motion as people use them. By contrast, emulators used by security researchers -- and possibly Google employees screening apps submitted to Play -- are less likely to use sensors. Two Google Play apps recently caught dropping the Anubis banking malware on infected devices would activate the payload only when motion was detected first. Otherwise, the trojan would remain dormant. Security firm Trend Micro found the motion-activated dropper in two apps -- BatterySaverMobi, which had about 5,000 downloads, and Currency Converter, which had an unknown number of downloads. Google removed them once it learned they were malicious. The motion detection wasn't the only clever feature of the malicious apps. Once one of the apps installed Anubis on a device, the dropper used requests and responses over Twitter and Telegram to locate the required command and control server. Once Anubis was installed, it used a built-in keylogger that can steal users' account credentials. The malware can also obtain credentials by taking screenshots of the infected users' screen.

Read more of this story at Slashdot.

Motorola's RAZR Is Returning As a $1,500 Folding Smartphone

Slashdot - Fri, 01/18/2019 - 18:00
A new report from The Wall Street Journal says the Motorola RAZR might be making a comeback as a $1,500 foldable screen smartphone, and it could launch as early as February. The Verge reports: The original RAZR was one of the most iconic cellphones ever made, and it seems that Motorola's parent company Lenovo is looking to cash in on that branding with an updated foldable phone (similar to the one that Samsung has teased for later this year). Per the WSJ, the new RAZR will be exclusive to Verizon in the U.S. with a planned February launch, although the device is still in testing and details have yet to be finalized. Also unknown is nearly any concrete information about the phone. There's no word yet on things like screen size, specifications, or even form factor. Will the revived RAZR just borrow the name but use a more traditional landscape folding display? Will Lenovo follow the original RAZR design and have some sort of super long vertically folding screen? According to the WSJ report, Lenovo is hoping to manufacture over 200,000 of the new RAZRs, which may seem optimistic for a $1,500 luxury smartphone. But considering that the (admittedly much cheaper) RAZR V3 model sold 130 million units over its lifespan, if lightning does manage to strike twice, that goal might not be so hard to hit.

Read more of this story at Slashdot.

Netflix Says It Has 10 Percent of All TV Time In the US

Slashdot - Fri, 01/18/2019 - 15:00
In its fourth-quarter 2018 earnings report, Netflix disclosed some of its viewership numbers for hits such as "Bird Box." "Overall, Netflix said it serves about 100 million hours of video per day, earning an estimated 10 percent of all time spent in front of the TV in the U.S.," reports CNBC. The company also said "Bird Box" reached 80 million member households in its first four weeks on the streaming service. Unfortunately, it still didn't show exactly how many people have viewed the content. From the report: By way of comparison, during the week of Jan. 7, the top TV show was an NFL playoff game between the New Orleans Saints and Dallas Cowboys on Sunday, Jan. 13, which drew 33 million viewers, according to Nielsen. The top scripted show, "The Big Bang Theory," drew over 13 million. But Netflix does not view TV as its only competition. In its earnings note, it also said games such as Fortnite compete for attention. Fortnite reportedly draws 200 million players per week. The company also highlighted several of its international projects. Netflix said its original from Spain, "Elite," was watched by over 20 million member households worldwide in the first four weeks. "Bodyguard," co-produced with BBC One; "Baby," an original series from Italy, and "Protector," an original series from Turkey, all reached more than 10 million member households in their first four weeks, the company said. There was still one notable hit that Netflix didn't disclose numbers for: "Black Mirror: Bandersnatch." Instead, the company discussed in its earnings letter that the technology used to create the movie, its first interactive choose-your-own-adventure-style flick, will be used for interactive projects in the future.

Read more of this story at Slashdot.

World's Oldest Periodic Table Chart Found At University of St Andrews In Scotland

Slashdot - Fri, 01/18/2019 - 11:30
An anonymous reader quotes a report from Phys.Org: A periodic table chart discovered at the University of St Andrews is thought to be the oldest in the world. The chart of elements, dating from 1885, was discovered in the University's School of Chemistry in 2014 by Dr. Alan Aitken during a clear out. The storage area was full of chemicals, equipment and laboratory paraphernalia that had accumulated since the opening of the chemistry department at its current location in 1968. Following months of clearing and sorting the various materials a stash of rolled up teaching charts was discovered. Within the collection was a large, extremely fragile periodic table that flaked upon handling. Suggestions that the discovery may be the earliest surviving example of a classroom periodic table in the world meant the document required urgent attention to be authenticated, repaired and restored. Mendeleev made his famous disclosure on periodicity in 1869, the newly unearthed table was rather similar, but not identical to Mendeleev's second table of 1871. However, the St Andrews table was clearly an early specimen. The table is annotated in German, and an inscription at the bottom left -- "Verlag v. Lenoir & Forster, Wien" -- identifies a scientific printer who operated in Vienna between 1875 and 1888. Another inscription -- "Lith. von Ant. Hartinger & Sohn, Wien" -- identifies the chart's lithographer, who died in 1890. Working with the University's Special Collections team, the University sought advice from a series of international experts. Following further investigations, no earlier lecture chart of the table appears to exist. Professor Eric Scerri, an expert on the history of the periodic table based at the University of California, Los Angeles, dated the table to between 1879 and 1886 based on the represented elements. For example, both gallium and scandium, discovered in 1875 and 1879 respectively, are present, while germanium, discovered in 1886, is not.

Read more of this story at Slashdot.

Bioacoustic Devices Could Help Save Rainforests

Slashdot - Fri, 01/18/2019 - 10:10
"Researchers writing in Science argue that networked audio recording devices mounted in trees could be used to monitor wildlife populations and better evaluate whether conservation projects are working or not," writes Slashdot reader Damien1972. From the report: Compared to ground surveys and camera traps, the technology provides cheap continuous, real-time biodiversity monitoring at the landscape scale. Thousands of hours of recordings can now be collected with long-lasting batteries and stored digitally. In sites with solar power and cellular signal, multi-year recordings have now been transmitted and saved to scientists' databases. That's possible thanks to the steep drop in the price of equipment that enables researchers to collect more than short, isolated sound snapshots. The key, says co-authors Eddie Game of The Nature Conservancy and Zuzana Burivalova at Princeton University, is to build out enough data to understand how changing soundscapes reflect biodiversity on the ground. Game says he has found plenty of "high-conservation value" tropical forests that are devoid of key species. This is common in reserves set aside by owners of plantation crops such as palm oil. Algorithms can use these recording to learn the sound of healthy forests, and infer the composition of their species. In Papua New Guinea, for example, the researchers found soundscapes in fragmented forests were far quieter during the dawn and evening choruses, the short cacophonous periods during the changing of day and night. Once enough data has been collected [...] the technology can be applied to the zero deforestation commitments set by corporations.

Read more of this story at Slashdot.

Court Rejects FCC Request To Delay Net Neutrality Case

Slashdot - Fri, 01/18/2019 - 09:30
A federal appeals court denied the FCC's request to postpone oral arguments in a court battle over the agency's decision to repeal its net neutrality rules. The FCC had asked for the hearing to be postponed since the commission's workforce has largely been furloughed due to the partial government shutdown. The hearing remains set for February 1. The Hill reports: After the FCC repealed the rules requiring internet service providers to treat all web traffic equally in December of 2017, a coalition of consumer groups and state attorneys general sued to reverse the move, arguing that the agency failed to justify it. The FCC asked the three-judge panel from the D.C. Circuit Court of Appeals to delay oral arguments out of "an abundance of caution" due to its lapse of funding. Net neutrality groups opposed the motion, arguing that there is an urgent need to settle the legal questions surrounding the FCC's order.

Read more of this story at Slashdot.

Adding New DNA Letters Make Novel Proteins Possible

Slashdot - Fri, 01/18/2019 - 08:50
An anonymous reader quotes a report from The Economist: The fuzzy specks growing on discs of jelly in Floyd Romesberg's lab at Scripps Research in La Jolla look much like any other culture of E. coli. But appearances deceive -- for the dna of these bacteria is written in an alphabet that has six chemical letters instead of the usual four. Every other organism on Earth relies on a quartet of genetic bases: a (adenine), c (cytosine), t (thymine) and g (guanine). These fit together in pairs inside a double-stranded dna molecule, a matching t and c, g. But in 2014 Dr Romesberg announced that he had synthesised a new, unnatural, base pair, dubbed x and y, and slipped them into the genome of E. coli as well. Kept supplied with sufficient quantities of X and Y, the new cells faithfully replicated the enhanced DNA -- and, crucially, their descendants continued to do so, too. Since then, Dr Romesberg and his colleagues have been encouraging their new, "semisynthetic" cells to use the expanded alphabet to make proteins that could not previously have existed, and which might have properties that are both novel and useful. Now they think they have found one. In collaboration with a spin-off firm called Synthorx, they hope to create a less toxic and more effective version of a cancer drug called interleukin-2. Interleukin-2 works by binding to, and stimulating the activity of, immune-system cells called lymphocytes. The receptor it attaches itself to on a lymphocyte's surface is made of three units: alpha, beta and gamma. Immune cells with all three form a strong bond to interleukin-2, and it is this which triggers the toxic effect. If interleukin-2 can be induced to bind only to the beta and gamma units, however, the toxicity goes away. And that, experiments have shown, can be done by attaching polyethylene glycol (PEG) molecules to it. The trick is to make the PEGs stick. This is where the extended genetic alphabet comes in. Using it, Synthorx has created versions of interleukin-2 to which PEGs attach themselves spontaneously in just the right place to stop them linking to the alpha unit. Tested on mice, the modified molecule has exactly the desired anti-tumor effects. Synthorx plans to ask permission for human trials later this year.

Read more of this story at Slashdot.

Jack Bogle, the Man Who Revolutionized Investing, Dies At 89

Slashdot - Fri, 01/18/2019 - 08:10
Thelasko shares a report from MarketWatch: You can thank Thomas Edison for the light bulb casting light in your home, Henry Ford for your affordable, mass-produced car, and Apple's Steve Jobs for the astonishing computer in your pocket. And Jack Bogle, who died Wednesday [at the age of 89]. The low-cost mutual funds he helped pioneer at Vanguard aren't as sexy or dramatic as other inventions. And you can't really touch or see them. But their effect on everyday lives has been enormous. Bogle's low-cost index funds, and the imitators they have inspired, may have saved ordinary Main Street Americans a staggering $250 billion, or more, in mutual fund fees over the last forty years. According to the Investment Company Institute (ICI), there are now about 450 index mutual funds with around $3.4 trillion in assets. There are also 1,800 exchange-traded funds, also with around $3.4 trillion in assets.

Read more of this story at Slashdot.

Vuln: Linux Kernel 'kernel/events/core.c' Local Denial of Service Vulnerability

SecurityFocus Vulnerabilities/Bugtraq - Fri, 01/18/2019 - 08:00
Linux Kernel 'kernel/events/core.c' Local Denial of Service Vulnerability

Vuln: Linux Kernel 'arch/x86/kernel/cpu/mcheck/mce.c' Local Denial of Service Vulnerability

SecurityFocus Vulnerabilities/Bugtraq - Fri, 01/18/2019 - 08:00
Linux Kernel 'arch/x86/kernel/cpu/mcheck/mce.c' Local Denial of Service Vulnerability

Vuln: NTP CVE-2018-12327 Stack Buffer Overflow Vulnerability

SecurityFocus Vulnerabilities/Bugtraq - Fri, 01/18/2019 - 08:00
NTP CVE-2018-12327 Stack Buffer Overflow Vulnerability
Syndicate content