servowire

The attack vector is a bit vague, and I'm not sure how to bring this news to some of my clients.

Is the exploit only for when running services on/to the internet (IIS, Exchange webmail, etc - ) , or is visiting an https (TLS) website on and end-user enough to make the exploit happen (even in Firefox/Chrome and behind a tradional proxy server).

Sadly Microsoft does not explain the exact parameters that make this exploit tick - this makes risk assessment hard.

Reminds me of BlackIce back in the day... awesome tool this Glasswire. This is what I wanted for everyday network paranoia.

I can't find prototype diagrams with dimensions or something, did you find any? Please link?

The paper is $25 .... mmm http://arc.aiaa.org/doi/abs/10.2514/6.2014-4029

This post has some more info https://plus.google.com/117663015413546257905/posts/WfFtJ8bY...

If this works, and if it's scale able, it would be something like the impulse drive. A normal spacedrive for speeds far below C and without space-warp.

But in space a few micronewtons per Kg is pretty usable.

I'm also looking for this.

This should be banned. Really. I don't want this on the same road as my loved ones. When you are driving, you are driving. Not reading/tweeting.

Even more, mounting "something" to the front window is illegal in a lot of places in the world [1]. At least Netherlands and U.S. In The Netherlands operating a phone while driving (voice operated carkit exempt) gives you a ~$250 fine.

Furthermore, obstructing part of your window is dangerous. You could miss something. And it's distracting (our eyes focus on motion).

What a idiotic idea.

[1]http://www.poi-factory.com/node/34521

This does seem valid, in a way. But is the same not true about Bitcoin then? I'm confused.

The solution to this kind of problems is: Make Read-only "disaster recovery" backups - zip it and burn it to a DVD set or Bluray, and put it off-site. Make incrementals or differentials of those discs every few months and a full data set each 3 months.

Takes a few hours, I like to burn all my data to Bluray (50GB per disk) while watching a movie.

Store the bluray data sets at a friend's house and never worry again.

All the miners would leave that pool if they did that. I would.

Well, you are flying a semi-toy without proper safety near people, buildings, above roads, cars, etc on a tourist site. An arrest might be slightly over the top, but this should not be allowed.

I'm a model RC pilot for 20 years and these kind of "stunts" are hurting the hobby. At least ask for permission next time.

A phantom only has 4 motors, and the quality is "meh" - there is hardly any 2nd control (fa I have tripple recievers in my jets, if one RC system fails I still regain control over another radio).

It has a "failsafe" - i=even if it works it's still not really good in an urban area. GPS signals might be weak (flyaway danger) and it's only flies to 25 meters when returning to home. It could fly into a tower or even not reach proper 25 meter when the 3D GPS lock is weak or disengaged.

My 2 cents. Sorry. Please people, don't fly above crowded areas. I've seen a Phantom hit a car it's almost 1KG of deadweight when it comes down. It's only a matter of time until someone gets hurt.

That would require trust - in the form of the SMS provider. No way to verify that SMS is valid, it could have been forged.

The proof-of-work blockchain transmission means it's the real and proper blockchain and is valid.

The blockchain can be pruned.

No, because proof-of-work prevents you from "faking" a blockchain. Let's say we are at block 100 and you would want to fake "the blockchain". You would have to fake a block every 10 minutes, but that requires mining, because you can't just make a block - it has to fit the previous one with the right difficulty.

You could stop sending new blocks, but that would alarm the endpoint because it will be stuck at block 100 (in our example).

The Proof-of-work scheme is pretty innovative.

With a DVB/Radio link to the network one could listen to transactions only to their address. You could think of bitcoin operated gas stations, bitcoin network-hubs in rural areas, micropayments to car-charging stations (all you need is power and a cheap DVB receiver to listen to the address "beacon" for a payment.

Now sending back transactions to the network is not covered, but can be done by using SMS or a small radio link to a local node. A bitcoin transaction is only about 64 bytes (!) so even a DTMF call or SMS should work fine.

A transaction send would look like this (normal TXid, in hex)

  a9d4599e15b53f3eb531608ddb31f48c695c3d0b3538a6bda871e8b34f2f430c

That would be

  76816061505687581068522220805344294890167166251289478281934616246172205973504 

in DTMF. Would take about 15 seconds to complete (http://www.audiocheck.net/audiocheck_dtmf.php)

Wouldn't it be possible to forge the SHA1 or a document?

Here's an idea: Put the files in encrypted containers on a Torrent network. Or use maidsafe.net or storj.io

I'm pretty sure any industry that handles documents etc. that would require a non-forgeable timestamp would not want (or are allowed due to regulation) to upload a billion dollar contract, legal document or patent to a website. No offence.

They would want an in-house, closed system with (of course) blockchain communication for the verification part. Or maybe a tool that creates a "Magic" executable that contains the a) file and b) a "Check" button to do the blockchain verification.

Yes, but that would be a centralized solution. When Twitter dies (wont happen, but still) or a rogue admin changes the timestamp, etc. - It requires a trusted party - Twitter - instead of the blockchain.

Nice project, really well done. Thanks for posting

I wonder how this deals with like .docx files or .xlsx (Excel) files. Even of you change 0 fields it might end up "mutated" and the Proof does not longer work.

A single flipped byte destroys the entire concept. Tech savvy people can deal with this, but not the average joe.

Cool concept nonetheless.

The fact that this machine is still in operation is awesome. What a piece of engineering.

I fly quad and tricopters a lot, and this is very unsafe. Any motor beyond 2210 size are flying meat-cutters. Even the plastic props, but especially the carbonfiber once can seriously cut flesh, en tendons. You see; these bruhless motors have mass in their bell, and once they rotate they won't stop (like a gasser). They keep chopping.

Story time. A flying buddy had his micro-quad (only 5 inch props) setup on the table. He bumped into the remote and throttle lock was not engaged. One of the props cut his wrist, and hit a few arteries and tendons. They had to pull back a tendon from inside his arm (so he told me). I feel sick just thinking how it looked.

All he said at that moment was "I'm going to need a Doctor".

Another story. I had a tricopter on top of the table. I was calibrating with (my mistake) props attached. I programmed the arduino telling it to arm when a certain switch was "On". But this switch was already on. The moment the Atmel cpu initalized it send the motors to "Arm" and in a panic I grabbed the remote hitting the throttle a bit. The battery was beside the tricopter so it was light. It took of, chopped off the chandeleer's power cable, in to the teak-wooden table and my arm. It was a mess and I still have a scar 2 inches long. It needed stitching. It was only 20% of throttle.

To the point: Tie-ing a meatgrinder, even if it's a Parrot, to a dog is a bad idea. So please don't try this on your favorite mutt. At the very least use propguards or impellors.

I don't remember the exact details, but I once had a DB admin flabbergasted because there was a non-numeric character in a field/row that was numeric. The DB engine crashed upon starting and could not clean it up.

I think it was Oracle.

If I remember correctly we had to get the vendor involved

This happened after an unclean shutdown (power failure). The disk were RAID, but the cache battery was dead so there was some corrupt data written to the disk on block level.

THis could happen too on a kill -9.

Don't exaggerate the impact of a kill -9. It can be safe if a homegrown application has a bug or there is a hardware failure preventing a clean reboot (like a locked IO to a disk that is no longer in order).

Sure it will mess up some things, but when management is pushing to limit the downtime of, for instance, a golden-image provisioned Linux machine, I'd kill it off no problem.

Now when we are talking a hardware box running some form of Oracle/mySQL - no, don't use -9 indeed.

Wow. I remember that cam.

Fun to do. Put one of those pics on your screen and walk back a few meters. For example the picture of the guy in the subway sleeping. You'll notice the details start appearing because your brain is filling in the details.

awesome. pledged.

16 bytes is the limit?

You don't need the entire blockchain to send/receive. Only when running a "Full node". If you are not intending to keep your node online for 24/7 you can use a SPV style client like Electrum or Multibit. They are lightweight clients without a blockchain attached.

Full nodes host the memory pool for the txid's - So they serve a purpose: Making transactions propagate over the network. And serve blocks to nodes that are not up-to-date (And clients).