Posts - #136, #138
Looks like the modified firmware not the Foxy Utility !
I *think* its the hmt utility running under linux in the jail-broken Humax, but yes, I know they were not talking about the PC version.
If we can just log in to a telnet console on the Humax and run utilities on it to "do stuff", and maybe start daemons to just sit there and do the stuff for us (this is all just a little beyond me at the moment, but I did dabble a little in UNIX in the 1980/90's), especially if the jail-breaking doesn't cock-up the firmware update process so is completely reversible, then in the absence of official stuff from Humax I see this as the way to go.
What I'm not clear on at the moment is whether the jail-break firmware update process ADDs stuff or REPLACES the official firmware, and therefore whether you need to somehow protect from the Humax auto-updating - would it wipe out the jail-break or just update the official facilities within it? If the box was updated to new firmware, would the existing jail-break still work or would we be waiting while the gurus rewrote the jail-break?
These uncertainties make the PC work-around a bit less of a second choice for the moment. Maybe somebody could write a script that automatically spots a new HD recording file, FTPs it to the PC, clears the protection flag, and writes it back.
I have to say it seems a bit odd that Humax have left it open like this. It seems incredibly stupid that a file that is encrypted on the hard drive (to stop you accessing the drive and ripping the content directly) can be fooled into copying it in the clear just by clearing a status flag in its container (which is what I presume is going on). Can we do the same with other DRM content - eg WMV or MP4?