Oh nice! I'll make https://github.com/prologic/go-gopher support this! That also means https://github.com/prologic/gopherproxy and https://github.com/prologic/gopherclient (which I want to port to Electron)
James Mills / prologic
E: prologic@shortcircuit.net.auOn Sun, Sep 17, 2017 at 12:01 AM, Kim Holviala <kim@holviala.com> wrote: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.- KimOn 17 Sep 2017, at 03:59, James Mills <prologic@shortcircuit.net.au> wrote:Wait.... There are gopher TLS holes? Did we decide on how this works already?cheersJames_______________________________________________
James Mills / prologic
E: prologic@shortcircuit.net.auOn Sat, Sep 16, 2017 at 3:01 PM, Mr. Leveck <leveck@leveck.us> wrote:Out of curiosity what clients properly handle gophers:// ?
I will have some spare time coming up next week... looks like I will be getting a cert. Maybe gopher.leveck.us (yeah, all my subdomains point to the same DSL router) will be the second TLS gopher site.
--
Leveck
16. Sep 2017 10:15 by kim@holviala.com: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://gophernicus.org:7070/) runs on a free Let's Encrypt certificate.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.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.- KimOn 16 Sep 2017, at 19:08, Mr. Leveck <leveck@leveck.us> wrote: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..._______________________________________________
Is renewing the LE cert scriptable or is this just something that will need a calendar entry and a reminder?
--
Leveck
16. Sep 2017 02:38 by irl@fsfe.org:Hi,
On 16/09/17 05:47, Stephen Kellat wrote:RFC 4217 comes to mind at this point & I wonder if letsencrypt.org supports that perchance.
By putting some records into the DNS, yes it is possible to have a cert
issued for a domain name that will then work for any service, including
FTPS or even some form of Gopher/TLS if such a thing exists.
Personally I've used the certs for mail servers, FTP servers, XMPP
servers as well as many many web servers.
Thanks,
Iain.
_______________________________________________
Gopher-Project mailing list
Gopher-Project@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project
Gopher-Project mailing list
Gopher-Project@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project
_______________________________________________
Gopher-Project mailing list
Gopher-Project@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project
Gopher-Project mailing list
Gopher-Project@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project
_______________________________________________
Gopher-Project mailing list
Gopher-Project@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project
_______________________________________________ Gopher-Project mailing list Gopher-Project@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project