Ghost wrote to All <=-
I have tried (and failed) using the setcap command to allow the
ports <1024 to be used, but the command has failed with the
following:
sbbs@greg-Virtual-Machine:~/sbbs/exec$ sudo setcap cap_net_bind_service=+ep /home/sbbs/sbbs/exec/sbbs Failed to set capabilities on file `/home/sbbs/sbbs/exec/sbbs' (Invalid
argument) The value of the capability argument is not permitted
for a file. Or the file is not a regular (non-symlink) file
any help would be appreciated. I have looked on the web and could
not come up with anything better than what I have done here.
I have tried (and failed) using the setcap command to allow the ports <1024 to be used, but the command has failed with the following:
sbbs@greg-Virtual-Machine:~/sbbs/exec$ sudo setcap cap_net_bind_service=+ep /home/sbbs/sbbs/exec/sbbs Failed to set capabilities on file `/home/sbbs/sbbs/exec/sbbs' (Invalid argument) The value of the capability argument is not permitted for a file. Or the file is not a regular (non-symlink) file
I have tried (and failed) using the setcap command to allow the ports <1024 to be used, but the command has failed with the following:
sbbs@greg-Virtual-Machine:~/sbbs/exec$ sudo setcap cap_net_bind_service=+ep /home/sbbs/sbbs/exec/sbbs
Failed to set capabilities on file `/home/sbbs/sbbs/exec/sbbs' (Invalid argument)
The value of the capability argument is not permitted for a file. Or the file is not a regular (non-symlink) file
any help would be appreciated. I have looked on the web and could not come up with anything better than what I have done here.
sbbs@greg-Virtual-Machine:~/sbbs/exec$ sudo setcap cap_net_bind_service=+ep /home/sbbs/sbbs/exec/sbbs Failed to
set
capabilities on file `/home/sbbs/sbbs/exec/sbbs' (Invalid
argument) The value of the capability argument is not permitted
for a file. Or the file is not a regular (non-symlink) file
any help would be appreciated. I have looked on the web and could
not come up with anything better than what I have done here.
My guess is that the 'sbbs' executable (/home/sbbs/sbbs/exec/sbbs) is actually a symlink to the actual file (/home/sbbs/sbbs/repo/exec/sbbs),
and it's failing for the reason given in that error message regarding a symlink.
Re: Re: setcap command
By: Gamgee to Ghost on Mon Oct 10 2022 08:18 am
sbbs@greg-Virtual-Machine:~/sbbs/exec$ sudo setcap cap_net_bind_service=+ep /home/sbbs/sbbs/exec/sbbs Failed to
set
capabilities on file `/home/sbbs/sbbs/exec/sbbs' (Invalid
argument) The value of the capability argument is not permitted
for a file. Or the file is not a regular (non-symlink) file
any help would be appreciated. I have looked on the web and could not come up with anything better than what I have done here.
My guess is that the 'sbbs' executable (/home/sbbs/sbbs/exec/sbbs) is actually a symlink to the actual file (/home/sbbs/sbbs/repo/exec/sbbs), and it's failing for the reason given in that error message regarding a symlink.
Well, I haven't set up any symlinks, so unless it was done when installed, I don't know.
However, I tried your suggestion and got the same response from
the system.
sbbs@greg-Virtual-Machine:~/sbbs/exec$ sudo setcap cap_net_bind_service=+ep /home/sbbs/sbbs/repo/exec/sbbs Failed to
set capabilities on file `/home/sbbs/sbbs/repo/exec/sbbs' (Invalid argument) The value of the capability argument is not permitted for a file. Or the file is not a regular (non-symlink) file
sbbs@greg-Virtual-Machine:~/sbbs/exec$ sudo setcap cap_net_bind_service=+ep /home/sbbs/sbbs/repo/exec/sbbs Failed to
set capabilities on file `/home/sbbs/sbbs/repo/exec/sbbs' (Invalid argument) The value of the capability argument is not permitted for a file. Or the file is not a regular
(non-symlink) file
Use "ls -l" or "readlink" to determine if a file is in fact a symlink, e.g.: $ readlink /sbbs/exec/sbbs ../../../home/rswindell/sbbs/src/sbbs3/gcc.linux.x64.exe.debug/sbbs
Again, the suggested method of setting capabilities is to use the "setcap" build target as instructed here:
http://wiki.synchro.net/install:nix#updating
--
Ghost wrote to Gamgee <=-cap_net_bind_service=+
Re: Re: setcap command
By: Gamgee to Ghost on Mon Oct 10 2022 08:18 am
sbbs@greg-Virtual-Machine:~/sbbs/exec$ sudo setcap
symlep /home/sbbs/sbbs/exec/sbbs Failed to
set
capabilities on file `/home/sbbs/sbbs/exec/sbbs' (Invalid
argument) The value of the capability argument is not permitted
for a file. Or the file is not a regular (non-symlink) file
any help would be appreciated. I have looked on the web and could
not come up with anything better than what I have done here.
My guess is that the 'sbbs' executable (/home/sbbs/sbbs/exec/sbbs) is actually a symlink to the actual file (/home/sbbs/sbbs/repo/exec/sbbs),
and it's failing for the reason given in that error message regarding a
ink.
Well, I haven't set up any symlinks, so unless it was done when
installed, I don't know. However, I tried your suggestion and got
the same response from the system.
Or just do the command "ls -l" while in the /sbbs directory, and see if there are symlinks there, or not.
have set up symlinks. On your "make install" command line to install,
did you also include "SYMLINK=1" ?
Or just do the command "ls -l" while in the /sbbs directory, and see if there are symlinks there, or not.
Ghost wrote to All <=-
I have tried (and failed) using the setcap command to allow the
ports <1024 to be used, but the command has failed with the
following:
sbbs@greg-Virtual-Machine:~/sbbs/exec$ sudo setcap cap_net_bind_service=+ep /home/sbbs/sbbs/exec/sbbs Failed to set capabilities on file `/home/sbbs/sbbs/exec/sbbs' (Invalid
argument) The value of the capability argument is not permitted
for a file. Or the file is not a regular (non-symlink) file
My guess is that the 'sbbs' executable (/home/sbbs/sbbs/exec/sbbs) is actually a symlink to the actual file (/home/sbbs/sbbs/repo/exec/sbbs), and it's failing for the reason given in that error message regarding a symlink.
setcap works fine on symlinks
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 412 |
Nodes: | 16 (2 / 14) |
Uptime: | 113:01:51 |
Calls: | 8,597 |
Calls today: | 10 |
Files: | 13,229 |
Messages: | 5,935,655 |