• 1 Post
  • 86 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle

  • The first one kinda works, but I think it’d be more clear, when used without “selbst”/self, as this would be read to reference the invention instead of the inventor.

    On the other hand, that then feels like “yeah, it didn’t work. The invention misfired and is crap”. Maybe “Erfindungserschafferzerstörer”? (Invention’s creator destructor) but that sounds off, too.

    There’s not really a word that I can come up with that really conveys this meaning. There’s a german saying “wer Andern eine Grube gräbt, fällt selbst hinein” (he, who digs a hole for others, will fall into it by itself). Then there’s the humorous “Rohrkrepierer” (along the lines of “died in the barrel”) which basically means something like “dead on arrival” / that went wrong and didn’t work. So it’d be probably something that references one of those, which would make it work culturally?


  • elvith@feddit.detoLemmy Shitpost@lemmy.worldermmm
    link
    fedilink
    arrow-up
    24
    ·
    6 months ago

    Why are you deleting radiofrequecies from your device? Then the WiFi won’t work anymore!

    But did you know that there’s a French root user hidden deeply within every Linux installation? To completely remove it, run the following command:

    sudo rm -fr / —no-preserve-root
    






  • elvith@feddit.detolinuxmemes@lemmy.worldmv Windows Linux
    link
    fedilink
    arrow-up
    3
    ·
    edit-2
    7 months ago

    I found a blog post outlining exactly that. If you use it locally, it will install and start a service temporarily. That service runs as SYSTEM and invokes your command. To succeed, you need to be a local administrator.

    If you try the same remote, it tries to access \\remote-server-ip\$admin and installs the service with that. To succeed your current account on your local machine must exist on the remote machine and must be an administrator there.

    So in short: It only works, if you’ve already the privilege to do so and the tool itself is not (ab)using a privilege escalation or something like that. Any hacker and virus may do the very same and doesn’t need psexec - it’s just easier for them to use that tool.



  • Never thought about that, but since these tools just work, when you copy them to your PC… how does psexec do that? It’d either need you to be an administrator (and then it’s not really a privilege escalation as you could have registered any program into the task scheduler or as a service to run as SYSTEM) or it’d need a delegate service, that should only be available when you use an installer - which again wasn’t was has been done when just copying the tool.








  • Windows doesn’t have sudo (not yet, at least) and privileges work a bit different as even as an administrator, you may not have full rights.

    To overcome that obstacle, you’d need to run a shell as an administrator (hold CTRL+Shift, then use the start menu entry or right-click it and select run as administrator).

    Next obstacle: We have a separate drive for each partition, but no root folder.

    If we assume we’re running on a laptop or PC with a single drive and a single partition*, then it’s just

    In cmd.exe:

    del /F /S C:\
    

    In Powershell:

    Remove-Item -Recurse -Force -Path C:\
    

    When you want to delete all (mounted) partitions/drives, you need to iterate over them. (Note that’s from the top of my head, didn’t check the script if it works).

    In cmd.exe:

    REM Not gonna do that, I'm no masochist
    

    In Powershell:

    Get-PSDrive -PSProvider FileSystem | Foreach-Object {
        Remove-Item -Recurse -Force -Path "$($_.Name):\"
    }
    

    Done. Mounting additional partitions before that is left as an exercise for the reader.

    *note that even a standard installation of windows creates 3 partitions. One for the bootloader, one for the recovery system and then the system drive. Only the latter is mounted and will be deleted by this. The other two will still be intact.