News for hackers. Stuff that matters.
Re:Man accidentally 'deletes his entire company' with one li... by nickpsecurity on Thursday April 14, 2016 @12:46PM (#11498263)
What's most epic about this is it's in the UNIX Hater's Handbook. One of its rants was how better-designed systems would warn you if you were going to nuke your whole system. The reason is that a command to wipe the whole system was more likely a mistake than developer or admin's intent. UNIX would do it without blinking. Inherently unsafe programming and scripting combined with tools like that meant lots of UNIX boxes went kaput.

And today, over two decades later, a person just accidentally destroyed his entire company with one line without warnings on a UNIX. History repeats when its lessons aren't learned. This problem, like setuid, should've been eliminated by design fairly quickly after it was discovered.

http://esr.ibiblio.org/?p=538

EDIT: Added link to ESR's review of UNIX Hater's Handbook which links to UHH itself. Nicely covers what was rant, what was fixed, and what remains true. Linking in case people want to work on the latter plus my sour relationship with UNIX. :)

Re:Man accidentally 'deletes his entire company' with one li... by vinceguidry on Thursday April 14, 2016 @01:16PM (#11498592)
One of the more fascinating aspects of human history is how much effort we're willing to devote to creating varied senses of safety, even if that safety is only an illusion.

Now, we can call this a failure of design, but really, people who rely on technology they don't understand can't be saved by good design. Sure, this particular case could be fixed by disallowing the recursive flag on the file system root, but safety is never going to be able to be the primary design concern of any technological system.

Imagine if a sword were made safety as first-class concern. You can't design a sword that can be used safely by the untrained. No weapon can be, training with a weapon is a prerequisite for safely using it. Similarly, every technology has to be understood by those using it. If you don't you're just inviting trouble.

For a business using technology, the needs are actually fairly straightforward. You need an understanding of what needs to be backed up, and a process for performing the backups. If you've picked the former right, (backing up human-readable information rather than data only readable by software programs that might go away in a crash) then risk is minimized.

Re:Man accidentally 'deletes his entire company' with one li... by xg15 on Thursday April 14, 2016 @03:33PM (#11499679)
This is a strange post. You imply that, only because it's impossible to absolutely prevent all kinds of disasters, no efforts in safety should be taken at all.

By the same logic, you could strip away all the airbags, seatbelts, comfy seats and assistance systems of modern cars: After all, accidents still happen and safety mechanisms might even lure drivers into more reckless behavior. (This is in fact happening with seatbelts)

I think it's less useful to think about absolute safety than about which failures are likely to occur and how effective our measures against those specific failures are.

The --force flag is obviously not an effective measure against root deletions, otherwise we wouldn't have so many stories about it. My theory is that there are three reasons for it:

- As other people wrote, if you frequently batch-delete files, you get trained very quickly to always use -f as plain rm is very annoying to use for large sets of files. Unlike other flags, -f won't make you stop and think. This could be fixed by making rm-without-f actually useable - for example by only asking once and not for every file like, oh I don't know... Windows.

- rm can interact with shell parsing in very intransparent and fatal ways. My guess is that most root deletions happen similar to this post: not a literal rm -rf / but some unfortunate variable interpolations where the author didn't realize that they can evaluate to "/". That's a very unobvious point of failure that takes a lot longer to learn than just using rm. Therefore rm should absolutely warn about it.

- there is actually an expectation that rm could be safe as most deletes you do on a modern system are reversible - either because you have a " recycle bin" or a backup. So a warning would make sense to counter that expectation.

Re:Man accidentally 'deletes his entire company' with one li... by TeMPOraL on Thursday April 14, 2016 @05:47PM (#11500587)
'vinceguidry actually makes a pretty good point. It's one thing to cover potential stupid mistakes with safety features. But beyond some point, safety starts to oppose utility - i.e. a perfectly safe car would be a simple chair. A perfectly safe software is also one that is totally useless for anything.

It's important to consider when designing software that safety should be about gracefully handling mistakes, and not something that should lure the user into false sense of not having to know what they're doing. Unfortunately, the latter attitude is what drives todays' UX patterns and software design in general, which is a big part of why tech-illiterate people remain tech-illiterate, and modern programs and devices are mostly shiny toys, not actual tools.

Re:Man accidentally 'deletes his entire company' with one li... by nickpsecurity on Thursday April 14, 2016 @08:21PM (#11501243)
It's true that safety and also security can impair the usefulness of something past a certain point. It's also irrelevant to our current topic given the existence of systems that don't self-nuke easily. This is a UNIX-specific problem that they've fought to keep for over 20 years with admittedly some improvement. There were alternatives, both UNIX setups and non-UNIX OS's, that protected critical files or kept backups from being deleted [at all] without very specific action from an administrator. And nobody complained that they couldn't get work done on or maintain a VMS box.

So, this isn't some theoretical, abstract, extreme thing some are making it out to be. It's a situation where there's a number of ways to handle a few, routine tasks with inherent risk. Some OS's chose safer methods w/ unsafe methods available where absolutely necessary. UNIX decided on unsafe all around. Many UNIX boxes were lost as a result whereas alternates rarely were. It wasn't a necessity: merely an avoidable, design decision.

Re:Man accidentally 'deletes his entire company' with one li... by xg15 on Thursday April 14, 2016 @06:41PM (#11500850)
I'm glad we have the same opinion then - as I said, it's not very useful to reason about "perfect safety".

It's certainly possible to make a product "safer" then necessary and hinder utility (though I think "safety" is the wrong concept to look at here - see below) but if the common opinion of your product from tech-illiterate people is "complicated and scary", I think you can be pretty sure that you are still a long way away from that point.

In fact, some versions of rm do add additional protection against root deletions, e.g. the --no-preserve-root flag. What utility did that flag destroy?

I believe if you really want to make people more tech-literate (which today's apps are doing a horrible job of, I agree), you have to give them a honest and consistent view of their system, yes. But you also have to design the system such that they can learn and experiment as safely as possible and can quickly deduce what a certain action would do before they do it.

Cryptic commands, which are only understandable after extensive study of documentation, and which oh by the way become deadly in very specific circumstances don't help at all here.

Re:Man accidentally 'deletes his entire company' with one li... by nickpsecurity on Thursday April 14, 2016 @08:22PM (#11501250)
"Cryptic commands, which are only understandable after extensive study of documentation, and which oh by the way become deadly in very specific circumstances don't help at all here."

Exactly. That's another problem that was repeatedly mentioned in UNIX Hater's Handbook. It still exists. Fortunately, there's distro's improving on aspects of organization, configuration, command shells, and so on. I'm particularly impressed with NixOS doing simple things that should've been done a long time ago.

Re:Man accidentally 'deletes his entire company' with one li... by vinceguidry on Thursday April 14, 2016 @05:05PM (#11500340)
> You imply that, only because it's impossible to absolutely prevent all kinds of disasters, no efforts in safety should be taken at all.

Not at all. We should absolutely work to make things safer. But we need to be realistic and temper our sense of idealism. Nothing was going to save this guy from disaster, if it wasn't 'rm' it just would have been something else.

My point is that you can't expect safety features to obviate the need to know what you're doing.

Re:Man accidentally 'deletes his entire company' with one li... by nickpsecurity on Thursday April 14, 2016 @08:13PM (#11501218)
This could've stopped it unless he specifically coded it to destroy system files:

https://launchpad.net/safe-rm

Re:Man accidentally 'deletes his entire company' with one li... by jacobush on Thursday April 14, 2016 @05:21PM (#11500444)
Sounds very fatalistic. All people killed in car accidents would also have died from something else?
Re:Man accidentally 'deletes his entire company' with one li... by TeMPOraL on Thursday April 14, 2016 @05:43PM (#11500567)
Many probably would - it's likely that the insanely reckless attitude towards motor vehicles will also reflect in other areas of life.
Re:Man accidentally 'deletes his entire company' with one li... by vinceguidry on Thursday April 14, 2016 @07:11PM (#11500985)
I don't know exactly how you'd plan on fighting reality. The fact that this guy was going to get hosed eventually isn't some justification, it's fact. People who do stupid things get burned.

If someone wants safety features, let them pay for them. If someone wants to add one, sure, so long as I can remove it if it gets in my way. Who knows, maybe they'll actually be worth having. But I'm not going to lose sleep over every idiot who ruins his life over something he didn't or couldn't learn about. There's absolutely nothing you can do to save stupid people from making stupid decisions.

Maybe I remove a safety feature I don't need and hurt myself with it. Now I'm the moron. Hopefully I learn from it. Nothing you could have done about that either.

Show me something foolproof, and I'll show you a greater fool.

Re:Man accidentally 'deletes his entire company' with one li... by bryik on Thursday April 14, 2016 @01:44PM (#11498854)
In the UNIX Hater's Handbook, defenders of rm consider accidental deletion a "rite of passage" and remark that "any decent systems administrator should be doing regular backups" (see page 62). The author's response is funny:

“A rite of passage”? In no other industry could a manufacturer take such a cavalier attitude toward a faulty product. “But your honor, the exploding gas tank was just a rite of passage.” “Ladies and gentlemen of the jury, we will prove that the damage caused by the failure of the safety catch on our chainsaw was just a rite of passage for its users.” “May it please the court, we will show that getting bilked of their life savings by Mr. Keating was just a rite of passage for those retirees.” Right.

I'm surprised how relevant parts of this book are 22 years later.

http://www.vbcf.ac.at/fileadmin/user_upload/BioComp/training...

Re:Man accidentally 'deletes his entire company' with one li... by erik14th on Thursday April 14, 2016 @03:14PM (#11499543)
Is there an alternative to allow scripted destructive actions without the risk of deleting important stuff?

Modern OS's will warn you if you try to delete stuff, but you can still ultimately do it anyway, I don't see it as something particular to UNIX.

The only similar problem I had was on windows, 98 I guess, I deleted all my files that weren't readonly by fiddling with a .bat script.

Re:Man accidentally 'deletes his entire company' with one li... by whitegrape on Thursday April 14, 2016 @04:01PM (#11499877)
Have an immutable filesystem, where "deletes" are recoverable by going back in time. At least until you do a scheduled "actual delete" that will reclaim disk space.

Another option (though last time I tried it, it didn't work..) is something like libtrash: http://pages.stern.nyu.edu/~marriaga/software/libtrash/ Deletes become moves and you can really delete when you like.

Practically speaking, if you're quick an 'rm' isn't totally destructive even without backups. There's a good chance your data is still there on the disk, it's just not associated with anything so it could be overridden at any point. Best to mount the disk read only and crawl through the raw bits to find your lost data (I recovered a week's worth of code this way several years ago).

Re:Man accidentally 'deletes his entire company' with one li... by derekp7 on Thursday April 14, 2016 @04:17PM (#11499990)
My favorite answer to the common interview question: "What was your biggest mistake, and how did you recover from it?" Answer: Back in 1993, I once deleted a critical data file. Fortunately, the AIX host was sitting next to me, so I quickly reached over and flipped the power switch off. The strategy being: writes were buffered and flushed out periodically, so hitting the power switch prevented that last write from hitting the disk. And if this didn't work (and caused more file system corruption), well I would have needed to restore from backup anyway.
Re:Man accidentally 'deletes his entire company' with one li... by nickpsecurity on Thursday April 14, 2016 @08:14PM (#11501220)
That's great. Straight out of an NCIS episode except it actually makes sense this time. :)
Re:Man accidentally 'deletes his entire company' with one li... by toomuchtodo on Thursday April 14, 2016 @04:08PM (#11499933)
> At least until you do a scheduled "actual delete" that will reclaim disk space.

And then you "actual delete" is where the data loss occurs :D

Re:Man accidentally 'deletes his entire company' with one li... by Avshalom on Thursday April 14, 2016 @04:20PM (#11500020)
Right but if you delete your entire file system there won't be anything to come along and do the "actual delete" so you're safe until some one comes along with a rescue disk or otherwise mounts it to a system that knows how to deal with this.

At the very least when you rm important-file.txt instead of importanr-file.txt you have a chance.

Re:Man accidentally 'deletes his entire company' with one li... by wruza on Sunday April 17, 2016 @02:09PM (#11515523)
Pre-delete would already hide files from apps and services for them to "fail fast", and actual delete would be just "i'm running fine for two days". Of course this implies that active open files should not be pre-deleted on unix at all (at least not by rm process). Even if you delete the entire filesystem with backups, there will be a chance to boot into recovery mode and undelete everything back. We can even go further and apply small-file-versioning on fs level to prevent misconfig accidents in /etc.

That's very simple and powerful, I can't tell why it is still not implemented today.

Re:Man accidentally 'deletes his entire company' with one li... by Avshalom on Thursday April 14, 2016 @03:35PM (#11499698)
well there's some safe guard checks you can do to prevent the easy abuses like require an additional flag for rm -rf-ing everything in the root or /home/*/, or across device boundaries as some one said.

You can redesign rm so people don't find themselves typing -rf as force of habit.

You can have multiple delete commands: mark as overwriteable if need and remove from 'ls -a', actually delete, overwrite sectors with zeros; like we have in guis.

You can have a permission system that isn't just "this account can do literally anything" or "this account can't do anything"

Re:Man accidentally 'deletes his entire company' with one li... by Avshalom on Thursday April 14, 2016 @04:03PM (#11499894)
here's a dumb idea off the top of my head: /etc/rmblacklist.conf autopopulated (by the distro) with a list of files (/boot and the actual bootimage for instance) that requires a GNU style long option --nuke to delete. It's still easily scriptable but you'd rarely ever actually need it and requiring a long option would serve as a double check that you meant it when you did.

Sure it's still possible to --nuke something due to a bug or negligence but I bet it'd cut down on fatal errors. Plus the user could have their own ~/.rmblacklist.conf to guard against particularly persistent dyslexias.

You could even erase the contents entirely if you really think being able to delete root on a whim keeps your kung fu strong.

Re:Man accidentally 'deletes his entire company' with one li... by nickpsecurity on Thursday April 14, 2016 @08:30PM (#11501279)
Good to see you fighting the fight with many sensible ideas. I've been posting this one in most responses as it's pretty simple:

https://launchpad.net/safe-rm

Re:Man accidentally 'deletes his entire company' with one li... by Avshalom on Thursday April 14, 2016 @09:37PM (#11501507)
Hah! Beat me to the punch by 5 years.
Re:Man accidentally 'deletes his entire company' with one li... by nickpsecurity on Thursday April 14, 2016 @10:14PM (#11501630)
Darn, I didnt notice it was that old. Makes situation even worse for UNIX rm defenders. Like when Trusted Xenix eliminated setuid vuln's mostly by clearing setuid bit during a write w/ admin having to manually reset it. Simple shit. Mainstream response? "Just audit all your apps for setuid and be extra careful in..." (sighs)
Re:Man accidentally 'deletes his entire company' with one li... by Tiksi on Thursday April 14, 2016 @10:14PM (#11501632)
You could just make the file immutable and read only:

http://paste.click/qMpmyO

Then remove the immutable flag if needed

Re:Man accidentally 'deletes his entire company' with one li... by justinlardinois on Thursday April 14, 2016 @08:04PM (#11501178)
This isn't a bad idea.
Re:Man accidentally 'deletes his entire company' with one li... by nickpsecurity on Thursday April 14, 2016 @08:30PM (#11501276)
https://launchpad.net/safe-rm

Use something like that with scripting. It really is that easy to protect critical stuff with otherwise easy-to-use rm. UNIX has always been resistant to do stuff like this. However, it's architecture makes it fairly easy for developers to do it themselves. That's to its credit.

Re:Man accidentally 'deletes his entire company' with one li... by blakeyrat on Thursday April 14, 2016 @04:28PM (#11500073)
There's no reason the Recycle Bin couldn't work for scripting languages, except for lazy OS and language developers haven't bothered to wire-it-up.
Re:Man accidentally 'deletes his entire company' with one li... by nickpsecurity on Thursday April 14, 2016 @08:52PM (#11501365)
That attitude was pervasive in both UNIX and C. That other systems avoided common problems of both with little work or penalty shows it's unnecessary today. Yet, the results of that attitude continue to do damage.
Re:Man accidentally 'deletes his entire company' with one li... by 0xdeadbeefbabe on Thursday April 14, 2016 @03:10PM (#11499516)
The author stretches his analogies substantially. It's nice to see this was happening 22 years ago just like it is nice to see UNIX from more than 22 years ago still being used today.

Edit: i.e. it isn't so nice. Not much progress.

Re:Man accidentally 'deletes his entire company' with one li... by nickpsecurity on Thursday April 14, 2016 @08:28PM (#11501266)
Yeah, I saw the same problem in the NSA backdoor debate where people liken it to brake failures and such. I pointed out repeatedly that computer breaches rarely maim or kill anyone. Usually don't even cost them their jobs or bankrupt their business. Such analogies are strawmen to try to boost their argument with an emotional response.
Re:Man accidentally 'deletes his entire company' with one li... by mason240 on Thursday April 14, 2016 @02:05PM (#11499046)
>You can't design a sword that can be used safely by the untrained. No weapon can be, training with a weapon is a prerequisite for safely using it.

I was tank crewman in the US military, and there is a high chance of death of dismemberment from regular tank operation. Drivers have very limited visibility, tank turrets can pin people as they traverse, the breech of the main gun violently recoils into the crew compartment with limited guards, the rounds can be exploded by static electricity (or just plain lit on fire), I've saw one guy smash all teeth out when riding inside and the tank hit a hole, and so on.

We had a saying: "tanks are designed to kill, they don't care who."

Re:Man accidentally 'deletes his entire company' with one li... by Avshalom on Thursday April 14, 2016 @03:06PM (#11499490)
I'm pretty sure my computer is not designed to destroy businesses though.
Re:Man accidentally 'deletes his entire company' with one li... by soneil on Thursday April 14, 2016 @03:24PM (#11499612)
Your computer is designed to do exactly what it was told, at ludicrous speed. Much like the tank analogy, this is the very essence of the thing.
Re:Man accidentally 'deletes his entire company' with one li... by Avshalom on Thursday April 14, 2016 @03:37PM (#11499714)
Then why does rm have the f flag in the first place? Clearly some one thought oh-hay-guys maybe a safeguard wouldn't be out of place. They just designed a really awful safety.
Re:Man accidentally 'deletes his entire company' with one li... by auntienomen on Thursday April 14, 2016 @02:24PM (#11499208)
For the last 1000 years, swords have typically been constructed with a guard. It's a simple and useful safety feature, and it almost never prevents an intended use. Same for disallowing '/' as the target of rm.
Re:Man accidentally 'deletes his entire company' with one li... by Semyaz on Thursday April 14, 2016 @04:35PM (#11500128)
It's worth noting that since 2006 the default behavior for "rm -rf /" is to exit immediately with warnings.

http://superuser.com/questions/542978/is-it-possible-to-remo...

Re:Man accidentally 'deletes his entire company' with one li... by Impl0x on Thursday April 14, 2016 @04:39PM (#11500159)
I don't want to sound fussy, but sword guards aren't designed to protect the user from the sword, they're for protecting the user from other swords. That they make using a sword safer is a side-effect. I agree with the point you're making though.
Re:Man accidentally 'deletes his entire company' with one li... by danielweber on Thursday April 14, 2016 @02:52PM (#11499404)
After every disaster, you can come up with a process that would have stopped that specific disaster. That doesn't mean it's a good idea to implement that process everywhere.
Re:Man accidentally 'deletes his entire company' with one li... by auntienomen on Thursday April 14, 2016 @03:00PM (#11499449)
And yet swords have guards.

If a disaster recurs repeatedly -- and if fixing it costs essentially nothing -- then it should be fixed.

Re:Man accidentally 'deletes his entire company' with one li... by danso on Thursday April 14, 2016 @06:22PM (#11500784)
It's too bad you're being downvoted. It was not too long ago that people blamed the Germanwings Flight 9525 crash on how the cockpit door was designed to protect against hijackers, post 9/11:

http://www.nytimes.com/interactive/2015/03/26/world/europe/g...

Re:Man accidentally 'deletes his entire company' with one li... by bryanrasmussen on Thursday April 14, 2016 @04:09PM (#11499947)
And after every disaster that occurs again and again you might increase your interest in averting the next disaster.
Re:Man accidentally 'deletes his entire company' with one li... by BinaryIdiot on Thursday April 14, 2016 @05:28PM (#11500481)
> Imagine if a sword were made safety as first-class concern.

This seems like a silly example. A weapon, meant to dismember and maim attackers of its owner, is one of those things that's impossible to completely make safe. Granted I could think of plenty of ideas that maybe would make it safer at first that wouldn't compromise its ability to be effective as a weapon but it's simply not an apt example to be used here.

A computer is a general purpose device. It can be used to help image cancer, launch a nuclear weapon or play games. Considering that it's meant to be used by everyone, without discrimination, it seems to make sense that you need to do the best you can to protect the user from themselves.

I worked in Apple Care support for about a year. The majority of your users are not going to know all of the consequences to their actions, even ones doing system administration (because let's face it almost every company in the world needs at least a little of that now and not all of them are going to hire someone who knows what they're ding).

You can't protect a user from everything. But when you can protect a user from doing something that would have screwed up their whole system, lost a project, etc? That's helpful. Correcting input is what computers are essentially there for.

Re:Man accidentally 'deletes his entire company' with one li... by pyre on Thursday April 14, 2016 @02:48PM (#11499380)
What you're essentially saying is:

> It's impossible to have 100% safety, so let's not bother placing any importance on safety.

Re:Man accidentally 'deletes his entire company' with one li... by nickpsecurity on Thursday April 14, 2016 @01:31PM (#11498719)
Interesting points. I think systems like Burroughs counter the concept in the a lot of safety can be baked into a system. Here's what they did in 1961:

http://www.smecc.org/The%20Architecture%20%20of%20the%20Burr...

Notice that's good UI design for the time, hardware elimination of worst problems, interface checks on functions, limits of what apps can do to system, and plenty recovery. Systems like NonStop, KeyKOS, OpenVMS, XTS-400, JX, and so on added to these ideas. You can certainly bake a strong foundation of safety into a system while allowing plenty flexibility.

So, for example, critical files should be write-protected except for use by specific software involved in updates or administrative action. Many above systems did that. Then, one can use VMS-style, versioned filesystem that leaves originals in there in case a rollback is needed so long as there's free space for that. Such a system handling backups and restores with modern-sized HD's wouldn't have nuked everything. Might have even left everything if using lean setup but can't say for this specific case.

"You can't design a sword that can be used safely by the untrained."

A sword is designed to do damage. A better example would be a saw that's designed to be constructive but with risk of cutting your hand off. Even that can be designed to minimize risk to user.

https://www.youtube.com/watch?v=esnQwVZOrUU

"If you've picked the former right, (backing up human-readable information rather than data only readable by software programs that might go away in a crash) then risk is minimized."

That's orthogonal. A machine-readable format just needs a program to read it. The risk is whether the data is actually there in whole or part. This leads to mechanisms like append-only storage or periodic, read-only backups that ensure it's there. Or these clustered, replicated filesystems on machines with RAID arrays that lots of HPC or cloud applications use. Also, multiple, geographical locations for the data.

People doing the above with proven protocols/tools rarely loose their data. Then there's this guy.

Re:Man accidentally 'deletes his entire company' with one li... by rosser on Thursday April 14, 2016 @01:37PM (#11498790)
Table saws should never be used on flesh. rm(1) should always be used on files. How in FSM's noodly universe is the command supposed to intuit which files it should safely delete versus those it shouldn't?

> ...or administrative action.

You mean like, "sudo rm -rf {$undefined_value}/{$other_undefined_value}"? D'oh!

Re:Man accidentally 'deletes his entire company' with one li... by nickpsecurity on Thursday April 14, 2016 @08:12PM (#11501212)
Two different people here have already figured out this wouldn't have happened in OpenVMS due to versioned filesystem w/ rollback. People also claim saner commands for this stuff but I can't recall if remove was smarter.

Anyway, pertaining to RM, here you go:

https://launchpad.net/safe-rm

Re:Man accidentally 'deletes his entire company' with one li... by yrro on Thursday April 14, 2016 @01:50PM (#11498926)
Make `--one-file-system` the default!
Re:Man accidentally 'deletes his entire company' with one li... by rbanffy on Thursday April 14, 2016 @07:40PM (#11501096)
He really should not have made the first element of the path variable. Doing an "rm -rf /folder/{$undefined_value}/{$other_undefined_value}" would have made his day much better.

Also, never having all backup disk volumes mounted at the same time is good practice.

Re:Man accidentally 'deletes his entire company' with one li... by ams6110 on Thursday April 14, 2016 @02:26PM (#11499230)
There's also the phenomenon that people have an inherent tolerance of risk, so the "safer" you make something, the more reckless people tend to be.

When traction control and antilock brakes became mainstream, one result was that some people started driving faster on snowy roads, up until their risk tolerance was the same as before.

If you understand that a typo can destroy your business, you'll be careful to not log in as "root" on a routine basis and double check everything you do and keep good backups. On the other hand if you expect the system to prevent you from doing anything really damaging, you might be more careless about your approach.

Re:Man accidentally 'deletes his entire company' with one li... by 794CD01 on Thursday April 14, 2016 @03:16PM (#11499558)
That's great. People got to their destinations faster with the same level of risk as before.
Re:Man accidentally 'deletes his entire company' with one li... by shadeless on Thursday April 14, 2016 @02:41PM (#11499323)
That theory is called Risk Compensation: https://en.wikipedia.org/wiki/Risk_compensation
Re:Man accidentally 'deletes his entire company' with one li... by vacri on Thursday April 14, 2016 @04:14PM (#11499978)
> You can't design a sword that can be used safely by the untrained. No weapon can be

This is a really weird argument, since weapons are used in combat, which is not 'safe' by definition.

But if you do want a weapon that the untrained can use without much chance of hurting themselves, look to a spear. It was the go-to weapon for untrained militias from the time history began up to gunpowder taking over - and even then, bayonets are stuck on rifles to turn them into spears.

Re:Man accidentally 'deletes his entire company' with one li... by randyrand on Thursday April 14, 2016 @06:50PM (#11500892)
Swords also don't run code. Just perhaps an importance difference.
Re:Man accidentally 'deletes his entire company' with one li... by nickpsecurity on Thursday April 14, 2016 @10:25PM (#11501661)
A counter that applies to almost every comparison the opposition brings up. Further, swords don't have an easy solution to stop problems that fits in a comment or two in this same thread. ;)
Re:Man accidentally 'deletes his entire company' with one li... by Koshkin on Thursday April 14, 2016 @10:40PM (#11501719)
Hmm... A self-wielding sword running Android sounds like a great idea.
Re:Man accidentally 'deletes his entire company' with one li... by ChrisArgyle on Thursday April 14, 2016 @05:15PM (#11500407)

  path=$foo/$bar

  if [[ $path =~ [[:space:]]*/[[:space:]]* ]]; then
  
      echo NOPE
  
  else
  
      rm -rf $path
  
  fi
Re:Man accidentally 'deletes his entire company' with one li... by clock_tower on Thursday April 14, 2016 @01:50PM (#11498919)
Or you could use VMS.
Re:Man accidentally 'deletes his entire company' with one li... by nickpsecurity on Thursday April 14, 2016 @08:32PM (#11501290)
BOOM! That's two of us that noticed an OS with the right combo of features to avoid this kind of crap.
Re:Man accidentally 'deletes his entire company' with one li... by SEJeff on Thursday April 14, 2016 @06:07PM (#11500711)

    $ sudo rm -rf /
    rm: it is dangerous to operate recursively on ‘/’
    rm: use --no-preserve-root to override this failsafe
Relatively modern distro, but this has been in coreutils for awhile (it was fixed in Ubuntu's coreutils in 2008 for instance)

    $ egrep '^(NAME|VERSION)=' /etc/os-release
    NAME="Red Hat Enterprise Linux Workstation"
    VERSION="7.2 (Maipo)"

Yes, I just did this on the workstation I'm typing on. I'm somewhat curious if he did that on absolutely ancient distros (>8 year old), or didn't actually run rm -rf, but the ansible python equivalent.
Re:Man accidentally 'deletes his entire company' with one li... by nickpsecurity on Thursday April 14, 2016 @08:34PM (#11501295)
Someone brought that to my attention on Schneier's blog suggesting the post was trolling. I'm holding off on going that far for now as some details might be missing & this sort of thing has happened many times. I don't use Ansible. Does it have the --no-preserve-root or other modifiers necessary on modern distros already in it?
Re:Man accidentally 'deletes his entire company' with one li... by gshulegaard on Thursday April 14, 2016 @01:32PM (#11498732)
I feel like if you use `rm -rf` particularly `--force` with privileges, it shouldn't be the job of Unix to stop you.

Also tangentially, if you don't have a sensible backup in place that would protect you from (or at least mitigate) a complete wipe of a single machine (or even all primary ones), you are doing something wrong.

Re:Man accidentally 'deletes his entire company' with one li... by eridius on Thursday April 14, 2016 @01:36PM (#11498772)
The problem with that is people are trained to use -f because it's so annoying to try and use rm without it.

Really, the -f flag should just mean "don't ask for confirmation" and a separate flag should be required to mean something like "yes I do want to nuke my computer". And maybe there should be a flag that means "cross device boundaries", and by default it could refuse to delete anything that has a device number different than the argument it started with. That would at least prevent you from nuking your network-attached storage.

Re:Man accidentally 'deletes his entire company' with one li... by rosser on Thursday April 14, 2016 @01:40PM (#11498816)
This is probably a far better solution than trying to make rm smarter about which kinds of files it's somehow either "safe" or "unsafe" to unlink. Even then, though, you'd still get people who invoke it with "--across-devices --yes-i-really-mean-it" set, with unexpected and disastrous consequences.

And then someone will come along and bitch that rm isn't safe enough yet again.

Re:Man accidentally 'deletes his entire company' with one li... by eridius on Thursday April 14, 2016 @02:01PM (#11499019)
Well, the point is that --across-devices won't be a flag you use as a matter of habit, it's something you'll only use when rm tells you it won't cross the device boundary and you realize that, yes, you really do want to delete across a device boundary. So you'll only add it in the specific cases where it's warranted, and you'll have already tried rm without it (to verify that you're deleting the right thing).

Come to think of it, I don't think I've ever used rm to delete across device boundaries. It just doesn't seem like an action you usually want to take.

Re:Man accidentally 'deletes his entire company' with one li... by blakeyrat on Thursday April 14, 2016 @04:50PM (#11500243)
... so then you change it to be more safe yet again.

I don't understand this attitude. Of course software isn't perfect; it's not even close, it's pretty awful. But the best thing about it: it's malleable. When things don't work, you change them to work better.

Re:Man accidentally 'deletes his entire company' with one li... by rosser on Thursday April 14, 2016 @07:03PM (#11500949)
When things don't work, you change them to work better.

I'd submit that adding layer upon layer of complexity to prevent all the myriad stupid things people might do using a particular piece of software isn't axiomatically "better".

Maybe if lives depend on its correct function, it's worth it, but that kind of strict requirements gathering and execution is well-understood by the people who live in that world.

Making sure that J. Random DevOps Dude doesn't foot-gun himself when he's paid to know better isn't that.

Re:Man accidentally 'deletes his entire company' with one li... by Avshalom on Friday April 15, 2016 @01:41AM (#11502438)
But J. Random DevOps doesn't foot-gun himself he foot-guns the whole Op. You can fire him because it turns out he didn't know better but it's not going to fix the problem he created, the problem now affecting the whole company.
Re:Man accidentally 'deletes his entire company' with one li... by rosser on Friday April 15, 2016 @06:26PM (#11508069)
Believe me, I know this. Entirely too well, in fact.

At my last job, the senior DevOps dude foot-gunned the entire company, by running a read-write disk benchmark (using fio(1)) against the block device (instead of a partition, which, while still stupid, would at least not have been actively destructive) on both my master and all of my slave PostgreSQL hosts. At the same time. And, of course, without telling anyone what he was doing, so the first inkling I had that there was a problem was about 20 minutes later, when I started getting a steadily increasing number of errors suggesting disk corruption.

How does one make such a tool drool-proof enough to prevent that kind of idiocy? Please, help me figure that out. And then give me a time machine, because that was a 16-hour day I'd really rather not have experienced.

And, no, the right move is generally not to fire the jackass who makes that kind of mistake. In my case, above, the company spent about three quarters of a million dollars (just in revenue, never mind how much time was burned in meetings about the incident, my efforts to fix the problem, as well as his and the rest of his team's efforts, and so on) teaching him never to do that again. You don't buy lessons that expensively and then let someone else benefit from them.

(That said, he did get fired several months later for telling the entire engineering lead team to fuck off, in so many words, for their having made a perfectly reasonable request, which was entirely within his responsibilities, and his skills, to satisfy.)

Re:Man accidentally 'deletes his entire company' with one li... by kruczek on Friday April 15, 2016 @06:58AM (#11503378)
Well, there is "cross device boundaries" flag, but not enabled by default:

"--one-file-system

when removing a hierarchy recursively, skip any directory that is on a file system different from that of the corresponding command line argument"

Re:Man accidentally 'deletes his entire company' with one li... by ArkyBeagle on Thursday April 14, 2016 @01:42PM (#11498838)
You should not use it the first time and verify that you actually need it. The second's pause may save your data :) If you're feeling rash, get up and walk around until it passes.
Re:Man accidentally 'deletes his entire company' with one li... by packetslave on Thursday April 14, 2016 @01:51PM (#11498932)
Bingo. See also, "the drill story":

When I was in seventh grade, I took an Industrial Arts class ("woodshop"). The first few weeks of the course were spent going over safety of the machinery. In particular, I remember a heavy-handed message that Mr. Hopfer gave at the drill press:

This is a piece of industrial machinery. It is not a toy. If you put your hand on the stage and lower the bit, the machine will not jam up and make funny noises because it is too difficult. Instead, it will drill a hole through your hand. That is what makes it useful. If it didn't do that, you wouldn't be able to cut through wood.

Re:Man accidentally 'deletes his entire company' with one li... by entee on Thursday April 14, 2016 @02:29PM (#11499239)
There are actually ways to make it so it will in fact stop when contact with one's hand (for saws but you could see an analogous system for a drill press):

http://www.sawstop.com/why-sawstop/the-technology

Just because people should use something responsibly doesn't mean one shouldn't try to improve its inherent safety.

Re:Man accidentally 'deletes his entire company' with one li... by makomk on Thursday April 14, 2016 @04:10PM (#11499950)
That will also apparently stop when in contact with wood that's recently been cut down or is damp, destroying the (expensive) brake and blade in the process. It even has a bypass mode for that reason.
Re:Man accidentally 'deletes his entire company' with one li... by kabr on Thursday April 14, 2016 @09:09PM (#11501424)
SawStop cartridges are ~$70 USD. Not very expensive -- your hands are worth far more!

http://www.amazon.com/SawStop-TSBC-10R2-Cartridge-10-Inch-Bl...

Re:Man accidentally 'deletes his entire company' with one li... by nickpsecurity on Thursday April 14, 2016 @10:22PM (#11501653)
Way more with tens of thousands of accidents annually:

http://www.fairwarning.org/2013/05/after-more-than-a-decade-...

Re:Man accidentally 'deletes his entire company' with one li... by AlgorithmicTime on Thursday April 14, 2016 @03:37PM (#11499719)
That will also stop for wet wood, which is annoying.
Re:Man accidentally 'deletes his entire company' with one li... by Scriptor on Thursday April 14, 2016 @02:07PM (#11499066)
Luckily for us, computers are slightly more sophisticated than drills and we can incorporate sane safety checks with relative ease. In this case people are just asking for an explicit flag in the rare situation when they do want to delete everything.
Re:Man accidentally 'deletes his entire company' with one li... by cmcginty on Thursday April 14, 2016 @04:32PM (#11500104)
I really hate this type of attitude. Just because .0001% of users want to do something, doesn't mean the other 99.9999% need to suffer for it.

Are you against aircraft collision avoidance too? If your pilot wants to fly into another plane, then the guidance system shouldn't try to stop him, right?

Re:Man accidentally 'deletes his entire company' with one li... by dghughes on Thursday April 14, 2016 @02:32PM (#11499255)
> I feel like if you use `rm -rf` particularly `--force` with privileges, it shouldn't be the job of Unix to stop you.

I agree, that's what's so good Unix and GNU-Linux the freedom of root to do anything even major mistakes.

Re:Man accidentally 'deletes his entire company' with one li... by mcv on Friday April 15, 2016 @10:20AM (#11504481)
`rm -r` does give warnings. You have to intentionally turn them off with the -f flag. It sounds like the -f has become too standard, a default flag, which undermines its entire purpose. You should only be using -f if you're absolutely 100% sure what you're doing, and that clearly wasn't the case here.
Re:Man accidentally 'deletes his entire company' with one li... by tripzilch on Friday April 15, 2016 @12:28PM (#11505553)
A question, I checked the manpage for -f (I don't really ever use it on purpose, rm seems to work fine for most of my file deleting needs).

It says "ignore nonexistent files and arguments, never prompt".

Seems to me that the "never prompt" behaviour is an important requirement for a backup-script, though? Cause backup-scripts should work unattended, and definitely not pause and wait for input under any circumstances, right?

Re:Man accidentally 'deletes his entire company' with one li... by mcv on Friday April 15, 2016 @05:17PM (#11507678)
True, but backup scripts that make use of rm -rf should have been really thoroughly tested, and contain a check that they are really only about to delete the thing they're supposed to delete.

Also, perhaps they shouldn't be running as root. There's no reason why any script should have permission to write everywhere. It just needs write access on the backup device.

Re:Man accidentally 'deletes his entire company' with one li... by vbezhenar on Thursday April 14, 2016 @02:33PM (#11499261)
He destroyed his company not with one line. He destroyed his company with extremely wrong setup. That one line just nailed it.
Re:Man accidentally 'deletes his entire company' with one li... by rbanffy on Thursday April 14, 2016 @07:44PM (#11501112)
He destroyed his company with a series of poor decisions. Running "rm -rf /" was just the last one. And it was the last one because it successfully destroyed the company.
Re:Man accidentally 'deletes his entire company' with one li... by eric_h on Thursday April 14, 2016 @05:06PM (#11500349)
Yep, it was an improper backup and recovery system that did him in. I'm sure many other businesses have been destroyed by the same, whether or not it was an rm -rf that was the trigger.
Re:Man accidentally 'deletes his entire company' with one li... by nickpsecurity on Thursday April 14, 2016 @08:51PM (#11501362)
Good point. It was a combination of things.
Re:Man accidentally 'deletes his entire company' with one li... by Natsu on Thursday April 14, 2016 @03:34PM (#11499689)
It's quite odd that his version of rm didn't require --no-preserve-root ... or else he has that turned on by default for some bizarre reason.
Re:Man accidentally 'deletes his entire company' with one li... by Reedx on Thursday April 14, 2016 @04:25PM (#11500059)
Also in the case of programs running rm -rf.

Like what happened with the Linux version of Steam: https://github.com/valvesoftware/steam-for-linux/issues/3671

Re:Man accidentally 'deletes his entire company' with one li... by colin_mccabe on Thursday April 14, 2016 @11:44PM (#11501946)
The UNIX Hater's handbook was written a long time ago. At least on Linux, rm -rf / does not work unless you also pass --no-preserve-root.
Re:Man accidentally 'deletes his entire company' with one li... by enraged_camel on Thursday April 14, 2016 @02:06PM (#11499057)
Not sure I agree. My grandpa had a saying: "It's impossible to make things fool-proof because fools are so ingenious." No matter how many safety checks you add to a system, someone will find a way to fuck it up.
Re:Man accidentally 'deletes his entire company' with one li... by SixSigma on Friday April 15, 2016 @02:46AM (#11502637)
That is not an excuse for letting sloppiness of thought introduce risk.

https://en.wikipedia.org/wiki/Poka-yoke

Poka-yoke (ポカヨケ?) is a Japanese term that means "mistake-proofing". A poka-yoke is any mechanism in a lean manufacturing process that helps an equipment operator avoid (yokeru) mistakes (poka). Its purpose is to eliminate product defects by preventing, correcting, or drawing attention to human errors as they occur. The concept was formalised, and the term adopted, by Shigeo Shingo as part of the Toyota Production System. It was originally described as baka-yoke, but as this means "fool-proofing" (or "idiot-proofing") the name was changed to the milder poka-yoke.

Re:Man accidentally 'deletes his entire company' with one li... by teh_klev on Thursday April 14, 2016 @01:41PM (#11498834)
The link to The UHH in that article appears to be broken, here's an archived copy:

https://web.archive.org/web/20120213211126/http://m.simson.n...

Re:Man accidentally 'deletes his entire company' with one li... by kenshaw on Friday April 15, 2016 @12:28AM (#11502149)
rm -RF didn't destroy this guy's business; failure to maintain and adhere to an adequate backup policy did.
Re:Man accidentally 'deletes his entire company' with one li... by chris_wot on Thursday April 14, 2016 @08:11PM (#11501207)
There are two issues with this:

1. -f specifically forces the change - it's a "I know what in doing, don't warn me" option

2. He was running this in a script, and automating a process so he didn't want a warning

Re:Man accidentally 'deletes his entire company' with one li... by nickpsecurity on Thursday April 14, 2016 @08:24PM (#11501253)
Those are good observations. Both true. xg15 addressed some of the reasons why this is still a problem:

https://news.ycombinator.com/item?id=11499679

Here's an example of a simple alternative that lets you do what this person is doing while avoiding unnecessary hits to critical files:

https://launchpad.net/safe-rm

Re:Man accidentally 'deletes his entire company' with one li... by chris_wot on Thursday April 14, 2016 @09:36PM (#11501505)
Cool script! Thanks for that :-)