News for hackers. Stuff that matters.
Re:4chan Intrusion Postmorterm by voltagex_ on Wednesday April 30, 2014 @01:05AM (#7671711)
Can't read it here, could someone post the text?
Re:4chan Intrusion Postmorterm by Buge on Wednesday April 30, 2014 @01:06AM (#7671717)
Concerning a recent intrusion

Last week we were made aware of a software vulnerability that allowed an intruder access to administrative functions and information from one of our databases. The intruder later stated their motive was to expose the posting habits of a specific user they disliked.

After careful review, we believe the intrusion was limited to imageboard moderation panels, our reports queue, and some tables in our backend database. Due to the way the intruder extracted information from the database, we have detailed logs of what was accessed. The logs indicate that primarily moderator account names and credentials were targeted.

Three 4chan Pass users had their Pass credentials accessed, and were notified and offered refunds and lifetime Passes shortly after the discovery. As a reminder, all payment information is processed securely by Stripe—we never see nor store any of it, and thus no payment information was compromised.

We patched the vulnerability quickly after it came to our attention, and have spent—and will continue to spend—dozens of hours poring over our software and systems to help mitigate and prevent future intrusions.

We’re sorry it happened, and will do our best to ensure it doesn’t happen again.

—moot

Re:4chan Intrusion Postmorterm by alloyed on Wednesday April 30, 2014 @01:15AM (#7671738)
I suspect a lot of people will be unable to read it if they use HTTPS everywhere: the 4chan blog does not support https and the EFF is currently in a ruleset freeze so they cannot reflect that until the next stable version is out.
Re:4chan Intrusion Postmorterm by ZoF on Wednesday April 30, 2014 @01:24AM (#7671759)
Tumblr only recently added SSL support, which is likely the reason Moot hasn't implemented it yet.

That said, I(unfortunately) doubt that HTTPS-everywhere is being utilized by that many people.

Re:4chan Intrusion Postmorterm by hrrsn on Wednesday April 30, 2014 @05:44AM (#7672375)
That's only for the dashboard. Blogs are still cleartext. It's possible to do SSL for *.tumblr.com domains but not (easily) for custom ones.
Re:4chan Intrusion Postmorterm by willvarfar on Wednesday April 30, 2014 @01:56AM (#7671832)
A lot of corporate firewalls block access to 4chan etc.
Re:4chan Intrusion Postmorterm by nwh on Wednesday April 30, 2014 @02:36AM (#7671916)
Re:4chan Intrusion Postmorterm by corobo on Wednesday April 30, 2014 @05:26AM (#7672331)
This is the first .newlongwordtld domain I've seen that isn't a spam site squatting on a popular domain equivalent. A new era has begun
Re:4chan Intrusion Postmorterm by nwh on Wednesday April 30, 2014 @08:26AM (#7672806)
Yeah, only because .is domains were being compromised and a new TLD was chosen as an easy alternative.
Re:4chan Intrusion Postmorterm by voltagex_ on Wednesday April 30, 2014 @07:22PM (#7677166)
>.is domains were being compromised

Can you elaborate?

Re:4chan Intrusion Postmorterm by nwh on Wednesday April 30, 2014 @11:39PM (#7678071)
Re:4chan Intrusion Postmorterm by voltagex_ on Thursday May 01, 2014 @12:38AM (#7678262)
> Content Blocked (content_filter_denied)

> Content Category: "Proxy Avoidance"

Another day, another block at $employer. Curiously, web.archive.org is allowed.

Thanks for the link.

Re:4chan Intrusion Postmorterm by id on Wednesday April 30, 2014 @01:08AM (#7671725)