URL:
  <http://gna.org/bugs/?func=detailitem&item_id=2880>

                 Summary: savane using hard-coded path in at least one
instance!
                 Project: Savane
            Submitted by: mech
            Submitted on: Wed 09/14/2005 at 01:06
                Category: None
                Priority: C - Normal
                Severity: 3 - Normal
                  Status: None
                 Privacy: Public
             Assigned to: None
        Originator Email: 
             Open/Closed: Open
                 Release: 
         Planned Release: 

    _______________________________________________________

Details:

When I attempt to run sv_membersh, it just says: `System misconfiguration,
contact administrators. Exiting at /usr/local/bin/sv_membersh line 65`.

This failure is because it is hard-coded at line 63 to look for its config
file at /etc/membersh-conf.pl, but in my installation it is in
$sys_www_topdir/../../etc/membersh-conf.pl (I'm sure there's a better way to
express that; in my case it is /data/savane/etc/membersh_conf.pl since I told
savane to install in /data/savane/ instead of the default.

See also savane sr #723 in the comments: membersh-conf.pl needs at least some
basic documentation!

Also, perhaps this should be its own bug: even after putting a copy of
membersh-conf.pl where sv_membersh expects to find it, in /etc/, which to me
is a terrible location for something that is sv-specific (same goes for
sv_membersh and various other sv binaries being in one of the system's own
bin directories instead of $sys_www_topdir/../../bin), sv_membersh STILL
doesn't work correctly, and dies with the error: `You tried to execute:
Sorry, you are not allowed to execute that command.`
Putting any argument after `sv_membersh` seems to have no effect other than
the argument appears after `execute:` in the error message.  How on earth is
this thing supposed to work?  I would suggest either fixing sv_membersh,
making it the default shell for user, and documenting it, or including cvssh
and doing the same with it.  Right now I feel I have no choice but to either
give users bash or give them nologin, the first of which is a security risk
and second of which renders user accounts useless.  <sigh>






    _______________________________________________________

Reply to this item at:

  <http://gna.org/bugs/?func=detailitem&item_id=2880>

_______________________________________________
  Message sent via/by Gna!
  http://gna.org/


_______________________________________________
Savane-dev mailing list
Savane-dev@gna.org
https://mail.gna.org/listinfo/savane-dev

Reply via email to