Skip to main content
The 2024 Developer Survey results are live! See the results

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

17
  • 3
    Does it really need rwx permission?
    – matanox
    Commented Apr 23, 2016 at 17:42
  • 18
    Beware that, with setcap, if you overwrite the executable you grant privileges to (ex: do a rebuild) then it loses its privileged port status and you have to give it privileges again :|
    – rogerdpack
    Commented Oct 27, 2016 at 22:25
  • 3
    Something that I had to fiddle with; I was trying to run a sysv service, that runs a ruby executable that uses ruby. You need to give the setcap permission on the version- specific ruby executable, e.g. /usr/bin/ruby1.9.1 Commented Jan 25, 2017 at 19:31
  • 10
    I have my doubts that chmoding to 777 the byport files is the best idea. I've seen giving permisions ranging from 500 to 744. I would stuck to the most restrictive one that works for you.
    – Pere
    Commented May 9, 2017 at 9:09
  • 5
    IMPO you really shouldn't be giving access to "all users and groups". Instead, you should pick a trusted user that needs to run this and then chown the /etc/authbind/byport/80 and 443 files by that user and chmod them so that they are executable by that user and no-one else. Otherwise you're increasing your security risk, not decreasing it.
    – deltaray
    Commented Feb 18, 2021 at 14:39