Message Area
Casually read the BBS message area using an easy to use interface. Messages are categorized exactly like they are on the BBS. You may post new messages or reply to existing messages!

You are not logged in. Login here for full access privileges.

Previous Message | Next Message | Back to Synchronet Multinode BBS Softwar...  <--  <--- Return to Home Page
   Networked Database  Synchronet Multinode BBS Softwar...   [531 / 900] RSS
 From   To   Subject   Date/Time 
Message   Digital Man    Va7aqd   Recycle semaphore?   April 1, 2019
 11:57 PM *  

  Re: Recycle semaphore?
  By: Va7aqd to Digital Man on Mon Apr 01 2019 07:49 pm

 >   Re: Recycle semaphore?
 >   By: Digital Man to Va7aqd on Mon Apr 01 2019 04:14 pm
 >
 >  > It sounds like you're missing some kernel module associated with
 >  > capabilities. Sorry, I don't know more than that (I didn't write this
 >  > portion of the code, Deuce did). I don't seem to have any modules with
 >  > "cap"
 >  > in the name installed/running on my Debian systems, yet the capabilites
 >  > work
 >  > fine.
 >
 > OK, I think I have things sorted, but much of what was wrong seems to be
 > with
 > the suggestions
 > in the documentation (and that's no complaint about the docs at all -
 > there's tons of great info in the wiki).  Specifically, it looks like SBBS
 > should be started as
 > root as it drops
 > privileges and runs as the user defined in ctrl/sbbs.ini appropriately.

That's how I run it.

 > However, in the wiki
 > docs, and I would point the finger mostly at the systemd page, which gives
 > an
 > example with
 > systemd starting it as a non-root user & group.

Someone contributed that wiki page. You can certainly update it to clarify your
findings.

 > When doing an
 > strace on sbbs when starting (and complaining about it's inability to
 > recycle),
 > it looks like
 > it's checking other capabilities (though I'm not familiar with granting
 > capabilities this way,
 > so I'm just guessing on what this means):

The source for this is in src/sbbs3/sbbscon.c

It looks to me like it tries to use the following privs before binding ports:

    caps |= (1 << CAP_NET_BIND_SERVICE);
    caps |= (1 << CAP_SETUID);
    caps |= (1 << CAP_SETGID);
    caps |= (1 << CAP_DAC_READ_SEARCH);
    caps |= (1 << CAP_SYS_RESOURCE);

And then after binding:

       caps |= (1 << CAP_NET_BIND_SERVICE);
       caps |= (1 << CAP_SYS_RESOURCE);

 > it needs, but it appears that "setcap 'cap_net_bind_service=ep'" isn't
 > enough.

It seems to work for people. I don't personally use that method, so I can't
vouch for it.

                                            digital man

Synchronet/BBS Terminology Definition #66:
SyncEdit = A defunct 3rd party full-screen editor written for Synchronet
Norco, CA WX: 62.4°F, 44.0% humidity, 0 mph SW wind, 0.00 inches rain/24hrs
--- SBBSecho 3.07-Linux
 * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  Show ANSI Codes | Hide BBCodes | Show Color Codes | Hide Encoding | Hide HTML Tags | Show Routing
Previous Message | Next Message | Back to Synchronet Multinode BBS Softwar...  <--  <--- Return to Home Page

VADV-PHP
Execution Time: 0.0766 seconds

If you experience any problems with this website or need help, contact the webmaster.
VADV-PHP Copyright © 2002-2024 Steve Winn, Aspect Technologies. All Rights Reserved.
Virtual Advanced Copyright © 1995-1997 Roland De Graaf.
v2.0.140505

Warning: Unknown: open(c:\Sessions\sess_tvdp8bpulmh1021ooiars3s6s4, O_RDWR) failed: No such file or directory (2) in Unknown on line 0 Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (c:\Sessions) in Unknown on line 0 PHP Warning: session_start(): open(c:\Sessions\sess_tvdp8bpulmh1021ooiars3s6s4, O_RDWR) failed: No such file or directory (2) in D:\wc5\http\public\VADV\include\common.inc.php on line 45 PHP Warning: Unknown: open(c:\Sessions\sess_tvdp8bpulmh1021ooiars3s6s4, O_RDWR) failed: No such file or directory (2) in Unknown on line 0 PHP Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (c:\Sessions) in Unknown on line 0