I've been thinking about this over the last few days, ever since the story popped up in wired.

If they exceed the captcha's rate limit, the captcha -might- leak information in its rate-limiting error message. The message would be something like "your server at IP has exceeded its request limit."

This is likely because if you exceed the rate limit you'd kind of want to know which one of your front-ends was be the bad one.

Nobody really would test that sort of thing either.

Different trajectories implies different origins, but I'm sure there's a way to show that they could have had the same origin and got thrown into different orbits...which occasionally intersect with Earth.

Like college age kids, meteors seem to always travel in packs. The Chelyabinsk one was said not to be related to 2012Da/367943 Duende, but it sure is a hell of a coincidence that close flying meteors have an "unrelated friend" that impacts the Earth.

Maybe we got the ugly friend?

The media says Target was breached due to a compromise at their HVAC vendor. Do you want to be the vendor that gets hit with a liability suit because someone broke in through your network?

It's obvious from your question that you're not really sure what you're doing. SNMP? That's for network crap, not for server and application level stuff. Why would you even talk about SNMP? Why would you even want a VPN into the customer network?

If you need access to your server, write it into your support contract, and ask the vendor for a VPN login. Then the vendor can turn that login on and off when an outage occurs. Then just use NewRelic for monitoring (assuming your machine can get out).

If you need continuous access to your server, write it into your support contract, then make sure that (1) you really need it, and (2)your security is better than your customers' security.

Or, if you want to screw everyone, just run a TeamViewer instance on it and connect to it on the sly. I'm sure your customers would love that, but that's what you're basically asking them to allow you to do.

Ping is almost the worst way to check to see if your server is up. In fact, certain machines will return an ICMP response even after you've broken into their bios-equivalent (hello, Solaris).

Do a service level check.It's not that hard to do a curl instead of a ping. A curl's results can show you if it's present and functioning. A ping just shows you that the network interface is responding or not.

People disable ping because if you don't know a server is there you can't attack it. It's like enabling MAC address filtering - it doesn't really help that much, but it in a specific set of circumstances help a bit.

Maybe if you had read the release notes you wouldn't have posted such a retarded comment. Oh, and large chunks of the llvm/clang team work at Apple.

"During the 3.5 release cycle, Apple released the source used to generate 64-bit ARM programs on iOS platforms. This took the form of a separate backend that had been developed in parallel to, and largely isolation from, the existing code.

We decided that maintaining the two backends indefinitely was not an option, since their features almost entirely overlapped. However, the implementation details in both were different enough that any merge had to firmly start with one backend as the core and cherry-pick the best features and optimisations from the other.

After discussion, we decided to start with the Apple backend (called ARM64 at the time) since it was older, more thoroughly tested in production use, and had fewer idiosyncracies in the implementation details.

Many people from across the community worked throughout April and May to ensure that this merge destination had all the features we wanted, from both sources. In many cases we could simply copy code across; others needed heavy modification for the new host; in the most worthwhile, we looked at both implementations and combined the best features of each in an entirely new way.

We had also decided that the name of the combined backend should be AArch64, following ARM’s official documentation. So, at the end of May the old AArch64 directory was removed, and ARM64 renamed into its place.
"

If Oracle doesn't have the authority to compel teams of government employees to finalize their requirements, then they by definition Oracle isn't running the project.

google global warming hiatus ipcc

http://www.motherjones.com/env...

http://washington.cbslocal.com...
http://www.weather.com/news/sc...
http://articles.latimes.com/20...
http://www.theguardian.com/env...
http://www.climatecentral.org/...

Bleach isn't just for laundry. Look for "industrial cleaners", not "Laundry products."

Clorox doesn't have a lock on the laundry or cleaning products market by far. Plus, the figure is worldwide. There's a lot of bleach all over the place.

Not sure how accurate this is, since it's from wikipedia, but the reference seems legit.

In 2008, a study of common cleaning products found the presence of carbon tetrachloride in "very high concentrations" (up to 101 mg/m3) as a result of manufacturers' mixing of surfactants or soap with sodium hypochlorite (bleach).[18]

http://pubs.acs.org/doi/abs/10...

FTA:

"By mixing surfactants or soap with NaOCl, it was shown that the formation of carbon tetrachloride and several other halogenated VOCs is possible"

First, kill all the outdoor cats. Once the bird population recovers we can go after the power plants.

https://www.sciencenews.org/ar...

Humans have been interacting with technology since the dawn of the species.

"Hey grog, stop staring into that fucking fire all the time, it'll ruin your eyes"
"That beer is going to kill you"
"That meat stuff you're eating is unnatural. Humans were meant to eat berries and plants and shit."
"Cooking is going to rot your brain. Meat was meant to be eaten raw."

I mean, come on. Blame chemicals, which are more likely to be the problem than "man interacting with technology." That's like blaming your fleshbot for the fact that you don't meet any women - oh wait.

Bugs mostly come from when you're not paying attention, or you forgot something.

If you've doing difficult coding then writing code is the last thing you doing be doing. By the time you get to writing code it shouldn't be difficult anymore.

Wait, is this guy talking about space drives or global warming?

FTA:

1. The magnitude of these effects varied tremendously from experiment to experiment.
2. The threshold of measurement—the difference between a detection and a non-detection—was always extremely close to the actual claimed detection.
3. Many attempts at confirming the experiments by some of the leading scientists of the day, including Lord Kelvin, Heinrich Rubens and Robert Wood, all produced null results.
4. And finally, even if you restricted your data sets to the positive the experimental results, their claims were inconsistent with one another. //endtroll

It doesn't. But it matters in the court of public opinion, which is why this is news.