I was quite suprised that a program so complete was lacking such a bug...
I'm trying a lots of client actually and yours is one of the best i've see BUT when i tried to open a link on a html page to a telnet session ( telnet:(URL OR IP) telnet:192.168.0.254 for exemple) it doesn't worked and u know why? because absolute telnet try to connect to the url/ip "telnet:192.168.0.254" and not "192.168.0.254" !!! Please tell me this will be corrected in the next version **;
This is the only thing who stop me from registering it...
[size=1][ February 07, 2003, 10:01 AM: Message edited by: Brian T. Pence ][/size]
hmmm... I use it this way every day - I have a map of the network switches and other equipment on the web and from IE 6 I am able to click on a switch on the map (linking to telnet://xxx.yyy.zzz.www) and AbsoluteTelnet opens the link just fine... Are you sure the URL is telnet://?
/msa
telnet:192.168.0.254
telnet://xxx.yyy.zzz.www
I would say in MUSUL's case the "//" is missing -- wrong type of link.
Agreed. However, I don't remember how I associated AbsoluteTelnet with the "telnet://" URLs...
You're both right. The correct form of the URL contains the forward slashes. Strangely, IE will still fire up the telnet client even if the forward slashes do not exists. Hmmmmm....
Absolute, of course, looks for the slashes to delimit the beginning of the IP address, optionally followed by a colon and the port number. So, when the slashes do not exist, it does not recognize it as a URL and the whole thing is interpreted as the hostname.
To make AbsoluteTelnet the default telnet client, check the 'Make AbsoluteTelnet the default telnet client' flag under Options->Properties->Global. With this flag, Absolute will check *AT EACH STARTUP* to make sure it is still set as the default telnet client. When enabled, AbsoluteTelnet will make itself the default client and optionally prompt you for verification.
The fact it is the default telnet client don't change a thing to the fact than url like telnet:adresses don't work...
Isn't there a mean to arrange that ? other client works fine with the two forms of urls...
I could probably make it work, but it would be a *hack* and not according to specs. What other client works this way??? On what pages do you see these links in this form?
From RFC1738:
3.8. TELNET
The Telnet URL scheme is used to designate interactive services that
may be accessed by the Telnet protocol.
A telnet URL takes the form:
telnet://:@:/
as specified in Section 3.1. The final "/" character may be omitted.
If : is omitted, the port defaults to 23. The : can
be omitted, as well as the whole : part.
This URL does not designate a data object, but rather an interactive
service. Remote interactive services vary widely in the means by
which they allow remote logins; in practice, the and
supplied are advisory only: clients accessing a telnet URL
merely advise the user of the suggested username and password.
BTW, AbsoluteTelnet does *not* support the username:password part of the url and it is rarely seen in practice, as it would be considered highly unsafe to do so. Perhaps, if I ever add an automatic login for telnet, I'd add this part of the telnet URL.
The fact that MS's telnet "client" does some magic rewriting of the URL does not imply that AT should violate the RFC.
Who talked about hyperterminal ?
Terminal client like Crt from vandyke softwares can use adress like those and it's not the only one who do it...
i don't think that it is a violation of the RFC since rfc constantly evolve but if u consider it is not important no problem don't get mad for this ^^
Nobody is mad, I was just curious what clients were out there that actually implement this. Also, I'm curious where these URLs exist because my first choice would be to notify the website operators and have them change their links.
See, the problem with reprogramming the application to allow things that are out of spec is that someone who is coding a new web page might write the URL as telnet:myhost and think that just because it seems to work that it must be right!! By allowing the incorrect syntax, you make your web page compatible only with software that is out of spec! Obviously, this web page owner is a VanDyke user! 😉
I understand that implementing the user:password for telnet may be hard (different banners, prompts and so on), but does it exist a standard for connecting with SSH? (like ssh://user:pwd@host) Since SSH handles the logins locally and passes on the information to the server (like AT does with its own prompt) it would be (theoretically) possible to get this to work. Handling private/public keys would be another issue though...
P.S I'm not mad either... 🙂 D.S
[size=1][ February 11, 2003, 02:38 AM: Message edited by: Mattias Sandstrom ][/size]
Just an observation: IE 6.0 rewrites URL:s entered "wrong" when it uses them self: "http:host" -> "http://host", "ftp:host" -> "ftp://host" etc, and then uses the URL. However, passing it on to other (external) applications, it does not rewrite the URLs.
Mattias u are right there is a mean to make IE6 handle adress like ssh://log:pass@ip
simpli make a reg file with the following content : (the 0000000000000 term can be anything u want of the same lenght)
[HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Advanced INF Setup\\IE40.Assoc\\RegBackup\\0.map]
"0000000000000000"=",1,HKCR,ssh,"
[HKEY_CLASSES_ROOT\\telnet]
@="URL : Protocole ssh"
"EditFlags"=dword:00000002
"URL Protocol"=""
[HKEY_CLASSES_ROOT\\ssh\\DefaultIcon]
@=""
[HKEY_CLASSES_ROOT\\ssh\\shell]
[HKEY_CLASSES_ROOT\\ssh\\shell\\open]
[HKEY_CLASSES_ROOT\\ssh\\shell\\open\\command]
@="\\"C:\\\\UTILITAIRES\\\\WEB LAN\\\\OUTILS\\\\CRT\\\\SecureCRT.EXE\\" %1"
[HKEY_CURRENT_USER\\Software\\Classes\\ssh]
@="URL : Protocole ssh"
"EditFlags"=dword:00000002
"URL Protocol"=""
[HKEY_CURRENT_USER\\Software\\Classes\\ssh\\shell]
[HKEY_CURRENT_USER\\Software\\Classes\\ssh\\shell\\open]
[HKEY_CURRENT_USER\\Software\\Classes\\ssh\\shell\\open\\command]
@="\\"C:\\\\UTILITAIRES\\\\WEB LAN\\\\OUTILS\\\\CRT\\\\SecureCRT.EXE\\" %1"
[HKEY_USERS\\S-1-5-21-1454471165-1677128483-1060284298-500_Classes\\ssh]
@="URL : Protocole ssh"
"EditFlags"=dword:00000002
"URL Protocol"=""
[HKEY_USERS\\S-1-5-21-1454471165-1677128483-1060284298-500_Classes\\ssh\\shell]
[HKEY_USERS\\S-1-5-21-1454471165-1677128483-1060284298-500_Classes\\ssh\\shell\\open]
[HKEY_USERS\\S-1-5-21-1454471165-1677128483-1060284298-500_Classes\\ssh\\shell\\open\\command]
@="\\"C:\\\\UTILITAIRES\\\\WEB LAN\\\\OUTILS\\\\CRT\\\\SecureCRT.EXE\\" %1"
(note than u can make the same thing for all protocol supported by AT
IMPORTANT DON'T FORGET TO MODIFY THE PATH OF THE APPLICATION
MUSUL,
thanks for the tip, will try it.
