<?xml version="1.0"?>
<!DOCTYPE wml PUBLIC "-//WAPFORUM//DTD WML 1.1//EN"
"http://www.wapforum.org/DTD/wml_1.1.xml">
<wml>
<card id="index" title="Text File" newcontext="true">
<p>
Received: with ECARTIS (v1.0.0; list gopher);
 Fri, 16 Jun 2006 11:15:39 -0500 (CDT)
Received: from sccrmhc14.comcast.net ([63.240.77.84])
	by glockenspiel.complete.org with esmtp
	(Exim 4.50)
	id 1FrGyu-0003Hq-0t
	for gopher@complete.org; Fri, 16 Jun 2006 11:15:39 -0500
Received: from tower (c-24-19-62-97.hsd1.wa.comcast.net[24.19.62.97])
          by comcast.net (sccrmhc14) with SMTP
          id &lt;2006061616150101400atmqve&gt;; Fri, 16 Jun 2006 16:15:01 +0000
From: &quot;Andrew Mahan&quot; &lt;mahanam@comcast.net&gt;
To: &lt;gopher@complete.org&gt;
Subject: [gopher] Re: RFC drafts
Date: Fri, 16 Jun 2006 09:14:59 -0700
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1807
thread-index: AcaRL0cp7RigSyWOTEGug3OTjurkwgAMJwvQ
In-Reply-To: &lt;449284AB.5050700@route-add.net&gt;
X-Spam-Status: No (score 0.4): AWL=0.426
X-Virus-Scanned: by Exiscan on glockenspiel.complete.org at Fri,
 16 Jun 2006 11:15:39 -0500
X-archive-position: 1316
X-ecartis-version: Ecartis v1.0.0
Sender: gopher-bounce@complete.org
Errors-to: gopher-bounce@complete.org
X-original-sender: mahanam@comcast.net
Precedence: bulk
Reply-to: gopher@complete.org
List-help: &lt;mailto:ecartis@complete.org?Subject=help&gt;
List-unsubscribe: &lt;mailto:gopher-request@complete.org?Subject=unsubscribe&gt;
List-software: Ecartis version 1.0.0
List-Id: Gopher &lt;gopher.complete.org&gt;
X-List-ID: Gopher &lt;gopher.complete.org&gt;
List-subscribe: &lt;mailto:gopher-request@complete.org?Subject=subscribe&gt;
List-owner: &lt;mailto:jgoerzen@complete.org&gt;
List-post: &lt;mailto:gopher@complete.org&gt;
List-archive: &lt;http://www.complete.org/mailinglists/archives/&gt;
X-list: gopher
</p>
<p>when running sftp usually the standard ssh port (22) is used from my
understanding
-----Original Message-----
From: gopher-bounce@complete.org [mailto:gopher-bounce@complete.org] On
Behalf Of Alessandro Selli
Sent: Friday, June 16, 2006 3:15 AM
To: gopher@complete.org
Subject: [gopher] Re: RFC drafts
</p>
<p>Andrew Mahan wrote:
&gt; or SSH-2?  Kinda like SFTP works
</p>
<p>   My /etc/services file tells me sftp uses port 115 tcp/udp.
</p>
<p></p>
<p>&gt; -----Original Message-----
&gt; From: gopher-bounce@complete.org [mailto:gopher-bounce@complete.org] On
&gt; Behalf Of Alessandro Selli
&gt; Sent: Friday, June 02, 2006 11:09 AM
&gt; To: gopher@complete.org
&gt; Subject: [gopher] Re: RFC drafts
&gt;
&gt; Benn Newman wrote:
&gt;&gt; On Fri, Jun 02, 2006 at 11:21:01AM -0400, Trevor wrote:
&gt;&gt;
&gt;&gt;&gt; this intrigues me.
&gt;&gt;&gt;
&gt;&gt;&gt; (sorry i don&#x27;t look familiar. been lurking the last couple of years.)
&gt;&gt;&gt;
&gt;&gt;&gt; one downfall, i feel, with gopher is it is clear text. has anyone
thought
&gt;
&gt;&gt;&gt; about, besides me, an sGopher protocol? i think gopher would get more
&gt;&gt;&gt; mainstream use if it had security built into it. many companies refuse
to
&gt;
&gt;&gt;&gt; use anything that sends clear text over a wire. just a thought.
&gt;&gt;&gt;
&gt;&gt; Gopher over SSL/TLS (from my understanding) is easy and already possible.
&gt;&gt; You can use something like stunnel (on the server) and socat (on the
&gt; client)
&gt;&gt;
&gt;   I agree.  Only, you will have to use a non-standard port where the
&gt; SSL-gopher server
&gt; will listen to, since there is no IANA-assigned &quot;gophers&quot; port like
&gt; there is a &quot;https&quot; port
&gt; (443 tcp).
&gt;
&gt;
</p>
<p>--
Alessandro Selli
Tel: 340.839.73.05
http://alessandro.route-add.net
</p>
<p></p>
<p></p>
<p></p>
</card>
</wml>
