From: "Gopher-Project" <gopher-project-bounces+rachael=telefisk.org@lists.alioth.debian.org> Date: Mon Feb 6 00:34:13 2017 Subject: Re: [gopher] Gophernicus 2.4 "Millennium Edition" released --===============5329436748256152650== Content-Type: multipart/alternative; boundary=94eb2c19bee05b08a50547d0f240 --94eb2c19bee05b08a50547d0f240 Content-Type: text/plain; charset=UTF-8 Can we just assume TLS if the destination port in the menu is 73 for example? James Mills / prologic E: prologic@shortcircuit.net.au W: prologic.shortcircuit.net.au On Sun, Feb 5, 2017 at 2:16 AM, Kim Holviala <kim@holviala.com> wrote: > > > On 04 Feb 2017, at 12:11, Cameron Kaiser <spectre@floodgap.com> wrote: > > > >> The only remaining problem is to figure out a way to tell which > connections > >> are TLS and which are plaintext in gopher menus. Alternative is not to > >> change menus at all and require the clients to read caps.txt first to > see > >> if there is a non-zero ServerTLSPort available for encrypted > connections. > >> That might actually be the most backwards-compatible method. > > > > That would certainly seem the most reasonable approach to me. > > I agree. I tried to come up with a way to add some kind of "encrypted or > not" flag in the menus... but the existing servers and clients out there > are *so* broken that I couldn't come up with a way that would not break > things. > > Oh well. Some day I'll try to patch Lynx or something to work with gopher > over TLS. > > > > - Kim > _______________________________________________ > Gopher-Project mailing list > Gopher-Project@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project > --94eb2c19bee05b08a50547d0f240 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">Can we just assume TLS if the destination port in the menu= is 73 for example?</div><div class=3D"gmail_extra"><br clear=3D"all"><div>= <div class=3D"gmail_signature" data-smartmail=3D"gmail_signature"><span sty= le=3D"border-collapse:collapse;color:rgb(136,136,136);font-size:13px"><br><= font face=3D"arial, sans-serif">James Mills / prologic</font><br><br><font = face=3D"arial, sans-serif"></font><font face=3D"'courier new', mono= space">E:=C2=A0<a href=3D"mailto:prologic@shortcircuit.net.au" style=3D"col= or:rgb(0,0,204)" target=3D"_blank">prologic@shortcircuit.net.au</a></font><= /span><div><span style=3D"font-family:'courier new',monospace;color= :rgb(136,136,136);font-size:13px">W:=C2=A0</span><a href=3D"http://prologic= .shortcircuit.net.au" style=3D"font-family:'courier new',monospace;= font-size:13px;color:rgb(0,0,204)" target=3D"_blank">prologic.shortcircuit.= net.au</a><br></div></div></div> <br><div class=3D"gmail_quote">On Sun, Feb 5, 2017 at 2:16 AM, Kim Holviala= <span dir=3D"ltr"><<a href=3D"mailto:kim@holviala.com" target=3D"_blank= ">kim@holviala.com</a>></span> wrote:<br><blockquote class=3D"gmail_quot= e" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">= <span class=3D""><br> > On 04 Feb 2017, at 12:11, Cameron Kaiser <<a href=3D"mailto:spectre= @floodgap.com">spectre@floodgap.com</a>> wrote:<br> ><br> >> The only remaining problem is to figure out a way to tell which co= nnections<br> >> are TLS and which are plaintext in gopher menus. Alternative is no= t to<br> >> change menus at all and require the clients to read caps.txt first= to see<br> >> if there is a non-zero ServerTLSPort available for encrypted conne= ctions.<br> >> That might actually be the most backwards-compatible method.<br> ><br> > That would certainly seem the most reasonable approach to me.<br> <br> </span>I agree. I tried to come up with a way to add some kind of "enc= rypted or not" flag in the menus... but the existing servers and clien= ts out there are *so* broken that I couldn't come up with a way that wo= uld not break things.<br> <br> Oh well. Some day I'll try to patch Lynx or something to work with goph= er over TLS.<br> <span class=3D"HOEnZb"><font color=3D"#888888"><br> <br> <br> - Kim<br> </font></span><div class=3D"HOEnZb"><div class=3D"h5">_____________________= _________<wbr>_________________<br> Gopher-Project mailing list<br> <a href=3D"mailto:Gopher-Project@lists.alioth.debian.org">Gopher-Project@li= sts.alioth.<wbr>debian.org</a><br> <a href=3D"http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-p= roject" rel=3D"noreferrer" target=3D"_blank">http://lists.alioth.debian.<wb= r>org/cgi-bin/mailman/listinfo/<wbr>gopher-project</a><br> </div></div></blockquote></div><br></div> --94eb2c19bee05b08a50547d0f240-- --===============5329436748256152650== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Gopher-Project mailing list Gopher-Project@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project --===============5329436748256152650==-- Thread start (DIR) [gopher] Gophernicus 2.4 "Millennium Edition" released (DIR) Followup: Re: [gopher] Gophernicus 2.4 "Millennium Edition" released