Discussion:
FISH vs SFTP
Gabriel Dragffy
2006-04-21 22:47:48 UTC
Permalink
when using the differnet protocols with Konqueror... what is the difference?
If I log in to a remote machine the same things happen so are they the same
but just written differently or what?
Billy Pollifrone
2006-04-21 23:08:56 UTC
Permalink
The protocol is just the 'language' used to communicate. If you're doing a
transfer of a file, you could use ftp, secure-ftp, scp, z-modem or whatever
protocol both ends are set up to understand. It really comes down to the way
the client and servers talk to one another.
Post by Gabriel Dragffy
when using the differnet protocols with Konqueror... what is the difference?
If I log in to a remote machine the same things happen so are they the same
but just written differently or what?
--
kubuntu-users mailing list
https://lists.ubuntu.com/mailman/listinfo/kubuntu-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ubuntu.com/archives/kubuntu-users/attachments/20060421/fb8c7358/attachment.htm
Christoph Wiesen
2006-04-21 23:17:42 UTC
Permalink
Post by Gabriel Dragffy
are they the same
but just written differently or what?
Exactly. fish:/ and sftp:/ are just different names for the same kio backend
(secure ftp over ssh).

Chris
Billy Pollifrone
2006-04-21 23:19:39 UTC
Permalink
Post by Christoph Wiesen
Post by Gabriel Dragffy
are they the same
but just written differently or what?
Exactly. fish:/ and sftp:/ are just different names for the same kio backend
(secure ftp over ssh).
Chris
Wow, did I misunderstand the question. Yup they are the same thing. :-D
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ubuntu.com/archives/kubuntu-users/attachments/20060421/d2b8cbd5/attachment-0001.htm
Toby Dickenson
2006-04-22 00:34:04 UTC
Permalink
Post by Christoph Wiesen
Post by Gabriel Dragffy
are they the same
but just written differently or what?
Exactly. fish:/ and sftp:/ are just different names for the same kio
backend (secure ftp over ssh).
Not quite....

The sftp kio uses the sftp subsystem of the ssh server. This is designed for
this purpose, but needs explicit support from the ssh server. Some ssh
servers may not support it, and some may have that subsystem disabled.

The fish kio is very different. It relies on the ssh providing a unix shell,
then it uploads a simple server program written in perl. A beautiful hack and
handy if sftp is not available on your ssh server, but nowhere near the
performance or reliability of sftp.

From a security point of view they are equivalent; both are protected by ssh.
--
Toby Dickenson
Christoph Wiesen
2006-04-22 00:53:20 UTC
Permalink
Post by Toby Dickenson
Post by Christoph Wiesen
Post by Gabriel Dragffy
are they the same
but just written differently or what?
Exactly. fish:/ and sftp:/ are just different names for the same kio
backend (secure ftp over ssh).
Not quite....
The sftp kio uses the sftp subsystem of the ssh server. This is designed
for this purpose, but needs explicit support from the ssh server. Some ssh
servers may not support it, and some may have that subsystem disabled.
The fish kio is very different. It relies on the ssh providing a unix
shell, then it uploads a simple server program written in perl. A beautiful
hack and handy if sftp is not available on your ssh server, but nowhere
near the performance or reliability of sftp.
From a security point of view they are equivalent; both are protected by ssh.
--
Toby Dickenson
phew, learned something new here. thanks =)
Derek Broughton
2006-04-22 04:31:36 UTC
Permalink
Post by Christoph Wiesen
Post by Toby Dickenson
The sftp kio uses the sftp subsystem of the ssh server. This is designed
for this purpose, but needs explicit support from the ssh server.
The fish kio is very different. It relies on the ssh providing a unix
shell, then it uploads a simple server program written in perl.
phew, learned something new here. thanks =)
Me too. Thanks Toby. I've been using fish: all along, and didn't realize
sftp: had an advantage (at least where it can be used).
--
derek
Michel D'HOOGE
2006-04-22 14:57:27 UTC
Permalink
Post by Toby Dickenson
The fish kio is very different. It relies on the ssh providing a unix shell,
then it uploads a simple server program written in perl. A beautiful hack and
handy if sftp is not available on your ssh server, but nowhere near the
performance or reliability of sftp.
From a security point of view they are equivalent; both are protected by ssh.
According to what you wrote, I would rather say "from a cryptographic point
of view". Indeed, both are equally encrypted but there could be more ("still
to be found") security holes in the perl script than in SFTP. Or can we
really rely on SSH to protect everything... I believe SFTP is harder to
"escape".
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ubuntu.com/archives/kubuntu-users/attachments/20060422/491f9afb/attachment.htm
Raphaël Pinson
2006-04-22 23:46:32 UTC
Permalink
Post by Toby Dickenson
Post by Christoph Wiesen
Post by Gabriel Dragffy
are they the same
but just written differently or what?
Exactly. fish:/ and sftp:/ are just different names for the same kio
backend (secure ftp over ssh).
Not quite....
The sftp kio uses the sftp subsystem of the ssh server. This is designed
for this purpose, but needs explicit support from the ssh server. Some ssh
servers may not support it, and some may have that subsystem disabled.
It is also true the other way : iirc you can have an ssh server allowing sftp
connection but not ssh. You will then be able to use secure ftp through ssh
on this server, even using RSA/DSA key pairs for authentication on it, but
not to log on a remote shell with ssh and execute commands.
--
Rapha?l Pinson
<***@ubuntu.com>
Ubuntu - Linux for Human Beings
http://www.ubuntulinux.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 191 bytes
Desc: not available
Url : https://lists.ubuntu.com/archives/kubuntu-users/attachments/20060422/341c837f/attachment.pgp
Loading...