The credit card information was first offered up for sale Tuesday on an underground site that trafficks in stolen financial information, security author Brian Krebs reported on his blog, Krebsonsecurity.com."
Link to Original Source
Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!
I don't know if we ever will receive the precise details of this NSA operation, but I would still like to know:
1) How was the integrity of the shipping chain tainted? At which point NSA grabbed the devices and who allowed them to do this?
2) What does this "spyware" do, and does this mean a modified system firmware or something else?
Most of that is covered in Greenwald's book, and also in the NSA documents that have been released. The specific physical interception point is not described, but the modified firmware is. Once the router goes into service it "phones home" periodically and allows NSA to send monitoring instructions.
I just received a private communication from the moderator of a Google Group. He says that mail from Yahoo members is being blocked by Comcast and Yahoo. Now that it's Google's ox being gored perhaps something will be done about it.
The thing to do here is to fix the MLM software to use the correct additional headers, rather than rewriting the headers the DMARC policy feels are important; in addition, this would allow the DMARC policy to "whitelist" based on the attached headers, assuming everything else wasn't a black mark, and avoid the "greylisting" that would happen ordinarily with most SPAM filtering systems in "medium posture" rather than "low posture" (i.e. the ones that have the concept of "suspect email" as a middle ground).
I think you will find that most MLM software uses correct additional headers. At least listserv and mailman (for the lists that I manage) do. We've been playing nicely with ISPs for years on our lists, we create no spam (once we fixed the bounceback spam problem 3 years ago) and generally are among the more well-behaved email users around. The problem is that Yahoo's implementation of DMARC is not using the additional headers. All it looks at is From.
It's not blocking relayed mail in the usual sense. Most mailing lists use the original poster's email address as the FROM field so everyone on the list knows who posted the message. The SENDER field contains the actual list address. And that should match the sending server's IP address. So reverse DNS and SPF (and DKIM if enabled) will validate the SENDER as the list server software. The REPLY TO will be either the list or the original poster, depending on list policy. DMARC requires that the FROM field also match the sending server, and ignores SPF and DKIM.
The second way, and probably a preferable one, is to make the bricking recoverable by the end user, who must enter a password that they chose for their phone to unbrick the device. The password should not be of any pre-determinable length so that a hacker who wanted to unbrick the phone would not even know what the domain to try to guess the password by brute force might be. Ideally, such a password should not get reset simply by changing the sim card in the device, and changing it would require that the old password be entered first.
A bricked phone would be utterly useless for virtually any task... even using the apps that might be installed on it... the only thing it would be able to do is call emergency/911, which would remove much of the incentive to bother to steal phones.
That's exactly the way Activation Lock on the iPhone works. The lock is actually in Apple's activation servers and tied to the owner's iCloud ID and password, so wiping the phone does not get around the lock. When its serial number attempts to re-activate the phone it fails to activate. The only way around it is to know the owner's Apple ID and password. So having a secure password is an essential element in securing an iPhone, iPad or Mac (Activation lock works with all of them).
I'm on FIOS with their 50 down/25 up plan. Linode in Newark is 48Mbps, AWS East is 60Mbps. Just saying that a particular path is slow doesn't mean that it's Verizon interfering - it's more likely something else that's causing the problem.
I was able to duplicate your results with my FIOS 50 down/35 up plan). Speed to AWS was FASTER than the benchmark speed test (60 Mbps for AWS, 48 for the benchmark, 50 Mbps for Linode). If this is throttling they're doing it wrong. I repeated it several times and got similar results.
If you want a gimmick watch Casio will do you a nice one for about $30 but I have to warn you that the days of digital watches being cool ended in about 1980 so you won't be getting any Hipsters putting down their skinny lattes in shock and envy by buying a Pebble either.
"The days of the digital [watch] are numbered"
- Tom Stoppard, the original script of The Real Thing
(he dropped the line in later revisions)
Correct; In the wild each set of teeth lasts about 10 years, because there's a lot of silica in the grasses that are an elephant's primary diet. Elephants in captivity can live longer because their diet is less abrasive to their teeth.
Stinginess with privileges is kindness in disguise. -- Guide to VAX/VMS Security, Sep. 1984