<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" encoding="UTF-8" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/" xmlns:atom="http://www.w3.org/2005/Atom/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:googleplay="http://www.google.com/schemas/play-podcasts/1.0" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:fireside="http://fireside.fm/modules/rss/fireside">
  <channel>
    <fireside:hostname>web02.fireside.fm</fireside:hostname>
    <fireside:genDate>Thu, 05 Mar 2026 20:19:38 -0600</fireside:genDate>
    <generator>Fireside (https://fireside.fm)</generator>
    <title>BSD Now - Episodes Tagged with “Ezjail”</title>
    <link>https://www.bsdnow.tv/tags/ezjail</link>
    <pubDate>Thu, 11 Apr 2019 12:00:00 -0400</pubDate>
    <description>Created by three guys who love BSD, we cover the latest news and have an extensive series of tutorials, as well as interviews with various people from all areas of the BSD community. It also serves as a platform for support and questions. We love and advocate FreeBSD, OpenBSD, NetBSD, DragonFlyBSD and TrueOS. Our show aims to be helpful and informative for new users that want to learn about them, but still be entertaining for the people who are already pros.
The show airs on Wednesdays at 2:00PM (US Eastern time) and the edited version is usually up the following day. 
</description>
    <language>en-us</language>
    <itunes:type>episodic</itunes:type>
    <itunes:subtitle>A weekly podcast and the place to B...SD</itunes:subtitle>
    <itunes:author>JT Pennington</itunes:author>
    <itunes:summary>Created by three guys who love BSD, we cover the latest news and have an extensive series of tutorials, as well as interviews with various people from all areas of the BSD community. It also serves as a platform for support and questions. We love and advocate FreeBSD, OpenBSD, NetBSD, DragonFlyBSD and TrueOS. Our show aims to be helpful and informative for new users that want to learn about them, but still be entertaining for the people who are already pros.
The show airs on Wednesdays at 2:00PM (US Eastern time) and the edited version is usually up the following day. 
</itunes:summary>
    <itunes:image href="https://media24.fireside.fm/file/fireside-images-2024/podcasts/images/c/c91b88f1-e824-4815-bcb8-5227818d6010/cover.jpg?v=4"/>
    <itunes:explicit>no</itunes:explicit>
    <itunes:keywords>berkeley,freebsd,openbsd,netbsd,dragonflybsd,trueos,trident,hardenedbsd,tutorial,howto,guide,bsd,interview</itunes:keywords>
    <itunes:owner>
      <itunes:name>JT Pennington</itunes:name>
      <itunes:email>feedback@bsdnow.tv</itunes:email>
    </itunes:owner>
<itunes:category text="News">
  <itunes:category text="Tech News"/>
</itunes:category>
<itunes:category text="Education">
  <itunes:category text="How To"/>
</itunes:category>
<item>
  <title>293: Booking Jails</title>
  <link>https://www.bsdnow.tv/293</link>
  <guid isPermaLink="false">ca87df46-31a6-4c71-883e-e34d10e4fd2d</guid>
  <pubDate>Thu, 11 Apr 2019 12:00:00 -0400</pubDate>
  <author>JT Pennington</author>
  <enclosure url="https://aphid.fireside.fm/d/1437767933/c91b88f1-e824-4815-bcb8-5227818d6010/ca87df46-31a6-4c71-883e-e34d10e4fd2d.mp3" length="46528143" type="audio/mp3"/>
  <itunes:episodeType>full</itunes:episodeType>
  <itunes:author>JT Pennington</itunes:author>
  <itunes:subtitle>This week we have a special episode with a Michael W. Lucas interview about his latest jail book that’s been released. We’re talking all things jails, writing, book sponsoring, the upcoming BSDCan 2019 conference, and more.</itunes:subtitle>
  <itunes:duration>1:16:41</itunes:duration>
  <itunes:explicit>no</itunes:explicit>
  <itunes:image href="https://media24.fireside.fm/file/fireside-images-2024/podcasts/images/c/c91b88f1-e824-4815-bcb8-5227818d6010/cover.jpg?v=4"/>
  <description>This week we have a special episode with a Michael W. Lucas interview about his latest jail book that’s been released. We’re talking all things jails, writing, book sponsoring, the upcoming BSDCan 2019 conference, and more.
&lt;p&gt;###Interview - Michael W. Lucas  - &lt;a href="mailto:mwl@mwl.io"&gt;mwl@mwl.io&lt;/a&gt; / &lt;a href="https://twitter.com/mwlauthor"&gt;@mwlauthor&lt;/a&gt;&lt;br&gt;
FreeBSD Mastery: Jails&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;BR: Welcome back to the show and congratulations on your latest book. How many books did you have to write before you could start on FreeBSD Mastery: Jails?&lt;/li&gt;
&lt;li&gt;AJ: How much research did you have to do about jails?&lt;/li&gt;
&lt;li&gt;BR: The book talks about something called ‘incomplete’ jails. What do you mean by that?&lt;/li&gt;
&lt;li&gt;AJ: There are a lot of jail management frameworks out there. Why did you chose to write about iocage in the book?&lt;/li&gt;
&lt;li&gt;BR: How many jails do you run yourself?&lt;/li&gt;
&lt;li&gt;AJ: Can you tell us a bit about how you handle book sponsorship these days?&lt;/li&gt;
&lt;li&gt;BR: What other books (fiction and non-fiction) are you currently working on?&lt;/li&gt;
&lt;li&gt;AJ: Which talks are you looking forward to attend at the upcoming BSDCan conference?&lt;/li&gt;
&lt;li&gt;BR: How is the BSD user group going?&lt;/li&gt;
&lt;li&gt;AJ: Anything else you’d like to mention before we release you from our interview jail cell?&lt;/li&gt;
&lt;/ul&gt;
&lt;hr&gt;
&lt;ul&gt;
&lt;li&gt;Send questions, comments, show ideas/topics, or stories you want mentioned on the show to &lt;a href="mailto:feedback@bsdnow.tv"&gt;feedback@bsdnow.tv&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;hr&gt;

    
    Your browser does not support the HTML5 video tag.

</description>
  <itunes:keywords>freebsd, openbsd, netbsd, dragonflybsd, trueos, trident, hardenedbsd, tutorial, howto, guide, bsd, interview, jails, iocage, ezjail, books, sudo, bsdcan, gelato, writing, sponsoring, user group</itunes:keywords>
  <content:encoded>
    <![CDATA[<p>This week we have a special episode with a Michael W. Lucas interview about his latest jail book that’s been released. We’re talking all things jails, writing, book sponsoring, the upcoming BSDCan 2019 conference, and more.</p>

<p>###Interview - Michael W. Lucas  - <a href="mailto:mwl@mwl.io">mwl@mwl.io</a> / <a href="https://twitter.com/mwlauthor">@mwlauthor</a><br>
FreeBSD Mastery: Jails</p>

<ul>
<li>BR: Welcome back to the show and congratulations on your latest book. How many books did you have to write before you could start on FreeBSD Mastery: Jails?</li>
<li>AJ: How much research did you have to do about jails?</li>
<li>BR: The book talks about something called ‘incomplete’ jails. What do you mean by that?</li>
<li>AJ: There are a lot of jail management frameworks out there. Why did you chose to write about iocage in the book?</li>
<li>BR: How many jails do you run yourself?</li>
<li>AJ: Can you tell us a bit about how you handle book sponsorship these days?</li>
<li>BR: What other books (fiction and non-fiction) are you currently working on?</li>
<li>AJ: Which talks are you looking forward to attend at the upcoming BSDCan conference?</li>
<li>BR: How is the BSD user group going?</li>
<li>AJ: Anything else you’d like to mention before we release you from our interview jail cell?</li>
</ul>

<p><hr></p>

<ul>
<li>Send questions, comments, show ideas/topics, or stories you want mentioned on the show to <a href="mailto:feedback@bsdnow.tv">feedback@bsdnow.tv</a></li>
</ul>

<p><hr></p>

<video controls preload="metadata" style=" width:426px;  height:240px;">
    <source src="http://201406.jb-dl.cdn.scaleengine.net/bsdnow/2019/bsd-0293.mp4" type="video/mp4">
    Your browser does not support the HTML5 video tag.
</video>]]>
  </content:encoded>
  <itunes:summary>
    <![CDATA[<p>This week we have a special episode with a Michael W. Lucas interview about his latest jail book that’s been released. We’re talking all things jails, writing, book sponsoring, the upcoming BSDCan 2019 conference, and more.</p>

<p>###Interview - Michael W. Lucas  - <a href="mailto:mwl@mwl.io">mwl@mwl.io</a> / <a href="https://twitter.com/mwlauthor">@mwlauthor</a><br>
FreeBSD Mastery: Jails</p>

<ul>
<li>BR: Welcome back to the show and congratulations on your latest book. How many books did you have to write before you could start on FreeBSD Mastery: Jails?</li>
<li>AJ: How much research did you have to do about jails?</li>
<li>BR: The book talks about something called ‘incomplete’ jails. What do you mean by that?</li>
<li>AJ: There are a lot of jail management frameworks out there. Why did you chose to write about iocage in the book?</li>
<li>BR: How many jails do you run yourself?</li>
<li>AJ: Can you tell us a bit about how you handle book sponsorship these days?</li>
<li>BR: What other books (fiction and non-fiction) are you currently working on?</li>
<li>AJ: Which talks are you looking forward to attend at the upcoming BSDCan conference?</li>
<li>BR: How is the BSD user group going?</li>
<li>AJ: Anything else you’d like to mention before we release you from our interview jail cell?</li>
</ul>

<p><hr></p>

<ul>
<li>Send questions, comments, show ideas/topics, or stories you want mentioned on the show to <a href="mailto:feedback@bsdnow.tv">feedback@bsdnow.tv</a></li>
</ul>

<p><hr></p>

<video controls preload="metadata" style=" width:426px;  height:240px;">
    <source src="http://201406.jb-dl.cdn.scaleengine.net/bsdnow/2019/bsd-0293.mp4" type="video/mp4">
    Your browser does not support the HTML5 video tag.
</video>]]>
  </itunes:summary>
</item>
<item>
  <title>102: May Contain ZFS</title>
  <link>https://www.bsdnow.tv/102</link>
  <guid isPermaLink="false">e0de53ca-3dcf-4df7-a556-faa52c7788a7</guid>
  <pubDate>Wed, 12 Aug 2015 08:00:00 -0400</pubDate>
  <author>JT Pennington</author>
  <enclosure url="https://aphid.fireside.fm/d/1437767933/c91b88f1-e824-4815-bcb8-5227818d6010/e0de53ca-3dcf-4df7-a556-faa52c7788a7.mp3" length="48985492" type="audio/mpeg"/>
  <itunes:episodeType>full</itunes:episodeType>
  <itunes:author>JT Pennington</itunes:author>
  <itunes:subtitle>This week on the show, we'll be talking with Peter Toth. He's got a jail management system called "iocage" that's been getting pretty popular recently. Have we finally found a replacement for ezjail? We'll see how it stacks up.</itunes:subtitle>
  <itunes:duration>1:08:02</itunes:duration>
  <itunes:explicit>no</itunes:explicit>
  <itunes:image href="https://media24.fireside.fm/file/fireside-images-2024/podcasts/images/c/c91b88f1-e824-4815-bcb8-5227818d6010/cover.jpg?v=4"/>
  <description>This week on the show, we'll be talking with Peter Toth. He's got a jail management system called "iocage" that's been getting pretty popular recently. Have we finally found a replacement for ezjail? We'll see how it stacks up.
This episode was brought to you by
&lt;a href="http://www.ixsystems.com/bsdnow" title="iXsystems"&gt;&lt;img src="/images/1.png" alt="iXsystems - Enterprise Servers and Storage for Open Source"&gt;&lt;/a&gt;&lt;a href="http://www.digitalocean.com/" title="DigitalOcean"&gt;&lt;img src="/images/2.png" alt="DigitalOcean - Simple Cloud Hosting, Built for Developers"&gt;&lt;/a&gt;&lt;a href="http://www.tarsnap.com/bsdnow" title="Tarsnap"&gt;&lt;img src="/images/3.png" alt="Tarsnap - Online Backups for the Truly Paranoid"&gt;&lt;/a&gt;
Headlines
FreeBSD on Olimex RT5350F-OLinuXino (https://www.bidouilliste.com/blog/2015/07/22/FreeBSD-on-Olimex-RT5350F-OLinuXino)
If you haven't heard of the RT5350F-OLinuXino-EVB, you're not alone (actually, we probably couldn't even remember the name if we did know about it)
It's a small board with a MIPS CPU, two ethernet ports, wireless support and... 32MB of RAM
This blog series documents installing FreeBSD on the device, but it is quite a DIY setup at the moment
In part two of the series (https://www.bidouilliste.com/blog/2015/07/24/FreeBSD-on-Olimex-RT5350F-OLinuXino-Part-2), he talks about the GPIO and how you can configure it
Part three is still in the works, so check the site later on for further progress and info
***
The modern OpenBSD home router (https://www.azabani.com/2015/08/06/modern-openbsd-home-router.html)
In a new series of blog posts, one guy takes you through the process of building an OpenBSD-based gateway (http://www.bsdnow.tv/tutorials/openbsd-router) for his home network
"It’s no secret that most consumer routers ship with software that’s flaky at best, and prohibitively insecure at worst"
Armed with a 600MHz Pentium III CPU, he shows the process of setting up basic NAT, firewalling and even getting hostap mode working for wireless
This guide also covers PPP and IPv6, in case you have those requirements
In a similar but unrelated series (http://jaytongarnett.blogspot.com/2015/07/openbsd-router-bt-home-hub-5-replacement.html), another user does a similar thing - his post also includes details on reusing your consumer router as a wireless bridge
He also has a separate post (http://jaytongarnett.blogspot.com/2015/08/openbsd-l2tpipsec-vpn-works-with.html) for setting up an IPSEC VPN on the router
***
NetBSD at Open Source Conference 2015 Kansai (https://mail-index.netbsd.org/netbsd-advocacy/2015/08/10/msg000691.html)
The Japanese NetBSD users group has teamed up with the Kansai BSD users group and Nagoya BSD users group to invade another conference
They had NetBSD running on all the usual (unusual?) devices, but some of the other BSDs also got a chance to shine at the event
Last time they mostly had ARM devices, but this time the centerpiece was an OMRON LUNA88k
They had at least one FreeBSD and OpenBSD device, and at least one NetBSD device even had Adobe Flash running on it
And what conference would be complete without an LED-powered towel
***
OpenSSH 7.0 released (https://lists.mindrot.org/pipermail/openssh-unix-dev/2015-August/034289.html)
The OpenSSH team has just finished up the 7.0 release, and the focus this time is deprecating legacy code
SSHv1 support is disabled, 1024 bit diffie-hellman-group1-sha1 KEX is disabled and the v00 cert format authentication is disabled
The syntax for permitting root logins has been changed, and is now called "prohibit-password" instead of "without-password" (this makes it so root can login, but only with keys) - all interactive authentication methods for root are also disabled by default now
If you're using an older configuration file, the "without-password" option still works, so no change is required
You can now control which public key types are available for authentication, as well as control which public key types are offered for host authentications
Various bug fixes and documentation improvements are also included
Aside from the keyboard-interactive and PAM-related bugs, this release includes one minor security fix: TTY permissions were too open, so users could write messages to other logged in users
In the next release, even more deprecation is planned: RSA keys will be refused if they're under 1024 bits, CBC-based ciphers will be disabled and the MD5 HMAC will also be disabled
***
Interview - Peter Toth - peter.toth198@gmail.com (mailto:peter.toth198@gmail.com) / @pannonp (https://twitter.com/pannonp)
Containment with iocage (https://github.com/iocage/iocage)
News Roundup
More c2k15 reports (http://undeadly.org/cgi?action=article&amp;amp;sid=20150809105132)
A few more hackathon reports from c2k15 in Calgary are still slowly trickling in
Alexander Bluhm's up first, and he continued improving OpenBSD's regression test suite (this ensures that no changes accidentally break existing things)
He also worked on syslogd, completing the TCP input code - the syslogd in 5.8 will have TLS support for secure remote logging
Renato Westphal sent in a report (http://undeadly.org/cgi?action=article&amp;amp;sid=20150811171006) of his very first hackathon
He finished up the VPLS implementation and worked on EIGRP (which is explained in the report) - the end result is that OpenBSD will be more easily deployable in a Cisco-heavy network
Philip Guenther also wrote in (http://undeadly.org/cgi?action=article&amp;amp;sid=20150809165912), getting some very technical and low-level stuff done at the hackathon
His report opens with "First came a diff to move the grabbing of the kernel lock for soft-interrupts from the ASM stubs to the C routine so that mere mortals can actually push it around further to reduce locking." - not exactly beginner stuff
There were also some C-state, suspend/resume and general ACPI improvements committed, and he gives a long list of random other bits he worked on as well
***
FreeBSD jails, the hard way (https://clinta.github.io/freebsd-jails-the-hard-way)
As you learned from our interview this week, there's quite a selection of tools available to manage your jails
This article takes the opposite approach, using only the tools in the base system: ZFS, nullfs and jail.conf
Unlike with iocage, ZFS isn't actually a requirement for this method
If you are using it, though, you can make use of snapshots for making template jails
***
OpenSSH hardware tokens (http://www.tancsa.com/mdtblog/?p=73)
We've talked about a number of ways to do two-factor authentication with SSH, but what if you want it on both the client and server?
This blog post will show you how to use a hardware token as a second authentication factor, for the "something you know, something you have" security model
It takes you through from start to finish: formatting the token, generating keys, getting it integrated with sshd
Most of this will apply to any OS that can run ssh, and the token used in the example can be found online for pretty cheap too
***
LibreSSL 2.2.2 released (http://ftp.openbsd.org/pub/OpenBSD/LibreSSL/libressl-2.2.2-relnotes.txt)
The LibreSSL team has released version 2.2.2, which signals the end of the 5.8 development cycle and includes many fixes
At the c2k15 hackathon, developers uncovered dozens of problems in the OpenSSL codebase with the Coverity code scanner, and this release incorporates all those: dead code, memory leaks, logic errors (which, by the way, you really don't want in a crypto tool...) and much more
SSLv3 support was removed from the "openssl" command, and only a few other SSLv3 bits remain - once workarounds are found for ports that specifically depend on it, it'll be removed completely
Various other small improvements were made: DH params are now 2048 bits by default, more old workarounds removed, cmake support added, etc
It'll be in 5.8 (due out earlier than usual) and it's in the FreeBSD ports tree as well
***
Feedback/Questions
James writes in (http://slexy.org/view/s216lrsVVd)
Stuart writes in (http://slexy.org/view/s20uGUHWLr)
*** 
</description>
  <itunes:keywords>freebsd, openbsd, netbsd, dragonflybsd, pcbsd, tutorial, howto, guide, bsd, interview, jails, iocage, bhyve, containers, lxc, docker, ezjail, router, gateway, ipsec, vpn, libressl, authentication, uefi, jails</itunes:keywords>
  <content:encoded>
    <![CDATA[<p>This week on the show, we&#39;ll be talking with Peter Toth. He&#39;s got a jail management system called &quot;iocage&quot; that&#39;s been getting pretty popular recently. Have we finally found a replacement for ezjail? We&#39;ll see how it stacks up.</p>

<h2>This episode was brought to you by</h2>

<p><a href="http://www.ixsystems.com/bsdnow" title="iXsystems"><img src="/images/1.png" alt="iXsystems - Enterprise Servers and Storage for Open Source" /></a><a href="http://www.digitalocean.com/" title="DigitalOcean"><img src="/images/2.png" alt="DigitalOcean - Simple Cloud Hosting, Built for Developers" /></a><a href="http://www.tarsnap.com/bsdnow" title="Tarsnap"><img src="/images/3.png" alt="Tarsnap - Online Backups for the Truly Paranoid" /></a></p>

<hr>

<h2>Headlines</h2>

<h3><a href="https://www.bidouilliste.com/blog/2015/07/22/FreeBSD-on-Olimex-RT5350F-OLinuXino" rel="nofollow">FreeBSD on Olimex RT5350F-OLinuXino</a></h3>

<ul>
<li>If you haven&#39;t heard of the RT5350F-OLinuXino-EVB, you&#39;re not alone (actually, we probably couldn&#39;t even remember the name if we did know about it)</li>
<li>It&#39;s a small board with a MIPS CPU, two ethernet ports, wireless support and... 32MB of RAM</li>
<li>This blog series documents installing FreeBSD on the device, but it is quite a DIY setup at the moment</li>
<li>In <a href="https://www.bidouilliste.com/blog/2015/07/24/FreeBSD-on-Olimex-RT5350F-OLinuXino-Part-2" rel="nofollow">part two of the series</a>, he talks about the GPIO and how you can configure it</li>
<li>Part three is still in the works, so check the site later on for further progress and info
***</li>
</ul>

<h3><a href="https://www.azabani.com/2015/08/06/modern-openbsd-home-router.html" rel="nofollow">The modern OpenBSD home router</a></h3>

<ul>
<li>In a new series of blog posts, one guy takes you through the process of building an <a href="http://www.bsdnow.tv/tutorials/openbsd-router" rel="nofollow">OpenBSD-based gateway</a> for his home network</li>
<li>&quot;It’s no secret that most consumer routers ship with software that’s flaky at best, and prohibitively insecure at worst&quot;</li>
<li>Armed with a 600MHz Pentium III CPU, he shows the process of setting up basic NAT, firewalling and even getting hostap mode working for wireless</li>
<li>This guide also covers PPP and IPv6, in case you have those requirements</li>
<li>In a <a href="http://jaytongarnett.blogspot.com/2015/07/openbsd-router-bt-home-hub-5-replacement.html" rel="nofollow">similar but unrelated series</a>, another user does a similar thing - his post also includes details on reusing your consumer router as a wireless bridge</li>
<li>He also has <a href="http://jaytongarnett.blogspot.com/2015/08/openbsd-l2tpipsec-vpn-works-with.html" rel="nofollow">a separate post</a> for setting up an IPSEC VPN on the router
***</li>
</ul>

<h3><a href="https://mail-index.netbsd.org/netbsd-advocacy/2015/08/10/msg000691.html" rel="nofollow">NetBSD at Open Source Conference 2015 Kansai</a></h3>

<ul>
<li>The Japanese NetBSD users group has teamed up with the Kansai BSD users group and Nagoya BSD users group to invade another conference</li>
<li>They had NetBSD running on all the usual (unusual?) devices, but some of the other BSDs also got a chance to shine at the event</li>
<li>Last time they mostly had ARM devices, but this time the centerpiece was an OMRON LUNA88k</li>
<li>They had at least one FreeBSD and OpenBSD device, and at least one NetBSD device even had Adobe Flash running on it</li>
<li>And what conference would be complete without an LED-powered towel
***</li>
</ul>

<h3><a href="https://lists.mindrot.org/pipermail/openssh-unix-dev/2015-August/034289.html" rel="nofollow">OpenSSH 7.0 released</a></h3>

<ul>
<li>The OpenSSH team has just finished up the 7.0 release, and the focus this time is deprecating legacy code</li>
<li>SSHv1 support is disabled, 1024 bit diffie-hellman-group1-sha1 KEX is disabled and the v00 cert format authentication is disabled</li>
<li>The syntax for permitting root logins has been changed, and is now called &quot;prohibit-password&quot; instead of &quot;without-password&quot; (this makes it so root can login, but only with keys) - all interactive authentication methods for root are also disabled by default now</li>
<li>If you&#39;re using an older configuration file, the &quot;without-password&quot; option still works, so no change is required</li>
<li>You can now control which public key types are available for authentication, as well as control which public key types are offered for host authentications</li>
<li>Various bug fixes and documentation improvements are also included</li>
<li>Aside from the keyboard-interactive and PAM-related bugs, this release includes one minor security fix: TTY permissions were too open, so users could write messages to other logged in users</li>
<li>In the <em>next release</em>, even more deprecation is planned: RSA keys will be refused if they&#39;re under 1024 bits, CBC-based ciphers will be disabled and the MD5 HMAC will also be disabled
***</li>
</ul>

<h2>Interview - Peter Toth - <a href="mailto:peter.toth198@gmail.com" rel="nofollow">peter.toth198@gmail.com</a> / <a href="https://twitter.com/pannonp" rel="nofollow">@pannonp</a></h2>

<p>Containment with <a href="https://github.com/iocage/iocage" rel="nofollow">iocage</a></p>

<hr>

<h2>News Roundup</h2>

<h3><a href="http://undeadly.org/cgi?action=article&sid=20150809105132" rel="nofollow">More c2k15 reports</a></h3>

<ul>
<li>A few more hackathon reports from c2k15 in Calgary are still slowly trickling in</li>
<li>Alexander Bluhm&#39;s up first, and he continued improving OpenBSD&#39;s regression test suite (this ensures that no changes accidentally break existing things)</li>
<li>He also worked on syslogd, completing the TCP input code - the syslogd in 5.8 will have TLS support for secure remote logging</li>
<li>Renato Westphal <a href="http://undeadly.org/cgi?action=article&sid=20150811171006" rel="nofollow">sent in a report</a> of his very first hackathon</li>
<li>He finished up the VPLS implementation and worked on EIGRP (which is explained in the report) - the end result is that OpenBSD will be more easily deployable in a Cisco-heavy network</li>
<li>Philip Guenther <a href="http://undeadly.org/cgi?action=article&sid=20150809165912" rel="nofollow">also wrote in</a>, getting some very technical and low-level stuff done at the hackathon</li>
<li>His report opens with &quot;First came a diff to move the grabbing of the kernel lock for soft-interrupts from the ASM stubs to the C routine so that mere mortals can actually push it around further to reduce locking.&quot; - not exactly beginner stuff</li>
<li>There were also some C-state, suspend/resume and general ACPI improvements committed, and he gives a long list of random other bits he worked on as well
***</li>
</ul>

<h3><a href="https://clinta.github.io/freebsd-jails-the-hard-way" rel="nofollow">FreeBSD jails, the hard way</a></h3>

<ul>
<li>As you learned from our interview this week, there&#39;s quite a selection of tools available to manage your jails</li>
<li>This article takes the opposite approach, using only the tools in the base system: ZFS, nullfs and jail.conf</li>
<li>Unlike with iocage, ZFS isn&#39;t actually a requirement for this method</li>
<li>If you are using it, though, you can make use of snapshots for making template jails
***</li>
</ul>

<h3><a href="http://www.tancsa.com/mdtblog/?p=73" rel="nofollow">OpenSSH hardware tokens</a></h3>

<ul>
<li>We&#39;ve talked about a number of ways to do two-factor authentication with SSH, but what if you want it on both the client <em>and</em> server?</li>
<li>This blog post will show you how to use a hardware token as a second authentication factor, for the &quot;something you know, something you have&quot; security model</li>
<li>It takes you through from start to finish: formatting the token, generating keys, getting it integrated with sshd</li>
<li>Most of this will apply to any OS that can run ssh, and the token used in the example can be found online for pretty cheap too
***</li>
</ul>

<h3><a href="http://ftp.openbsd.org/pub/OpenBSD/LibreSSL/libressl-2.2.2-relnotes.txt" rel="nofollow">LibreSSL 2.2.2 released</a></h3>

<ul>
<li>The LibreSSL team has released version 2.2.2, which signals the end of the 5.8 development cycle and includes many fixes</li>
<li>At the c2k15 hackathon, developers uncovered dozens of problems in the OpenSSL codebase with the Coverity code scanner, and this release incorporates all those: dead code, memory leaks, logic errors (which, by the way, you really don&#39;t want in a crypto tool...) and much more</li>
<li>SSLv3 support was removed from the &quot;openssl&quot; command, and only a few other SSLv3 bits remain - once workarounds are found for ports that specifically depend on it, it&#39;ll be removed completely</li>
<li>Various other small improvements were made: DH params are now 2048 bits by default, more old workarounds removed, cmake support added, etc</li>
<li>It&#39;ll be in 5.8 (due out earlier than usual) and it&#39;s in the FreeBSD ports tree as well
***</li>
</ul>

<h2>Feedback/Questions</h2>

<ul>
<li><a href="http://slexy.org/view/s216lrsVVd" rel="nofollow">James writes in</a></li>
<li><a href="http://slexy.org/view/s20uGUHWLr" rel="nofollow">Stuart writes in</a>
***</li>
</ul>]]>
  </content:encoded>
  <itunes:summary>
    <![CDATA[<p>This week on the show, we&#39;ll be talking with Peter Toth. He&#39;s got a jail management system called &quot;iocage&quot; that&#39;s been getting pretty popular recently. Have we finally found a replacement for ezjail? We&#39;ll see how it stacks up.</p>

<h2>This episode was brought to you by</h2>

<p><a href="http://www.ixsystems.com/bsdnow" title="iXsystems"><img src="/images/1.png" alt="iXsystems - Enterprise Servers and Storage for Open Source" /></a><a href="http://www.digitalocean.com/" title="DigitalOcean"><img src="/images/2.png" alt="DigitalOcean - Simple Cloud Hosting, Built for Developers" /></a><a href="http://www.tarsnap.com/bsdnow" title="Tarsnap"><img src="/images/3.png" alt="Tarsnap - Online Backups for the Truly Paranoid" /></a></p>

<hr>

<h2>Headlines</h2>

<h3><a href="https://www.bidouilliste.com/blog/2015/07/22/FreeBSD-on-Olimex-RT5350F-OLinuXino" rel="nofollow">FreeBSD on Olimex RT5350F-OLinuXino</a></h3>

<ul>
<li>If you haven&#39;t heard of the RT5350F-OLinuXino-EVB, you&#39;re not alone (actually, we probably couldn&#39;t even remember the name if we did know about it)</li>
<li>It&#39;s a small board with a MIPS CPU, two ethernet ports, wireless support and... 32MB of RAM</li>
<li>This blog series documents installing FreeBSD on the device, but it is quite a DIY setup at the moment</li>
<li>In <a href="https://www.bidouilliste.com/blog/2015/07/24/FreeBSD-on-Olimex-RT5350F-OLinuXino-Part-2" rel="nofollow">part two of the series</a>, he talks about the GPIO and how you can configure it</li>
<li>Part three is still in the works, so check the site later on for further progress and info
***</li>
</ul>

<h3><a href="https://www.azabani.com/2015/08/06/modern-openbsd-home-router.html" rel="nofollow">The modern OpenBSD home router</a></h3>

<ul>
<li>In a new series of blog posts, one guy takes you through the process of building an <a href="http://www.bsdnow.tv/tutorials/openbsd-router" rel="nofollow">OpenBSD-based gateway</a> for his home network</li>
<li>&quot;It’s no secret that most consumer routers ship with software that’s flaky at best, and prohibitively insecure at worst&quot;</li>
<li>Armed with a 600MHz Pentium III CPU, he shows the process of setting up basic NAT, firewalling and even getting hostap mode working for wireless</li>
<li>This guide also covers PPP and IPv6, in case you have those requirements</li>
<li>In a <a href="http://jaytongarnett.blogspot.com/2015/07/openbsd-router-bt-home-hub-5-replacement.html" rel="nofollow">similar but unrelated series</a>, another user does a similar thing - his post also includes details on reusing your consumer router as a wireless bridge</li>
<li>He also has <a href="http://jaytongarnett.blogspot.com/2015/08/openbsd-l2tpipsec-vpn-works-with.html" rel="nofollow">a separate post</a> for setting up an IPSEC VPN on the router
***</li>
</ul>

<h3><a href="https://mail-index.netbsd.org/netbsd-advocacy/2015/08/10/msg000691.html" rel="nofollow">NetBSD at Open Source Conference 2015 Kansai</a></h3>

<ul>
<li>The Japanese NetBSD users group has teamed up with the Kansai BSD users group and Nagoya BSD users group to invade another conference</li>
<li>They had NetBSD running on all the usual (unusual?) devices, but some of the other BSDs also got a chance to shine at the event</li>
<li>Last time they mostly had ARM devices, but this time the centerpiece was an OMRON LUNA88k</li>
<li>They had at least one FreeBSD and OpenBSD device, and at least one NetBSD device even had Adobe Flash running on it</li>
<li>And what conference would be complete without an LED-powered towel
***</li>
</ul>

<h3><a href="https://lists.mindrot.org/pipermail/openssh-unix-dev/2015-August/034289.html" rel="nofollow">OpenSSH 7.0 released</a></h3>

<ul>
<li>The OpenSSH team has just finished up the 7.0 release, and the focus this time is deprecating legacy code</li>
<li>SSHv1 support is disabled, 1024 bit diffie-hellman-group1-sha1 KEX is disabled and the v00 cert format authentication is disabled</li>
<li>The syntax for permitting root logins has been changed, and is now called &quot;prohibit-password&quot; instead of &quot;without-password&quot; (this makes it so root can login, but only with keys) - all interactive authentication methods for root are also disabled by default now</li>
<li>If you&#39;re using an older configuration file, the &quot;without-password&quot; option still works, so no change is required</li>
<li>You can now control which public key types are available for authentication, as well as control which public key types are offered for host authentications</li>
<li>Various bug fixes and documentation improvements are also included</li>
<li>Aside from the keyboard-interactive and PAM-related bugs, this release includes one minor security fix: TTY permissions were too open, so users could write messages to other logged in users</li>
<li>In the <em>next release</em>, even more deprecation is planned: RSA keys will be refused if they&#39;re under 1024 bits, CBC-based ciphers will be disabled and the MD5 HMAC will also be disabled
***</li>
</ul>

<h2>Interview - Peter Toth - <a href="mailto:peter.toth198@gmail.com" rel="nofollow">peter.toth198@gmail.com</a> / <a href="https://twitter.com/pannonp" rel="nofollow">@pannonp</a></h2>

<p>Containment with <a href="https://github.com/iocage/iocage" rel="nofollow">iocage</a></p>

<hr>

<h2>News Roundup</h2>

<h3><a href="http://undeadly.org/cgi?action=article&sid=20150809105132" rel="nofollow">More c2k15 reports</a></h3>

<ul>
<li>A few more hackathon reports from c2k15 in Calgary are still slowly trickling in</li>
<li>Alexander Bluhm&#39;s up first, and he continued improving OpenBSD&#39;s regression test suite (this ensures that no changes accidentally break existing things)</li>
<li>He also worked on syslogd, completing the TCP input code - the syslogd in 5.8 will have TLS support for secure remote logging</li>
<li>Renato Westphal <a href="http://undeadly.org/cgi?action=article&sid=20150811171006" rel="nofollow">sent in a report</a> of his very first hackathon</li>
<li>He finished up the VPLS implementation and worked on EIGRP (which is explained in the report) - the end result is that OpenBSD will be more easily deployable in a Cisco-heavy network</li>
<li>Philip Guenther <a href="http://undeadly.org/cgi?action=article&sid=20150809165912" rel="nofollow">also wrote in</a>, getting some very technical and low-level stuff done at the hackathon</li>
<li>His report opens with &quot;First came a diff to move the grabbing of the kernel lock for soft-interrupts from the ASM stubs to the C routine so that mere mortals can actually push it around further to reduce locking.&quot; - not exactly beginner stuff</li>
<li>There were also some C-state, suspend/resume and general ACPI improvements committed, and he gives a long list of random other bits he worked on as well
***</li>
</ul>

<h3><a href="https://clinta.github.io/freebsd-jails-the-hard-way" rel="nofollow">FreeBSD jails, the hard way</a></h3>

<ul>
<li>As you learned from our interview this week, there&#39;s quite a selection of tools available to manage your jails</li>
<li>This article takes the opposite approach, using only the tools in the base system: ZFS, nullfs and jail.conf</li>
<li>Unlike with iocage, ZFS isn&#39;t actually a requirement for this method</li>
<li>If you are using it, though, you can make use of snapshots for making template jails
***</li>
</ul>

<h3><a href="http://www.tancsa.com/mdtblog/?p=73" rel="nofollow">OpenSSH hardware tokens</a></h3>

<ul>
<li>We&#39;ve talked about a number of ways to do two-factor authentication with SSH, but what if you want it on both the client <em>and</em> server?</li>
<li>This blog post will show you how to use a hardware token as a second authentication factor, for the &quot;something you know, something you have&quot; security model</li>
<li>It takes you through from start to finish: formatting the token, generating keys, getting it integrated with sshd</li>
<li>Most of this will apply to any OS that can run ssh, and the token used in the example can be found online for pretty cheap too
***</li>
</ul>

<h3><a href="http://ftp.openbsd.org/pub/OpenBSD/LibreSSL/libressl-2.2.2-relnotes.txt" rel="nofollow">LibreSSL 2.2.2 released</a></h3>

<ul>
<li>The LibreSSL team has released version 2.2.2, which signals the end of the 5.8 development cycle and includes many fixes</li>
<li>At the c2k15 hackathon, developers uncovered dozens of problems in the OpenSSL codebase with the Coverity code scanner, and this release incorporates all those: dead code, memory leaks, logic errors (which, by the way, you really don&#39;t want in a crypto tool...) and much more</li>
<li>SSLv3 support was removed from the &quot;openssl&quot; command, and only a few other SSLv3 bits remain - once workarounds are found for ports that specifically depend on it, it&#39;ll be removed completely</li>
<li>Various other small improvements were made: DH params are now 2048 bits by default, more old workarounds removed, cmake support added, etc</li>
<li>It&#39;ll be in 5.8 (due out earlier than usual) and it&#39;s in the FreeBSD ports tree as well
***</li>
</ul>

<h2>Feedback/Questions</h2>

<ul>
<li><a href="http://slexy.org/view/s216lrsVVd" rel="nofollow">James writes in</a></li>
<li><a href="http://slexy.org/view/s20uGUHWLr" rel="nofollow">Stuart writes in</a>
***</li>
</ul>]]>
  </itunes:summary>
</item>
<item>
  <title>99: BSD Gnow</title>
  <link>https://www.bsdnow.tv/99</link>
  <guid isPermaLink="false">c234f2ea-9f17-4c25-bd28-db41586b32de</guid>
  <pubDate>Wed, 22 Jul 2015 08:00:00 -0400</pubDate>
  <author>JT Pennington</author>
  <enclosure url="https://aphid.fireside.fm/d/1437767933/c91b88f1-e824-4815-bcb8-5227818d6010/c234f2ea-9f17-4c25-bd28-db41586b32de.mp3" length="57071380" type="audio/mpeg"/>
  <itunes:episodeType>full</itunes:episodeType>
  <itunes:author>JT Pennington</itunes:author>
  <itunes:subtitle>This week we'll be talking with Ryan Lortie and Baptiste Daroussin about GNOME on BSD. Upstream development is finally treating the BSDs as a first class citizen, so we'll hear about how the recent porting efforts have been since.</itunes:subtitle>
  <itunes:duration>1:19:15</itunes:duration>
  <itunes:explicit>no</itunes:explicit>
  <itunes:image href="https://media24.fireside.fm/file/fireside-images-2024/podcasts/images/c/c91b88f1-e824-4815-bcb8-5227818d6010/cover.jpg?v=4"/>
  <description>This week we'll be talking with Ryan Lortie and Baptiste Daroussin about GNOME on BSD. Upstream development is finally treating the BSDs as a first class citizen, so we'll hear about how the recent porting efforts have been since.
This episode was brought to you by
&lt;a href="http://www.ixsystems.com/bsdnow" title="iXsystems"&gt;&lt;img src="/images/1.png" alt="iXsystems - Enterprise Servers and Storage for Open Source"&gt;&lt;/a&gt;&lt;a href="http://www.digitalocean.com/" title="DigitalOcean"&gt;&lt;img src="/images/2.png" alt="DigitalOcean - Simple Cloud Hosting, Built for Developers"&gt;&lt;/a&gt;&lt;a href="http://www.tarsnap.com/bsdnow" title="Tarsnap"&gt;&lt;img src="/images/3.png" alt="Tarsnap - Online Backups for the Truly Paranoid"&gt;&lt;/a&gt;
Headlines
OpenBSD presents tame (https://www.marc.info/?l=openbsd-tech&amp;amp;m=143725996614627&amp;amp;w=2)
Theo de Raadt sent out an email detailing OpenBSD's new "tame" subsystem, written by Nicholas Marriott and himself, for restricting what processes can and can't do
When using tame, programs will switch to a "restricted-service operating mode," limiting them to only the things they actually need to do
As for the background: "Generally there are two models of operation. The first model requires a major rewrite of application software for effective use (ie. capsicum). The other model in common use lacks granularity, and allows or denies an operation throughout the entire lifetime of a process. As a result, they lack differentiation between program 'initialization' versus 'main servicing loop.' systrace had the same problem. My observation is that programs need a large variety of calls during initialization, but few in their main loops."
Some initial categories of operation include: computation, memory management, read-write operations on file descriptors, opening of files and, of course, networking
Restrictions can also be stacked further into the lifespan of the process, but removed abilities can never be regained (obviously)
Anything that tries to access resources outside of its in-place limits gets terminated with a SIGKILL or, optionally, a SIGABRT (which can produce useful core dumps for investigation)
Also included are 29 examples of userland programs that get additional protection with very minimal changes to the source - only 2 or 3 lines needing changed in the case of binaries like cat, ps, dmesg, etc.
This is an initial work-in-progress version of tame, so there may be more improvements or further (https://www.marc.info/?l=openbsd-tech&amp;amp;m=143740834710502&amp;amp;w=2) control (https://www.marc.info/?l=openbsd-tech&amp;amp;m=143741052411159&amp;amp;w=2) options added before it hits a release (very specific access policies can sometimes backfire (https://forums.grsecurity.net/viewtopic.php?f=7&amp;amp;t=2522), however)
The man page, also included in the mail, provides some specifics about how to integrate tame properly into your code (which, by design, was made very easy to do - making it simple means third party programs are more likely to actually use it)
Kernel bits are in the tree now (https://www.marc.info/?l=openbsd-cvs&amp;amp;m=143727335416513&amp;amp;w=2), with userland changes starting to trickle in too
Combined with a myriad of memory protections (http://www.bsdnow.tv/episodes/2015_05_13-exclusive_disjunction), tight privilege separation and (above all else (https://en.wikipedia.org/wiki/OpenBSD_security_features)) good coding practices, tame should further harden the OpenBSD security fortress
Further discussion (https://news.ycombinator.com/item?id=9928221) can (https://www.reddit.com/r/programming/comments/3dsr0t) be (http://undeadly.org/cgi?action=article&amp;amp;sid=20150719000800&amp;amp;mode=flat) found (https://news.ycombinator.com/item?id=9909429) in (https://www.reddit.com/r/linux/comments/3ds66o) the (https://lobste.rs/s/tbbtfs) usual (https://www.reddit.com/r/openbsd/comments/3ds64c) places (https://www.reddit.com/r/BSD/comments/3ds681) you'd expect
***
Using Docker on FreeBSD (https://wiki.freebsd.org/Docker)
With the experimental Docker port landing in FreeBSD a few weeks ago, some initial docs are starting to show up
This docker is "the real thing," and isn’t using a virtual machine as the backend - as such, it has some limitations
The FreeBSD wiki has a page detailing how it works in general, as well as more info about those limitations
When running Linux containers, it will only work as well as the Linux ABI compat layer for your version of FreeBSD (11.0, or -CURRENT when we're recording this, is where all the action is for 64bit support)
For users on 10.X, there's also a FreeBSD container available, which allows you to use Docker as a fancy jail manager (it uses the jail subsystem internally)
Give it a try, let us know how you find it to be compared to other solutions
***
OpenBSD imports doas, removes sudo (http://www.tedunangst.com/flak/post/doas)
OpenBSD has included the ubiquitous "sudo" utility for many years now, and the current maintainer of sudo (Todd C. Miller) is also a long-time OpenBSD dev
The version included in the base system was much smaller than the latest current version used elsewhere, but was based on older code
Some internal discussion lead to the decision that sudo should probably be moved to ports now, where it can be updated easily and offer all the extra features that were missing in base (LDAP and whatnot)
Ted Unangst conjured up with a rewritten utility to replace it in the base system, dubbed "do as," with the aim of being more simple and compact
There were concerns that sudo was too big and too complicated, and a quick 'n' dirty check reveals that doas is around 350 lines of code, while sudo is around 10,000 - which would you rather have as a setuid root binary?
After the initial import, a number of developers began reviewing and improving various bits here and there
You can check out the code (http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/usr.bin/doas/) now if you're interested
Command usage (http://www.openbsd.org/cgi-bin/man.cgi/OpenBSD-current/man1/doas.1) and config syntax (http://www.openbsd.org/cgi-bin/man.cgi/OpenBSD-current/man5/doas.conf.5) seem pretty straightforward
More discussion (https://news.ycombinator.com/item?id=9914693) on HN
***
What would you like to see in FreeBSD (https://www.reddit.com/r/freebsd/comments/3d80vt/what_would_you_like_to_see_in_freebsd/)
Adrian Chadd started a reddit thread about areas in which FreeBSD could be improved, asking the community what they'd like to see
There are over 200 comments that span a wide range of topics, so we'll just cover a few of the more popular requests - check the very long thread if you're interested in more
The top comment says things don't "just work," citing failover link aggregation of LACP laggs, PPPoE issues, disorganized jail configuration options, unclear CARP configuration and userland dtrace being unstable
Another common one was that there are three firewalls in the base system, with ipfilter and pf being kinda dead now - should they be removed, and more focus put into ipfw?
Video drivers also came up frequently, with users hoping for better OpenGL support and support for newer graphics cards from Intel and AMD - similar comments were made about wireless chipsets as well
Some other replies included more clarity with pkgng output, paying more attention to security issues, updating PF to match the one in OpenBSD, improved laptop support, a graphical installer, LibreSSL in base, more focus on embedded MIPS devices, binary packages with different config options, steam support and lots more
At least one user suggested better "marketing" for FreeBSD, with more advocacy and (hopefully) more business adoption
That one really applies to all the BSDs, and regular users (that's you listening to this) can help make it happen for whichever ones you use right now
Maybe Adrian can singlehandedly do all the work and make all the users happy
***
Interview - Ryan Lortie &amp;amp; Baptiste Daroussin
Porting the latest GNOME code to FreeBSD
News Roundup
Introducing resflash (http://stable.rcesoftware.com/resflash/)
If you haven't heard of resflash before, it's "a tool for building OpenBSD images for embedded and cloud environments in a programmatic, reproducible way"
One of the major benefits to images like this is the read-only filesystem, so there's no possibility of filesystem corruption if power is lost
There's an optional read-write partition as well, used for any persistent changes you want to make
You can check out the source code on Github (https://github.com/bconway/resflash) or read the main site for more info
***
Jails with iocage (http://pid1.com/posts/post10.html)
There are a growing number of FreeBSD jail management utilities: ezjail, cbsd, warden and a few others
After looking at all the different choices, the author of this blog post eventually settled on iocage (https://github.com/iocage/iocage) for the job
The post walks you through the basic configuration and usage of iocage for creating managing jails
If you've been unhappy with ezjail or some of the others, iocage might be worth giving a try instead (it also has really good ZFS integration)
***
DragonFly GPU improvements (http://lists.dragonflybsd.org/pipermail/users/2015-July/207892.html)
DragonFlyBSD continues to up their graphics game, this time with Intel's ValleyView series of CPUs
These GPUs are primarily used in the newer Atom CPUs and offer much better performance than the older ones
A git branch was created to hold the fixes for now while the last remaining bugs get fixed
Fully-accelerated Broadwell support and an update to newer DRM code are also available in the git branch, and will be merged to the main tree after some testing
***
Branchless development (http://www.tedunangst.com/flak/post/branchless-development)
Ted Unangst has a new blog post up, talking about software branches and the effects of having (or not having) them
He covers integrating and merging code, and the versioning problems that can happen with multiple people contributing at once
"For an open source project, branching is counter intuitively antisocial. For instance, I usually tell people I’m running OpenBSD, but that’s kind of a lie. I’m actually running teduBSD, which is like OpenBSD but has some changes to make it even better. Of course, you can’t have teduBSD because I’m selfish. I’m also lazy, and only inclined to make my changes work for me, not everyone else."
The solution, according to him, is bringing all the code the developers are using closer together
One big benefit is that WIP code gets tested much faster (and bugs get fixed early on)
***
Feedback/Questions
Matthew writes in (http://slexy.org/view/s21yQtBCCK)
Chris writes in (http://slexy.org/view/s21oFA80kY)
Anonymous writes in (http://slexy.org/view/s2JYvTlJlm)
Bill writes in (http://slexy.org/view/s21LXvk53z)
*** 
</description>
  <itunes:keywords>freebsd, openbsd, netbsd, dragonflybsd, pcbsd, tutorial, howto, guide, bsd, interview, gnome, gnome shell, gnome3, puns i will regret forever, doas, sudo, resflash, flashrd, nanobsd, tame, capsicum, iocage, ezjail, docker</itunes:keywords>
  <content:encoded>
    <![CDATA[<p>This week we&#39;ll be talking with Ryan Lortie and Baptiste Daroussin about GNOME on BSD. Upstream development is finally treating the BSDs as a first class citizen, so we&#39;ll hear about how the recent porting efforts have been since.</p>

<h2>This episode was brought to you by</h2>

<p><a href="http://www.ixsystems.com/bsdnow" title="iXsystems"><img src="/images/1.png" alt="iXsystems - Enterprise Servers and Storage for Open Source" /></a><a href="http://www.digitalocean.com/" title="DigitalOcean"><img src="/images/2.png" alt="DigitalOcean - Simple Cloud Hosting, Built for Developers" /></a><a href="http://www.tarsnap.com/bsdnow" title="Tarsnap"><img src="/images/3.png" alt="Tarsnap - Online Backups for the Truly Paranoid" /></a></p>

<hr>

<h2>Headlines</h2>

<h3><a href="https://www.marc.info/?l=openbsd-tech&m=143725996614627&w=2" rel="nofollow">OpenBSD presents tame</a></h3>

<ul>
<li>Theo de Raadt sent out an email detailing OpenBSD&#39;s new &quot;tame&quot; subsystem, written by Nicholas Marriott and himself, for restricting what processes can and can&#39;t do</li>
<li>When using tame, programs will switch to a &quot;restricted-service operating mode,&quot; limiting them to only the things they actually need to do</li>
<li>As for the background: &quot;Generally there are two models of operation. The first model requires a major rewrite of application software for effective use (ie. capsicum). The other model in common use lacks granularity, and allows or denies an operation throughout the entire lifetime of a process. As a result, they lack differentiation between program &#39;initialization&#39; versus &#39;main servicing loop.&#39; systrace had the same problem. My observation is that programs need a large variety of calls during initialization, but few in their main loops.&quot;</li>
<li>Some initial categories of operation include: computation, memory management, read-write operations on file descriptors, opening of files and, of course, networking</li>
<li>Restrictions can also be stacked further into the lifespan of the process, but removed abilities can never be regained (obviously)</li>
<li>Anything that tries to access resources outside of its in-place limits gets terminated with a SIGKILL or, optionally, a SIGABRT (which can produce useful core dumps for investigation)</li>
<li>Also included are 29 examples of userland programs that get additional protection with very minimal changes to the source - only 2 or 3 lines needing changed in the case of binaries like cat, ps, dmesg, etc.</li>
<li>This is an initial work-in-progress version of tame, so there may be more improvements or <a href="https://www.marc.info/?l=openbsd-tech&m=143740834710502&w=2" rel="nofollow">further</a> <a href="https://www.marc.info/?l=openbsd-tech&m=143741052411159&w=2" rel="nofollow">control</a> options added before it hits a release (very specific access policies can <a href="https://forums.grsecurity.net/viewtopic.php?f=7&t=2522" rel="nofollow">sometimes backfire</a>, however)</li>
<li>The man page, also included in the mail, provides some specifics about how to integrate tame properly into your code (which, by design, was made very easy to do - making it simple means third party programs are more likely to <em>actually use it</em>)</li>
<li>Kernel bits are <a href="https://www.marc.info/?l=openbsd-cvs&m=143727335416513&w=2" rel="nofollow">in the tree now</a>, with userland changes starting to trickle in too</li>
<li>Combined with a <a href="http://www.bsdnow.tv/episodes/2015_05_13-exclusive_disjunction" rel="nofollow">myriad of memory protections</a>, tight privilege separation and (above <a href="https://en.wikipedia.org/wiki/OpenBSD_security_features" rel="nofollow">all else</a>) good coding practices, tame should further harden the OpenBSD security fortress</li>
<li>Further <a href="https://news.ycombinator.com/item?id=9928221" rel="nofollow">discussion</a> <a href="https://www.reddit.com/r/programming/comments/3dsr0t" rel="nofollow">can</a> <a href="http://undeadly.org/cgi?action=article&sid=20150719000800&mode=flat" rel="nofollow">be</a> <a href="https://news.ycombinator.com/item?id=9909429" rel="nofollow">found</a> <a href="https://www.reddit.com/r/linux/comments/3ds66o" rel="nofollow">in</a> <a href="https://lobste.rs/s/tbbtfs" rel="nofollow">the</a> <a href="https://www.reddit.com/r/openbsd/comments/3ds64c" rel="nofollow">usual</a> <a href="https://www.reddit.com/r/BSD/comments/3ds681" rel="nofollow">places</a> you&#39;d expect
***</li>
</ul>

<h3><a href="https://wiki.freebsd.org/Docker" rel="nofollow">Using Docker on FreeBSD</a></h3>

<ul>
<li>With the experimental Docker port landing in FreeBSD a few weeks ago, some initial docs are starting to show up</li>
<li>This docker is &quot;the real thing,&quot; and isn’t using a virtual machine as the backend - as such, it has some limitations</li>
<li>The FreeBSD wiki has a page detailing how it works in general, as well as more info about those limitations</li>
<li>When running Linux containers, it will only work as well as the Linux ABI compat layer for your version of FreeBSD (11.0, or -CURRENT when we&#39;re recording this, is where all the action is for 64bit support)</li>
<li>For users on 10.X, there&#39;s also a FreeBSD container available, which allows you to use Docker as a fancy jail manager (it uses the jail subsystem internally)</li>
<li>Give it a try, let us know how you find it to be compared to other solutions
***</li>
</ul>

<h3><a href="http://www.tedunangst.com/flak/post/doas" rel="nofollow">OpenBSD imports doas, removes sudo</a></h3>

<ul>
<li>OpenBSD has included the ubiquitous &quot;sudo&quot; utility for many years now, and the current maintainer of sudo (Todd C. Miller) is also a long-time OpenBSD dev</li>
<li>The version included in the base system was much smaller than the latest current version used elsewhere, but was based on older code</li>
<li>Some internal discussion lead to the decision that sudo should probably be moved to ports now, where it can be updated easily and offer all the extra features that were missing in base (LDAP and whatnot)</li>
<li>Ted Unangst conjured up with a rewritten utility to replace it in the base system, dubbed &quot;do as,&quot; with the aim of being more simple and compact</li>
<li>There were concerns that sudo was too big and too complicated, and a quick &#39;n&#39; dirty check reveals that doas is around 350 lines of code, while sudo is around 10,000 - which would you rather have as a setuid root binary?</li>
<li>After the initial import, a number of developers began reviewing and improving various bits here and there</li>
<li>You can <a href="http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/usr.bin/doas/" rel="nofollow">check out the code</a> now if you&#39;re interested</li>
<li><a href="http://www.openbsd.org/cgi-bin/man.cgi/OpenBSD-current/man1/doas.1" rel="nofollow">Command usage</a> and <a href="http://www.openbsd.org/cgi-bin/man.cgi/OpenBSD-current/man5/doas.conf.5" rel="nofollow">config syntax</a> seem pretty straightforward</li>
<li>More <a href="https://news.ycombinator.com/item?id=9914693" rel="nofollow">discussion</a> on HN
***</li>
</ul>

<h3><a href="https://www.reddit.com/r/freebsd/comments/3d80vt/what_would_you_like_to_see_in_freebsd/" rel="nofollow">What would you like to see in FreeBSD</a></h3>

<ul>
<li>Adrian Chadd started a reddit thread about areas in which FreeBSD could be improved, asking the community what they&#39;d like to see</li>
<li>There are over <strong>200</strong> comments that span a wide range of topics, so we&#39;ll just cover a few of the more popular requests - check the very long thread if you&#39;re interested in more</li>
<li>The top comment says things don&#39;t &quot;just work,&quot; citing failover link aggregation of LACP laggs, PPPoE issues, disorganized jail configuration options, unclear CARP configuration and userland dtrace being unstable</li>
<li>Another common one was that there are <em>three</em> firewalls in the base system, with ipfilter and pf being kinda dead now - should they be removed, and more focus put into ipfw?</li>
<li>Video drivers also came up frequently, with users hoping for better OpenGL support and support for newer graphics cards from Intel and AMD - similar comments were made about wireless chipsets as well</li>
<li>Some other replies included more clarity with pkgng output, paying more attention to security issues, updating PF to match the one in OpenBSD, improved laptop support, a graphical installer, LibreSSL in base, more focus on embedded MIPS devices, binary packages with different config options, steam support and lots more</li>
<li>At least one user suggested better &quot;marketing&quot; for FreeBSD, with more advocacy and (hopefully) more business adoption</li>
<li>That one really applies to all the BSDs, and regular users (that&#39;s you listening to this) can help make it happen for whichever ones you use <em>right now</em></li>
<li>Maybe Adrian can singlehandedly do all the work and make all the users happy
***</li>
</ul>

<h2>Interview - Ryan Lortie &amp; Baptiste Daroussin</h2>

<p>Porting the latest GNOME code to FreeBSD</p>

<hr>

<h2>News Roundup</h2>

<h3><a href="http://stable.rcesoftware.com/resflash/" rel="nofollow">Introducing resflash</a></h3>

<ul>
<li>If you haven&#39;t heard of resflash before, it&#39;s &quot;a tool for building OpenBSD images for embedded and cloud environments in a programmatic, reproducible way&quot;</li>
<li>One of the major benefits to images like this is the read-only filesystem, so there&#39;s no possibility of filesystem corruption if power is lost</li>
<li>There&#39;s an optional read-write partition as well, used for any persistent changes you want to make</li>
<li>You can check out the source code <a href="https://github.com/bconway/resflash" rel="nofollow">on Github</a> or read the main site for more info
***</li>
</ul>

<h3><a href="http://pid1.com/posts/post10.html" rel="nofollow">Jails with iocage</a></h3>

<ul>
<li>There are a growing number of FreeBSD jail management utilities: ezjail, cbsd, warden and a few others</li>
<li>After looking at all the different choices, the author of this blog post eventually settled on <a href="https://github.com/iocage/iocage" rel="nofollow">iocage</a> for the job</li>
<li>The post walks you through the basic configuration and usage of iocage for creating managing jails</li>
<li>If you&#39;ve been unhappy with ezjail or some of the others, iocage might be worth giving a try instead (it also has really good ZFS integration)
***</li>
</ul>

<h3><a href="http://lists.dragonflybsd.org/pipermail/users/2015-July/207892.html" rel="nofollow">DragonFly GPU improvements</a></h3>

<ul>
<li>DragonFlyBSD continues to up their graphics game, this time with Intel&#39;s ValleyView series of CPUs</li>
<li>These GPUs are primarily used in the newer Atom CPUs and offer much better performance than the older ones</li>
<li>A git branch was created to hold the fixes for now while the last remaining bugs get fixed</li>
<li>Fully-accelerated Broadwell support and an update to newer DRM code are also available in the git branch, and will be merged to the main tree after some testing
***</li>
</ul>

<h3><a href="http://www.tedunangst.com/flak/post/branchless-development" rel="nofollow">Branchless development</a></h3>

<ul>
<li>Ted Unangst has a new blog post up, talking about software branches and the effects of having (or not having) them</li>
<li>He covers integrating and merging code, and the versioning problems that can happen with multiple people contributing at once</li>
<li>&quot;For an open source project, branching is counter intuitively antisocial. For instance, I usually tell people I’m running OpenBSD, but that’s kind of a lie. I’m actually running teduBSD, which is like OpenBSD but has some changes to make it even better. Of course, you can’t have teduBSD because I’m selfish. I’m also lazy, and only inclined to make my changes work for me, not everyone else.&quot;</li>
<li>The solution, according to him, is bringing all the code the developers are using closer together</li>
<li>One big benefit is that WIP code gets tested much faster (and bugs get fixed early on)
***</li>
</ul>

<h2>Feedback/Questions</h2>

<ul>
<li><a href="http://slexy.org/view/s21yQtBCCK" rel="nofollow">Matthew writes in</a></li>
<li><a href="http://slexy.org/view/s21oFA80kY" rel="nofollow">Chris writes in</a></li>
<li><a href="http://slexy.org/view/s2JYvTlJlm" rel="nofollow">Anonymous writes in</a></li>
<li><a href="http://slexy.org/view/s21LXvk53z" rel="nofollow">Bill writes in</a>
***</li>
</ul>]]>
  </content:encoded>
  <itunes:summary>
    <![CDATA[<p>This week we&#39;ll be talking with Ryan Lortie and Baptiste Daroussin about GNOME on BSD. Upstream development is finally treating the BSDs as a first class citizen, so we&#39;ll hear about how the recent porting efforts have been since.</p>

<h2>This episode was brought to you by</h2>

<p><a href="http://www.ixsystems.com/bsdnow" title="iXsystems"><img src="/images/1.png" alt="iXsystems - Enterprise Servers and Storage for Open Source" /></a><a href="http://www.digitalocean.com/" title="DigitalOcean"><img src="/images/2.png" alt="DigitalOcean - Simple Cloud Hosting, Built for Developers" /></a><a href="http://www.tarsnap.com/bsdnow" title="Tarsnap"><img src="/images/3.png" alt="Tarsnap - Online Backups for the Truly Paranoid" /></a></p>

<hr>

<h2>Headlines</h2>

<h3><a href="https://www.marc.info/?l=openbsd-tech&m=143725996614627&w=2" rel="nofollow">OpenBSD presents tame</a></h3>

<ul>
<li>Theo de Raadt sent out an email detailing OpenBSD&#39;s new &quot;tame&quot; subsystem, written by Nicholas Marriott and himself, for restricting what processes can and can&#39;t do</li>
<li>When using tame, programs will switch to a &quot;restricted-service operating mode,&quot; limiting them to only the things they actually need to do</li>
<li>As for the background: &quot;Generally there are two models of operation. The first model requires a major rewrite of application software for effective use (ie. capsicum). The other model in common use lacks granularity, and allows or denies an operation throughout the entire lifetime of a process. As a result, they lack differentiation between program &#39;initialization&#39; versus &#39;main servicing loop.&#39; systrace had the same problem. My observation is that programs need a large variety of calls during initialization, but few in their main loops.&quot;</li>
<li>Some initial categories of operation include: computation, memory management, read-write operations on file descriptors, opening of files and, of course, networking</li>
<li>Restrictions can also be stacked further into the lifespan of the process, but removed abilities can never be regained (obviously)</li>
<li>Anything that tries to access resources outside of its in-place limits gets terminated with a SIGKILL or, optionally, a SIGABRT (which can produce useful core dumps for investigation)</li>
<li>Also included are 29 examples of userland programs that get additional protection with very minimal changes to the source - only 2 or 3 lines needing changed in the case of binaries like cat, ps, dmesg, etc.</li>
<li>This is an initial work-in-progress version of tame, so there may be more improvements or <a href="https://www.marc.info/?l=openbsd-tech&m=143740834710502&w=2" rel="nofollow">further</a> <a href="https://www.marc.info/?l=openbsd-tech&m=143741052411159&w=2" rel="nofollow">control</a> options added before it hits a release (very specific access policies can <a href="https://forums.grsecurity.net/viewtopic.php?f=7&t=2522" rel="nofollow">sometimes backfire</a>, however)</li>
<li>The man page, also included in the mail, provides some specifics about how to integrate tame properly into your code (which, by design, was made very easy to do - making it simple means third party programs are more likely to <em>actually use it</em>)</li>
<li>Kernel bits are <a href="https://www.marc.info/?l=openbsd-cvs&m=143727335416513&w=2" rel="nofollow">in the tree now</a>, with userland changes starting to trickle in too</li>
<li>Combined with a <a href="http://www.bsdnow.tv/episodes/2015_05_13-exclusive_disjunction" rel="nofollow">myriad of memory protections</a>, tight privilege separation and (above <a href="https://en.wikipedia.org/wiki/OpenBSD_security_features" rel="nofollow">all else</a>) good coding practices, tame should further harden the OpenBSD security fortress</li>
<li>Further <a href="https://news.ycombinator.com/item?id=9928221" rel="nofollow">discussion</a> <a href="https://www.reddit.com/r/programming/comments/3dsr0t" rel="nofollow">can</a> <a href="http://undeadly.org/cgi?action=article&sid=20150719000800&mode=flat" rel="nofollow">be</a> <a href="https://news.ycombinator.com/item?id=9909429" rel="nofollow">found</a> <a href="https://www.reddit.com/r/linux/comments/3ds66o" rel="nofollow">in</a> <a href="https://lobste.rs/s/tbbtfs" rel="nofollow">the</a> <a href="https://www.reddit.com/r/openbsd/comments/3ds64c" rel="nofollow">usual</a> <a href="https://www.reddit.com/r/BSD/comments/3ds681" rel="nofollow">places</a> you&#39;d expect
***</li>
</ul>

<h3><a href="https://wiki.freebsd.org/Docker" rel="nofollow">Using Docker on FreeBSD</a></h3>

<ul>
<li>With the experimental Docker port landing in FreeBSD a few weeks ago, some initial docs are starting to show up</li>
<li>This docker is &quot;the real thing,&quot; and isn’t using a virtual machine as the backend - as such, it has some limitations</li>
<li>The FreeBSD wiki has a page detailing how it works in general, as well as more info about those limitations</li>
<li>When running Linux containers, it will only work as well as the Linux ABI compat layer for your version of FreeBSD (11.0, or -CURRENT when we&#39;re recording this, is where all the action is for 64bit support)</li>
<li>For users on 10.X, there&#39;s also a FreeBSD container available, which allows you to use Docker as a fancy jail manager (it uses the jail subsystem internally)</li>
<li>Give it a try, let us know how you find it to be compared to other solutions
***</li>
</ul>

<h3><a href="http://www.tedunangst.com/flak/post/doas" rel="nofollow">OpenBSD imports doas, removes sudo</a></h3>

<ul>
<li>OpenBSD has included the ubiquitous &quot;sudo&quot; utility for many years now, and the current maintainer of sudo (Todd C. Miller) is also a long-time OpenBSD dev</li>
<li>The version included in the base system was much smaller than the latest current version used elsewhere, but was based on older code</li>
<li>Some internal discussion lead to the decision that sudo should probably be moved to ports now, where it can be updated easily and offer all the extra features that were missing in base (LDAP and whatnot)</li>
<li>Ted Unangst conjured up with a rewritten utility to replace it in the base system, dubbed &quot;do as,&quot; with the aim of being more simple and compact</li>
<li>There were concerns that sudo was too big and too complicated, and a quick &#39;n&#39; dirty check reveals that doas is around 350 lines of code, while sudo is around 10,000 - which would you rather have as a setuid root binary?</li>
<li>After the initial import, a number of developers began reviewing and improving various bits here and there</li>
<li>You can <a href="http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/usr.bin/doas/" rel="nofollow">check out the code</a> now if you&#39;re interested</li>
<li><a href="http://www.openbsd.org/cgi-bin/man.cgi/OpenBSD-current/man1/doas.1" rel="nofollow">Command usage</a> and <a href="http://www.openbsd.org/cgi-bin/man.cgi/OpenBSD-current/man5/doas.conf.5" rel="nofollow">config syntax</a> seem pretty straightforward</li>
<li>More <a href="https://news.ycombinator.com/item?id=9914693" rel="nofollow">discussion</a> on HN
***</li>
</ul>

<h3><a href="https://www.reddit.com/r/freebsd/comments/3d80vt/what_would_you_like_to_see_in_freebsd/" rel="nofollow">What would you like to see in FreeBSD</a></h3>

<ul>
<li>Adrian Chadd started a reddit thread about areas in which FreeBSD could be improved, asking the community what they&#39;d like to see</li>
<li>There are over <strong>200</strong> comments that span a wide range of topics, so we&#39;ll just cover a few of the more popular requests - check the very long thread if you&#39;re interested in more</li>
<li>The top comment says things don&#39;t &quot;just work,&quot; citing failover link aggregation of LACP laggs, PPPoE issues, disorganized jail configuration options, unclear CARP configuration and userland dtrace being unstable</li>
<li>Another common one was that there are <em>three</em> firewalls in the base system, with ipfilter and pf being kinda dead now - should they be removed, and more focus put into ipfw?</li>
<li>Video drivers also came up frequently, with users hoping for better OpenGL support and support for newer graphics cards from Intel and AMD - similar comments were made about wireless chipsets as well</li>
<li>Some other replies included more clarity with pkgng output, paying more attention to security issues, updating PF to match the one in OpenBSD, improved laptop support, a graphical installer, LibreSSL in base, more focus on embedded MIPS devices, binary packages with different config options, steam support and lots more</li>
<li>At least one user suggested better &quot;marketing&quot; for FreeBSD, with more advocacy and (hopefully) more business adoption</li>
<li>That one really applies to all the BSDs, and regular users (that&#39;s you listening to this) can help make it happen for whichever ones you use <em>right now</em></li>
<li>Maybe Adrian can singlehandedly do all the work and make all the users happy
***</li>
</ul>

<h2>Interview - Ryan Lortie &amp; Baptiste Daroussin</h2>

<p>Porting the latest GNOME code to FreeBSD</p>

<hr>

<h2>News Roundup</h2>

<h3><a href="http://stable.rcesoftware.com/resflash/" rel="nofollow">Introducing resflash</a></h3>

<ul>
<li>If you haven&#39;t heard of resflash before, it&#39;s &quot;a tool for building OpenBSD images for embedded and cloud environments in a programmatic, reproducible way&quot;</li>
<li>One of the major benefits to images like this is the read-only filesystem, so there&#39;s no possibility of filesystem corruption if power is lost</li>
<li>There&#39;s an optional read-write partition as well, used for any persistent changes you want to make</li>
<li>You can check out the source code <a href="https://github.com/bconway/resflash" rel="nofollow">on Github</a> or read the main site for more info
***</li>
</ul>

<h3><a href="http://pid1.com/posts/post10.html" rel="nofollow">Jails with iocage</a></h3>

<ul>
<li>There are a growing number of FreeBSD jail management utilities: ezjail, cbsd, warden and a few others</li>
<li>After looking at all the different choices, the author of this blog post eventually settled on <a href="https://github.com/iocage/iocage" rel="nofollow">iocage</a> for the job</li>
<li>The post walks you through the basic configuration and usage of iocage for creating managing jails</li>
<li>If you&#39;ve been unhappy with ezjail or some of the others, iocage might be worth giving a try instead (it also has really good ZFS integration)
***</li>
</ul>

<h3><a href="http://lists.dragonflybsd.org/pipermail/users/2015-July/207892.html" rel="nofollow">DragonFly GPU improvements</a></h3>

<ul>
<li>DragonFlyBSD continues to up their graphics game, this time with Intel&#39;s ValleyView series of CPUs</li>
<li>These GPUs are primarily used in the newer Atom CPUs and offer much better performance than the older ones</li>
<li>A git branch was created to hold the fixes for now while the last remaining bugs get fixed</li>
<li>Fully-accelerated Broadwell support and an update to newer DRM code are also available in the git branch, and will be merged to the main tree after some testing
***</li>
</ul>

<h3><a href="http://www.tedunangst.com/flak/post/branchless-development" rel="nofollow">Branchless development</a></h3>

<ul>
<li>Ted Unangst has a new blog post up, talking about software branches and the effects of having (or not having) them</li>
<li>He covers integrating and merging code, and the versioning problems that can happen with multiple people contributing at once</li>
<li>&quot;For an open source project, branching is counter intuitively antisocial. For instance, I usually tell people I’m running OpenBSD, but that’s kind of a lie. I’m actually running teduBSD, which is like OpenBSD but has some changes to make it even better. Of course, you can’t have teduBSD because I’m selfish. I’m also lazy, and only inclined to make my changes work for me, not everyone else.&quot;</li>
<li>The solution, according to him, is bringing all the code the developers are using closer together</li>
<li>One big benefit is that WIP code gets tested much faster (and bugs get fixed early on)
***</li>
</ul>

<h2>Feedback/Questions</h2>

<ul>
<li><a href="http://slexy.org/view/s21yQtBCCK" rel="nofollow">Matthew writes in</a></li>
<li><a href="http://slexy.org/view/s21oFA80kY" rel="nofollow">Chris writes in</a></li>
<li><a href="http://slexy.org/view/s2JYvTlJlm" rel="nofollow">Anonymous writes in</a></li>
<li><a href="http://slexy.org/view/s21LXvk53z" rel="nofollow">Bill writes in</a>
***</li>
</ul>]]>
  </itunes:summary>
</item>
<item>
  <title>27: BSD Now vs. BSDTalk</title>
  <link>https://www.bsdnow.tv/27</link>
  <guid isPermaLink="false">9c2ed198-48a2-4ed6-988c-6d5ce1ed66c7</guid>
  <pubDate>Wed, 05 Mar 2014 08:00:00 -0500</pubDate>
  <author>JT Pennington</author>
  <enclosure url="https://aphid.fireside.fm/d/1437767933/c91b88f1-e824-4815-bcb8-5227818d6010/9c2ed198-48a2-4ed6-988c-6d5ce1ed66c7.mp3" length="73930325" type="audio/mpeg"/>
  <itunes:episodeType>full</itunes:episodeType>
  <itunes:author>JT Pennington</itunes:author>
  <itunes:subtitle>The long-awaited meetup is finally happening on today's show. We're going to be interviewing the original BSD podcaster, Will Backman, to discuss what he's been up to and what the future of BSD advocacy looks like. After that, we'll be showing you how to track (and even cross-compile!) the -CURRENT branch of NetBSD. We've got answers to user-submitted questions and the latest news, on BSD Now - the place to B.. SD.</itunes:subtitle>
  <itunes:duration>1:42:40</itunes:duration>
  <itunes:explicit>no</itunes:explicit>
  <itunes:image href="https://media24.fireside.fm/file/fireside-images-2024/podcasts/images/c/c91b88f1-e824-4815-bcb8-5227818d6010/cover.jpg?v=4"/>
  <description>The long-awaited meetup is finally happening on today's show. We're going to be interviewing the original BSD podcaster, Will Backman, to discuss what he's been up to and what the future of BSD advocacy looks like. After that, we'll be showing you how to track (and even cross-compile!) the -CURRENT branch of NetBSD. We've got answers to user-submitted questions and the latest news, on BSD Now - the place to B.. SD.
This episode was brought to you by
&lt;a href="http://www.ixsystems.com/bsdnow" title="iXsystems"&gt;&lt;img src="/images/iXlogo2.png" alt="iXsystems - Enterprise Servers and Storage For Open Source"&gt;&lt;/a&gt;
Headlines
FreeBSD and OpenBSD in GSOC2014 (https://wiki.freebsd.org/SummerOfCode2014)
The Google Summer of Code is a way to encourage students to write code for open source projects and make some money
Both FreeBSD and OpenBSD were accepted, and we'd love for anyone listening to check out their GSOC pages
The FreeBSD wiki has a list of things that they'd be interested in someone helping out with
OpenBSD's want list was also posted (http://www.openbsdfoundation.org/gsoc2014.html)
DragonflyBSD and NetBSD were sadly not accepted this year
***
Yes, you too can be an evil network overlord (http://bsdly.blogspot.com/2014/02/yes-you-too-can-be-evil-network.html)
A new blog post about monitoring your network using only free tools
OpenBSD is a great fit, and has all the stuff you need in the base system or via packages
It talks about the pflow pseudo-interface, its capabilities and relation to NetFlow (also goes well with pf)
There's also details about flowd and nfsen, more great tools to make network monitoring easy
If you're listening, Peter... stop ignoring our emails and come on the show! We know you're watching!
***
BSDMag's February issue is out (http://bsdmag.org/magazine/1858-openbsd-5-4-configure-openbsd-basic-services)
The theme is "configuring basic services on OpenBSD 5.4"
There's also an interview with Peter Hansteen (oh hey...)
Topics also include locking down SSH, a GIMP lesson, user/group management, and...
Linux and Solaris articles? Why??
***
Changes in bcrypt (http://marc.info/?l=openbsd-misc&amp;amp;m=139320023202696&amp;amp;w=2)
Not specific to any OS, but the OpenBSD team is updating their bcrypt implementation
There is a bug in bcrypt when hashing long passwords - other OSes need to update theirs too! (FreeBSD already has)
"The length is stored in an unsigned char type, which will overflow and wrap at 256. Although we consider the existence of affected hashes very rare, in order to differentiate hashes generated before and after the fix, we are introducing a new minor 'b'."
As long as you upgrade your OpenBSD system in order (without skipping versions) you should be ok going forward
Lots of specifics in the email, check the full thing
***
Interview - Will Backman - bitgeist@yahoo.com (mailto:bitgeist@yahoo.com) / @bsdtalk (https://twitter.com/bsdtalk)
The BSDTalk podcast, BSD advocacy, various topics
Tutorial
Tracking and cross-compiling -CURRENT (NetBSD) (http://www.bsdnow.tv/tutorials/current-nbsd)
News Roundup
X11 no longer needs root (http://undeadly.org/cgi?action=article&amp;amp;sid=20140223112426)
Xorg has long since required root privileges to run the main server
With recent work (http://marc.info/?l=openbsd-cvs&amp;amp;;m=139245772023497&amp;amp;w=2) from the OpenBSD team, now everything (even KMS) can run as a regular user
Now you can set the "machdep.allowaperture" sysctl to 0 and still use a GUI
***
OpenSSH 6.6 CFT (https://lists.mindrot.org/pipermail/openssh-unix-dev/2014-March/032259.html)
Shortly after the huge 6.5 release, we get a routine bugfix update
Test it out on as many systems as you can
Check the mailing list for the full bug list
***
Creating an OpenBSD USB drive (http://undeadly.org/cgi?action=article&amp;amp;sid=20140225072408)
Since OpenBSD doesn't distribute any official USB images, here are some instructions on how to do it
Step by step guide on how you can make your very own
However, there's some recent emails (http://undeadly.org/cgi?action=article&amp;amp;sid=20140228231258) that suggest official USB images may be coming soon... oh wait (http://marc.info/?l=openbsd-cvs&amp;amp;m=139377587526463&amp;amp;w=2)
***
PCBSD weekly digest (http://blog.pcbsd.org/2014/02/pc-bsd-weekly-feature-digest-19/)
New PBI updates that allow separate ports from /usr/local
You need to rebuild pbi-manager if you want to try it out
Updates and changes to Life Preserver, App Cafe, PCDM
***
Feedback/Questions
espressowar writes in (http://slexy.org/view/s2JpJ5EaZp)
Antonio writes in (http://slexy.org/view/s2QpPevJ3J)
Christian writes in (http://slexy.org/view/s2EZLxDfWh)
Adam writes in (http://slexy.org/view/s21gEBZbmG)
Alex writes in (http://slexy.org/view/s2RnCO1p9c)
*** 
</description>
  <itunes:keywords>freebsd, openbsd, netbsd, dragonflybsd, pcbsd, tutorial, howto, guide, bsd, interview, will backman, bsdtalk, podcast, cross compile, build.sh, portable, portability, cross-build, building a release, google summer of code, gsoc, gsoc2014, 2014, spamd, dd, opensmtpd, tcpdump, packet filtering, monitoring, network, bcrypt, solar designer, ixsystems, usb, bootable, jails, openbsd usb drive, ezjail, jails, bsd jail, x11, openssh, pflow, pf</itunes:keywords>
  <content:encoded>
    <![CDATA[<p>The long-awaited meetup is finally happening on today&#39;s show. We&#39;re going to be interviewing the original BSD podcaster, Will Backman, to discuss what he&#39;s been up to and what the future of BSD advocacy looks like. After that, we&#39;ll be showing you how to track (and even cross-compile!) the -CURRENT branch of NetBSD. We&#39;ve got answers to user-submitted questions and the latest news, on BSD Now - the place to B.. SD.</p>

<h2>This episode was brought to you by</h2>

<p><a href="http://www.ixsystems.com/bsdnow" title="iXsystems"><img src="/images/iXlogo2.png" alt="iXsystems - Enterprise Servers and Storage For Open Source" /></a></p>

<hr>

<h2>Headlines</h2>

<h3><a href="https://wiki.freebsd.org/SummerOfCode2014" rel="nofollow">FreeBSD and OpenBSD in GSOC2014</a></h3>

<ul>
<li>The Google Summer of Code is a way to encourage students to write code for open source projects and make some money</li>
<li>Both FreeBSD and OpenBSD were accepted, and we&#39;d love for anyone listening to check out their GSOC pages</li>
<li>The FreeBSD wiki has a list of things that they&#39;d be interested in someone helping out with</li>
<li>OpenBSD&#39;s want list was <a href="http://www.openbsdfoundation.org/gsoc2014.html" rel="nofollow">also posted</a></li>
<li>DragonflyBSD and NetBSD were sadly not accepted this year
***</li>
</ul>

<h3><a href="http://bsdly.blogspot.com/2014/02/yes-you-too-can-be-evil-network.html" rel="nofollow">Yes, you too can be an evil network overlord</a></h3>

<ul>
<li>A new blog post about monitoring your network using only free tools</li>
<li>OpenBSD is a great fit, and has all the stuff you need in the base system or via packages</li>
<li>It talks about the pflow pseudo-interface, its capabilities and relation to NetFlow (also goes well with pf)</li>
<li>There&#39;s also details about flowd and nfsen, more great tools to make network monitoring easy</li>
<li>If you&#39;re listening, Peter... stop ignoring our emails and come on the show! We know you&#39;re watching!
***</li>
</ul>

<h3><a href="http://bsdmag.org/magazine/1858-openbsd-5-4-configure-openbsd-basic-services" rel="nofollow">BSDMag&#39;s February issue is out</a></h3>

<ul>
<li>The theme is &quot;configuring basic services on OpenBSD 5.4&quot;</li>
<li>There&#39;s also an interview with Peter Hansteen (oh hey...)</li>
<li>Topics also include locking down SSH, a GIMP lesson, user/group management, and...</li>
<li>Linux and Solaris articles? Why??
***</li>
</ul>

<h3><a href="http://marc.info/?l=openbsd-misc&m=139320023202696&w=2" rel="nofollow">Changes in bcrypt</a></h3>

<ul>
<li>Not specific to any OS, but the OpenBSD team is updating their bcrypt implementation</li>
<li>There is a bug in bcrypt when hashing long passwords - other OSes need to update theirs too! (FreeBSD already has)</li>
<li>&quot;The length is stored in an unsigned char type, which will overflow and wrap at 256. Although we consider the existence of affected hashes very rare, in order to differentiate hashes generated before and after the fix, we are introducing a new minor &#39;b&#39;.&quot;</li>
<li>As long as you upgrade your OpenBSD system in order (without skipping versions) you should be ok going forward</li>
<li>Lots of specifics in the email, check the full thing
***</li>
</ul>

<h2>Interview - Will Backman - <a href="mailto:bitgeist@yahoo.com" rel="nofollow">bitgeist@yahoo.com</a> / <a href="https://twitter.com/bsdtalk" rel="nofollow">@bsdtalk</a></h2>

<p>The BSDTalk podcast, BSD advocacy, various topics</p>

<hr>

<h2>Tutorial</h2>

<h3><a href="http://www.bsdnow.tv/tutorials/current-nbsd" rel="nofollow">Tracking and cross-compiling -CURRENT (NetBSD)</a></h3>

<hr>

<h2>News Roundup</h2>

<h3><a href="http://undeadly.org/cgi?action=article&sid=20140223112426" rel="nofollow">X11 no longer needs root</a></h3>

<ul>
<li>Xorg has long since required root privileges to run the main server</li>
<li>With <a href="http://marc.info/?l=openbsd-cvs&;m=139245772023497&w=2" rel="nofollow">recent work</a> from the OpenBSD team, now everything (even KMS) can run as a regular user</li>
<li>Now you can set the &quot;machdep.allowaperture&quot; sysctl to 0 and still use a GUI
***</li>
</ul>

<h3><a href="https://lists.mindrot.org/pipermail/openssh-unix-dev/2014-March/032259.html" rel="nofollow">OpenSSH 6.6 CFT</a></h3>

<ul>
<li>Shortly after the huge 6.5 release, we get a routine bugfix update</li>
<li>Test it out on as many systems as you can</li>
<li>Check the mailing list for the full bug list
***</li>
</ul>

<h3><a href="http://undeadly.org/cgi?action=article&sid=20140225072408" rel="nofollow">Creating an OpenBSD USB drive</a></h3>

<ul>
<li>Since OpenBSD doesn&#39;t distribute any official USB images, here are some instructions on how to do it</li>
<li>Step by step guide on how you can make your very own</li>
<li>However, there&#39;s some <a href="http://undeadly.org/cgi?action=article&sid=20140228231258" rel="nofollow">recent emails</a> that suggest official USB images may be coming soon... <a href="http://marc.info/?l=openbsd-cvs&m=139377587526463&w=2" rel="nofollow">oh wait</a>
***</li>
</ul>

<h3><a href="http://blog.pcbsd.org/2014/02/pc-bsd-weekly-feature-digest-19/" rel="nofollow">PCBSD weekly digest</a></h3>

<ul>
<li>New PBI updates that allow separate ports from /usr/local</li>
<li>You need to rebuild pbi-manager if you want to try it out</li>
<li>Updates and changes to Life Preserver, App Cafe, PCDM
***</li>
</ul>

<h2>Feedback/Questions</h2>

<ul>
<li><a href="http://slexy.org/view/s2JpJ5EaZp" rel="nofollow">espressowar writes in</a></li>
<li><a href="http://slexy.org/view/s2QpPevJ3J" rel="nofollow">Antonio writes in</a></li>
<li><a href="http://slexy.org/view/s2EZLxDfWh" rel="nofollow">Christian writes in</a></li>
<li><a href="http://slexy.org/view/s21gEBZbmG" rel="nofollow">Adam writes in</a></li>
<li><a href="http://slexy.org/view/s2RnCO1p9c" rel="nofollow">Alex writes in</a>
***</li>
</ul>]]>
  </content:encoded>
  <itunes:summary>
    <![CDATA[<p>The long-awaited meetup is finally happening on today&#39;s show. We&#39;re going to be interviewing the original BSD podcaster, Will Backman, to discuss what he&#39;s been up to and what the future of BSD advocacy looks like. After that, we&#39;ll be showing you how to track (and even cross-compile!) the -CURRENT branch of NetBSD. We&#39;ve got answers to user-submitted questions and the latest news, on BSD Now - the place to B.. SD.</p>

<h2>This episode was brought to you by</h2>

<p><a href="http://www.ixsystems.com/bsdnow" title="iXsystems"><img src="/images/iXlogo2.png" alt="iXsystems - Enterprise Servers and Storage For Open Source" /></a></p>

<hr>

<h2>Headlines</h2>

<h3><a href="https://wiki.freebsd.org/SummerOfCode2014" rel="nofollow">FreeBSD and OpenBSD in GSOC2014</a></h3>

<ul>
<li>The Google Summer of Code is a way to encourage students to write code for open source projects and make some money</li>
<li>Both FreeBSD and OpenBSD were accepted, and we&#39;d love for anyone listening to check out their GSOC pages</li>
<li>The FreeBSD wiki has a list of things that they&#39;d be interested in someone helping out with</li>
<li>OpenBSD&#39;s want list was <a href="http://www.openbsdfoundation.org/gsoc2014.html" rel="nofollow">also posted</a></li>
<li>DragonflyBSD and NetBSD were sadly not accepted this year
***</li>
</ul>

<h3><a href="http://bsdly.blogspot.com/2014/02/yes-you-too-can-be-evil-network.html" rel="nofollow">Yes, you too can be an evil network overlord</a></h3>

<ul>
<li>A new blog post about monitoring your network using only free tools</li>
<li>OpenBSD is a great fit, and has all the stuff you need in the base system or via packages</li>
<li>It talks about the pflow pseudo-interface, its capabilities and relation to NetFlow (also goes well with pf)</li>
<li>There&#39;s also details about flowd and nfsen, more great tools to make network monitoring easy</li>
<li>If you&#39;re listening, Peter... stop ignoring our emails and come on the show! We know you&#39;re watching!
***</li>
</ul>

<h3><a href="http://bsdmag.org/magazine/1858-openbsd-5-4-configure-openbsd-basic-services" rel="nofollow">BSDMag&#39;s February issue is out</a></h3>

<ul>
<li>The theme is &quot;configuring basic services on OpenBSD 5.4&quot;</li>
<li>There&#39;s also an interview with Peter Hansteen (oh hey...)</li>
<li>Topics also include locking down SSH, a GIMP lesson, user/group management, and...</li>
<li>Linux and Solaris articles? Why??
***</li>
</ul>

<h3><a href="http://marc.info/?l=openbsd-misc&m=139320023202696&w=2" rel="nofollow">Changes in bcrypt</a></h3>

<ul>
<li>Not specific to any OS, but the OpenBSD team is updating their bcrypt implementation</li>
<li>There is a bug in bcrypt when hashing long passwords - other OSes need to update theirs too! (FreeBSD already has)</li>
<li>&quot;The length is stored in an unsigned char type, which will overflow and wrap at 256. Although we consider the existence of affected hashes very rare, in order to differentiate hashes generated before and after the fix, we are introducing a new minor &#39;b&#39;.&quot;</li>
<li>As long as you upgrade your OpenBSD system in order (without skipping versions) you should be ok going forward</li>
<li>Lots of specifics in the email, check the full thing
***</li>
</ul>

<h2>Interview - Will Backman - <a href="mailto:bitgeist@yahoo.com" rel="nofollow">bitgeist@yahoo.com</a> / <a href="https://twitter.com/bsdtalk" rel="nofollow">@bsdtalk</a></h2>

<p>The BSDTalk podcast, BSD advocacy, various topics</p>

<hr>

<h2>Tutorial</h2>

<h3><a href="http://www.bsdnow.tv/tutorials/current-nbsd" rel="nofollow">Tracking and cross-compiling -CURRENT (NetBSD)</a></h3>

<hr>

<h2>News Roundup</h2>

<h3><a href="http://undeadly.org/cgi?action=article&sid=20140223112426" rel="nofollow">X11 no longer needs root</a></h3>

<ul>
<li>Xorg has long since required root privileges to run the main server</li>
<li>With <a href="http://marc.info/?l=openbsd-cvs&;m=139245772023497&w=2" rel="nofollow">recent work</a> from the OpenBSD team, now everything (even KMS) can run as a regular user</li>
<li>Now you can set the &quot;machdep.allowaperture&quot; sysctl to 0 and still use a GUI
***</li>
</ul>

<h3><a href="https://lists.mindrot.org/pipermail/openssh-unix-dev/2014-March/032259.html" rel="nofollow">OpenSSH 6.6 CFT</a></h3>

<ul>
<li>Shortly after the huge 6.5 release, we get a routine bugfix update</li>
<li>Test it out on as many systems as you can</li>
<li>Check the mailing list for the full bug list
***</li>
</ul>

<h3><a href="http://undeadly.org/cgi?action=article&sid=20140225072408" rel="nofollow">Creating an OpenBSD USB drive</a></h3>

<ul>
<li>Since OpenBSD doesn&#39;t distribute any official USB images, here are some instructions on how to do it</li>
<li>Step by step guide on how you can make your very own</li>
<li>However, there&#39;s some <a href="http://undeadly.org/cgi?action=article&sid=20140228231258" rel="nofollow">recent emails</a> that suggest official USB images may be coming soon... <a href="http://marc.info/?l=openbsd-cvs&m=139377587526463&w=2" rel="nofollow">oh wait</a>
***</li>
</ul>

<h3><a href="http://blog.pcbsd.org/2014/02/pc-bsd-weekly-feature-digest-19/" rel="nofollow">PCBSD weekly digest</a></h3>

<ul>
<li>New PBI updates that allow separate ports from /usr/local</li>
<li>You need to rebuild pbi-manager if you want to try it out</li>
<li>Updates and changes to Life Preserver, App Cafe, PCDM
***</li>
</ul>

<h2>Feedback/Questions</h2>

<ul>
<li><a href="http://slexy.org/view/s2JpJ5EaZp" rel="nofollow">espressowar writes in</a></li>
<li><a href="http://slexy.org/view/s2QpPevJ3J" rel="nofollow">Antonio writes in</a></li>
<li><a href="http://slexy.org/view/s2EZLxDfWh" rel="nofollow">Christian writes in</a></li>
<li><a href="http://slexy.org/view/s21gEBZbmG" rel="nofollow">Adam writes in</a></li>
<li><a href="http://slexy.org/view/s2RnCO1p9c" rel="nofollow">Alex writes in</a>
***</li>
</ul>]]>
  </itunes:summary>
</item>
  </channel>
</rss>
