How can I avoid details in the openser.cfg?
modparam("usrloc|auth_db","db_url","mysql://openser:openserrw@localhost/openser")
bye
Ronald
Roland,
you can not hide the passwd. What you can do is to set more restrictive access to your config file (use chmod)
regards, bogdan
Ronald Wiplinger wrote:
How can I avoid details in the openser.cfg?
modparam("usrloc|auth_db","db_url","mysql://openser:openserrw@localhost/openser")
bye
Ronald
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Bogdan-Andrei Iancu wrote:
Roland,
you can not hide the passwd. What you can do is to set more restrictive access to your config file (use chmod)
Is it possible to use include a file? and keep the passwords there? If you have a problem, you would like to share the real code, but with passwords in it, it is difficulty.
bye
Ronald
regards, bogdan
Ronald Wiplinger wrote:
How can I avoid details in the openser.cfg?
modparam("usrloc|auth_db","db_url","mysql://openser:openserrw@localhost/openser")
bye
Ronald
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
avast! Antivirus: Inbound message clean. Virus Database (VPS): 0639-3, 2006/09/27 Tested on: 2006/9/28 ¤U¤È 04:36:54 avast! - copyright (c) 1988-2006 ALWIL Software. http://www.avast.com
Ronald Wiplinger wrote:
Bogdan-Andrei Iancu wrote:
Roland,
you can not hide the passwd. What you can do is to set more restrictive access to your config file (use chmod)
Is it possible to use include a file? and keep the passwords there? If you have a problem, you would like to share the real code, but with passwords in it, it is difficulty.
the cfg file does not support an "include" directive - you can use M4 for this purpose, but guess it will not help in your case, as the generated cfg file will contain the passwd. I think the only solution is to set restrictive "read" permission on the file.
regards, bogdan
* Bogdan-Andrei Iancu bogdan@voice-system.ro [060928 11:11]:
Ronald Wiplinger wrote:
Bogdan-Andrei Iancu wrote:
Roland,
you can not hide the passwd. What you can do is to set more restrictive access to your config file (use chmod)
Is it possible to use include a file? and keep the passwords there? If you have a problem, you would like to share the real code, but with passwords in it, it is difficulty.
the cfg file does not support an "include" directive - you can use M4 for this purpose, but guess it will not help in your case, as the generated cfg file will contain the passwd. I think the only solution is to set restrictive "read" permission on the file.
What about dropping the password in the config file, and rather put them directly in the config.h file for *ser ? (or what ever that file is called ...) then he wouldBnt need to have the database config in the config file at all :)
-A
Atle Samuelsen wrote:
you can not hide the passwd. What you can do is to set more restrictive access to your config file (use chmod)
Is it possible to use include a file? and keep the passwords there? If you have a problem, you would like to share the real code, but with passwords in it, it is difficulty.
the cfg file does not support an "include" directive - you can use M4 for this purpose, but guess it will not help in your case, as the generated cfg file will contain the passwd. I think the only solution is to set restrictive "read" permission on the file.
What about dropping the password in the config file, and rather put them directly in the config.h file for *ser ? (or what ever that file is called ...) then he wouldBnt need to have the database config in the config file at all :)
yes, it's about the config.h file #define DEFAULT_DB_URL "mysql://openser:openserrw@localhost/openser"
and
#define DEFAULT_RODB_URL "mysql://openserro:openserro@localhost/openser"
it is a solution, but is not quite flexible as you need to recompile/reinstall each time you change the passwd :).
regards, bogdan
Hi Again Bogdan-Andrei,
it is a solution, but is not quite flexible as you need to recompile/reinstall each time you change the passwd :).
Offcource. :) but, it should'nt really be tooo hard to make it as mysql, when starting *ser you can either use a default username/password (my.cnf in mysql, *ser.cfg in this case) OR use a command line parameter.
But, dont see the problem to just have it in the config file, and do rather strict rights on it.
-A
-
Atle Samuelsen -
Bogdan-Andrei Iancu -
Ronald Wiplinger