I wrote to patches for the two things I talked about last week. I
don't know if it is in the interest of Manuel Kasper to have it in the
main distribution(I did my best, but I don know if it is good enough),
but if anyone wants to use them, they are attached.
The password requirement in console uses the same database that webgui
uses, so to change password you need to do so using the web interface.
Change it in console can be very easily implemented.
The other part of the patch let enable and disable the webgui, using a
new flag in config.xml file, so when you restart, monowall will keep the
Now I'm working on the third part I suggested, that is the
I started doing things on the "right" way. I rebuilt php now requiring
gettext, but I dont know if it was a real good ideia. look:
In monowall main distribution I have php like this:
-r-xr-xr-x 1 root wheel 1060380 Jul 18 04:57 usr/local/bin/php
libcrypt.so.2 => /usr/lib/libcrypt.so.2 (0x2815d000)
libm.so.2 => /usr/lib/libm.so.2 (0x28176000)
libc.so.4 => /usr/lib/libc.so.4 (0x28191000)
And in my build things growed a litle bit more than I expected:
-r-xr-xr-x 1 root wheel 1066328 Sep 16 13:08 usr/local/bin/php
libcrypt.so.2 => /usr/lib/libcrypt.so.2 (0x2815e000)
libintl.so.6 => /usr/local/lib/libintl.so.6 (0x28177000)
libm.so.2 => /usr/lib/libm.so.2 (0x28180000)
libc.so.4 => /usr/lib/libc.so.4 (0x2819b000)
libiconv.so.3 => /usr/local/lib/libiconv.so.3 (0x28234000)
-r--r--r-- 1 root wheel 967992 Sep 18 22:41 usr/local/lib/libiconv.so.3
-r--r--r-- 1 root wheel 32056 Sep 18 22:41 usr/local/lib/libintl.so.6
So I realized that doing this I added more 1MB in monowall.
Working on this way I created one new directory in / called /locale, and
inside I have the internationalization files. Until now I just have
English and Brazilian Portuguese. I translated 6 pages in
/usr/local/www, and I'm expecting that every new language in this
directory will add more 30Kb to the monowall. Comparing to other
internationalized projects we can easily have 30 languages in monowall
very soon (900Kb).
My questions are:
- Adding more 2Mb to monowall can be very space consuming due to it will
be a 30% increase in size, but it still fits in a 8Mb CF. So should I
continue this effort?
- Working with gettext is the standarized way to internationalize
programs, but it is very space consuming, can/should it be done another way?
- If the internationalization project continues, does any one wants to
translate the pot files to your local language? I just speak English,
Portuguese and Italian :)
Sorry for the long e-mail.
Matt Juszczak wrote:
> I kind of agree that there should be a "Enable Web GUI"/"Disable Web
> GUI" option right from the main menu of m0n0wall. It wouldn't be that
> hard to do, its really just starting and stopping the webserver that
> manages the Web GUI (considering I believe the captive portal runs on a
> different port...)
> On Mon, 13 Sep 2004, Jean Everson Martina wrote:
>> Hi all,
>> I'm currently working with m0n0wall on some projects. To
>> accomplish some tasks I need to change a little bit the way monowall
>> boot. I need to ask a password before the user have access to the
>> console. I wrote a little patch to do this. The patch is attached.
>> I'm having problems with the authentication scheme used by
>> m0n0wall. When I run the function checkPass outside monowall
>> everything is OK, but inside monowall this function don't work at all.
>> I opened a Shell to test the function, and its returning the wrong
>> value inside monowall.
>> This is one of our tasks to improve m0n0wall to our needs, but I
>> think it could help anybody else.
>> Another thing wre need to change in m0n0wall is the automatic
>> starting of the webGUI. We need to disable it, as we do with console.
>> Some of our clients think that keeping the admin web port open is a
>> security flaw. How can we start to do this? is there some
>> documentation about the m0n0wall XML Schema to us to include this
>> setting there?
>> For last, we are planning here an effort to internationalize
>> m0n0wall. We have people here experienced in internationalization of
>> programs and we think that monowall could be much more attractive it
>> was internationalized. Do you have any suggestions/comment about this