this post was submitted on 12 Feb 2024
754 points (97.4% liked)

linuxmemes

21263 readers
503 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.

  • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] [email protected] 91 points 9 months ago (1 children)

    Did they execute the command on localhost or the remote? Because hey if they had privileges to root-nuke the target that's gotta count for something right? Lmao

    [–] [email protected] 60 points 9 months ago (4 children)

    The way this reads I think the company did not actually provide a good sandboxed environemt. So when they rm -rf /'d the thing they actually deleted a lot of stuff the recruiters still needed (likely the pentest environments for other candidates). Because imo that's the only reason I can think of to just outright ban a candidate from applying for any other role at the company.

    [–] [email protected] 6 points 9 months ago

    I mean it reads like a shitpost to me lol.

    [–] [email protected] 22 points 9 months ago (1 children)

    To be honest, considering the role they're applying for, I would reject their job application too even if it occurred inside a sandboxed environment.

    They should know exactly what rm -rf does. The fact they didn't and they still arbitrary ran the command anyway... massive red flags. Could even say he failed to twart a social engineering attack.

    [–] [email protected] 13 points 9 months ago

    The two cases, they knew what it was and they did it maliciously. They didn't know what they were doing and got socially engineered in the process. Both cases are cause for failure.

    [–] [email protected] 12 points 9 months ago

    To me it reads like the recruiter thought the person was a troll and banned them.

    [–] [email protected] 38 points 9 months ago (2 children)

    You should ban anyone who tries this regardless of the outcome. There is always a small chance they did it on purpose trying to cause damage. There is no benefit by giving them another chance, you just riks giving them the possibility of doing more damage. If the thing was a mistake, the person will learn from it and find another job.

    [–] [email protected] 2 points 9 months ago

    We'll I'm this case too, if true, the person didn't know anything about the job they were aplyiyfor and tried to cheat their way into the company. Also not really great.

    [–] [email protected] 26 points 9 months ago (3 children)

    If the task would have been to find general security risks this would have counted. I mean, he did some serious harm, but he was able to find a security issue.

    [–] [email protected] 2 points 9 months ago

    They did but it might have been a good idea to prove that the command works instead of actually doing it.

    [–] [email protected] 1 points 9 months ago

    Yeah so is tossing a molotov on thier machines, "found a security issue not firproofing everything"

    [–] [email protected] 4 points 9 months ago (1 children)

    I think there is kind of an assumption that the scenario is "outside host gains privileged access" so there's not really a security issue with some attacker deleting root on their own box.

    [–] [email protected] 6 points 9 months ago

    If it has been done properly you're right. If this also affected the host machine it is a security issue.