devicenull

You get to respond to a continuous stream of DMCA and abuse complaints!

However, this largely doesn't happen. (If it happened everywhere, we wouldn't have issues like this)

> Security. Kill the _GET and _POST and _SERVER arrays and introduce a proper API that can be used to filter all incoming data.

So, reinvent magic quotes?

> kill save_mode, open_basedir and other acient concepts

safe mode is already gone (removed in 5.4)

So, you're complaining about a completely unrelated company... for what reason?

  Lets look at what it can read.
  ... It can read apache static content, like web page data.
  Well what can't it read?
  user_home_t - This is where I keep my credit card data
  *db_t - No database data.

So, it can't read database data directly, but presumably your website can already connect to the database. Which means it can read out your database credentials, and just connect to the database?

On shared hosting systems, you have to design the system with the assumption that someone is always compromised. So, additional accounts getting compromised should just be business as usual.

Seriously, if you're on shared hosting, it's almost certain that at least one person on the server is compromised/malicious

Post the script?

It seems they could easily hit the metadata service to determine if a machine is patched or not.

You can buy an OBD-II reader for $8. It's cheap enough that the first time it tells you your gas cap was loose, it's paid for itself.

So, for a trivial cost you can get your verbose option. Most people are not going to have any knowledge or desire to have this information, so it's a silly feature to include.

Does the VirtIO-RNG functionality provided by qemu help here? Linux will use it as a hardware RNG.

And any other x86 OS that supports VirtIO :)

This, just like IP spoofing is something that should be straightforward to correct. However, the carrier in both cases has incentives to continue allowing it (getting to charge for minutes, or bandwidth).

> Citing the Ubiquiti ER-lite 'Tolly' results just shows that you don't understand what they did to get their cited "performance".

What did they do?

It is, https://blog.torproject.org/blog/bittorrent-over-tor-isnt-go...

but hey.. anything to get free movies!

Think about this from your average end users perspective. They somehow manage to revoke permissions for an app, and parts of it stop working. They may not even realize they have revoked permissions, they would likely just assume the app is buggy.

Then they go and contact the developer for support, and make the developer spend a bunch of time troubleshooting why features aren't working.

All a feature like this would do is waste a lot of developer time, and cause users to unhappy with their phone/apps.

There appear to be a couple third party apps that do this: http://www.xda-developers.com/android/protecting-your-privac...

At least it wasn't a Python 3 book!

Half your pictures in that post are unavailable.

It is just about copyright infringement (and some other types of IP). Hence the name: Digital Millennium Copyright Act

EBR?

A PR article by Lyft makes you want to use them. No surprise there!

Although... if you have the engineering resources of Facebook, you can write your own IPMI software and probably get it working pretty well. They're all just embedded ARM systems after all..

I ran out of motivation, but I did manage to fix up some of the SuperMicro IPMI firmware: https://github.com/devicenull/supermicro_ipmi_firmware

Not without causing some significant disruptions. A lot of these are going to be compromised machines in someone's house. If you start launching attacks at a residential connection, you can start to interfere with other users that are near that person. (Since most residential connections are shared, at one point or another)

NANOG post from this morning has the AS path:

http://mailman.nanog.org/pipermail/nanog/2014-August/069131....

I'm unsure exactly which was originating the route.

A /24 is not a 'weirdly specific route'. I agree, that the upstream should have been filtering things, but you can't expect them to just filter out all the /24's.

For example, Google DNS anycast would stop working: http://bgp.he.net/net/8.8.8.0/24 as would basically anyone else doing anycast.

Getting IPMI controllers to do what you want is anything but trivial :)

IPMI firmware. It's insecure, unusable garbage.

HEPA filter + box fan is very common, and very cheap. Not sure why this is particularly notable.

Getting consumer ISPs to respond to obvious abuse cases (DDOS attacks) is very difficult. Getting them to respond to fraud (which they'd have to investigate more then looking at a bandwidth graph) seems impossible.

Now throw a language barrier on top, and it's even more difficult.

Hell, getting accurate abuse contact information is a project all by itself.

Just make sure you don't run into https://github.com/coreos/docs/issues/219 !

Read up on the actual DMCA procedure, if the hosting company is in the US. You can file a counter-claim if they actually end up receiving a valid DMCA.

If only the BBB had any actual power!