"delete kickstart.ini after installation" option

Next topic

Author	Message
Stephan Staubli	Tuesday 07 March 2006 5:16:09 am hy i use kickstart.ini to install ezpublish on client domains. so there are some hot informations like uncrypted passwords in it which are only used for the installation wizzard. so i think it would be good to have an option like "killKistartIniAfterInstallation=true" or something like this. i use the provided .htaccess but still dont like to the have the kickstart.ini after installation. thanks s staubli
Gabriel Ambuehl	Tuesday 07 March 2006 5:49:40 am Those passwords are stored in the site.ini anyhow so it's probably not a very big additional risk... Visit http://triligon.org
Stephan Staubli	Wednesday 08 March 2006 2:31:09 am so because the risk is their anyway its no problem to have more additional risk?? i dont know how often people use kickstart.ini but i think chances that access to domain.tld/kickstart.ini are allowed than domain.tld/settings/site.ini are much bigger if someone uses not the .htaccess of ezpublish. i think its also not difficult for some kiddies to search with google for "Powered by eZ publish® " to find a bad configured ezp and try to find a kickstart.ini with admin pw.

Author

Message

Tuesday 07 March 2006 5:16:09 am

i use kickstart.ini to install ezpublish on client domains.
so there are some hot informations like uncrypted passwords in it which are only used for the installation wizzard. so i think it would be good to have an option like
"killKistartIniAfterInstallation=true" or something like this.

i use the provided .htaccess but still dont like to the have the kickstart.ini after installation.

thanks
s staubli

Gabriel Ambuehl

Tuesday 07 March 2006 5:49:40 am

Those passwords are stored in the site.ini anyhow so it's probably not a very big additional risk...

Visit http://triligon.org

Stephan Staubli

Wednesday 08 March 2006 2:31:09 am

so because the risk is their anyway its no problem to have more additional risk??

i dont know how often people use kickstart.ini but i think chances that access to
domain.tld/kickstart.ini are allowed than domain.tld/settings/site.ini are much bigger if someone uses not the .htaccess of ezpublish.

i think its also not difficult for some kiddies to search with google for "Powered by eZ publish® " to find a bad configured ezp and try to find a kickstart.ini with admin pw.

eZ debug

Timing:	Jan 18 2025 14:51:07
Script start
Timing:	Jan 18 2025 14:51:07
Module start 'layout'
Timing:	Jan 18 2025 14:51:07
Module start 'content'
Timing:	Jan 18 2025 14:51:07
Module end 'content'
Timing:	Jan 18 2025 14:51:07
Script end

Main resources:

Total runtime	0.0161 sec
Peak memory usage	2,048.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0048	588.0469	152.6406
Module start 'layout'	0.0048	0.0025	740.6875	39.4766
Module start 'content'	0.0073	0.0068	780.1641	89.2578
Module end 'content'	0.0142	0.0019	869.4219	30.3047
Script end	0.0161		899.7266

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0025	15.2801	14	0.0002
Check MTime	0.0011	6.6709	14	0.0001
Mysql Total
Database connection	0.0008	5.1836	1	0.0008
Mysqli_queries	0.0021	12.8184	3	0.0007
Looping result	0.0000	0.0680	1	0.0000
Template Total	0.0016	9.8	1	0.0016
Template load	0.0008	5.2649	1	0.0008
Template processing	0.0007	4.5389	1	0.0007
Override
Cache load	0.0006	3.8869	1	0.0006
General
dbfile	0.0025	15.5714	8	0.0003
String conversion	0.0000	0.0488	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs