From 0bde2103000edb70a69d02e1f35f9b910dfb3178 Mon Sep 17 00:00:00 2001 From: "Eric S. Raymond" Date: Wed, 25 Jun 1997 15:00:40 +0000 Subject: Added Charlie Brady's SSH recipe. svn path=/trunk/; revision=1117 --- fetchmail-FAQ.html | 60 +++++++++++++++++++++++++++++++++++++++++++++++++++--- 1 file changed, 57 insertions(+), 3 deletions(-) diff --git a/fetchmail-FAQ.html b/fetchmail-FAQ.html index cd9d94c9..fbe41f07 100644 --- a/fetchmail-FAQ.html +++ b/fetchmail-FAQ.html @@ -9,7 +9,7 @@

Frequently Asked Questions About Fetchmail

-The current version of fetchmail is 3.9.8.

+The current version of fetchmail is 3.9.9.

Before reporting any bug, please read G3 for advice on how to include diagnostic information that will get your bug fixed @@ -466,7 +466,10 @@ would work. To range over any value of the last two octets

C4. How can I get fetchmail to work with ssh?

-This is a lightly edited version of a recipe from Masafumi NAKANE.

+We have two recipes for this. The first is a little easier to set up, +but only supports one user at a time.

+ +First, a lightly edited version of a recipe from Masafumi NAKANE:

1. You must have ssh (the ssh client) on the local host and sshd (ssh server) on the remote mail server. And, you have to configure ssh so @@ -501,6 +504,57 @@ preconnect "ssh -f -L 1234:mailhost:110 sshdhost sleep 20 /dev/null" You can work this trick with IMAP too, but the port number 110 in the above would need to become 143.

+Second, a recipe frm Charlie Brady <cbrady@ind.tansu.com.au>. + +Charlie says: "The [previous] recipe certainly works, but +the solution I post here is better in a few respects": + +

this method will not fail if two or more users attempt to use fetchmail + simultaneously. +
you are able to use the full facilities of tcpd to control access +
this method does not depend on the preconnect feature of fetchmail, so + can be used for tunneling of other services as well. +

+ +Here are the steps: + +

+Make sure that the "socket" program is installed on the server machine. +
+Set up an unprivileged account on your system with a .ssh directory +containing an SSH identity file "identity" with no pass phrase, +"identity.pub" and "known_hosts" containing the host key of your +mailhost. Let's call this account "noddy". +
+On mailhost, set up no-password access for noddy@yourhost. Add to your +SSH authorised_keys file: + +
```
+command="socket localhost 110",no-port-forwarding 1024 ......
+
```
+ +where "1024 ......" is the content of noddy's identity.pub file. +

+Create a script /usr/local/bin/ssh.fm and make it executable: + +

+#! /bin/sh
+exec ssh -q -C -l your.login.id -e none mailhost socket localhost 110
+

+Add an entry in inetd.conf for whatever port you choose to use - say: + +
```
+1234 stream tcp nowait noddy /usr/sbin/tcpd /usr/local/bin/ssh.fm
+
```
+
+Send a HUP signal to your inetd. +

+ +Now just use localhost:1234 to access your POP server.

C5. How can I set up support for sendmail's anti-spam 571 response?

@@ -1059,7 +1113,7 @@ biff n to solve theproblem system-wide. -$Id: fetchmail-FAQ.html,v 1.37 1997/06/24 16:12:12 esr Exp $

+$Id: fetchmail-FAQ.html,v 1.38 1997/06/25 15:00:40 esr Exp $

Eric S. Raymond <esr@snark.thyrsus.com>

-- cgit v1.2.3