The tweet announcing his passing:
— Terry Pratchett (@terryandrob)
March 12, 2015
AT LAST, SIR TERRY, WE MUST WALK TOGETHER.
Internet providers no longer have to keep their clients phone, internet and email details because privacy is more important, a Dutch court ruled on Wednesday.
Digital Rights organisation Bits of Freedom writes in a Blog:
The law’s underlying European directive was meant as a tool in the fight against serious crimes. The Dutch law, however, is much more expansive, including everything from terrorism to bike theft. During the hearing, the state’s attorneys avowed that the Public Prosecution does not take the law lightly, and would not call on the law to request data in case of a bicycle theft. The judge’s response: it doesn’t matter if you exploit the possibility or not, the fact that the possibility exists is already reason enough to conclude that the current safeguards are unsatisfactory.
Link to Original Source
Link to Original Source
Wow, Gmail finally caught up with Hotmail. (That should stir the pot sufficiently.)
Caught up? gmail has offered 2 factor authentication for at least 5 years.
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
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.
Well, AOL has finally come clean. Apparently individuals unknown accessed AOL's servers and took screen names, account information including mailing addresses, contact lists, encrypted passwords and encrypted answers to security questions. And possibly credit card information. AOL claims that it affects "only" 2% of their members, but recommends that everyone change their passwords and security questions.
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.
DMARC (Domain-based Message Authentication, Reporting & Conformance) is a two year old proposed standard previously discussed on Slashdot that is intended to curb email abuse, including spoofing an phishing. Unfortunately, as implemented by Yahoo, it claims most mailing list users as collateral damage. Messages posted to mailing lists (including listserv, mailman, majordomo, etc) by Yahoo subscribers are blocked when the list forwards them to other Yahoo (and other participating ISP's) subscribers. List members not using Yahoo or its partners are not affected and will receive posts from Yahoo users. And posts from non-Yahoo users are delivered to Yahoo members. So essentially those suffering the most are Yahoo's (comcast's, att's, etc) own customers. Hacker News has details about why DMARC has this affect on mailing lists. Their best proposed solution is to ban Yahoo email users from mailing lists and encourage them to switch to other ISPs. Unfortunately, it isn't just Yahoo, although they are getting the most attention.