Content-type: text/plain; charset=iso-8859-1
From: Timm Murray <hardburn@runbox.com>
To: gopher@complete.org
Subject: [gopher] Re: Uploading
Date: Wed, 9 Oct 2002 17:03:49 -0500
References: <200210091223.FAA28328@stockholm.ptloma.edu>
In-Reply-To: <200210091223.FAA28328@stockholm.ptloma.edu>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Message-Id: <200210091703.53365.hardburn@runbox.com>
Sender: gopher-bounce@complete.org
Errors-to: gopher-bounce@complete.org
Precedence: bulk
Reply-to: gopher@complete.org


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wednesday 09 October 2002 07:23, Cameron Kaiser wrote:
> > Are there any current standards for uploading via Gopher?  I'm working on
> > a new Gopher server and I'd like to have a nice, easy Perl command line
> > program for uploading new content, but many of the protocols used just
> > aren't good enough.  FTP opens a big security risk, TFTP is too
> > primitive, and SCP's Perl module doesn't support password authentication.
> >  Gopher upload would make everything integrate nicely.
>
> I don't think any clients support it, but theoretically, you could do this
> using ASK protocol over Gopher+. The thing is, you would need to roll your
> own app, but that shouldn't be very difficult.

Ahh, I forgot about ASK.  Yes, ASK would work perfectly with SRP 
authentication (RFC 2945).  Which I find greatly ironic--not long ago, I was 
trying to implement SRP over HTTP and kept hitting the wall of trying to keep 
stateful information.  ASK should nicely circumvent that problem.

Thanks for reminding me :)

- -- 
There should be an old-fasioned platform game starring Tux . . . and 
you hit the CD to toss Bill Gates into the lava and then see a little 
picture of RMS that says "Thanks for saving me Tux, but Linus Torvalds 
is in another castle!"
		--Seen on irc.openprojects.net, #debian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iEYEARECAAYFAj2kp8gACgkQqpueKcacfLQc7wCglLOOtoRbLYWZ6e/AE3nCUBUd
hGQAoKrOfCq1IkGNpQnCxfhw3M4SwJPv
=tZmG
-----END PGP SIGNATURE-----