Yes, I was looking at the wrong package.It's the mongoose package which isn't often updated, and the mongoose.conf file is flagged as a config file so your local changes will not be overwritten.
Yes, I was looking at the wrong package.It's the mongoose package which isn't often updated, and the mongoose.conf file is flagged as a config file so your local changes will not be overwritten.
That secures the web interface, but not the FTP, DLNA, or Telnet. FTP and Telnet can be secured (to some extent) by changing from Humax's default "0000" password.
Here's an interesting variation on a theme. I've got my port forwarding working both from my netbook and my HTC Desire, through both the main WebIf and the /iphone variant. I've followed TomT's guide to the letter to add a password, even going through the revised instructions from later in this thread to add it to the /iphone directory.
All well and good so far, and the .htpasswd file is in both directories.
Now for the funny bit.
1. From a PC - Entering either [my external IP address] or [my external IP address/iphone] prompts me for a password, all of which tends to indicate that I've done it right so far (and people who slavishly follow instructions because they don't know what they're doing frequently do!) however....
2. From my HTC Desire - Entering the full sized WebIf address i.e. just my external IP address, does indeed get me prompted for a password, whereas accessing the /iphone variant takes me straight into the page and leaving the page navigable without a peep from a password request.
'Fraid I just don't understand xyz321's syntax. Copying instructions is one thing, editting is another.I'd try this way of doing it, works for me.
Sorry about my cryptic post (there is a reason why I haven't made much of a contribution to the Wiki).'Fraid I just don't understand xyz321's syntax. Copying instructions is one thing, editting is another.
cd /mod/etc
echo "global_passwords_file /mod/etc/.htpasswd" >> mongoose.conf
/mod/sbin/mongoose -A ./.htpasswd mydomain.com admin pass
service stop mongoose
service start mongoose
cat mongoose.conf
Thanks for that. Just what I need (and no sarcasm intended), a set of actual instructions. That's probably why I also don't tend to contribute to wikis. I did for a while on the 3View site but I'm not sure anyone ever read what I'd put anyway!Sorry about my cryptic post (there is a reason why I haven't made much of a contribution to the Wiki).
Try the following from the telnet command prompt:
Code:cd /mod/etc echo "global_passwords_file /mod/etc/.htpasswd" >> mongoose.conf /mod/sbin/mongoose -A ./.htpasswd mydomain.com admin pass service stop mongoose service start mongoose
The echo command appends the text in double quotes to the file /mod/etc/mongoose.conf. You can check that it is correct by typing
Code:cat mongoose.conf
This is incorrect. It should be "vi mongoose.conf". Just a slip of the keyboard.Then open the file to edit it with vi .htpasswd <enter> - that will then show you the contents of the file and allow you to change it.
Chris - I think the gap in your understanding is the command line. Did you ever use PCs in the days of MS-DOS - ie before Windows? If you did, then perhaps you can understand that the Humax Linux command line via Telnet is like dealing with the DOS C:> prompt. XYZ's "echo" line was a means to append specific text contents by sending a string to the console output but diverting the output to be appended to a named file (">>"). If you want to edit a file you have to start up an editor ("vi") and use the editor's commands (vi isn't the easiest of editors), nothing to do with the program that is going to read the file as input (mongoose).
This is incorrect. It should be "vi mongoose.conf". Just a slip of the keyboard.
However, just one query. When using either Telnet or PUTTY, the command "o humax" to access the box gets me nowhere with an error message to say that the host could not be found, whereas typing "o 192.168.0.2" does work. I've checked that the hostname is set to 'humax' in the WebIf Settings page.
Perhaps the udhcpc client should be restarted with the '-h <hostname>' option, it might help in some cases.Unless your network has a DHCP server (the thing that hands out IP addresses) that's also acting as your DNS server (the thing that turns names into IP addresses) and the DHCP information is imported into the DNS database, you won't be able to access the device by hostname.
Well this is what I found curious in the first place. I've made no changes to my router nor have I ever added anything to the windows hosts file, but prior to loading the latest variant of the modded software, I was able to use the 'o humax' command and now I'm not. I've checked to make sure that the Humax is set to a fixed IP address.Unless your network has a DHCP server (the thing that hands out IP addresses) that's also acting as your DNS server (the thing that turns names into IP addresses) and the DHCP information is imported into the DNS database, you won't be able to access the device by hostname.
That is unless you're using a static IP and you place the name to IP mapping into the windows hosts file.