<div dir="ltr">I actually quite like this idea to start with :)<div><br></div><div>cheers</div><div>James</div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><span style="border-collapse:collapse;color:rgb(136,136,136);font-size:13px"><br><font face="arial, sans-serif">James Mills / prologic</font><br><br><font face="arial, sans-serif"></font><font face="'courier new', monospace">E: <a href="mailto:prologic@shortcircuit.net.au" style="color:rgb(0,0,204)" target="_blank">prologic@shortcircuit.net.au</a></font></span><div><span style="font-family:'courier new',monospace;color:rgb(136,136,136);font-size:13px">W: </span><a href="http://prologic.shortcircuit.net.au" style="font-family:'courier new',monospace;font-size:13px;color:rgb(0,0,204)" target="_blank">prologic.shortcircuit.net.au</a><br></div></div></div>
<br><div class="gmail_quote">On Fri, Apr 24, 2015 at 5:18 AM, <span dir="ltr"><<a href="mailto:simple@sdf.org" target="_blank">simple@sdf.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">New thread for an important topic :)<br>
<br>
Looking in my OS's /etc/services file it appears there are several<br>
available ports in the 700-799 range:<br>
<br>
# 703 Unassigned<br>
# 708 Unassigned<br>
# 717-728 Unassigned<br>
# 703 Unassigned<br>
# 708 Unassigned<br>
# 717-728 Unassigned<br>
# 732-740 Unassigned<br>
# 743 Unassigned<br>
# 745-746 Unassigned<br>
# 755-756 Unassigned<br>
# 766 Unassigned<br>
# 768 Unassigned<br>
# 778-779 Unassigned<br>
# 781-785 Unassigned<br>
# 786 Unassigned<br>
# 787 Unassigned<br>
# 788-799 Unassigned<br>
<br>
As for implementation of the concept, I feel it should be done in a way<br>
that doesn't shut out existing gopher clients/servers.<br>
<br>
Perhaps adopting some sort of external client+server proxy model would be<br>
the best starting point such that, for example, someone with a lynx(1)<br>
browser could install a "secure_gopher" proxy on their computer such that<br>
their now local port 70 requests are SSL-wrapped and sent on to a<br>
corresponding "secure_gopher" proxy server listening on the new gopherS<br>
TLS encrypted port (785 maybe?). Probably it's already doable using<br>
opensshd and SOCKS, just need to pick a port.<br>
<br>
The above approach would not preclude others from basically incorporating<br>
the proxy model into their new clients and servers for an all-in-one<br>
solution.<br>
<br>
For making it officially part of Gopher World I think it means a new RFC<br>
for "secure gopher" or at least adding the spec to the existing gopher<br>
RFC; I don't know which would be easier.<br>
<br>
Jeff / gopher://<a href="http://jgw.mdns.org" target="_blank">jgw.mdns.org</a><br>
<br>
_______________________________________________<br>
Gopher-Project mailing list<br>
<a href="mailto:Gopher-Project@lists.alioth.debian.org">Gopher-Project@lists.alioth.debian.org</a><br>
<a href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project" target="_blank">http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project</a><br>
</blockquote></div><br></div>