BSD News 30/11/2015

Last week in BSD

Releases: DragonFly, OPNsense
Other news:OPNsense, OpenBSD, DragonFly BSD, FreeBSD, HardenedBSD, HardenedBSD



DragonFly 4.4 release candidate branched

The next release of DragonFly is coming due, since it’s been 6 months.  I just tagged 4.4RC, and I’ll have an image built soon.  Current estimate is that we’ll have the 4.4-RELEASE at the end of the month.

DragonFly 4.4-RC image for download

DragonFly BSD Digest by Justin Sherrill
The release candidate for DragonFly 4.4 is built and available for download.  The main site has it as an ISO or IMG file, and the mirrors should have it soon if not already.
Here’s a question I need feedback on: if we compressed these images using xz instead of bzip2 – would that inconvenience you?

OPNsense 15.7.20 Released

Here are the full patch notes:
  • src: fix kqueue write events never fired for files greater 2GB. [1]
  • src: remove obsolete locking primitives IFA_LOCK() / IFA_UNLOCK()
  • src: enable netmap(4) driver support in the kernel
  • src: merge stf(4) driver modifications from pfSense [2]
  • ports: squid 5.3.11 [3]
  • ports: strongswan 5.3.4 [4]
  • ports: choparp 20150613 [5]
  • ports: libxml 2.9.3 [6]
  • ports: pkg 1.6.2 [7]
  • ports: opnsense-bootstrap, the infamous installer that works on stock FreeBSD [8]
  • intrusion detection: ignore json parse errors in eve log file
  • intrusion prevention (development): added Suricata 2.1beta4 in inline mode[9]
  • interfaces: reverted cache removal due to multiple speed regressions reports
  • backend: send timeouts with proper description to syslog
  • openvpn: fix auth server selection for translations
  • filter: make the status reload page provide better debug info
  • interfaces: fix mobile carrier selection on main interface edit page
  • interfaces: unify release/renew/connect/disconnect buttons in status page
  • dashboard: show cell mode for ppp if available



Interview: Renato Westphal ([email protected])

Renato Westphal ([email protected]) recently agreed to answer some questions in the wake of committing eigrpd(8):

First off, thanks for agreeing to this interview. Tell us a little about yourself, your technical background, and how you came to the OpenBSD project.

My name is Renato Westphal and I was born and live in the south of Brazil. Currently I work for Taghos Tecnologia developing web cache and CDN solutions and in my previous job I worked for a small network equipment manufacturer, which is where my background in routing protocols comes from.

The Cantrill Strikes Back | BSD Now 117

As we get ready for the Holiday season, we wanted to give you a special present early! Back by popular demand, Brian Cantrill is here to give us his latest rants, specifically on Linux Interfaces! All this and the weeks headlines, coming right up on BSDNow!

Hackfest OpenBSD presentations

Two OpenBSD developers gave presentations at this year's Hackfest security conference in Quebec. The videos of both are now online for your viewing pleasure:

  • "Kernel W^X Improvements In OpenBSD" by Mike Larkin ([email protected]) (slides)
  • "Pledge: A New Security Technology in OpenBSD" by Theo de Raadt ([email protected]) (slides)

  • Binary dports for DragonFly 4.5 users

    Since DragonFly 4.4 has been branched, bleeding-edge DragonFly is now at version 4.5.  As John Marino detailed in his post, that means pkg on 4.5 systems will look in a new place for downloads.  (“dragonfly:4.6:x86:64”, since it always uses even numbers)  
    To cover for this, set ABI to point at DragonFly 4.4 packages in pkg.conf for now.  They’re freshly built and functionally the same, anyway.  Once there’s a 4.6 download path, that ABI setting can be removed. Packages for DragonFly-current are available now and probably at the mirrors by the time this posts.
    Update: as John Marino pointed out to me, anyone on DragonFly-master who upgrades now will be at version 4.5.  This means pkg will get the new (4.5) packages on the next pkg upgrade.  That means a mix of old and new packages unless you either reinstall anything (pkg update -f) or hardcode the 4.4 download path until you are ready to switch everything.
    So: DragonFly-current users should either hardcode the 4.4 path for now or force an pkg upgrade for everything.  DragonFly 4.2-release users are unaffected.

    Code stuff


    Interesting articles

    Wallpaper of the week 

    argh, blogger is broken a bit, can't embed picture here.
    from[email protected]/5748071913


    Jan Hovancik

    software developer - guitar player - poetry lover