<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">We didn't decide... so I just did straight up gopher-over-TLS (no STARTLS though) running on randomly chosen port 7070. And as far as I know there are no clients which would support the gophers// protocol.</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">- Kim</div><div class=""><br class=""></div><div class=""><br class=""></div><br class=""><div><blockquote type="cite" class=""><div class="">On 17 Sep 2017, at 03:59, James Mills <<a href="mailto:prologic@shortcircuit.net.au" class="">prologic@shortcircuit.net.au</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Wait.... There are gopher TLS holes? Did we decide on how this works already?<div class=""><br class=""></div><div class="">cheers</div><div class="">James</div></div><div class="gmail_extra"><br clear="all" class=""><div class=""><div class="gmail_signature" data-smartmail="gmail_signature"><span style="border-collapse:collapse;color:rgb(136,136,136);font-size:13px" class=""><br class=""><font face="arial, sans-serif" class="">James Mills / prologic</font><br class=""><br class=""><font face="arial, sans-serif" class=""></font><font face="'courier new', monospace" class="">E: <a href="mailto:prologic@shortcircuit.net.au" style="color:rgb(0,0,204)" target="_blank" class="">prologic@shortcircuit.net.au</a></font></span><div class=""><span style="font-family:'courier new',monospace;color:rgb(136,136,136);font-size:13px" class="">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" class="">prologic.shortcircuit.net.au</a><br class=""></div></div></div>
<br class=""><div class="gmail_quote">On Sat, Sep 16, 2017 at 3:01 PM, Mr. Leveck <span dir="ltr" class=""><<a href="mailto:leveck@leveck.us" target="_blank" class="">leveck@leveck.us</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="">
Out of curiosity what clients properly handle gophers:// ?<br class=""><br class="">I will have some spare time coming up next week... looks like I will be getting a cert. Maybe <a href="http://gopher.leveck.us/" target="_blank" class="">gopher.leveck.us</a> (yeah, all my subdomains point to the same DSL router) will be the second TLS gopher site.<span class="HOEnZb"><font color="#888888" class=""><br class="">
--
<br class="">Leveck<br class=""><br class="">16. Sep 2017 10:15 by <a href="mailto:kim@holviala.com" rel="noopener noreferrer" target="_blank" class="">kim@holviala.com</a>:</font></span><div class=""><div class="h5"><br class=""><br class=""><blockquote class="m_4491657073125482669tutanota_quote" style="border-left:1px solid #93a3b8;padding-left:10px;margin-left:5px"><div class="">Not even going offtopic since Gophernicus - The Most Awesome(tm) gopher server \o/ - actually supports TLS and the only existing TLS-enabled gopher server (gophers://<a href="http://gophernicus.org:7070/" target="_blank" class="">gophernicus.org:<wbr class="">7070/</a>) runs on a free Let's Encrypt certificate.</div><div class=""><br class=""></div><div class="">I was really against the whole thing until start of this year when my existing certs were due to renewal. So being slightly autistic I wrote down the steps to renew a cert between the traditional way vs. up and coming Let's Encrypt that I hated. </div><div class=""><br class=""></div><div class="">That was not even a competition... and yes, it's fully scritable - I've got a simple bash script running form /etc/cron.monthly/ to renew the cert every two months (they're valid for three). As long as Let's Encrypt is operational I never ever have to do anything to renew. Nada.</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">- Kim</div><div class=""><br class=""></div><br class=""><div class=""><blockquote class="m_4491657073125482669thunderbird_quote" style="border-left:1px solid #93a3b8;padding-left:10px;margin-left:5px"><div class="">On 16 Sep 2017, at 19:08, Mr. Leveck <<a href="mailto:leveck@leveck.us" rel="noopener noreferrer" target="_blank" class="">leveck@leveck.us</a>> wrote:</div><br class="m_4491657073125482669Apple-interchange-newline"><div class="">
<div class="">
I have looked at Let's Encrypt in the past. There is quite a bit of smack talk floating around vis-a-vis this service particularly because it is free. Every single free cert I have seen in the last 20 years eventually shut down due to misuse by idiots. I guess I'll grab one while it is still around...<br class=""><br class="">Is renewing the LE cert scriptable or is this just something that will need a calendar entry and a reminder?<br class=""><br class="">
--
<br class="">Leveck<br class=""><br class="">16. Sep 2017 02:38 by <a href="mailto:irl@fsfe.org" rel="noopener noreferrer" target="_blank" class="">irl@fsfe.org</a>:<br class=""><br class=""><blockquote class="m_4491657073125482669tutanota_quote" style="border-left:1px solid #93a3b8;padding-left:10px;margin-left:5px">Hi,<br class=""><br class="">On 16/09/17 05:47, Stephen Kellat wrote:<blockquote class="">RFC 4217 comes to mind at this point & I wonder if <a href="http://letsencrypt.org/" rel="noopener noreferrer" target="_blank" class="">letsencrypt.org</a> supports that perchance.</blockquote><br class="">By putting some records into the DNS, yes it is possible to have a cert<br class="">issued for a domain name that will then work for any service, including<br class="">FTPS or even some form of Gopher/TLS if such a thing exists.<br class=""><br class="">Personally I've used the certs for mail servers, FTP servers, XMPP<br class="">servers as well as many many web servers.<br class=""><br class="">Thanks,<br class="">Iain.<br class=""><br class="">______________________________<wbr class="">_________________<br class="">Gopher-Project mailing list<br class=""><a href="mailto:Gopher-Project@lists.alioth.debian.org" rel="noopener noreferrer" target="_blank" class="">Gopher-Project@lists.alioth.<wbr class="">debian.org</a><br class=""><a href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project" rel="noopener noreferrer" target="_blank" class="">http://lists.alioth.debian.<wbr class="">org/cgi-bin/mailman/listinfo/<wbr class="">gopher-project</a></blockquote> </div>
______________________________<wbr class="">_________________<br class="">Gopher-Project mailing list<br class=""><a href="mailto:Gopher-Project@lists.alioth.debian.org" rel="noopener noreferrer" target="_blank" class="">Gopher-Project@lists.alioth.<wbr class="">debian.org</a><br class=""><a href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project" rel="noopener noreferrer" target="_blank" class="">http://lists.alioth.debian.<wbr class="">org/cgi-bin/mailman/listinfo/<wbr class="">gopher-project</a></div></blockquote></div><br class=""></blockquote> </div></div></div>
<br class="">______________________________<wbr class="">_________________<br class="">
Gopher-Project mailing list<br class="">
<a href="mailto:Gopher-Project@lists.alioth.debian.org" class="">Gopher-Project@lists.alioth.<wbr class="">debian.org</a><br class="">
<a href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project" rel="noreferrer" target="_blank" class="">http://lists.alioth.debian.<wbr class="">org/cgi-bin/mailman/listinfo/<wbr class="">gopher-project</a><br class=""></blockquote></div><br class=""></div>
_______________________________________________<br class="">Gopher-Project mailing list<br class=""><a href="mailto:Gopher-Project@lists.alioth.debian.org" class="">Gopher-Project@lists.alioth.debian.org</a><br class="">http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project</div></blockquote></div><br class=""></body></html>