Posted by
timothy
on from the ssh-don't-tell-anyone dept.
Mithix writes "Gizmodo is reporting that the popular (and free) SSH client PuTTY is now in beta for Symbian OS, the OS of choice for the Nokia Series 60, the Nokia 9200 Communicator Series, and the N-Gage. Finally, something redeeming for the N-Gage?"
Um.... Sony Ericsson T616 isn't a Symbian OS based phone.
And it is pretty much impossible to write an ssh client for it simply because of the crappy Sony Ericsson J2ME implementation. Sony Ericsson has chosen not to implement sockets so j2me "internet" apps must utilize wap push mechanisms in order to send/receive data.
If you want a phone that supports sockets look for a phone with a phone that has MIDP 2.0 implemented. I'm pretty sure that sockets is a requirement in MIDP 2 and optional in MIDP 1.
some j2me midp1.0 phones do support sockets(google search says that t616 doesn't though), in fact, almost all the recent one's. midp1.0 doesn't require it though. however, I'd be very skeptical of it being feasible to do a ssh client in one of them.
the series60 putty has been out for months already.
but yeah, people should not mix up feeble j2me apps and native symbian apps, the native one's have so much more power and access that j2me seems like a joke in comparision.
-- world was created 5 seconds before this post as it is.
Re:Ah, PuTTY
by
Anonymous Coward
·
· Score: 2, Informative
OpenSSH for Cygwin doesn't produce a log file. Instead, it writes to the event log, and it only writes diagnostic messages not the entire session output.
It's good
by
squiggleslash
·
· Score: 4, Informative
I use PuTTY on my Nokia 9290 (and have done for a while.) It "just works".
One thing to be aware of though is that it is limited to SSH - the PuTTY client for Windows does telnet and rlogin too, but not this version.
-- You are not alone. This is not normal. None of this is normal.
PuTTY for Windows is the best software of its kind. When I need an SSH/XTerm window to a Linux box, PuTTY is what I use, because I can't find an alternative that works nearly as well. That being said:
PuTTY insists that you use default XWindows conventions for cutting and pasting. Even most XWindows software is more flexible than that, never mind a cross-platform app. It's a pain for somebody who works primarily in Windows.
Configuration is horribly idiosyncratic. Options are not arranged in anything like a logical fashion, creating or modifying sessions is a pain, and it's too easy to make a bunch of changes and then lose them.
Either the PuTTY people are totally bored by UI design issues, or they just like to torture people. I hate to complain, because it's basically good (even excellent) software, and the price is right. But come on, guys!
Re:PuTTY Experience
by
MS_is_the_best
·
· Score: 2, Informative
Putty's authors advise you too use a 3rd party app for transparency (http://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/transparency.html).
Adding a bitmap will bloat the binary too much, according to them. But forks of putty which do this, exist. (only they are most of the time outdated).
I am still waiting for the Tab support, nowadays my desktop at work is full of putty windows, what is a bit annoying. (Screen doesn't work good in Cygwin..).
Re:PuTTY Experience
by
kisielk
·
· Score: 3, Interesting
Also, portable configuration files in PuTTY would be a real blessing. One of the best parts of PuTTY is you can easily fit it on the tiny portable media of your choice and use it anywhere. Unfortunately it uses the registry to store its settings, sessions, etc and it would be nice if I didn't have to write to the registry of every machine I ever used it on. It would be nice to just carry a config file with all my sessions along with my PuTTY executable.
One of us is completely misunderstanding the other.
Text mode programs don't know about terminal cut and paste. They all think they're running on DEC-compatible terminals, which is what all XTerm implementations emulate. (Actually, they assume whatever terminal you specify via $TERM, but nowadays that's almost always set to "xterm", since hardware terminals are more or less dead.)
Agreed.
They don't see mouse gestures. They just see input. They have no way of knowing whether these inputs come from a keyboard or a clipboard.
But ^C and ^V aren't mouse gestures! They are keyboard commands, and many (if not all) programs that run in the terminal use them. Suppose putty were to intercept ^C and everytime I pressed ^C it would copy the text I had highlighted, instead of passing the ^C over the SSH connection. Then how would I send the SIGINT signal to programs that had hung? How would I use the ^C command in pico (displays current line number)? How would I quit out of emacs (^X^C)? Intercepting ^V is almost as bad because it is the keyboard shortcut for "page down" in just about every terminal program I have ever used.
If putty were to start capturing keyboard input and using it for other purposes, then it would have to provide another method for you to send those key sequences.
putty doesn't need cygwin, but you need putty even if you have cygwin.
cygwin's ssh client has some annoying problems, expecially when using curses programs. They are just annoyances, but why put up with them when you can get putty that works nearly flawlessly.
Slashdot Mirror
But I'm still not buying an Ngage.
Blogging Weight Loss, Distance Education, and more at verlin.com
I just got a Symbian OS based phone on Sunday. (Sony Ericsson T616) and had the idea to write a SSH client for it.
:(
A day late and a dollar short again
If bad puns were like deli meat, this would be the wurst
OpenSSH for Cygwin doesn't produce a log file. Instead, it writes to the event log, and it only writes diagnostic messages not the entire session output.
One thing to be aware of though is that it is limited to SSH - the PuTTY client for Windows does telnet and rlogin too, but not this version.
You are not alone. This is not normal. None of this is normal.
- PuTTY insists that you use default XWindows conventions for cutting and pasting. Even most XWindows software is more flexible than that, never mind a cross-platform app. It's a pain for somebody who works primarily in Windows.
- Configuration is horribly idiosyncratic. Options are not arranged in anything like a logical fashion, creating or modifying sessions is a pain, and it's too easy to make a bunch of changes and then lose them.
Either the PuTTY people are totally bored by UI design issues, or they just like to torture people. I hate to complain, because it's basically good (even excellent) software, and the price is right. But come on, guys!putty doesn't need cygwin, but you need putty even if you have cygwin.
cygwin's ssh client has some annoying problems, expecially when using curses programs. They are just annoyances, but why put up with them when you can get putty that works nearly flawlessly.