W3C home > Mailing lists > Public > uri@w3.org > October 2009

Re: [Uri-review] ssh URI

From: David Booth <david@dbooth.org>
Date: Mon, 12 Oct 2009 21:42:20 -0400
To: bob@sporkmonger.com
Cc: Kristof Zelechovski <giecrilj@stegny.2a.pl>, uri-review@ietf.org, uri@w3.org
Message-Id: <1255398140.5481.10279.camel@dbooth-laptop>
On Mon, 2009-10-12 at 21:16 -0400, Bob Aman wrote:
> >  - Downloadable software that would cause the browser to recognize such
> > URIs in the future, and handle them appropriately (i.e., by opening a
> > secure shell, rather than by fetching a page from sshuri.org).
> > Furthermore, such software might even be programmed to recognize and
> > handle the "ssh:" URI scheme as well.
> 
> I have a problem with this in the general case because I don't think
> there's currently a way for such a URI to be registered to a specific
> application in any major browser.  

Take a look at greasemonkey:
https://addons.mozilla.org/en-US/firefox/addon/748 
Greasemonkey is based on recognizing URI patterns and performing special
functions when such patterns are recognized.

David Booth

> And for the specific case, I can
> think of at least one use case where you might want to link to an ssh
> URI in a browser:  HTTP-based admin interfaces to machines.
> 
> And I'll also repeat my previous comment for emphasis:  This concept
> is just confusing.
> 
> -1 to the concept of using anything under the http/https scheme to
> formally represent an ssh identifier.
> 
> -Bob Aman
> 
> 
-- 
David Booth, Ph.D.
Cleveland Clinic (contractor)

Opinions expressed herein are those of the author and do not necessarily
reflect those of Cleveland Clinic.
Received on Tuesday, 13 October 2009 01:42:49 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 13 January 2011 12:15:42 GMT