<?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>app02</fireside:hostname>
    <fireside:genDate>Fri, 19 Jun 2026 08:03:48 +0000</fireside:genDate>
    <generator>Fireside (https://fireside.fm)</generator>
    <title>BSD Now - Episodes Tagged with “Ntimed”</title>
    <link>https://www.bsdnow.tv/tags/ntimed</link>
    <pubDate>Wed, 11 Feb 2015 08:00:00 -0500</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>76: Time for a Change</title>
  <link>https://www.bsdnow.tv/76</link>
  <guid isPermaLink="false">b872a625-f3d6-477b-b162-fd4248aef998</guid>
  <pubDate>Wed, 11 Feb 2015 08:00:00 -0500</pubDate>
  <author>JT Pennington</author>
  <enclosure url="https://aphid.fireside.fm/d/1437767933/c91b88f1-e824-4815-bcb8-5227818d6010/b872a625-f3d6-477b-b162-fd4248aef998.mp3" length="64285204" type="audio/mpeg"/>
  <itunes:episodeType>full</itunes:episodeType>
  <itunes:author>JT Pennington</itunes:author>
  <itunes:subtitle>This week, we'll be talking to Henning Brauer about OpenNTPD and its recently revived portable version. After that, we'll be discussing different ways to securely tunnel your traffic: specifically OpenVPN, IPSEC, SSH and Tor. All that and the latest news, coming up on BSD Now - the place to B.. SD.</itunes:subtitle>
  <itunes:duration>1:29:17</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>&lt;p&gt;This week, we'll be talking to Henning Brauer about OpenNTPD and its recently revived portable version. After that, we'll be discussing different ways to securely tunnel your traffic: specifically OpenVPN, IPSEC, SSH and Tor. All that and the latest news, coming up on BSD Now - the place to B.. SD.&lt;/p&gt;

&lt;h2&gt;This episode was brought to you by&lt;/h2&gt;

&lt;p&gt;&lt;a href="http://www.ixsystems.com/bsdnow" title="iXsystems" rel="nofollow noopener"&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" rel="nofollow noopener"&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" rel="nofollow noopener"&gt;&lt;img src="/images/3.png" alt="Tarsnap - Online Backups for the Truly Paranoid"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;hr&gt;

&lt;h2&gt;Headlines&lt;/h2&gt;

&lt;h3&gt;&lt;a href="https://lists.freebsd.org/pipermail/freebsd-current/2015-February/054295.html" rel="nofollow noopener"&gt;Strange timer bug in FreeBSD 11&lt;/a&gt;&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="http://www.bsdnow.tv/episodes/2014_09_24-beastly_infrastructure" rel="nofollow noopener"&gt;Peter Wemm&lt;/a&gt; wrote in to the FreeBSD -CURRENT mailing list with an interesting observation&lt;/li&gt;
&lt;li&gt;Running the latest development code in the infrastructure, the clock would stop keeping time after 24 days of uptime&lt;/li&gt;
&lt;li&gt;This meant things like cron and sleep would break, TCP/IP wouldn't time out or resend packets, a lot of things would break&lt;/li&gt;
&lt;li&gt;A workaround until it was fixed was to reboot every 24 days, but this is BSD we're talking about - uptime is our game&lt;/li&gt;
&lt;li&gt;An initial proposal was adding a CFLAG to the build options which makes makes signed arithmetic wrap&lt;/li&gt;
&lt;li&gt;Peter disagreed and &lt;a href="https://lists.freebsd.org/pipermail/freebsd-current/2015-February/054320.html" rel="nofollow noopener"&gt;gave some background&lt;/a&gt;, offering a different patch to &lt;a href="https://lists.freebsd.org/pipermail/svn-src-head/2015-February/067827.html" rel="nofollow noopener"&gt;fix&lt;/a&gt; the issue and &lt;a href="https://lists.freebsd.org/pipermail/svn-src-head/2015-February/067828.html" rel="nofollow noopener"&gt;detect it early&lt;/a&gt; if it happens again&lt;/li&gt;
&lt;li&gt;Ultimately, the problem was traced back to an issue with a recent clang import&lt;/li&gt;
&lt;li&gt;It only affected -CURRENT, not -RELEASE or -STABLE, but was definitely a bizarre bug to track down
***&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;&lt;a href="http://technoquarter.blogspot.com/p/series.html" rel="nofollow noopener"&gt;An OpenBSD mail server&lt;/a&gt;&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;There's been a recent influx of blog posts about building a BSD mail server for some reason&lt;/li&gt;
&lt;li&gt;In this fancy series of posts, the author sets up OpenSMTPD in its native OpenBSD home, whereas previous posts have been aimed at FreeBSD and Linux&lt;/li&gt;
&lt;li&gt;In addition to the usual steps, this one also covers DKIMproxy, ClamAV for scanning attachments, Dovecot for IMAP and also multiple choices of spam filtering: spamd or SpamAssassin&lt;/li&gt;
&lt;li&gt;It also shows you how to set up Roundcube for building a web interface, using the new in-base httpd&lt;/li&gt;
&lt;li&gt;That means this is more of a "complete solution" - right down to what the end users see&lt;/li&gt;
&lt;li&gt;The series is split up into categories so it's very easy to follow along step-by-step
***&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;&lt;a href="http://lists.dragonflybsd.org/pipermail/users/2015-January/207421.html" rel="nofollow noopener"&gt;How DragonFlyBSD uses git&lt;/a&gt;&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;DragonFlyBSD, along with PCBSD and EdgeBSD, uses git as its version control system for the system source code&lt;/li&gt;
&lt;li&gt;In a &lt;a href="http://lists.dragonflybsd.org/pipermail/users/2015-January/207422.html" rel="nofollow noopener"&gt;series&lt;/a&gt; of &lt;a href="http://lists.dragonflybsd.org/pipermail/users/2015-January/207424.html" rel="nofollow noopener"&gt;posts&lt;/a&gt;, Matthew Dillon (the project lead) details their internal setup&lt;/li&gt;
&lt;li&gt;They're using vanilla git over ssh, with the developers' accounts set to git-only (no shell access)&lt;/li&gt;
&lt;li&gt;The maintainers of the server are the only ones with shell access available&lt;/li&gt;
&lt;li&gt;He also details how a cron job syncs from the master to a public box that anyone can check out code from&lt;/li&gt;
&lt;li&gt;It would be interesting to hear about how other BSD projects manage their master source repository
***&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;&lt;a href="http://www.itwire.com/business-it-news/open-source/66900-fed-up-with-systemd-and-linux?-why-not-try-pc-bsd" rel="nofollow noopener"&gt;Why not try PCBSD?&lt;/a&gt;&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;ITwire, another more mainstream tech site, published a recent article about switching to PCBSD&lt;/li&gt;
&lt;li&gt;They interview a guy named Kris that we've never heard of before&lt;/li&gt;
&lt;li&gt;In the article, they touch on how easy it can potentially be for Linux users looking to switch over to the BSD side - lots of applications are exactly the same&lt;/li&gt;
&lt;li&gt;"With the growing adoption of systemd, dissatisfaction with Linux has reached proportions not seen in recent years, to the extent that people have started talking of switching to FreeBSD."&lt;/li&gt;
&lt;li&gt;If you have some friends who complain to you about systemd all the time, this might be a good article to show them
***&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;Interview - Henning Brauer - &lt;a href="mailto:henning@openbsd.org" rel="nofollow noopener"&gt;henning@openbsd.org&lt;/a&gt; / &lt;a href="https://twitter.com/henningbrauer" rel="nofollow noopener"&gt;@henningbrauer&lt;/a&gt;&lt;/h2&gt;

&lt;p&gt;&lt;a href="http://openntpd.org/" rel="nofollow noopener"&gt;OpenNTPD&lt;/a&gt; and its portable variant&lt;/p&gt;

&lt;hr&gt;

&lt;h2&gt;News Roundup&lt;/h2&gt;

&lt;h3&gt;&lt;a href="https://www.marc.info/?l=openbsd-tech&amp;amp;m=142356166731390&amp;amp;w=2" rel="nofollow noopener"&gt;Authenticated time in OpenNTPD&lt;/a&gt;&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;We recorded that interview with Henning just a few days ago, and it looks like part of it may be outdated &lt;em&gt;already&lt;/em&gt;&lt;/li&gt;
&lt;li&gt;While at the hackathon, some developers came up with an &lt;a href="https://www.marc.info/?l=openbsd-cvs&amp;amp;m=142355043928397&amp;amp;w=2" rel="nofollow noopener"&gt;alternate way&lt;/a&gt; to get authenticated NTP responses&lt;/li&gt;
&lt;li&gt;You can now add an HTTPS URL to your ntpd.conf in addition to the time server pool&lt;/li&gt;
&lt;li&gt;OpenNTPD will query it (over TLS, with CA verification) and look at the date sent in the HTTPS header&lt;/li&gt;
&lt;li&gt;It's not intended to be a direct time source, just a constraint to keep things within reason&lt;/li&gt;
&lt;li&gt;If you receive regular NTP packets that are way off from the TLS packet, those will be discarded and the server(s) marked as invalid&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.marc.info/?l=openbsd-tech&amp;amp;m=142363215730069&amp;amp;w=2" rel="nofollow noopener"&gt;Henning&lt;/a&gt; and &lt;a href="https://www.marc.info/?l=openbsd-tech&amp;amp;m=142363400330522&amp;amp;w=2" rel="nofollow noopener"&gt;Theo&lt;/a&gt; also weigh in to give some of the backstory on the idea&lt;/li&gt;
&lt;li&gt;Lots more detail can be found in Reyk's email explaining the new feature (and it's optional of course)
***&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;&lt;a href="https://mail-index.netbsd.org/netbsd-advocacy/2015/02/08/msg000678.html" rel="nofollow noopener"&gt;NetBSD at Open Source Conference 2015 Oita and Hamanako&lt;/a&gt;&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;It's been a while since we've featured one of these trip reports, but the Japanese NetBSD users group is still doing them&lt;/li&gt;
&lt;li&gt;This time the conferences were in Oita &lt;a href="https://mail-index.netbsd.org/netbsd-advocacy/2015/02/11/msg000679.html" rel="nofollow noopener"&gt;and Hamanako&lt;/a&gt;, Japan&lt;/li&gt;
&lt;li&gt;Machines running NetBSD included the CubieBoard2 Allwinner A20, Raspberry Pi and Banana Pi, Sharp NetWalker and a couple Zaurus devices&lt;/li&gt;
&lt;li&gt;As always, they took lots of pictures from the event of NetBSD on all these weird machines
***&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;&lt;a href="http://www.tobeannounced.org/2015/02/poudriere-in-a-jail/" rel="nofollow noopener"&gt;Poudriere in a jail&lt;/a&gt;&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;A common question we get about our &lt;a href="http://www.bsdnow.tv/tutorials/poudriere" rel="nofollow noopener"&gt;poudriere tutorial&lt;/a&gt; is "how do I run it in a jail?" - this blog post is about exactly that&lt;/li&gt;
&lt;li&gt;It takes you through the networking setup, zpool setup, nginx setup, making the jail and finally poking the right holes in the jail to allow poudriere to work its magic
***&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;&lt;a href="http://easyos.net/articles/bsd/freebsd/bruteblock_protection_against_bruteforce_attacks_in_ssh" rel="nofollow noopener"&gt;Bruteblock, another way to stop bruteforce&lt;/a&gt;&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;We've mentioned a few different ways to stop ssh bruteforce attempts in the past: fail2ban, denyhosts, or even just with pf's built-in rate limiting&lt;/li&gt;
&lt;li&gt;Bruteblock is a similar tool, but it's not just for ssh logins - it can do a number of other services&lt;/li&gt;
&lt;li&gt;It can also work directly with IPFW, which is a plus if you're using that as your firewall&lt;/li&gt;
&lt;li&gt;Add a few lines to your syslog.conf and bruteblock will get executed automatically&lt;/li&gt;
&lt;li&gt;The rest of the article takes you through the different settings you can configure for blocking
***&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;&lt;a href="https://www.marc.info/?l=openbsd-cvs&amp;amp;m=142325218626853&amp;amp;w=2" rel="nofollow noopener"&gt;New iwm(4) driver and cross-polination&lt;/a&gt;&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;The OpenBSD guys recently imported a new "iwm" driver for newer Intel 7260 wireless cards (commonly found in Thinkpads)&lt;/li&gt;
&lt;li&gt;NetBSD wasted no time in &lt;a href="https://mail-index.netbsd.org/source-changes/2015/02/07/msg062979.html" rel="nofollow noopener"&gt;porting it over&lt;/a&gt;, giving a bit of interesting backstory&lt;/li&gt;
&lt;li&gt;According to &lt;a href="http://www.bsdnow.tv/episodes/2013_10_23-a_brief_intorduction" rel="nofollow noopener"&gt;Antti Kantee&lt;/a&gt;, "it was created for OpenBSD by writing and porting a NetBSD driver which was developed in a rump kernel in Linux userspace"&lt;/li&gt;
&lt;li&gt;Both projects would appreciate further testing if you have the hardware and can provide useful bug reports&lt;/li&gt;
&lt;li&gt;Maybe FreeBSD and DragonFly will port it over too, or come up with something that's partially based on the code
***&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;&lt;a href="http://blog.pcbsd.org/2015/02/pc-bsd-11-0-current-images-now-available/" rel="nofollow noopener"&gt;PCBSD current images&lt;/a&gt;&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;The first PCBSD -CURRENT images should be available this weekend&lt;/li&gt;
&lt;li&gt;This image will be tagged 11.0-CURRENTFEB2015, with planned monthly updates&lt;/li&gt;
&lt;li&gt;For the more adventurous this will allow testing both FreeBSD and PCBSD bleeding edge
***&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;Feedback/Questions&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="http://slexy.org/view/s2E4NbJwzs" rel="nofollow noopener"&gt;Antonio writes in&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://slexy.org/view/s2FkxcSYKy" rel="nofollow noopener"&gt;Richard writes in&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://slexy.org/view/s217EgA1JC" rel="nofollow noopener"&gt;Charlie writes in&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://slexy.org/view/s21vlCbGDt" rel="nofollow noopener"&gt;Ben writes in&lt;/a&gt;
***&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;Mailing List Gold&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://lists.gnu.org/archive/html/emacs-devel/2015-02/msg00360.html" rel="nofollow noopener"&gt;A systematic effort&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://lists.gnu.org/archive/html/emacs-devel/2015-02/msg00457.html" rel="nofollow noopener"&gt;GCC's lunch&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://marc.info/?l=openbsd-cvs&amp;amp;m=142331891908776&amp;amp;w=2" rel="nofollow noopener"&gt;Hopes and dreams&lt;/a&gt;
***&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;Discussion&lt;/h2&gt;

&lt;h3&gt;Comparison of ways to securely tunnel your traffic&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://openvpn.net/index.php/open-source.html" rel="nofollow noopener"&gt;OpenVPN&lt;/a&gt;, &lt;a href="http://www.openiked.org/" rel="nofollow noopener"&gt;OpenBSD IKED&lt;/a&gt;, &lt;a href="https://www.freebsd.org/doc/handbook/ipsec.html" rel="nofollow noopener"&gt;FreeBSD IPSEC&lt;/a&gt;, &lt;a href="http://www.openssh.com/" rel="nofollow noopener"&gt;OpenSSH&lt;/a&gt;, &lt;a href="https://www.torproject.org/" rel="nofollow noopener"&gt;Tor&lt;/a&gt;
*** &lt;/li&gt;
&lt;/ul&gt;
</description>
  <itunes:keywords>freebsd, openbsd, netbsd, dragonflybsd, pcbsd, tutorial, howto, guide, bsd, interview, ntp, ntpd, ntimed, openntpd, time keeping, stratum, ipsec, openvpn, ssh, openiked, ike, tor, tunneling, bhws, afl-fuzz, opensmtpd</itunes:keywords>
  <content:encoded>
    <![CDATA[<p>This week, we'll be talking to Henning Brauer about OpenNTPD and its recently revived portable version. After that, we'll be discussing different ways to securely tunnel your traffic: specifically OpenVPN, IPSEC, SSH and Tor. All that and the latest news, coming up 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" rel="nofollow noopener"><img src="/images/1.png" alt="iXsystems - Enterprise Servers and Storage for Open Source"></a><a href="http://www.digitalocean.com/" title="DigitalOcean" rel="nofollow noopener"><img src="/images/2.png" alt="DigitalOcean - Simple Cloud Hosting, Built for Developers"></a><a href="http://www.tarsnap.com/bsdnow" title="Tarsnap" rel="nofollow noopener"><img src="/images/3.png" alt="Tarsnap - Online Backups for the Truly Paranoid"></a></p>

<hr>

<h2>Headlines</h2>

<h3><a href="https://lists.freebsd.org/pipermail/freebsd-current/2015-February/054295.html" rel="nofollow noopener">Strange timer bug in FreeBSD 11</a></h3>

<ul>
<li><a href="http://www.bsdnow.tv/episodes/2014_09_24-beastly_infrastructure" rel="nofollow noopener">Peter Wemm</a> wrote in to the FreeBSD -CURRENT mailing list with an interesting observation</li>
<li>Running the latest development code in the infrastructure, the clock would stop keeping time after 24 days of uptime</li>
<li>This meant things like cron and sleep would break, TCP/IP wouldn't time out or resend packets, a lot of things would break</li>
<li>A workaround until it was fixed was to reboot every 24 days, but this is BSD we're talking about - uptime is our game</li>
<li>An initial proposal was adding a CFLAG to the build options which makes makes signed arithmetic wrap</li>
<li>Peter disagreed and <a href="https://lists.freebsd.org/pipermail/freebsd-current/2015-February/054320.html" rel="nofollow noopener">gave some background</a>, offering a different patch to <a href="https://lists.freebsd.org/pipermail/svn-src-head/2015-February/067827.html" rel="nofollow noopener">fix</a> the issue and <a href="https://lists.freebsd.org/pipermail/svn-src-head/2015-February/067828.html" rel="nofollow noopener">detect it early</a> if it happens again</li>
<li>Ultimately, the problem was traced back to an issue with a recent clang import</li>
<li>It only affected -CURRENT, not -RELEASE or -STABLE, but was definitely a bizarre bug to track down
***</li>
</ul>

<h3><a href="http://technoquarter.blogspot.com/p/series.html" rel="nofollow noopener">An OpenBSD mail server</a></h3>

<ul>
<li>There's been a recent influx of blog posts about building a BSD mail server for some reason</li>
<li>In this fancy series of posts, the author sets up OpenSMTPD in its native OpenBSD home, whereas previous posts have been aimed at FreeBSD and Linux</li>
<li>In addition to the usual steps, this one also covers DKIMproxy, ClamAV for scanning attachments, Dovecot for IMAP and also multiple choices of spam filtering: spamd or SpamAssassin</li>
<li>It also shows you how to set up Roundcube for building a web interface, using the new in-base httpd</li>
<li>That means this is more of a "complete solution" - right down to what the end users see</li>
<li>The series is split up into categories so it's very easy to follow along step-by-step
***</li>
</ul>

<h3><a href="http://lists.dragonflybsd.org/pipermail/users/2015-January/207421.html" rel="nofollow noopener">How DragonFlyBSD uses git</a></h3>

<ul>
<li>DragonFlyBSD, along with PCBSD and EdgeBSD, uses git as its version control system for the system source code</li>
<li>In a <a href="http://lists.dragonflybsd.org/pipermail/users/2015-January/207422.html" rel="nofollow noopener">series</a> of <a href="http://lists.dragonflybsd.org/pipermail/users/2015-January/207424.html" rel="nofollow noopener">posts</a>, Matthew Dillon (the project lead) details their internal setup</li>
<li>They're using vanilla git over ssh, with the developers' accounts set to git-only (no shell access)</li>
<li>The maintainers of the server are the only ones with shell access available</li>
<li>He also details how a cron job syncs from the master to a public box that anyone can check out code from</li>
<li>It would be interesting to hear about how other BSD projects manage their master source repository
***</li>
</ul>

<h3><a href="http://www.itwire.com/business-it-news/open-source/66900-fed-up-with-systemd-and-linux?-why-not-try-pc-bsd" rel="nofollow noopener">Why not try PCBSD?</a></h3>

<ul>
<li>ITwire, another more mainstream tech site, published a recent article about switching to PCBSD</li>
<li>They interview a guy named Kris that we've never heard of before</li>
<li>In the article, they touch on how easy it can potentially be for Linux users looking to switch over to the BSD side - lots of applications are exactly the same</li>
<li>"With the growing adoption of systemd, dissatisfaction with Linux has reached proportions not seen in recent years, to the extent that people have started talking of switching to FreeBSD."</li>
<li>If you have some friends who complain to you about systemd all the time, this might be a good article to show them
***</li>
</ul>

<h2>Interview - Henning Brauer - <a href="mailto:henning@openbsd.org" rel="nofollow noopener">henning@openbsd.org</a> / <a href="https://twitter.com/henningbrauer" rel="nofollow noopener">@henningbrauer</a></h2>

<p><a href="http://openntpd.org/" rel="nofollow noopener">OpenNTPD</a> and its portable variant</p>

<hr>

<h2>News Roundup</h2>

<h3><a href="https://www.marc.info/?l=openbsd-tech&amp;m=142356166731390&amp;w=2" rel="nofollow noopener">Authenticated time in OpenNTPD</a></h3>

<ul>
<li>We recorded that interview with Henning just a few days ago, and it looks like part of it may be outdated <em>already</em></li>
<li>While at the hackathon, some developers came up with an <a href="https://www.marc.info/?l=openbsd-cvs&amp;m=142355043928397&amp;w=2" rel="nofollow noopener">alternate way</a> to get authenticated NTP responses</li>
<li>You can now add an HTTPS URL to your ntpd.conf in addition to the time server pool</li>
<li>OpenNTPD will query it (over TLS, with CA verification) and look at the date sent in the HTTPS header</li>
<li>It's not intended to be a direct time source, just a constraint to keep things within reason</li>
<li>If you receive regular NTP packets that are way off from the TLS packet, those will be discarded and the server(s) marked as invalid</li>
<li><a href="https://www.marc.info/?l=openbsd-tech&amp;m=142363215730069&amp;w=2" rel="nofollow noopener">Henning</a> and <a href="https://www.marc.info/?l=openbsd-tech&amp;m=142363400330522&amp;w=2" rel="nofollow noopener">Theo</a> also weigh in to give some of the backstory on the idea</li>
<li>Lots more detail can be found in Reyk's email explaining the new feature (and it's optional of course)
***</li>
</ul>

<h3><a href="https://mail-index.netbsd.org/netbsd-advocacy/2015/02/08/msg000678.html" rel="nofollow noopener">NetBSD at Open Source Conference 2015 Oita and Hamanako</a></h3>

<ul>
<li>It's been a while since we've featured one of these trip reports, but the Japanese NetBSD users group is still doing them</li>
<li>This time the conferences were in Oita <a href="https://mail-index.netbsd.org/netbsd-advocacy/2015/02/11/msg000679.html" rel="nofollow noopener">and Hamanako</a>, Japan</li>
<li>Machines running NetBSD included the CubieBoard2 Allwinner A20, Raspberry Pi and Banana Pi, Sharp NetWalker and a couple Zaurus devices</li>
<li>As always, they took lots of pictures from the event of NetBSD on all these weird machines
***</li>
</ul>

<h3><a href="http://www.tobeannounced.org/2015/02/poudriere-in-a-jail/" rel="nofollow noopener">Poudriere in a jail</a></h3>

<ul>
<li>A common question we get about our <a href="http://www.bsdnow.tv/tutorials/poudriere" rel="nofollow noopener">poudriere tutorial</a> is "how do I run it in a jail?" - this blog post is about exactly that</li>
<li>It takes you through the networking setup, zpool setup, nginx setup, making the jail and finally poking the right holes in the jail to allow poudriere to work its magic
***</li>
</ul>

<h3><a href="http://easyos.net/articles/bsd/freebsd/bruteblock_protection_against_bruteforce_attacks_in_ssh" rel="nofollow noopener">Bruteblock, another way to stop bruteforce</a></h3>

<ul>
<li>We've mentioned a few different ways to stop ssh bruteforce attempts in the past: fail2ban, denyhosts, or even just with pf's built-in rate limiting</li>
<li>Bruteblock is a similar tool, but it's not just for ssh logins - it can do a number of other services</li>
<li>It can also work directly with IPFW, which is a plus if you're using that as your firewall</li>
<li>Add a few lines to your syslog.conf and bruteblock will get executed automatically</li>
<li>The rest of the article takes you through the different settings you can configure for blocking
***</li>
</ul>

<h3><a href="https://www.marc.info/?l=openbsd-cvs&amp;m=142325218626853&amp;w=2" rel="nofollow noopener">New iwm(4) driver and cross-polination</a></h3>

<ul>
<li>The OpenBSD guys recently imported a new "iwm" driver for newer Intel 7260 wireless cards (commonly found in Thinkpads)</li>
<li>NetBSD wasted no time in <a href="https://mail-index.netbsd.org/source-changes/2015/02/07/msg062979.html" rel="nofollow noopener">porting it over</a>, giving a bit of interesting backstory</li>
<li>According to <a href="http://www.bsdnow.tv/episodes/2013_10_23-a_brief_intorduction" rel="nofollow noopener">Antti Kantee</a>, "it was created for OpenBSD by writing and porting a NetBSD driver which was developed in a rump kernel in Linux userspace"</li>
<li>Both projects would appreciate further testing if you have the hardware and can provide useful bug reports</li>
<li>Maybe FreeBSD and DragonFly will port it over too, or come up with something that's partially based on the code
***</li>
</ul>

<h3><a href="http://blog.pcbsd.org/2015/02/pc-bsd-11-0-current-images-now-available/" rel="nofollow noopener">PCBSD current images</a></h3>

<ul>
<li>The first PCBSD -CURRENT images should be available this weekend</li>
<li>This image will be tagged 11.0-CURRENTFEB2015, with planned monthly updates</li>
<li>For the more adventurous this will allow testing both FreeBSD and PCBSD bleeding edge
***</li>
</ul>

<h2>Feedback/Questions</h2>

<ul>
<li><a href="http://slexy.org/view/s2E4NbJwzs" rel="nofollow noopener">Antonio writes in</a></li>
<li><a href="http://slexy.org/view/s2FkxcSYKy" rel="nofollow noopener">Richard writes in</a></li>
<li><a href="http://slexy.org/view/s217EgA1JC" rel="nofollow noopener">Charlie writes in</a></li>
<li><a href="http://slexy.org/view/s21vlCbGDt" rel="nofollow noopener">Ben writes in</a>
***</li>
</ul>

<h2>Mailing List Gold</h2>

<ul>
<li><a href="https://lists.gnu.org/archive/html/emacs-devel/2015-02/msg00360.html" rel="nofollow noopener">A systematic effort</a></li>
<li><a href="https://lists.gnu.org/archive/html/emacs-devel/2015-02/msg00457.html" rel="nofollow noopener">GCC's lunch</a></li>
<li><a href="https://marc.info/?l=openbsd-cvs&amp;m=142331891908776&amp;w=2" rel="nofollow noopener">Hopes and dreams</a>
***</li>
</ul>

<h2>Discussion</h2>

<h3>Comparison of ways to securely tunnel your traffic</h3>

<ul>
<li><a href="https://openvpn.net/index.php/open-source.html" rel="nofollow noopener">OpenVPN</a>, <a href="http://www.openiked.org/" rel="nofollow noopener">OpenBSD IKED</a>, <a href="https://www.freebsd.org/doc/handbook/ipsec.html" rel="nofollow noopener">FreeBSD IPSEC</a>, <a href="http://www.openssh.com/" rel="nofollow noopener">OpenSSH</a>, <a href="https://www.torproject.org/" rel="nofollow noopener">Tor</a>
***</li>
</ul>]]>
  </content:encoded>
  <itunes:summary>
    <![CDATA[<p>This week, we'll be talking to Henning Brauer about OpenNTPD and its recently revived portable version. After that, we'll be discussing different ways to securely tunnel your traffic: specifically OpenVPN, IPSEC, SSH and Tor. All that and the latest news, coming up 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" rel="nofollow noopener"><img src="/images/1.png" alt="iXsystems - Enterprise Servers and Storage for Open Source"></a><a href="http://www.digitalocean.com/" title="DigitalOcean" rel="nofollow noopener"><img src="/images/2.png" alt="DigitalOcean - Simple Cloud Hosting, Built for Developers"></a><a href="http://www.tarsnap.com/bsdnow" title="Tarsnap" rel="nofollow noopener"><img src="/images/3.png" alt="Tarsnap - Online Backups for the Truly Paranoid"></a></p>

<hr>

<h2>Headlines</h2>

<h3><a href="https://lists.freebsd.org/pipermail/freebsd-current/2015-February/054295.html" rel="nofollow noopener">Strange timer bug in FreeBSD 11</a></h3>

<ul>
<li><a href="http://www.bsdnow.tv/episodes/2014_09_24-beastly_infrastructure" rel="nofollow noopener">Peter Wemm</a> wrote in to the FreeBSD -CURRENT mailing list with an interesting observation</li>
<li>Running the latest development code in the infrastructure, the clock would stop keeping time after 24 days of uptime</li>
<li>This meant things like cron and sleep would break, TCP/IP wouldn't time out or resend packets, a lot of things would break</li>
<li>A workaround until it was fixed was to reboot every 24 days, but this is BSD we're talking about - uptime is our game</li>
<li>An initial proposal was adding a CFLAG to the build options which makes makes signed arithmetic wrap</li>
<li>Peter disagreed and <a href="https://lists.freebsd.org/pipermail/freebsd-current/2015-February/054320.html" rel="nofollow noopener">gave some background</a>, offering a different patch to <a href="https://lists.freebsd.org/pipermail/svn-src-head/2015-February/067827.html" rel="nofollow noopener">fix</a> the issue and <a href="https://lists.freebsd.org/pipermail/svn-src-head/2015-February/067828.html" rel="nofollow noopener">detect it early</a> if it happens again</li>
<li>Ultimately, the problem was traced back to an issue with a recent clang import</li>
<li>It only affected -CURRENT, not -RELEASE or -STABLE, but was definitely a bizarre bug to track down
***</li>
</ul>

<h3><a href="http://technoquarter.blogspot.com/p/series.html" rel="nofollow noopener">An OpenBSD mail server</a></h3>

<ul>
<li>There's been a recent influx of blog posts about building a BSD mail server for some reason</li>
<li>In this fancy series of posts, the author sets up OpenSMTPD in its native OpenBSD home, whereas previous posts have been aimed at FreeBSD and Linux</li>
<li>In addition to the usual steps, this one also covers DKIMproxy, ClamAV for scanning attachments, Dovecot for IMAP and also multiple choices of spam filtering: spamd or SpamAssassin</li>
<li>It also shows you how to set up Roundcube for building a web interface, using the new in-base httpd</li>
<li>That means this is more of a "complete solution" - right down to what the end users see</li>
<li>The series is split up into categories so it's very easy to follow along step-by-step
***</li>
</ul>

<h3><a href="http://lists.dragonflybsd.org/pipermail/users/2015-January/207421.html" rel="nofollow noopener">How DragonFlyBSD uses git</a></h3>

<ul>
<li>DragonFlyBSD, along with PCBSD and EdgeBSD, uses git as its version control system for the system source code</li>
<li>In a <a href="http://lists.dragonflybsd.org/pipermail/users/2015-January/207422.html" rel="nofollow noopener">series</a> of <a href="http://lists.dragonflybsd.org/pipermail/users/2015-January/207424.html" rel="nofollow noopener">posts</a>, Matthew Dillon (the project lead) details their internal setup</li>
<li>They're using vanilla git over ssh, with the developers' accounts set to git-only (no shell access)</li>
<li>The maintainers of the server are the only ones with shell access available</li>
<li>He also details how a cron job syncs from the master to a public box that anyone can check out code from</li>
<li>It would be interesting to hear about how other BSD projects manage their master source repository
***</li>
</ul>

<h3><a href="http://www.itwire.com/business-it-news/open-source/66900-fed-up-with-systemd-and-linux?-why-not-try-pc-bsd" rel="nofollow noopener">Why not try PCBSD?</a></h3>

<ul>
<li>ITwire, another more mainstream tech site, published a recent article about switching to PCBSD</li>
<li>They interview a guy named Kris that we've never heard of before</li>
<li>In the article, they touch on how easy it can potentially be for Linux users looking to switch over to the BSD side - lots of applications are exactly the same</li>
<li>"With the growing adoption of systemd, dissatisfaction with Linux has reached proportions not seen in recent years, to the extent that people have started talking of switching to FreeBSD."</li>
<li>If you have some friends who complain to you about systemd all the time, this might be a good article to show them
***</li>
</ul>

<h2>Interview - Henning Brauer - <a href="mailto:henning@openbsd.org" rel="nofollow noopener">henning@openbsd.org</a> / <a href="https://twitter.com/henningbrauer" rel="nofollow noopener">@henningbrauer</a></h2>

<p><a href="http://openntpd.org/" rel="nofollow noopener">OpenNTPD</a> and its portable variant</p>

<hr>

<h2>News Roundup</h2>

<h3><a href="https://www.marc.info/?l=openbsd-tech&amp;m=142356166731390&amp;w=2" rel="nofollow noopener">Authenticated time in OpenNTPD</a></h3>

<ul>
<li>We recorded that interview with Henning just a few days ago, and it looks like part of it may be outdated <em>already</em></li>
<li>While at the hackathon, some developers came up with an <a href="https://www.marc.info/?l=openbsd-cvs&amp;m=142355043928397&amp;w=2" rel="nofollow noopener">alternate way</a> to get authenticated NTP responses</li>
<li>You can now add an HTTPS URL to your ntpd.conf in addition to the time server pool</li>
<li>OpenNTPD will query it (over TLS, with CA verification) and look at the date sent in the HTTPS header</li>
<li>It's not intended to be a direct time source, just a constraint to keep things within reason</li>
<li>If you receive regular NTP packets that are way off from the TLS packet, those will be discarded and the server(s) marked as invalid</li>
<li><a href="https://www.marc.info/?l=openbsd-tech&amp;m=142363215730069&amp;w=2" rel="nofollow noopener">Henning</a> and <a href="https://www.marc.info/?l=openbsd-tech&amp;m=142363400330522&amp;w=2" rel="nofollow noopener">Theo</a> also weigh in to give some of the backstory on the idea</li>
<li>Lots more detail can be found in Reyk's email explaining the new feature (and it's optional of course)
***</li>
</ul>

<h3><a href="https://mail-index.netbsd.org/netbsd-advocacy/2015/02/08/msg000678.html" rel="nofollow noopener">NetBSD at Open Source Conference 2015 Oita and Hamanako</a></h3>

<ul>
<li>It's been a while since we've featured one of these trip reports, but the Japanese NetBSD users group is still doing them</li>
<li>This time the conferences were in Oita <a href="https://mail-index.netbsd.org/netbsd-advocacy/2015/02/11/msg000679.html" rel="nofollow noopener">and Hamanako</a>, Japan</li>
<li>Machines running NetBSD included the CubieBoard2 Allwinner A20, Raspberry Pi and Banana Pi, Sharp NetWalker and a couple Zaurus devices</li>
<li>As always, they took lots of pictures from the event of NetBSD on all these weird machines
***</li>
</ul>

<h3><a href="http://www.tobeannounced.org/2015/02/poudriere-in-a-jail/" rel="nofollow noopener">Poudriere in a jail</a></h3>

<ul>
<li>A common question we get about our <a href="http://www.bsdnow.tv/tutorials/poudriere" rel="nofollow noopener">poudriere tutorial</a> is "how do I run it in a jail?" - this blog post is about exactly that</li>
<li>It takes you through the networking setup, zpool setup, nginx setup, making the jail and finally poking the right holes in the jail to allow poudriere to work its magic
***</li>
</ul>

<h3><a href="http://easyos.net/articles/bsd/freebsd/bruteblock_protection_against_bruteforce_attacks_in_ssh" rel="nofollow noopener">Bruteblock, another way to stop bruteforce</a></h3>

<ul>
<li>We've mentioned a few different ways to stop ssh bruteforce attempts in the past: fail2ban, denyhosts, or even just with pf's built-in rate limiting</li>
<li>Bruteblock is a similar tool, but it's not just for ssh logins - it can do a number of other services</li>
<li>It can also work directly with IPFW, which is a plus if you're using that as your firewall</li>
<li>Add a few lines to your syslog.conf and bruteblock will get executed automatically</li>
<li>The rest of the article takes you through the different settings you can configure for blocking
***</li>
</ul>

<h3><a href="https://www.marc.info/?l=openbsd-cvs&amp;m=142325218626853&amp;w=2" rel="nofollow noopener">New iwm(4) driver and cross-polination</a></h3>

<ul>
<li>The OpenBSD guys recently imported a new "iwm" driver for newer Intel 7260 wireless cards (commonly found in Thinkpads)</li>
<li>NetBSD wasted no time in <a href="https://mail-index.netbsd.org/source-changes/2015/02/07/msg062979.html" rel="nofollow noopener">porting it over</a>, giving a bit of interesting backstory</li>
<li>According to <a href="http://www.bsdnow.tv/episodes/2013_10_23-a_brief_intorduction" rel="nofollow noopener">Antti Kantee</a>, "it was created for OpenBSD by writing and porting a NetBSD driver which was developed in a rump kernel in Linux userspace"</li>
<li>Both projects would appreciate further testing if you have the hardware and can provide useful bug reports</li>
<li>Maybe FreeBSD and DragonFly will port it over too, or come up with something that's partially based on the code
***</li>
</ul>

<h3><a href="http://blog.pcbsd.org/2015/02/pc-bsd-11-0-current-images-now-available/" rel="nofollow noopener">PCBSD current images</a></h3>

<ul>
<li>The first PCBSD -CURRENT images should be available this weekend</li>
<li>This image will be tagged 11.0-CURRENTFEB2015, with planned monthly updates</li>
<li>For the more adventurous this will allow testing both FreeBSD and PCBSD bleeding edge
***</li>
</ul>

<h2>Feedback/Questions</h2>

<ul>
<li><a href="http://slexy.org/view/s2E4NbJwzs" rel="nofollow noopener">Antonio writes in</a></li>
<li><a href="http://slexy.org/view/s2FkxcSYKy" rel="nofollow noopener">Richard writes in</a></li>
<li><a href="http://slexy.org/view/s217EgA1JC" rel="nofollow noopener">Charlie writes in</a></li>
<li><a href="http://slexy.org/view/s21vlCbGDt" rel="nofollow noopener">Ben writes in</a>
***</li>
</ul>

<h2>Mailing List Gold</h2>

<ul>
<li><a href="https://lists.gnu.org/archive/html/emacs-devel/2015-02/msg00360.html" rel="nofollow noopener">A systematic effort</a></li>
<li><a href="https://lists.gnu.org/archive/html/emacs-devel/2015-02/msg00457.html" rel="nofollow noopener">GCC's lunch</a></li>
<li><a href="https://marc.info/?l=openbsd-cvs&amp;m=142331891908776&amp;w=2" rel="nofollow noopener">Hopes and dreams</a>
***</li>
</ul>

<h2>Discussion</h2>

<h3>Comparison of ways to securely tunnel your traffic</h3>

<ul>
<li><a href="https://openvpn.net/index.php/open-source.html" rel="nofollow noopener">OpenVPN</a>, <a href="http://www.openiked.org/" rel="nofollow noopener">OpenBSD IKED</a>, <a href="https://www.freebsd.org/doc/handbook/ipsec.html" rel="nofollow noopener">FreeBSD IPSEC</a>, <a href="http://www.openssh.com/" rel="nofollow noopener">OpenSSH</a>, <a href="https://www.torproject.org/" rel="nofollow noopener">Tor</a>
***</li>
</ul>]]>
  </itunes:summary>
</item>
<item>
  <title>70: Daemons in the North</title>
  <link>https://www.bsdnow.tv/70</link>
  <guid isPermaLink="false">55684d1a-97da-439b-a037-b02c8d49de70</guid>
  <pubDate>Wed, 31 Dec 2014 08:00:00 -0500</pubDate>
  <author>JT Pennington</author>
  <enclosure url="https://aphid.fireside.fm/d/1437767933/c91b88f1-e824-4815-bcb8-5227818d6010/55684d1a-97da-439b-a037-b02c8d49de70.mp3" length="60663316" type="audio/mpeg"/>
  <itunes:episodeType>full</itunes:episodeType>
  <itunes:author>JT Pennington</itunes:author>
  <itunes:subtitle>It's our last episode of 2014, and we'll be chatting with Dan Langille about the upcoming BSDCan conference. We'll find out what's planned and what sorts of presentations they're looking for. As usual, answers to viewer-submitted questions and all the week's news, coming up on BSD Now - the place to B.. SD.</itunes:subtitle>
  <itunes:duration>1:24: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>&lt;p&gt;It's our last episode of 2014, and we'll be chatting with Dan Langille about the upcoming BSDCan conference. We'll find out what's planned and what sorts of presentations they're looking for. As usual, answers to viewer-submitted questions and all the week's news, coming up on BSD Now - the place to B.. SD.&lt;/p&gt;

&lt;h2&gt;This episode was brought to you by&lt;/h2&gt;

&lt;p&gt;&lt;a href="http://www.ixsystems.com/bsdnow" title="iXsystems" rel="nofollow noopener"&gt;&lt;img src="/images/iXlogo2.png" alt="iXsystems - Enterprise servers and storage for open source"&gt;&lt;/a&gt;&lt;a href="http://www.tarsnap.com/bsdnow" title="Tarsnap" rel="nofollow noopener"&gt;&lt;img src="/images/tarsnap1.png" alt="Tarsnap - online backups for the truly paranoid"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;hr&gt;

&lt;h2&gt;Headlines&lt;/h2&gt;

&lt;h3&gt;&lt;a href="http://2014.asiabsdcon.org/timetable.html.en" rel="nofollow noopener"&gt;More conference presentation videos&lt;/a&gt;&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;Some more of the presentation videos from AsiaBSDCon are appearing online&lt;/li&gt;
&lt;li&gt;Masanobu Saitoh, &lt;a href="https://www.youtube.com/watch?v=ApruZrU5fVs" rel="nofollow noopener"&gt;Developing CPE Routers Based on NetBSD&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://www.bsdnow.tv/episodes/2014_09_03-its_hammer_time" rel="nofollow noopener"&gt;Reyk Floeter&lt;/a&gt;, &lt;a href="https://www.youtube.com/watch?v=ufeEP_hzFN0" rel="nofollow noopener"&gt;VXLAN and Cloud-based Networking with OpenBSD&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Jos Jansen, &lt;a href="https://www.youtube.com/watch?v=gOPfRQgTjNo" rel="nofollow noopener"&gt;Adapting OS X to the enterprise&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://www.bsdnow.tv/episodes/2014_04_01-edgy_bsd_users" rel="nofollow noopener"&gt;Pierre Pronchery&lt;/a&gt; &amp;amp; Guillaume Lasmayous, &lt;a href="https://www.youtube.com/watch?v=vh-TjLUj6os" rel="nofollow noopener"&gt;Carve your NetBSD&lt;/a&gt; &amp;lt;!-- skip to 5:06 for henning trolling --&amp;gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://www.bsdnow.tv/episodes/2014_01_22-tendresse_for_ten" rel="nofollow noopener"&gt;Colin Percival&lt;/a&gt;, &lt;a href="https://www.youtube.com/watch?v=jzY3m5Kv7Y8" rel="nofollow noopener"&gt;Everything you need to know about cryptography in 1 hour&lt;/a&gt; (not from AsiaBSDCon)&lt;/li&gt;
&lt;li&gt;The "bsdconferences" YouTube channel has quite a lot of interesting &lt;a href="https://www.youtube.com/user/bsdconferences/videos?sort=da&amp;amp;view=0&amp;amp;flow=grid" rel="nofollow noopener"&gt;older BSD talks&lt;/a&gt; too - you may want to go back and watch them if you haven't already
***&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;&lt;a href="https://www.marc.info/?l=openbsd-cvs&amp;amp;m=141922027318727&amp;amp;w=2" rel="nofollow noopener"&gt;OpenBSD PIE enhancements&lt;/a&gt;&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://en.wikipedia.org/wiki/Address_space_layout_randomization" rel="nofollow noopener"&gt;ASLR&lt;/a&gt; and &lt;a href="https://en.wikipedia.org/wiki/Position-independent_executable" rel="nofollow noopener"&gt;PIE&lt;/a&gt; are great security features that OpenBSD has had enabled by default for a long time, in both the base system and ports, but they have one inherent problem&lt;/li&gt;
&lt;li&gt;They only work with &lt;em&gt;dynamic&lt;/em&gt; libraries and binaries, so if you have any static binaries, they don't get the same treatment&lt;/li&gt;
&lt;li&gt;For example, the default shells (and many other things in /bin and /sbin) are statically linked&lt;/li&gt;
&lt;li&gt;In the case of the static ones, you can always predict the memory layout, which is very bad and sort of &lt;a href="https://en.wikipedia.org/wiki/Return-oriented_programming" rel="nofollow noopener"&gt;defeats the whole purpose&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;With this and a few &lt;a href="https://www.marc.info/?l=openbsd-cvs&amp;amp;m=141927571832106&amp;amp;w=2" rel="nofollow noopener"&gt;related commits&lt;/a&gt;, OpenBSD fixes this by introducing &lt;strong&gt;static self-relocation&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;More and more CPU architectures are being tested and getting support too; this isn't just for amd64 and i386 - VAX users can rest easy&lt;/li&gt;
&lt;li&gt;It'll be available in 5.7 in May, or you can use a &lt;a href="http://www.openbsd.org/faq/faq5.html#BldBinary" rel="nofollow noopener"&gt;-current snapshot&lt;/a&gt; if you want to get a &lt;em&gt;slice&lt;/em&gt; of the action now
***&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;&lt;a href="https://www.freebsdfoundation.org/press/2014dec-newsletter.html" rel="nofollow noopener"&gt;FreeBSD foundation semi-annual newsletter&lt;/a&gt;&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;The FreeBSD foundation publishes a huge newsletter twice a year, detailing their funded projects and some community activities&lt;/li&gt;
&lt;li&gt;As always, it starts with a letter from the president of the foundation - this time it's about encouraging students and new developers to get involved&lt;/li&gt;
&lt;li&gt;The article also has a fundraising update with a list of sponsored projects, and they note that the donations meter has changed from dollars to number of donors (since they exceeded the goal already)&lt;/li&gt;
&lt;li&gt;You can read summaries of all the BSD conferences of 2014 and see a list of upcoming ones next year too&lt;/li&gt;
&lt;li&gt;There are also sections about the &lt;a href="http://www.bsdnow.tv/episodes/2014_01_29-journaled_news_updates" rel="nofollow noopener"&gt;FreeBSD Journal&lt;/a&gt;'s progress, a new staff member and a testimonial from NetApp&lt;/li&gt;
&lt;li&gt;It's a very long report, so dedicate some time to read all the way through it&lt;/li&gt;
&lt;li&gt;This year was pretty great for BSD: both the FreeBSD and OpenBSD foundations exceeded their goals and the NetBSD foundation came really close too&lt;/li&gt;
&lt;li&gt;As we go into 2015, consider donating to &lt;a href="https://www.freebsdfoundation.org/donate" rel="nofollow noopener"&gt;whichever&lt;/a&gt; &lt;a href="http://www.openbsdfoundation.org/donations.html" rel="nofollow noopener"&gt;BSD&lt;/a&gt; &lt;a href="https://www.netbsd.org/donations/" rel="nofollow noopener"&gt;you&lt;/a&gt; &lt;a href="http://www.dragonflybsd.org/donations/" rel="nofollow noopener"&gt;use&lt;/a&gt;, it really can make a difference
***&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;&lt;a href="https://www.marc.info/?l=openbsd-cvs&amp;amp;m=141920089614758&amp;amp;w=4" rel="nofollow noopener"&gt;Modernizing OpenSSH fingerprints&lt;/a&gt;&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;When you connect to a server for the first time, you'll get what's called a fingerprint of the host's public key - this is used to verify that you're actually talking to the same server you intended to&lt;/li&gt;
&lt;li&gt;Up until now, the key fingerprints have been an MD5 hash, displayed as hex&lt;/li&gt;
&lt;li&gt;This &lt;a href="https://lists.mindrot.org/pipermail/openssh-unix-dev/2014-November/033117.html" rel="nofollow noopener"&gt;can be problematic&lt;/a&gt;, especially for larger key types like RSA that give lots of wiggle room for collisions, as an attacker could generate a fake host key that gives the same MD5 string as the one you wanted to connect to&lt;/li&gt;
&lt;li&gt;This new change replaces the default MD5 and hex with a base64-encoded SHA256 fingerprint&lt;/li&gt;
&lt;li&gt;You can add a "FingerprintHash" line in your ssh_config to force using only the new type&lt;/li&gt;
&lt;li&gt;There's also a &lt;a href="https://www.marc.info/?l=openbsd-cvs&amp;amp;m=141923470520906&amp;amp;w=2" rel="nofollow noopener"&gt;new option&lt;/a&gt; to require users to authenticate with &lt;strong&gt;more than one&lt;/strong&gt; public key, so you can really lock down login access to your servers - also useful if you're not 100% confident in any single key type&lt;/li&gt;
&lt;li&gt;The new options should be in the upcoming 6.8 release
***&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;Interview - Dan Langille - &lt;a href="mailto:info@bsdcan.org" rel="nofollow noopener"&gt;info@bsdcan.org&lt;/a&gt; / &lt;a href="https://twitter.com/bsdcan" rel="nofollow noopener"&gt;@bsdcan&lt;/a&gt;&lt;/h2&gt;

&lt;p&gt;Plans for the BSDCan 2015 conference&lt;/p&gt;

&lt;hr&gt;

&lt;h2&gt;News Roundup&lt;/h2&gt;

&lt;h3&gt;&lt;a href="https://github.com/bsdphk/Ntimed" rel="nofollow noopener"&gt;Introducing ntimed, a new NTP daemon&lt;/a&gt;&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;As we've mentioned before in &lt;a href="http://www.bsdnow.tv/tutorials/ntpd" rel="nofollow noopener"&gt;our tutorials&lt;/a&gt;, there are two main daemons for the Network Time Protocol - ISC's NTPd and OpenBSD's OpenNTPD&lt;/li&gt;
&lt;li&gt;With all the recent security problems with ISC's NTPd, &lt;a href="http://www.bsdnow.tv/episodes/2013_10_16-go_directly_to_jail" rel="nofollow noopener"&gt;Poul-Henning Kamp&lt;/a&gt; has been working on a third NTP daemon&lt;/li&gt;
&lt;li&gt;It's called "ntimed" and you can try out a preview version of it right now - it's &lt;a href="https://www.freshports.org/net/ntimed/" rel="nofollow noopener"&gt;in FreeBSD ports&lt;/a&gt; or on Github&lt;/li&gt;
&lt;li&gt;PHK also has a few &lt;a href="http://phk.freebsd.dk/time/" rel="nofollow noopener"&gt;blog entries&lt;/a&gt; about the project, including status updates
***&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;&lt;a href="http://mdocml.bsd.lv/openbsd_projects.html" rel="nofollow noopener"&gt;OpenBSD-maintained projects list&lt;/a&gt;&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;There was recently a read on the &lt;a href="https://www.marc.info/?t=141961588200003&amp;amp;r=1&amp;amp;w=2" rel="nofollow noopener"&gt;misc mailing list&lt;/a&gt; asking about different projects started by OpenBSD developers&lt;/li&gt;
&lt;li&gt;The initial list had marks for which software had portable versions to other operating systems (OpenSSH being the most popular example)&lt;/li&gt;
&lt;li&gt;A developer compiled a new list from all of the replies to that thread into a nice organized webpage&lt;/li&gt;
&lt;li&gt;Most people are only familiar with things like OpenSSH, OpenSMTPD, OpenNTPD and more recently LibreSSL, but there are quite a lot more&lt;/li&gt;
&lt;li&gt;This page also serves as a good history lesson for BSD in general: FreeBSD and others have ported some things over, while a couple OpenBSD tools were born from forks of FreeBSD tools (mergemaster, pkg tools, portscout)
***&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;&lt;a href="https://forums.freebsd.org/threads/howto-monitor-network-traffic-with-netflow-nfdump-nfsen-on-freebsd.49724/" rel="nofollow noopener"&gt;Monitoring network traffic with FreeBSD&lt;/a&gt;&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;If you've ever been curious about monitoring network traffic on your FreeBSD boxes, this forum post may be exactly the thing for you&lt;/li&gt;
&lt;li&gt;It'll show you how to combine the Netflow, NfDump and NfSen suite of tools to get some pretty detailed network stats (and of course put them into a fancy webpage)&lt;/li&gt;
&lt;li&gt;This is especially useful for finding out what was going on at a certain point in time, for example if you had a traffic spike
***&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;&lt;a href="http://www.protoc.org/blog/2014/12/22/trapping-spammers-with-the-openbsd-spam-deferral-daemon" rel="nofollow noopener"&gt;Trapping spammers with spamd&lt;/a&gt;&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;This is a blog post about OpenBSD's &lt;a href="https://en.wikipedia.org/wiki/Spamd" rel="nofollow noopener"&gt;spamd&lt;/a&gt; - a spam email deferral daemon - and how to use it for your mail&lt;/li&gt;
&lt;li&gt;It gives some background on the greylisting approach to spam, rather than just a typical host blacklist&lt;/li&gt;
&lt;li&gt;"Greylisting is a method of defending e-mail users against spam. A mail transfer agent (MTA) using greylisting will "temporarily reject" any email from a sender it does not recognize. If the sender re-attempts mail delivery at a later time, the sender may be allowed to continue the mail delivery conversation."&lt;/li&gt;
&lt;li&gt;The post also shows how to combine it with PF and other tools for a pretty fancy mail setup&lt;/li&gt;
&lt;li&gt;You can find spamd in the OpenBSD &lt;a href="http://www.openbsd.org/cgi-bin/man.cgi/OpenBSD-current/man8/spamd.8" rel="nofollow noopener"&gt;base system&lt;/a&gt;, or use it &lt;a href="https://www.freshports.org/mail/spamd" rel="nofollow noopener"&gt;with FreeBSD&lt;/a&gt; &lt;a href="http://pkgsrc.se/mail/spamd" rel="nofollow noopener"&gt;or NetBSD&lt;/a&gt; via ports and pkgsrc&lt;/li&gt;
&lt;li&gt;You might also want to go back and listen to &lt;a href="https://archive.org/details/bsdtalk068" rel="nofollow noopener"&gt;BSDTalk episode 68&lt;/a&gt;, where Will talks to Bob Beck about spamd
***&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;Feedback/Questions&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="http://slexy.org/view/s20rUK9XVJ" rel="nofollow noopener"&gt;Sean writes in&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://slexy.org/view/s20nfzIuT2" rel="nofollow noopener"&gt;Brandon writes in&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://slexy.org/view/s20wCBhFLO" rel="nofollow noopener"&gt;Anders writes in&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://slexy.org/view/s20xGrBIyl" rel="nofollow noopener"&gt;David writes in&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://slexy.org/view/s2QHRaiZJW" rel="nofollow noopener"&gt;Kyle writes in&lt;/a&gt;
***&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;Mailing List Gold&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://www.marc.info/?l=openbsd-tech&amp;amp;m=141903858708123&amp;amp;w=2" rel="nofollow noopener"&gt;NTP code comparison&lt;/a&gt; - &lt;a href="https://www.marc.info/?l=openbsd-tech&amp;amp;m=141905854411370&amp;amp;w=2" rel="nofollow noopener"&gt;192870 vs. 2898&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://lists.freebsd.org/pipermail/freebsd-hackers/2014-December/046741.html" rel="nofollow noopener"&gt;NICs have feelings too&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.marc.info/?l=openbsd-ports&amp;amp;m=141998130824977&amp;amp;w=2" rel="nofollow noopener"&gt;Just think about it&lt;/a&gt;
*** &lt;/li&gt;
&lt;/ul&gt;
</description>
  <itunes:keywords>freebsd, openbsd, netbsd, dragonflybsd, pcbsd, tutorial, howto, guide, bsd, interview, bsdcan, call for papers, conference, talk, presentation, vxlan, static, pie, openssh, ntimed, ntp, openntpd</itunes:keywords>
  <content:encoded>
    <![CDATA[<p>It's our last episode of 2014, and we'll be chatting with Dan Langille about the upcoming BSDCan conference. We'll find out what's planned and what sorts of presentations they're looking for. As usual, answers to viewer-submitted questions and all the week's news, coming up 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" rel="nofollow noopener"><img src="/images/iXlogo2.png" alt="iXsystems - Enterprise servers and storage for open source"></a><a href="http://www.tarsnap.com/bsdnow" title="Tarsnap" rel="nofollow noopener"><img src="/images/tarsnap1.png" alt="Tarsnap - online backups for the truly paranoid"></a></p>

<hr>

<h2>Headlines</h2>

<h3><a href="http://2014.asiabsdcon.org/timetable.html.en" rel="nofollow noopener">More conference presentation videos</a></h3>

<ul>
<li>Some more of the presentation videos from AsiaBSDCon are appearing online</li>
<li>Masanobu Saitoh, <a href="https://www.youtube.com/watch?v=ApruZrU5fVs" rel="nofollow noopener">Developing CPE Routers Based on NetBSD</a></li>
<li><a href="http://www.bsdnow.tv/episodes/2014_09_03-its_hammer_time" rel="nofollow noopener">Reyk Floeter</a>, <a href="https://www.youtube.com/watch?v=ufeEP_hzFN0" rel="nofollow noopener">VXLAN and Cloud-based Networking with OpenBSD</a></li>
<li>Jos Jansen, <a href="https://www.youtube.com/watch?v=gOPfRQgTjNo" rel="nofollow noopener">Adapting OS X to the enterprise</a></li>
<li><a href="http://www.bsdnow.tv/episodes/2014_04_01-edgy_bsd_users" rel="nofollow noopener">Pierre Pronchery</a> &amp; Guillaume Lasmayous, <a href="https://www.youtube.com/watch?v=vh-TjLUj6os" rel="nofollow noopener">Carve your NetBSD</a> &lt;!-- skip to 5:06 for henning trolling --&gt;</li>
<li><a href="http://www.bsdnow.tv/episodes/2014_01_22-tendresse_for_ten" rel="nofollow noopener">Colin Percival</a>, <a href="https://www.youtube.com/watch?v=jzY3m5Kv7Y8" rel="nofollow noopener">Everything you need to know about cryptography in 1 hour</a> (not from AsiaBSDCon)</li>
<li>The "bsdconferences" YouTube channel has quite a lot of interesting <a href="https://www.youtube.com/user/bsdconferences/videos?sort=da&amp;view=0&amp;flow=grid" rel="nofollow noopener">older BSD talks</a> too - you may want to go back and watch them if you haven't already
***</li>
</ul>

<h3><a href="https://www.marc.info/?l=openbsd-cvs&amp;m=141922027318727&amp;w=2" rel="nofollow noopener">OpenBSD PIE enhancements</a></h3>

<ul>
<li><a href="https://en.wikipedia.org/wiki/Address_space_layout_randomization" rel="nofollow noopener">ASLR</a> and <a href="https://en.wikipedia.org/wiki/Position-independent_executable" rel="nofollow noopener">PIE</a> are great security features that OpenBSD has had enabled by default for a long time, in both the base system and ports, but they have one inherent problem</li>
<li>They only work with <em>dynamic</em> libraries and binaries, so if you have any static binaries, they don't get the same treatment</li>
<li>For example, the default shells (and many other things in /bin and /sbin) are statically linked</li>
<li>In the case of the static ones, you can always predict the memory layout, which is very bad and sort of <a href="https://en.wikipedia.org/wiki/Return-oriented_programming" rel="nofollow noopener">defeats the whole purpose</a></li>
<li>With this and a few <a href="https://www.marc.info/?l=openbsd-cvs&amp;m=141927571832106&amp;w=2" rel="nofollow noopener">related commits</a>, OpenBSD fixes this by introducing <strong>static self-relocation</strong></li>
<li>More and more CPU architectures are being tested and getting support too; this isn't just for amd64 and i386 - VAX users can rest easy</li>
<li>It'll be available in 5.7 in May, or you can use a <a href="http://www.openbsd.org/faq/faq5.html#BldBinary" rel="nofollow noopener">-current snapshot</a> if you want to get a <em>slice</em> of the action now
***</li>
</ul>

<h3><a href="https://www.freebsdfoundation.org/press/2014dec-newsletter.html" rel="nofollow noopener">FreeBSD foundation semi-annual newsletter</a></h3>

<ul>
<li>The FreeBSD foundation publishes a huge newsletter twice a year, detailing their funded projects and some community activities</li>
<li>As always, it starts with a letter from the president of the foundation - this time it's about encouraging students and new developers to get involved</li>
<li>The article also has a fundraising update with a list of sponsored projects, and they note that the donations meter has changed from dollars to number of donors (since they exceeded the goal already)</li>
<li>You can read summaries of all the BSD conferences of 2014 and see a list of upcoming ones next year too</li>
<li>There are also sections about the <a href="http://www.bsdnow.tv/episodes/2014_01_29-journaled_news_updates" rel="nofollow noopener">FreeBSD Journal</a>'s progress, a new staff member and a testimonial from NetApp</li>
<li>It's a very long report, so dedicate some time to read all the way through it</li>
<li>This year was pretty great for BSD: both the FreeBSD and OpenBSD foundations exceeded their goals and the NetBSD foundation came really close too</li>
<li>As we go into 2015, consider donating to <a href="https://www.freebsdfoundation.org/donate" rel="nofollow noopener">whichever</a> <a href="http://www.openbsdfoundation.org/donations.html" rel="nofollow noopener">BSD</a> <a href="https://www.netbsd.org/donations/" rel="nofollow noopener">you</a> <a href="http://www.dragonflybsd.org/donations/" rel="nofollow noopener">use</a>, it really can make a difference
***</li>
</ul>

<h3><a href="https://www.marc.info/?l=openbsd-cvs&amp;m=141920089614758&amp;w=4" rel="nofollow noopener">Modernizing OpenSSH fingerprints</a></h3>

<ul>
<li>When you connect to a server for the first time, you'll get what's called a fingerprint of the host's public key - this is used to verify that you're actually talking to the same server you intended to</li>
<li>Up until now, the key fingerprints have been an MD5 hash, displayed as hex</li>
<li>This <a href="https://lists.mindrot.org/pipermail/openssh-unix-dev/2014-November/033117.html" rel="nofollow noopener">can be problematic</a>, especially for larger key types like RSA that give lots of wiggle room for collisions, as an attacker could generate a fake host key that gives the same MD5 string as the one you wanted to connect to</li>
<li>This new change replaces the default MD5 and hex with a base64-encoded SHA256 fingerprint</li>
<li>You can add a "FingerprintHash" line in your ssh_config to force using only the new type</li>
<li>There's also a <a href="https://www.marc.info/?l=openbsd-cvs&amp;m=141923470520906&amp;w=2" rel="nofollow noopener">new option</a> to require users to authenticate with <strong>more than one</strong> public key, so you can really lock down login access to your servers - also useful if you're not 100% confident in any single key type</li>
<li>The new options should be in the upcoming 6.8 release
***</li>
</ul>

<h2>Interview - Dan Langille - <a href="mailto:info@bsdcan.org" rel="nofollow noopener">info@bsdcan.org</a> / <a href="https://twitter.com/bsdcan" rel="nofollow noopener">@bsdcan</a></h2>

<p>Plans for the BSDCan 2015 conference</p>

<hr>

<h2>News Roundup</h2>

<h3><a href="https://github.com/bsdphk/Ntimed" rel="nofollow noopener">Introducing ntimed, a new NTP daemon</a></h3>

<ul>
<li>As we've mentioned before in <a href="http://www.bsdnow.tv/tutorials/ntpd" rel="nofollow noopener">our tutorials</a>, there are two main daemons for the Network Time Protocol - ISC's NTPd and OpenBSD's OpenNTPD</li>
<li>With all the recent security problems with ISC's NTPd, <a href="http://www.bsdnow.tv/episodes/2013_10_16-go_directly_to_jail" rel="nofollow noopener">Poul-Henning Kamp</a> has been working on a third NTP daemon</li>
<li>It's called "ntimed" and you can try out a preview version of it right now - it's <a href="https://www.freshports.org/net/ntimed/" rel="nofollow noopener">in FreeBSD ports</a> or on Github</li>
<li>PHK also has a few <a href="http://phk.freebsd.dk/time/" rel="nofollow noopener">blog entries</a> about the project, including status updates
***</li>
</ul>

<h3><a href="http://mdocml.bsd.lv/openbsd_projects.html" rel="nofollow noopener">OpenBSD-maintained projects list</a></h3>

<ul>
<li>There was recently a read on the <a href="https://www.marc.info/?t=141961588200003&amp;r=1&amp;w=2" rel="nofollow noopener">misc mailing list</a> asking about different projects started by OpenBSD developers</li>
<li>The initial list had marks for which software had portable versions to other operating systems (OpenSSH being the most popular example)</li>
<li>A developer compiled a new list from all of the replies to that thread into a nice organized webpage</li>
<li>Most people are only familiar with things like OpenSSH, OpenSMTPD, OpenNTPD and more recently LibreSSL, but there are quite a lot more</li>
<li>This page also serves as a good history lesson for BSD in general: FreeBSD and others have ported some things over, while a couple OpenBSD tools were born from forks of FreeBSD tools (mergemaster, pkg tools, portscout)
***</li>
</ul>

<h3><a href="https://forums.freebsd.org/threads/howto-monitor-network-traffic-with-netflow-nfdump-nfsen-on-freebsd.49724/" rel="nofollow noopener">Monitoring network traffic with FreeBSD</a></h3>

<ul>
<li>If you've ever been curious about monitoring network traffic on your FreeBSD boxes, this forum post may be exactly the thing for you</li>
<li>It'll show you how to combine the Netflow, NfDump and NfSen suite of tools to get some pretty detailed network stats (and of course put them into a fancy webpage)</li>
<li>This is especially useful for finding out what was going on at a certain point in time, for example if you had a traffic spike
***</li>
</ul>

<h3><a href="http://www.protoc.org/blog/2014/12/22/trapping-spammers-with-the-openbsd-spam-deferral-daemon" rel="nofollow noopener">Trapping spammers with spamd</a></h3>

<ul>
<li>This is a blog post about OpenBSD's <a href="https://en.wikipedia.org/wiki/Spamd" rel="nofollow noopener">spamd</a> - a spam email deferral daemon - and how to use it for your mail</li>
<li>It gives some background on the greylisting approach to spam, rather than just a typical host blacklist</li>
<li>"Greylisting is a method of defending e-mail users against spam. A mail transfer agent (MTA) using greylisting will "temporarily reject" any email from a sender it does not recognize. If the sender re-attempts mail delivery at a later time, the sender may be allowed to continue the mail delivery conversation."</li>
<li>The post also shows how to combine it with PF and other tools for a pretty fancy mail setup</li>
<li>You can find spamd in the OpenBSD <a href="http://www.openbsd.org/cgi-bin/man.cgi/OpenBSD-current/man8/spamd.8" rel="nofollow noopener">base system</a>, or use it <a href="https://www.freshports.org/mail/spamd" rel="nofollow noopener">with FreeBSD</a> <a href="http://pkgsrc.se/mail/spamd" rel="nofollow noopener">or NetBSD</a> via ports and pkgsrc</li>
<li>You might also want to go back and listen to <a href="https://archive.org/details/bsdtalk068" rel="nofollow noopener">BSDTalk episode 68</a>, where Will talks to Bob Beck about spamd
***</li>
</ul>

<h2>Feedback/Questions</h2>

<ul>
<li><a href="http://slexy.org/view/s20rUK9XVJ" rel="nofollow noopener">Sean writes in</a></li>
<li><a href="http://slexy.org/view/s20nfzIuT2" rel="nofollow noopener">Brandon writes in</a></li>
<li><a href="http://slexy.org/view/s20wCBhFLO" rel="nofollow noopener">Anders writes in</a></li>
<li><a href="http://slexy.org/view/s20xGrBIyl" rel="nofollow noopener">David writes in</a></li>
<li><a href="http://slexy.org/view/s2QHRaiZJW" rel="nofollow noopener">Kyle writes in</a>
***</li>
</ul>

<h2>Mailing List Gold</h2>

<ul>
<li><a href="https://www.marc.info/?l=openbsd-tech&amp;m=141903858708123&amp;w=2" rel="nofollow noopener">NTP code comparison</a> - <a href="https://www.marc.info/?l=openbsd-tech&amp;m=141905854411370&amp;w=2" rel="nofollow noopener">192870 vs. 2898</a></li>
<li><a href="https://lists.freebsd.org/pipermail/freebsd-hackers/2014-December/046741.html" rel="nofollow noopener">NICs have feelings too</a></li>
<li><a href="https://www.marc.info/?l=openbsd-ports&amp;m=141998130824977&amp;w=2" rel="nofollow noopener">Just think about it</a>
***</li>
</ul>]]>
  </content:encoded>
  <itunes:summary>
    <![CDATA[<p>It's our last episode of 2014, and we'll be chatting with Dan Langille about the upcoming BSDCan conference. We'll find out what's planned and what sorts of presentations they're looking for. As usual, answers to viewer-submitted questions and all the week's news, coming up 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" rel="nofollow noopener"><img src="/images/iXlogo2.png" alt="iXsystems - Enterprise servers and storage for open source"></a><a href="http://www.tarsnap.com/bsdnow" title="Tarsnap" rel="nofollow noopener"><img src="/images/tarsnap1.png" alt="Tarsnap - online backups for the truly paranoid"></a></p>

<hr>

<h2>Headlines</h2>

<h3><a href="http://2014.asiabsdcon.org/timetable.html.en" rel="nofollow noopener">More conference presentation videos</a></h3>

<ul>
<li>Some more of the presentation videos from AsiaBSDCon are appearing online</li>
<li>Masanobu Saitoh, <a href="https://www.youtube.com/watch?v=ApruZrU5fVs" rel="nofollow noopener">Developing CPE Routers Based on NetBSD</a></li>
<li><a href="http://www.bsdnow.tv/episodes/2014_09_03-its_hammer_time" rel="nofollow noopener">Reyk Floeter</a>, <a href="https://www.youtube.com/watch?v=ufeEP_hzFN0" rel="nofollow noopener">VXLAN and Cloud-based Networking with OpenBSD</a></li>
<li>Jos Jansen, <a href="https://www.youtube.com/watch?v=gOPfRQgTjNo" rel="nofollow noopener">Adapting OS X to the enterprise</a></li>
<li><a href="http://www.bsdnow.tv/episodes/2014_04_01-edgy_bsd_users" rel="nofollow noopener">Pierre Pronchery</a> &amp; Guillaume Lasmayous, <a href="https://www.youtube.com/watch?v=vh-TjLUj6os" rel="nofollow noopener">Carve your NetBSD</a> &lt;!-- skip to 5:06 for henning trolling --&gt;</li>
<li><a href="http://www.bsdnow.tv/episodes/2014_01_22-tendresse_for_ten" rel="nofollow noopener">Colin Percival</a>, <a href="https://www.youtube.com/watch?v=jzY3m5Kv7Y8" rel="nofollow noopener">Everything you need to know about cryptography in 1 hour</a> (not from AsiaBSDCon)</li>
<li>The "bsdconferences" YouTube channel has quite a lot of interesting <a href="https://www.youtube.com/user/bsdconferences/videos?sort=da&amp;view=0&amp;flow=grid" rel="nofollow noopener">older BSD talks</a> too - you may want to go back and watch them if you haven't already
***</li>
</ul>

<h3><a href="https://www.marc.info/?l=openbsd-cvs&amp;m=141922027318727&amp;w=2" rel="nofollow noopener">OpenBSD PIE enhancements</a></h3>

<ul>
<li><a href="https://en.wikipedia.org/wiki/Address_space_layout_randomization" rel="nofollow noopener">ASLR</a> and <a href="https://en.wikipedia.org/wiki/Position-independent_executable" rel="nofollow noopener">PIE</a> are great security features that OpenBSD has had enabled by default for a long time, in both the base system and ports, but they have one inherent problem</li>
<li>They only work with <em>dynamic</em> libraries and binaries, so if you have any static binaries, they don't get the same treatment</li>
<li>For example, the default shells (and many other things in /bin and /sbin) are statically linked</li>
<li>In the case of the static ones, you can always predict the memory layout, which is very bad and sort of <a href="https://en.wikipedia.org/wiki/Return-oriented_programming" rel="nofollow noopener">defeats the whole purpose</a></li>
<li>With this and a few <a href="https://www.marc.info/?l=openbsd-cvs&amp;m=141927571832106&amp;w=2" rel="nofollow noopener">related commits</a>, OpenBSD fixes this by introducing <strong>static self-relocation</strong></li>
<li>More and more CPU architectures are being tested and getting support too; this isn't just for amd64 and i386 - VAX users can rest easy</li>
<li>It'll be available in 5.7 in May, or you can use a <a href="http://www.openbsd.org/faq/faq5.html#BldBinary" rel="nofollow noopener">-current snapshot</a> if you want to get a <em>slice</em> of the action now
***</li>
</ul>

<h3><a href="https://www.freebsdfoundation.org/press/2014dec-newsletter.html" rel="nofollow noopener">FreeBSD foundation semi-annual newsletter</a></h3>

<ul>
<li>The FreeBSD foundation publishes a huge newsletter twice a year, detailing their funded projects and some community activities</li>
<li>As always, it starts with a letter from the president of the foundation - this time it's about encouraging students and new developers to get involved</li>
<li>The article also has a fundraising update with a list of sponsored projects, and they note that the donations meter has changed from dollars to number of donors (since they exceeded the goal already)</li>
<li>You can read summaries of all the BSD conferences of 2014 and see a list of upcoming ones next year too</li>
<li>There are also sections about the <a href="http://www.bsdnow.tv/episodes/2014_01_29-journaled_news_updates" rel="nofollow noopener">FreeBSD Journal</a>'s progress, a new staff member and a testimonial from NetApp</li>
<li>It's a very long report, so dedicate some time to read all the way through it</li>
<li>This year was pretty great for BSD: both the FreeBSD and OpenBSD foundations exceeded their goals and the NetBSD foundation came really close too</li>
<li>As we go into 2015, consider donating to <a href="https://www.freebsdfoundation.org/donate" rel="nofollow noopener">whichever</a> <a href="http://www.openbsdfoundation.org/donations.html" rel="nofollow noopener">BSD</a> <a href="https://www.netbsd.org/donations/" rel="nofollow noopener">you</a> <a href="http://www.dragonflybsd.org/donations/" rel="nofollow noopener">use</a>, it really can make a difference
***</li>
</ul>

<h3><a href="https://www.marc.info/?l=openbsd-cvs&amp;m=141920089614758&amp;w=4" rel="nofollow noopener">Modernizing OpenSSH fingerprints</a></h3>

<ul>
<li>When you connect to a server for the first time, you'll get what's called a fingerprint of the host's public key - this is used to verify that you're actually talking to the same server you intended to</li>
<li>Up until now, the key fingerprints have been an MD5 hash, displayed as hex</li>
<li>This <a href="https://lists.mindrot.org/pipermail/openssh-unix-dev/2014-November/033117.html" rel="nofollow noopener">can be problematic</a>, especially for larger key types like RSA that give lots of wiggle room for collisions, as an attacker could generate a fake host key that gives the same MD5 string as the one you wanted to connect to</li>
<li>This new change replaces the default MD5 and hex with a base64-encoded SHA256 fingerprint</li>
<li>You can add a "FingerprintHash" line in your ssh_config to force using only the new type</li>
<li>There's also a <a href="https://www.marc.info/?l=openbsd-cvs&amp;m=141923470520906&amp;w=2" rel="nofollow noopener">new option</a> to require users to authenticate with <strong>more than one</strong> public key, so you can really lock down login access to your servers - also useful if you're not 100% confident in any single key type</li>
<li>The new options should be in the upcoming 6.8 release
***</li>
</ul>

<h2>Interview - Dan Langille - <a href="mailto:info@bsdcan.org" rel="nofollow noopener">info@bsdcan.org</a> / <a href="https://twitter.com/bsdcan" rel="nofollow noopener">@bsdcan</a></h2>

<p>Plans for the BSDCan 2015 conference</p>

<hr>

<h2>News Roundup</h2>

<h3><a href="https://github.com/bsdphk/Ntimed" rel="nofollow noopener">Introducing ntimed, a new NTP daemon</a></h3>

<ul>
<li>As we've mentioned before in <a href="http://www.bsdnow.tv/tutorials/ntpd" rel="nofollow noopener">our tutorials</a>, there are two main daemons for the Network Time Protocol - ISC's NTPd and OpenBSD's OpenNTPD</li>
<li>With all the recent security problems with ISC's NTPd, <a href="http://www.bsdnow.tv/episodes/2013_10_16-go_directly_to_jail" rel="nofollow noopener">Poul-Henning Kamp</a> has been working on a third NTP daemon</li>
<li>It's called "ntimed" and you can try out a preview version of it right now - it's <a href="https://www.freshports.org/net/ntimed/" rel="nofollow noopener">in FreeBSD ports</a> or on Github</li>
<li>PHK also has a few <a href="http://phk.freebsd.dk/time/" rel="nofollow noopener">blog entries</a> about the project, including status updates
***</li>
</ul>

<h3><a href="http://mdocml.bsd.lv/openbsd_projects.html" rel="nofollow noopener">OpenBSD-maintained projects list</a></h3>

<ul>
<li>There was recently a read on the <a href="https://www.marc.info/?t=141961588200003&amp;r=1&amp;w=2" rel="nofollow noopener">misc mailing list</a> asking about different projects started by OpenBSD developers</li>
<li>The initial list had marks for which software had portable versions to other operating systems (OpenSSH being the most popular example)</li>
<li>A developer compiled a new list from all of the replies to that thread into a nice organized webpage</li>
<li>Most people are only familiar with things like OpenSSH, OpenSMTPD, OpenNTPD and more recently LibreSSL, but there are quite a lot more</li>
<li>This page also serves as a good history lesson for BSD in general: FreeBSD and others have ported some things over, while a couple OpenBSD tools were born from forks of FreeBSD tools (mergemaster, pkg tools, portscout)
***</li>
</ul>

<h3><a href="https://forums.freebsd.org/threads/howto-monitor-network-traffic-with-netflow-nfdump-nfsen-on-freebsd.49724/" rel="nofollow noopener">Monitoring network traffic with FreeBSD</a></h3>

<ul>
<li>If you've ever been curious about monitoring network traffic on your FreeBSD boxes, this forum post may be exactly the thing for you</li>
<li>It'll show you how to combine the Netflow, NfDump and NfSen suite of tools to get some pretty detailed network stats (and of course put them into a fancy webpage)</li>
<li>This is especially useful for finding out what was going on at a certain point in time, for example if you had a traffic spike
***</li>
</ul>

<h3><a href="http://www.protoc.org/blog/2014/12/22/trapping-spammers-with-the-openbsd-spam-deferral-daemon" rel="nofollow noopener">Trapping spammers with spamd</a></h3>

<ul>
<li>This is a blog post about OpenBSD's <a href="https://en.wikipedia.org/wiki/Spamd" rel="nofollow noopener">spamd</a> - a spam email deferral daemon - and how to use it for your mail</li>
<li>It gives some background on the greylisting approach to spam, rather than just a typical host blacklist</li>
<li>"Greylisting is a method of defending e-mail users against spam. A mail transfer agent (MTA) using greylisting will "temporarily reject" any email from a sender it does not recognize. If the sender re-attempts mail delivery at a later time, the sender may be allowed to continue the mail delivery conversation."</li>
<li>The post also shows how to combine it with PF and other tools for a pretty fancy mail setup</li>
<li>You can find spamd in the OpenBSD <a href="http://www.openbsd.org/cgi-bin/man.cgi/OpenBSD-current/man8/spamd.8" rel="nofollow noopener">base system</a>, or use it <a href="https://www.freshports.org/mail/spamd" rel="nofollow noopener">with FreeBSD</a> <a href="http://pkgsrc.se/mail/spamd" rel="nofollow noopener">or NetBSD</a> via ports and pkgsrc</li>
<li>You might also want to go back and listen to <a href="https://archive.org/details/bsdtalk068" rel="nofollow noopener">BSDTalk episode 68</a>, where Will talks to Bob Beck about spamd
***</li>
</ul>

<h2>Feedback/Questions</h2>

<ul>
<li><a href="http://slexy.org/view/s20rUK9XVJ" rel="nofollow noopener">Sean writes in</a></li>
<li><a href="http://slexy.org/view/s20nfzIuT2" rel="nofollow noopener">Brandon writes in</a></li>
<li><a href="http://slexy.org/view/s20wCBhFLO" rel="nofollow noopener">Anders writes in</a></li>
<li><a href="http://slexy.org/view/s20xGrBIyl" rel="nofollow noopener">David writes in</a></li>
<li><a href="http://slexy.org/view/s2QHRaiZJW" rel="nofollow noopener">Kyle writes in</a>
***</li>
</ul>

<h2>Mailing List Gold</h2>

<ul>
<li><a href="https://www.marc.info/?l=openbsd-tech&amp;m=141903858708123&amp;w=2" rel="nofollow noopener">NTP code comparison</a> - <a href="https://www.marc.info/?l=openbsd-tech&amp;m=141905854411370&amp;w=2" rel="nofollow noopener">192870 vs. 2898</a></li>
<li><a href="https://lists.freebsd.org/pipermail/freebsd-hackers/2014-December/046741.html" rel="nofollow noopener">NICs have feelings too</a></li>
<li><a href="https://www.marc.info/?l=openbsd-ports&amp;m=141998130824977&amp;w=2" rel="nofollow noopener">Just think about it</a>
***</li>
</ul>]]>
  </itunes:summary>
</item>
  </channel>
</rss>
