Podcast Season 4 Episode 7
Podcast RSS feeds: Ogg Vorbis, MP3 and Opus.
Title: Sometimes it snows in April
In this episode: Let’s Encrypt is out of beta, the US Government will make more open source and Microsoft sues the US Government. Plus Finds and, er, more. finds?
What’s in the show:
- News:
-
Let’s Encrypt is out of beta. US Government issues draft source code policy saying all publically funded software should be FOSS. Vim 8 (sort of) has been announced. Microsoft sues US Government to be able to tell users about data requests.
-
- Finds of the Fortnight:
- Graham:
- Along with Stuart Langridge, Dave MegaSlippers, Joe Ressington, Linux Luddites and the Ubuntu Podcast, we’re going to be at FOSS Talk, Saturday 6th August 2016 in London.
- Two days left to help support qutebrowser.
- (big thanks to James for this find!) To get all the packages installed as a file:
dpkg --get-selections > /backup/installed-software.log
and then using this command to reinstall after the new distro is in place:
dpkg --set-selections < /backup/installed-software.log - Version control your configuration files with etckeeper.
- Andrew:
- HMRC's payroll submissions software will stop supporting Windows XP at the end of this year.
- The film Deep Web on Netflix is written and directed by Bill S Preston.
- Ben:
- BBC's micro:bit
- Hackerteam hacker tells all: https://ghostbin.com/paste/6kho7
- Graham:
-
If you want Mike to read out your neurons next time, email your thoughts to mike@linuxvoice.com.
-
Sorry for not having one this episode - normal service will resume next time.
Presenters: Ben Everard, Andrew Gregory, Graham Morrison and not Mike Saunders.
Download as high-quality Ogg Vorbis (35MB)
Download as low-quality MP3 (47MB)
Download the smaller yet even more awesome Opus file (15MB)
Duration: 43:54
Theme Music by Brad Sucks.
This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.
Related Posts
About The Author
Graham Morrison
A free software advocate and writer since the late 1990s, Graham is a lapsed KDE contributor and author of the Meeq MIDI step sequencer. @degville on Twitter.
When I set up Let’s Encrypt I looked a bit into how it verifies that your domain belongs to your server. As I understand it it works something like this:
– example.com points to your server. You run the letsencrypt client on that server, and tell it you’d like a certificate for example.com
– letsencrypt starts an authentication service on your web server, then tells the letsencrypt.org server that it’s requesting a certificate for example.com on the server it’s calling from
– letsencrypt.org calls to the authentication service on the server that example.com points to, and verifies that it’s the same server the request came from (I’m guessing there’s some clever crypto here so it’s not easily spoofable).
– If it checks out, it issues the certificate and sends it to the client, then the client shuts down the authentication service.
Thanks for the details. IIRC, this is why you have to stop your web server to run the client — Lets encrypt runs on port 80 to verify that you really have control of the server.