judgecorp writes "Fears that mobile phones cause cancer have never had strong backing from scientific research, but Israeli startup Tawkon is using those fears for an interesting business model. Its free app (banned from Apple's App Store, but on Android, BlackBerry and unlocked iPhones) tracks how much radiation your phone is emitting. This lets concerned users hold their phones away form their heads or whatever — but it also gives Tawkon a useful map of cellphone coverage around the world, which is the real asset it is monetizing — for the benefit of everyone, it says."

Read more of this story at Slashdot.

En man påträffades död på golvet inne i ett gatukök i Angereds centrum i kväll.

An anonymous reader writes "Smartphones running the open source Ubuntu operating system will be available to customers beginning in October 2013, Canonical CEO Mark Shuttleworth told CIO Journal. Ubuntu will be available on a full range of devices, including desktop and tablet computers, potentially providing corporate IT executives a way to reduce the number of devices they purchase and manage, and would allow users to access all manner of corporate data through a single, pocket-sized device. 'You can share Windows apps to the phone desktop,' said Mr. Shuttleworth during a meeting in New York Tuesday." Jon Brodkin adds, "Canonical is taking community input on what the core applications (e-mail, calendar, clock/alarm, weather, file manager, document viewer, YouTube, Facebook, and Twitter) should look like. The best aspects of community proposals will hopefully make it into Ubuntu phones when they finally hit the market sometime toward the end of 2013 or beginning of 2014. Take a look at the best designs Canonical has received so far."

Read more of this story at Slashdot.

An anonymous reader writes "In a move likely to have major political implications, the University of Düsseldorf has revoked the doctoral degree of Germany's science and education minister, Annette Schavan. The committee investigating allegations of plagiarism came to the conclusion that she 'systematically and deliberately claimed as her own intellectual achievements which she had in fact not produced herself.' Schavan wants to appeal the decision in court and has not resigned from her post so far."

Read more of this story at Slashdot.

An interesting blog post by Kristian Kielhofer describes how a specific SPI packet can kill an Intel Gigabit ethernet card [1]. If a card is exposed to this traffic, the system has to be physically power cycled. A reboot will not recover the system.

The network card crashed whenever the value 0x32 or 0x33 was found at offset 0x47f. Kristian first noticed this happening for specific SIP packets, but in the end, it turned out that any packet with 0x32 at 0x47f caused the crash. Intel traced the problem to an EEPROM used in this specific card (82574L). There are some links in the comment to the blog suggesting that others have run into this problem before. For example, the commend: ping -p 32 -s 1110 x.x.x.x can crash an affected card remotely.

[1]http://blog.krisk.org/2013/02/packets-of-death.html

------

Johannes B. Ullrich, Ph.D.

SANS Technology Institute

Twitter
(c) SANS Internet Storm Center. http://isc.sans.edu Creative Commons Attribution-Noncommercial 3.0 United States License.

Polisen spärrade av ett område i Angereds centrum i kväll.

An anonymous reader sends this quote from a blog post about a very odd technical issue and some clever debugging: "Packets of death. I started calling them that because that’s exactly what they are. ... This customer location, for some reason or another, could predictably bring down the ethernet controller with voice traffic on their network. Let me elaborate on that for a second. When I say “bring down” an ethernet controller I mean BRING DOWN an ethernet controller. The system and ethernet interfaces would appear fine and then after a random amount of traffic the interface would report a hardware error (lost communication with PHY) and lose link. Literally the link lights on the switch and interface would go out. It was dead. Nothing but a power cycle would bring it back. ... While debugging with this very patient reseller I started stopping the packet captures as soon as the interface dropped. Eventually I caught on to a pattern: the last packet out of the interface was always a 100 Trying provisional response, and it was always a specific length. Not only that, I ended up tracing this (Asterisk) response to a specific phone manufacturer’s INVITE. ... With a modified HTTP server configured to generate the data at byte value (based on headers, host, etc) you could easily configure an HTTP 200 response to contain the packet of death — and kill client machines behind firewalls!"

Read more of this story at Slashdot.