MidpSSH | SSH and Telnet client for Mobile Devices

Sparrow · Joined: 23 Feb 2005 Posts: 10

Okay, I've been at this issue from several different sides (Trying to get j2me VNC working, which has same errrors), including muTelnet as well. And this is what seems to be the problem.

Later model Motorola phones implement a "Code Signing" feature set which is neat, however blocks unverified applications from being able to write to sockets that aren't HTTP, or HTTPS.

From http://www-106.ibm.com/developerworks/java/library/wi-secj2me.html#head5

Sparrow · Joined: 23 Feb 2005 Posts: 10

And it really seems like this guy may have figured out how to sign applications

http://motofan.ru/board/index.php?s=e14ffadf70f675b63f2d587dad0e3207&showtopic=3324&st=

Shame it's in russian Smile

_________________
----
Motorola V3 Razr, Unlocked
Provider, T-Mobile

Comrad · Posted: Fri Mar 11, 2005 6:03 pm Post subject: Re: Errr...

Karl · Posted: Fri Mar 11, 2005 9:59 pm Post subject:

Wow, that sounds complicated. Is it successful? If it is could someone write up a short piece on it so that I can attach it to the FAQ? A definitive solution!

Otherwise - my understanding is that the code would need to be signed by an authority trusted by the phone... That's probably Verisign etc? Can anyone confirm that? If it's the case then we can investigate what's involved in being able to sign!

Sparrow · Joined: 23 Feb 2005 Posts: 10

Edited Mispost, read below
_________________
----
Motorola V3 Razr, Unlocked
Provider, T-Mobile

Sparrow · Joined: 23 Feb 2005 Posts: 10

Yes, maybe. It's just a guess and I still haven't gotten it working yet. What I need is a j2me_domain_registry.sm file from /a/kjava on a motorola phone that WORKS with your program so that I can swap it with my locked up one. I'm pretty certain that file is the culprit, and it seems that if it isn't present then it assumes all apps don't have that privledge so that solution won't work. I need to edit the file to allow some external verifier, or you'll have to sign your app with one of the known verifiers. Here is a copy of the j2me_domain_registry.sm file that I have:

http://www.logichigh.com/files/j2me_domain_registry.sm.zip

Here's a version of the file I converted to ASCII so I could post it in a readable format (download the file above if you want the real deal), but you can see in it what verifiers are trusted.

guzzirider · Posted: Mon Mar 14, 2005 3:42 am Post subject:

Let me just say that if ithis problem can be resolved by a simple code signing cert from Verisign, I for one would be happy to contribute some cash to help pay for the cert! Smile

__Jason

Sparrow · Joined: 23 Feb 2005 Posts: 10

All that may be needed is a the Verisign codesigner program.. though it looks like it's a little pricey...

http://www.verisign.com/products-services/security-services/code-signing/digital-ids-code-signing/index.html
_________________
----
Motorola V3 Razr, Unlocked
Provider, T-Mobile

mercaptan · Posted: Mon Mar 14, 2005 2:27 pm Post subject:

Sparrow, I believe some fine folks over at HowardsForums have put together quite a package for the java issue, although I just tried applying the unbranded v620 session file and still got the same "write denied" error.

Still, to be helpful, here's the thread about replacing various j2me components to try and uncripple the ports/sockets:
http://www.howardforums.com/showthread.php?s=&threadid=555657&highlight=%2Ba630+%2Bsocket

Also, your session file is available (posted from a link on the Moto A630 superthread): http://homepage.mac.com/rmarquez/index.html (look under "Java Packs")

mercaptan · Posted: Wed Mar 16, 2005 3:40 am Post subject:

UPDATE (Mar15):
Getting closer to success. By deleting everything from the kjava directory on my a630 and uploading the j2me files from yakky's java pack (and reuploading the original J2MEPCK, I seem to have gotten past the "Reader: access denied" error.

Now MidPSSH gets to the "connecting to host...ok" phase, and then drops the connection, flashing "Reader: read.filter:java.lang ArrayIndex out of bounds exception" nearly too quickly for me to read clearly before the session report pops up.

I am able to connect successfully via SSH using Idokorro's J2ME SSH client, but their input scheme sucks (it uses ITAP instead of my Moto A630's QWERTY keyboard) and I don't want to shell out $45 to those guys. But I can now get past the crippled sockets on my T-Mobile A630 (I have the regular T-Zones plan and connect to a computer running sshd on port 995).

Still, what is that Java error? And what can I do about it? I feel like I'm so close to getting this to work!

Sparrow · Joined: 23 Feb 2005 Posts: 10

Having some trouble finding the a630 flex you mentioned, could you do me a favor and zip the java folder (the good one) that you've got and e-mail it to me so I can try putting it on my Razr?

01@logichigh.com

Thanks in advance!
_________________
----
Motorola V3 Razr, Unlocked
Provider, T-Mobile

Karl · Posted: Wed Mar 16, 2005 8:25 pm Post subject:

Hi,

Great - it sounds like code signing may be a solution. It looks like the Verisign one is US$400? Does anyone have any experience signing code with Verisign?

Part 2 - the ArrayIndexOutOfBoundsException. Perhaps you could start a new thread and mention the version that you're trying? There are a few of these exceptions occurring and I'd like to track them down!

mercaptan · Posted: Wed Mar 16, 2005 8:45 pm Post subject: Re: Hey

ksheehan · Joined: 14 Feb 2005 Posts: 18

I have information that newer devices (v551, etc.) from Cingular are set to dissallow untrusted or 3rd party trusted apps that use javax.microedition.io.Connection.socket (as well as ssl and various other 'fun' services). They flat out refuse to grant it...

Now my 'removing' the file on my phone allowed the MIDPSSH app to work as it now does not 'see' that restriction.

It should be possible without much difficulty to pursue and obtain a free validation and certificate from Cingular. Cingular only 'trusts' apps signed by Cingular or the manufacturer... Motorola in this case... not Verisign.

The site I found all this on is here.

BTW... below is the document that describes the Cingular j2me MIDP 2.0 security policy.

Karl · Posted: Wed Mar 16, 2005 9:12 pm Post subject:

Thank you for that. As we've discussed - this indicates that we require Cingular signing for it to work on Cingular devices. Or Motorola signing etc.