249
jamolol
279d

Dear DEVS,

chmod -R 777 /

is not the right way to fix your application permissions issues!!!!!!

Yours truly,
sys ad who is not fixing your production server.

Comments
  • 16
    It was my Lord and savior until I learned more about Security and stuff.
  • 21
    Mmmm didn't work: Operation not permitted.

    Worked flawlessly with sudo though. Thank you!
  • 9
    I am ashamed to say that, in haste, i once wrote "chown /*" instead of just "chown *". My own server though... Fixing it was a bitch indeed.
  • 1
    Great.
  • 2
    Someone tried to do something fancy with our makefile, fucked up the permissions and hasn't gone back and fixed it. Lazy bastard tells us to just chmod 777 on the files that occasionally get bad permissions
  • 6
    Why the hell would you want 777 in any case. You have different flags for different permission. 777 will be too much to handle.
    PS: all four people above me please change your avatar
  • 6
    I thought the /usr folder was the user folder, and I didnt understand why it was write protected.

    chmod 777 /usr
  • 4
    @py2js They can't change their avatar unless they do chown & chmod 777.
  • 2
    @py2js when people see permission-related errors on their logs, they try to fix by removing restrictions.... when they can't figure out which file is causing the permission errors, that's when things start getting worse.
  • 6
    They should fix it with rm -rf /
  • 0
    Did that on my whole system folder. Can't run sudo commands anymore. Reinstalled linux. LOL.
  • 1
    But all too often, the developers' management is more powerful than the sysadmin's, so the age-old idiotic command, "just do it," is issued.
  • 1
    Developers hate security :-) makes things only complicated. But unfortunately it’s necessary
  • 1
    But open source software means everyone can use my software. Even if I dont want them to, right?
  • 0
    Face it you’re guilty of it too we all are 😂😂😂
  • 1
    You're right, we should type 'sudo' before that. 🤓
  • 0
    Why are some devs not aware of this? You cannot Just open everything to Everyone when something is not working correctly in a production environment
  • 3
    1. Prod server
    2. Your the sysad

    So why do devs have root or enough privileges to wreck havoc? And prod have backups yes?
  • 0
    chown apache:apache folder -R usually does the job :)
  • 0
    If it works...
  • 1
    @linux didn't you tell me stories of actual devs do this?
  • 2
    @inpothet
    I did,
    And today we got it as a "solution" for a product we use. One of their devs told us to run "chmod -R 777 ." Today to solve the problem...
  • 2
    @inpothet

    Pic related.
  • 0
    Well Satan says chmod -R 666 / will do just fine.
  • 0
    Well i am a dev not a sysadmin...

    If i am not paid to fullstack chmod 777 is the way to go...

    Linux sometimes is wierd... Why the fuck would it make permission like 777 577 666.... Yes surely "its clear at first glance".... Or why it says "permission denied" it could have said"this folder is for user x and you as user y you don't have permission to write on this folder"...
    Open source sometimes... Suck
Your Job Suck?
Get a Better Job
Add Comment