  DogFace05
join:2005-12-09 Cary, NC
| [Preview] NAizer for CYT
 Environment editing. |  XML editor. |  Full read/write access to SquashFS file system in installed firmware images. |
If anyone's been wondering what ever happened to the NAizer project for CYT devices, it's still in the works. It was originally planned simply as a tool for editing both boot block environments (the fixed environment embedded in the bootloader code, and the standalone variable environment that occupies its own partition) through software means alone, to eliminate having to turn to hardware invasive, warranty voiding means such as JTAG.
A proof of concept, console version of the program was successfully tested in early January on several different CYT platforms and with different firmware versions, so I embarked on the second phase of the project--making it into a user friendly, GUI variant.
It has since grown significantly in scope, becoming a full fledge adapter customization/management tool, with the addition of a built-in XML editor and full read/write access to the SquashFS file system in the installed firmware images.
Following is a summary of main features:
• Flash backup/restore; • Editing of both fixed and variable boot loader environments; • Editing of "read only" variables; • Password entry with hashing support; • Encryption key editing, both as stored and actual; • Viewing of changes to actual encryption key as the stored key is being edited, and vice versa; • Editing of embedded configuration partitions through built-in XML editor; • Read/write access to SquashFS file system in both installed firmware images; • Full support for both SquashFS version 1.x and 2.x; • File drag-and-drop integration with Windows Explorer; • Expected support for most, if not all currently available CYT devices; • Tentative support for WRTU54G-TM;
There still remains alot of work to be done before the program will be ready for beta test, but I wanted to provide something of a status update. |
|
 AndrewZ Premium join:2003-07-17 somewhere | Great news! I'm ready to test, have PAP2v2 & VTech ip8100. |
|
 mazilo From Mazilo Premium join:2002-05-30 Lilburn, GA | reply to DogFace05 DF05,
Looks good to me. As a matter of fact, the program itself looks very professional. Honestly, perhaps you should consider to sell this program to make little income. After all, you have invested a lot of your time on this project. |
|
 hoolahoous
join:2004-08-25 Red Valley, AZ
| said by mazilo :perhaps you should consider to sell this program to make little income. coming from mazilo who 'prays' for freebies this is a big compliment..  |
|
 mazilo From Mazilo Premium join:2002-05-30 Lilburn, GA
| said by hoolahoous :said by mazilo :perhaps you should consider to sell this program to make little income. coming from mazilo who 'prays' for freebies this is a big compliment..  LOL ... You are damn right (the proof is on my signature below)! 
I know DF05, not only a very humble person, but he really works hard to earn his $$$. BTW, didn't I say honestly on my previous post? -- Mazilo always prays for FREEBIES! US Phone: +1-678-601-0907 UK Phone: +44-703-194-2574
|
|
 ilhy
join:2005-11-07 Detroit, MI | reply to DogFace05 When will it be available? |
|
 Hard_Drive
join:2008-10-04 Muskegon, MI
| reply to DogFace05 This is great news, I have a couple of devices that I managed to unlock but not convert to true -NA devices, so it's possible, though not highly likely, they could go back to being locked to a provider. I'm just curious, though, will your program be able to recover devices if someone attempted to unlock them and botched it? I almost did that on one of the devices, but realized what I'd done wrong before it was too late.
Eventually what would be really great is if there were a way to modify the actual firmware to add capabilities not included by the manufacturer, such as some form of secure tunneling to an Asterisk server using something like an SSH or OpenVPN connection. But that's just a thought for future development - for now I'll be happy to see a working beta of your software as you've shown it here! |
|
 hoolahoous
join:2004-08-25 Red Valley, AZ
| reply to DogFace05 said by DogFace05 : • Tentative support for WRTU54G-TM; i am holding my breath starting now..  |
|
  DogFace05
join:2005-12-09 Cary, NC
| reply to ilhy said by ilhy :When will it be available? When I first mentioned the project a few months ago, I was hoping it would only take another few weeks. As a former manager of mine once remarked, you ask an engineer for a time estimate, then you have to tripple it, and again double it before passing it on to upper management. Truth be told, I don't have the remotest clue how much longer it will take. What I do know, is that there's lots of work left:
• Many features are still buggy, incomplete, or not yet implemented. This is especially true of parts of the SuqashFS file system support, which I decided to add to the project some three weeks ago. It's a rewrite from scratch not based on any open source project. Also, conversion between Linux symlinks and Windows shortcuts is still in the works. • My current code uses the public domain LZMA library from Igor Pavlov's latest 7Zip SDK. However, I'm currently rewriting all LZMA code from scratch--in assembly language. This will take a while. • There are lots of user interface details that need work--the tedious, boring kind of work I usually end up deferring until later, but eventually have to get done. • I haven't even started looking into how to do the online help. Can't release the program, not even for beta test, without at least some form of online/context help. • Although not relevant to the free limited beta test, there are lots of issues to be worked out as to how the program's to be marketed eventually, if at all.
Bottom line, I can't give a meaningful ETA yet. |
|
  DogFace05
join:2005-12-09 Cary, NC
1 edit | reply to Hard_Drive said by Hard_Drive :I'm just curious, though, will your program be able to recover devices if someone attempted to unlock them and botched it? The program depends on the device being able to boot and run normally. If someone has screwed it up such that it won't boot, well, then depending on the severity (whether the boot loader runs or not), it will likely be necessary to turn to either a serial interface or J-TAG to recover it. However, so long as the Linux installation and the web interface run normally, the program will provide full access to anything in the adapter's flash memory.
Eventually what would be really great is if there were a way to modify the actual firmware to add capabilities not included by the manufacturer, such as some form of secure tunneling to an Asterisk server using something like an SSH or OpenVPN connection. But that's just a thought for future development - for now I'll be happy to see a working beta of your software as you've shown it here!
That's what the SquashFS file system support is for. You'll be able to modify, replace, add anything to the firmware's SquashFS file system at your heart's content. If you want a different busybox with more features, just drag and drop a replacement over the current one. You want to modify the startup scripts? Just edit them with the built-in editor. Then commit the updates to flash. NAizer™ will rebuild the firmware image's file system and flash it for you. |
|
  DogFace05
join:2005-12-09 Cary, NC
| reply to hoolahoous said by hoolahoous :said by DogFace05 : • Tentative support for WRTU54G-TM; i am holding my breath starting now.. I hope you have an oxygen tank handy.  |
|
 toro
join:2006-01-27 Scarborough, ON
·TekSavvy Solutions..
| reply to DogFace05 said by DogFace05 :NAizer(tm) will rebuild ... Just curious, did you really register a TradeMark for your NAizer ?  Anyways, the project looks great so far ! |
|
  DogFace05
join:2005-12-09 Cary, NC
1 edit | There are two forms of trademarking. One is a registered trademark, which is obtained by formally registering the trademark with the appropriate trademarking authority of your country, and paying any required fees, and entitles the owner to bear the encircled R mark, as in for example FrigginGadget®.
The other is the so-called poor-man's trade mark, which the trademark claimant simply claims by publicly using the mark with an appended raised ™, as in NAizer™, and doesn't cost a penny, nor requires any form of formal registration. The claimant does have a year to actually start marketing and selling the product for which the trademark is claimed, from the time it's first claimed, or the trademark becomes null and void.
The former trademark type does provide stronger legal protection, though, as its validity can more easily be verified and established, should it ever be challenged in court.
You can read more about it at the US Patent and Trademark office's web site. I'm not sure which the proper authority is in Canada, but trademarking rules are generally consistent throughout most western countries and elsewhere, through international trade agreements.
In the post you quoted, I thus made a public claim to the trademark. However, I did make a mistake, though, as writing tm in parentheses isn't the correct way of doing it--it has to actually be a raised TM appended to the claimed name. I have since corrected it, and again lay claim to NAizer™ as my trademark for any software and/or hardware product that permamently alters and/or removes the customization of any provider customized ATA or other embedded device.
I am actually the one who came up with and coined the verb to NAize (NAizing, etc) (in behind the scenes communications with various members of this forum, as well as posts here at DSLR), but it isn't something I believe or feel I could trademark, as it's now become so widely used (at least at this site). However, the specific noun NAizer, very much is something that I can trademark under the trademark rules, provided of course that noone else already has laid claim to it for a similar product. |
|
 Dan_voip
join:2007-01-03 Canada | Good news! I'm looking forward to test the NAizer on Dlink VTA if that will be covered. |
|
  DogFace05
join:2005-12-09 Cary, NC | Indeed, I do expect it to support the D-Link VTA. |
|
 HelloG
join:2007-11-27 Manchester, NH | reply to DogFace05 DogFace05:
The list of features sounds great, nice work! Looking forward to the beta - count me in for testing. I've got a few ATAs lying around that I can use for testing. |
|
 ogdensburg
join:2006-12-12 Ogdensburg, NY | reply to DogFace05 I want to be a tester too. Have a few VTECH IP8100 and D-Link VTA sitting in my basement right now. |
|
 FastAtLast 300 baud and beyond
join:2004-04-07 Rotonda West, FL | reply to DogFace05 I have a VT2442 and am available for testing, if needed. |
|
 qingz
join:2003-10-20 Canada | reply to DogFace05 That's great news. I have a few of Vtech 8100 laying around. I like to be a tester, and willing to donate one or two Vtech 8100 for the project. |
|
  UHF All static, all day, Forever Premium,MVM join:2002-05-24 clubs: | reply to DogFace05 I have a Dlink ATA that needs unlocked. I'd love to give this a spin when it's ready. |
|