Just drop the attached file to /usr/www/cgi-bin and the configure button will
magically appear :)
Then you only have to parse inetd.conf and present the relevant option; you
then need to write ssh_proc.cgi and 'sed -i' the relevant option.
When settings are saved, inetd.conf will be saved on flash.
If you do that, please contribute back, adding a one-line copyright/licence
message.
If openssh is installed, you could even ask if the ssh service should use
dropbear or ssh (not recommended, if the disk containing packages is
removed/damaged then ssh will not work)
I have not thought "deeply" about dropbear/openssh compatibility problems, the
openssh package is there only for "advanced" cli-users, kind of "you are now
on your own"
> Unfortunately dropbear has no config file options as vsftpd, so I can't
> clone the config management of this package.
> So the choices are:
>
> 1. Write a specific routine to manage dropbear line in inetd.conf
> 2. Define together a best-practice/framewrok to do this for other
> packages too
> 3. Evaluate something like uci (http://wiki.openwrt.org/doc/uci)
>
> Cheers,
> Gabriele
Just drop the attached file to /usr/www/cgi-bin and the configure button will
magically appear :)
Then you only have to parse inetd.conf and present the relevant option; you
then need to write ssh_proc.cgi and 'sed -i' the relevant option.
openssh package is there only for "advanced" cli-users, kind of "you are now
on your own"
> 3. Evaluate something like uci (http://wiki.openwrt.org/doc/uci)