Comment 9 for bug 693834

Built-in defaults sound nice but we don't have that luxury in HIP (there shouldn't be any default private keys, right?). So refusing to run is the only option but this sucks from the view point of usability. Nobody wants to copy files based on templates or whatever, and this is why hipd currently creates all necessary configuration files on first run. Another reason why hipd creates them is because we have currently four different ways to use hipd (directly from sources, make install, .deb and .rpm) and the current method just worked with all of them.

"make install" should probably create the necessary configuration files but not all people want to install (before trying out). So at least there should be "hipconf createconfigs" at the very least (*). Hipd/hipfw failing to start due to missing configs should instruct the user to run the command.

(*) It shouldn't be too difficult to move this functionality from hipd/init.c to hipconf.