linuxdcpp-team team mailing list archive
-
linuxdcpp-team team
-
Mailing list archive
-
Message #05415
[Bug 945674] [NEW] Please add more UNIX friendly paths.
Public bug reported:
Currently the adch++ server uses a quite centralized system which is awful from a security point of view and is anything but helpful on most unices. Here is the propossal:
* Since we don't have SONAMEs for the libraries we can install them along with the adchppd binary in /usr/lib/adchpp (or /usr/lib/adchpp-version ) the adchppd binary can then be executed with a simple script that takes care of changing into that directory so libraries are found.
* All the default scripts (from my current installation I get
generate_certs.sh, pyutil, rbutil and scripts ) should be stored
elsewhere since they are not binary files in Gentoo we have chosen
/usr/share/adchpp-version
* Long term configuration files (i.e. those not meant to be changed
frequently) should be stored in /etc/adchpp as it is currently done.
Amongst those I think we should include Script.xml, adchpp.xml, the
certificates, en_settings.txt, fl_settings.txt, li_settings.txt,
motd.txt and maybe settings.txt (although the topic may be changed more
frequently and maybe should go elsewhere).
* Short term configuration files (i.e. those changed frequently like
databases) should be stored in /var/lib/adchpp Amongst those I think we
should include users.txt history.txt, the FL_DataBase and maybe the hub
topic. Currently we are missing a way to get this path to the scripts so
it should be added.
* The logging directory should be clear before the config is read (maybe
with an option switch) since otherwise the core will try writting into
the long term configuration dir on startup and shutdown before reading
the configuration.
So summarizing up:
* We need a way to pass a short term configuration path to adch++
* We need a way to set the logging directory before the core is started (or store logs in memory until we know where to put them).
** Affects: adchpp
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
Dcplusplus-team, which is subscribed to ADCH++.
https://bugs.launchpad.net/bugs/945674
Title:
Please add more UNIX friendly paths.
Status in ADCH++:
New
Bug description:
Currently the adch++ server uses a quite centralized system which is awful from a security point of view and is anything but helpful on most unices. Here is the propossal:
* Since we don't have SONAMEs for the libraries we can install them along with the adchppd binary in /usr/lib/adchpp (or /usr/lib/adchpp-version ) the adchppd binary can then be executed with a simple script that takes care of changing into that directory so libraries are found.
* All the default scripts (from my current installation I get
generate_certs.sh, pyutil, rbutil and scripts ) should be stored
elsewhere since they are not binary files in Gentoo we have chosen
/usr/share/adchpp-version
* Long term configuration files (i.e. those not meant to be changed
frequently) should be stored in /etc/adchpp as it is currently done.
Amongst those I think we should include Script.xml, adchpp.xml, the
certificates, en_settings.txt, fl_settings.txt, li_settings.txt,
motd.txt and maybe settings.txt (although the topic may be changed
more frequently and maybe should go elsewhere).
* Short term configuration files (i.e. those changed frequently like
databases) should be stored in /var/lib/adchpp Amongst those I think
we should include users.txt history.txt, the FL_DataBase and maybe the
hub topic. Currently we are missing a way to get this path to the
scripts so it should be added.
* The logging directory should be clear before the config is read
(maybe with an option switch) since otherwise the core will try
writting into the long term configuration dir on startup and shutdown
before reading the configuration.
So summarizing up:
* We need a way to pass a short term configuration path to adch++
* We need a way to set the logging directory before the core is started (or store logs in memory until we know where to put them).
To manage notifications about this bug go to:
https://bugs.launchpad.net/adchpp/+bug/945674/+subscriptions
Follow ups
References