39714 - Add support for secure protocols SSH and SFTP

Status: VERIFIED WONTFIX

(Core Graveyard :: Security: UI, enhancement, P3)

Description

[David Krause]

Mozilla should have support for secure protocols such as ssh and sftp.  Clicking

on ssh://unixbox should either open a terminal window with ssh or should be

implemented throught xmlterm.  Clicking sftp://server should work like the ftp

client currently does.  Basically we need some glue between ssl, xmlterm, and

openssh.

Comment 1

[David Krause]

Moving to m30 and assigning to Security: Crypto.

Comment 2

[David Krause]

Reassigning to crypto owner.

Comment 3

[Jesse Ruderman]

related: handle "telnet" urls, bug 33282

Comment 4

[Doug Turner (:dougt)]

Reassigning all https/cartman/security bugs to valeski.  He will be finding new 
owner(s).  This shift is so that I can focus on embedding issues.  If the new 
owner has questions that can not be resovled, I may be able to lend a (quick) 
hand.

over to valeski....

Comment 5

[Gagan]

robert-- welcome to necko!

Comment 6

[Gagan]

->helpwanted

Comment 7

[J Luh]

sftp and ssh are not currently IANA-registered URL scheme names. Relevant 

documents:



http://www.isi.edu/in-notes/iana/assignments/url-schemes

http://www.ietf.org/rfc/rfc1738.txt 

http://www.ietf.org/rfc/rfc2717.txt

Comment 8

[David P. Drinan]

Changing product from Browser:Security:Crypto --> PSM 2.0

Comment 9

[John Unruh]

Mass assigning QA to ckritzer.

Comment 10

[John Unruh]

Marking wontfix. See http://www.iana.org/assignments/uri-schemes - (last updated
2001 August 20)
Please open a new bug when and if ssh, sftp are IANA-registered URL scheme names.

Comment 11

[Olivier Cahagne]

Really marking WONTFIX as this seems to be forgotten by previous user.

Comment 12

[John Unruh]

Verified.

Comment 13

[R.K.Aa.]

*** Bug 145324 has been marked as a duplicate of this bug. ***

Comment 14

[Matthias Versen [:Matti]]

*** Bug 158925 has been marked as a duplicate of this bug. ***

Comment 15

[Josh Birnbaum]

*** Bug 174417 has been marked as a duplicate of this bug. ***

Comment 16

[Greg K.]

The most recent SFTP Internet-Draft (<http://www.snailbook.com/docs/sftp.txt)>
appears to have expired on April 1, 2002. Anyone have any more recent documentation?

Comment 17

[Josh Birnbaum]

http://www.ietf.org/internet-drafts/draft-ietf-secsh-filexfer-04.txt

Comment 18

[Aleksander Adamowski]

Updated URL for assigned URI shemes:
http://www.iana.org/assignments/uri-schemes

Comment 19

[Joseph Delaney]

Draft for SSH (expires July 2004)
http://www.ietf.org/internet-drafts/draft-ietf-secsh-filexfer-05.txt

Draft for new URIs (expires any day now)
http://www.ietf.org/internet-drafts/draft-ietf-secsh-scp-sftp-ssh-uri-01.txt

Comment 20

[Paul Kruger]

this feature is all over the forums..
why is it getting ping ponged around

Comment 21

[Alexander Skwar]

(In reply to comment #20)
> this feature is all over the forums..
> why is it getting ping ponged around

Probably, because nobody feels like implementing it?

Comment 22

[August Mayer]

The IETF secsh working group is still active, the current draft is http://www.ietf.org/internet-drafts/draft-ietf-secsh-filexfer-10.txt . Anyway, I think this is a strawman argument, because the scp and sftp protocols have in practice been there for several years now; as more and more sites tighten their security, the need increases (in my opinion).

But I think it would just need someone to step up and do it... it surely would be a killer feature!