Back when I migrated my file server to a VM, I used robocopy to copy everything over (and caused quite a few fuckups before it'd behave halfway decent.. or so I thought). Now I tried to add my desktop's SSH key to the authorized_keys on said server but it wouldn't accept my key after that. After a bit of digging I've found that my entire home directory (where the file server hosts its mirror of my D: drive) had everything set to 777, and that's why the key isn't accepted. Great permission mode, isn't it? Much secure, very wow! Thank you so much robocopy!!!

  • 9
    Note to self: To fix Robocopy's shit regarding permissions on directories without affecting files: chmod -R u=rwX,g=,o= ~
    Essentially this sets files to 600 and directories to 700.
  • 5
    "robocopy" must be condor, on another note, autocorrect wanted to change it to robocops, which I think would've been a great name instead 😂
  • 2
    fuck robocopy. It tries to take NTFS ACLs and apply them to Linux files and doesn’t know wtf it’s doing. As much as Powershell is my Windows management go-to, I won’t touch it if I need to interface with *Nix. If I even smell Linux on the horizon I put Powershell in the corner with its dunce cap firmly in place.
Your Job Suck?
Get a Better Job
Add Comment