From: "Richard Fish" <bigfish@asmallpond.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] ssh2 and xover LAN
Date: Thu, 6 Apr 2006 09:28:03 -0700 [thread overview]
Message-ID: <7573e9640604060928n7d0eb4f3w6e1da48c6440d6ef@mail.gmail.com> (raw)
In-Reply-To: <20060406155414.47216.qmail@web31702.mail.mud.yahoo.com>
Answers are out of order...as they will make more sense that way...
On 4/6/06, maxim wexler <blissfix@yahoo.com> wrote:
> And what's this all got to do with ftp?
Nothing at all. But you were not running an ftp _server_ on the
machine you were trying to connect to. I think it has already been
answered that the 'ftp' command is a client, and needs a server to
connect to.
So on the other machine, you need a server. There are several in
portage: net-ftp/ftpd, net-ftp/proftpd are probaby the most popular,
and thus if you have problems or questions the most likely that people
will be able to help you with.
If the default configuration of the ftp server doesn't work for your
needs however, you will need to reconfigure it. This is no more
difficult than other servers, but will require reading some
documentation, howto's, etc.
However ssh is quite a bit easier, because the default configuration
is quite usable for most tasks. You still need a server on the other
machine (the commands 'ssh' and 'scp' are clients), but that just
means merging openssh there as well, and running '/etc/init.d/sshd
start'.
> But what's this bit at the end of the console o/p:
>
> <snip>
> >>> /usr/share/openssh/Ssh.bin
> * Remember to merge your config files in /etc/ssh/
> and then
> * restart sshd: '/etc/init.d/sshd restart'.
This will be necessary on the server machine to restart the ssh server
in the case where it already exists.
> * As of version 3.4 the default is to enable the
> UsePrivelegeSeparation
You can ignore the rest of this output if you use the default
configuration files. Actually, since you don't care about security
here at all, you can ignore it completely.
-Richard
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-04-06 16:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-01 18:53 [gentoo-user] ssh2 and xover LAN maxim wexler
2006-04-01 21:17 ` Bryan Whitehead
2006-04-01 21:37 ` Matt Richards
2006-04-01 21:44 ` Bryan Whitehead
2006-04-01 21:55 ` Matt Richards
2006-04-02 13:46 ` Mick
2006-04-03 15:44 ` maxim wexler
2006-04-03 16:07 ` Hans-Werner Hilse
2006-04-05 22:52 ` maxim wexler
2006-04-05 23:18 ` Richard Fish
2006-04-06 15:54 ` maxim wexler
2006-04-06 16:28 ` Richard Fish [this message]
2006-04-05 23:18 ` Neil Bothwick
2006-04-04 22:09 ` Mick
2006-04-03 0:02 ` maxim wexler
2006-04-03 6:22 ` Alexander Skwar
2006-04-03 16:13 ` maxim wexler
2006-04-03 7:48 ` Nick Rout
2006-04-03 15:58 ` maxim wexler
2006-04-03 16:11 ` Mike Williams
2006-04-05 23:17 ` maxim wexler
2006-04-06 0:05 ` Richard Fish
2006-04-06 5:44 ` Alexander Skwar
2006-04-06 17:05 ` maxim wexler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7573e9640604060928n7d0eb4f3w6e1da48c6440d6ef@mail.gmail.com \
--to=bigfish@asmallpond.org \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox