Date: Mon, 22 Jul 2002 22:57:09 -0500
From: John Goerzen <jgoerzen@complete.org>
To: gopher@complete.org
Subject: [gopher] Re: [Bug 71916] security problem with gopher and arbitary
 ports
Message-ID: <20020723035709.GC23369@complete.org>
References: <200207222335.g6MNZvl09279@mothra.mozilla.org>
 <20020723010900.GA27682@complete.org>
 <1027387505.16207.19.camel@transa.aquarius.null>
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1027387505.16207.19.camel@transa.aquarius.null>
User-Agent: Mutt/1.4i
Content-Transfer-Encoding: 8bit
Sender: gopher-bounce@complete.org
Errors-to: gopher-bounce@complete.org
Precedence: bulk
Reply-to: gopher@complete.org


On Mon, Jul 22, 2002 at 08:25:05PM -0500, Aaron J. Angel wrote:

I think you may have missed some of the sarcasm and rhetorical questions in
my message, so I'll just omit replies to those...

> The point was Gopher URLs and (ab)using the Gopher protocol can be used
> to simulate virtually any protocol, including SMTP (read down a little
> further on the comments, there's an example with SMTP).

It's pretty trivial to do that with IMAP too, since "GET " forms the
beginning of any IMAP command.

> I think I'll go check up on bug reports, and see if one hasn't already
> been submitted regarding the buggy Gopher URL bugfix.

Good idea.

-- John

-- 
John Goerzen <jgoerzen@complete.org>    GPG: 0x8A1D9A1F    www.complete.org