on (#3Q39Y)
Peter Hessler (phessler@) writes about his time in Nantes:
OpenBSD Journal
| Link | http://undeadly.org/ |
| Feed | http://undeadly.org/cgi?action=rss |
| Updated | 2024-12-03 19:01 |
on (#3Q39Z)
Eric Faurot (eric@) is next with his report on what he did in Nantes:
on (#3Q3A0)
Stefan Sperling (stsp@) kindly sent in a report on his activities around p2k18:
on (#3Q3A1)
Our next p2k18 report comes from Christian "naddy" Weisgerber, who writes:
on (#3Q3A2)
Landry Breuil (landry@) has an extensive report for our readers:
on (#3Q3A3)
Next up with a p2k18 report is Jasper Lievisse Adriaanse (jasper@):
on (#3P3YZ)
Next up with a p2k18 report is Bob Beck (beck@):
on (#3P2DG)
Next up is the report from Ken Westerback (krw@):
on (#3P1C6)
The latest p2k18 hackathon report comes from Gilles Chehade (gilles@),who writes:
on (#3P1AQ)
As more and more developers arrive back home from France, more reports arrive to you to keep you informed of what happened in Nantes. This time, it's Philip Guenther (guenther@) who writes in with his report:
on (#3P0TF)
Next up in our series of p2k18 reports is that from Klemens Nanni (kn@):
on (#3NZY7)
Here is another report from the just concluded p2k18 hackathon, from Marc Espie (espie@), who writes:
on (#3NZ4J)
Working at p2k18, Theo de Raadt (deraadt@) hascommittedSpectre Variant 2 mitigations:
on (#3NTSH)
Working at p2k18, Eric Faurot (eric@) hascommitteda simple SMTP client to -current:
on (#3N45C)
Ken Westerback (krw@ when wearing his developer hat) writes:
on (#3N171)
In this commit, visa@ submitted code (disabled for now) to use built-in accelerationon octeon CPUs, much like AESNI for x86s.I decided to test tcpbench(1) and IPsec, before and after updating and enabling the octcrypto(4) driver.Read more…
on (#3MRRP)
The MAP_STACK anti-ROP mechanism described in a recentarticlehas beencommittedto-current.Thecommit messageincludes:
on (#3MRRQ)
Landry Breuil (landry@ when wearing his developer hat) wrotein…
on (#3KQDB)
April 2, 2018: The OpenBSDproject has announced the availability of the newest release,OpenBSD 6.3:
on (#3HSSV)
Recently, Theo de Raadt (deraadt@)describeda new type of mitigation he has been working on together with Stefan Kempf (stefan@):
on (#3HQF1)
Mike Larkin (mlarkin@) has just given a presentation atbhyvecon Tokyo 2018.The slides are nowavailable (as PDF).In addition to the excellent summary of the state-of-play forvmmand friends, the presentation offers a tantalizing glimpse at possible futuredirections.Update: videois available
on (#3HKTZ)
Good news for people doing upgrades only once per year: syspatches will be provided for both supported releases. The commit from T.J. Townsend (tj@) speaks for itself:
on (#3H4HY)
Ken Westerback (krw@) has sent in the first report from the (recently concluded) a2k18 hackathon:
on (#3H1EK)
The recent changes in -current mitigating the Meltdown vulnerability have been backported to the6.1 and6.2(amd64) releases, and thesyspatch update (for 6.2) is now available.Happy syspatching, and don't forget to show your appreciation bydonating to the project.
on (#3GEPR)
Meltdown mitigation is coming to OpenBSD. Philip Guenther (guenther@) has just committed a diff that implements a new mitigation technique to OpenBSD: Separation of page tables for kernel and userland. This fixes the Meltdown problems that affect most CPUs from Intel. Both Philip and Mike Larkin (mlarkin@) spent a lot of time implementing this solution, talking to various people from other projects on best approaches.In the commit message, Philip briefly describes the implementation:Read more…
on (#3F9TM)
As you may have heard, the a2k18 hackathon is in progress. As can be seen from the commit messages, several items of goodness are being worked on.One eagerly anticipated item is the arrival of TCP syncookies (read: another important tool in your anti-DDoS toolset) in PF. Henning Brauer (henning@) added the code in a series of commits on February 6th, 2018, with this one containing the explanation:Read more…
on (#3EK2J)
Details of the2018 campaign have been added to the Foundation's website. The goal for theyear is for $300,000. The total for "smaller" donations has alreadytaken the OpenBSD community to bronze level sponsorship!Please show your support by contributing.
on (#3DAHJ)
Patrick Wildt (patrick@) recently committed some code that will update the Intel microcode on many Intel CPUs, a diff initially written by Stefan Fritsch (sf@). The microcode of your CPU is basically the firmware that runs on your (Intel) processor, defining its instruction set in terms of so called "microinstructions". The new code depends, of course, on the corresponding firmware package, ported by Patrick which can be installed using a very recent fw_update(1). Of course, this all plays into the recently revealed problems in Intel (and other) CPUs, Meltdown and Spectre.Read more…
on (#3CWXB)
ITWirehas publishedan articleregarding Theo de Raadt's (deraadt@) reaction to theMeltdown/Spectre disclosures.One choice quote reads:
on (#3CSDX)
If you run a mail service, you probably like to have greylisting in place, via spamd(8) or similar means. However, there are some sites that simply do not play well with greylisting, and for those it's useful to extract SPF information to identify their valid outgoing SMTP hosts. Now OpenBSD offers a straightforward mechanism to do that and fill your nospamd table, right from the smtpctl utility via the subcommand spf walk. Gilles Chehade (gilles@) describes how in a recent blog post titled spfwalk.This feature is still in need of testing, so please grab a snapshot and test!
on (#3CHA2)
Amessage to tech@from Philip Guenther (guenther@) provides the first publicinformation from developers regarding the OpenBSD response to the recentlyannouncedCPU vulnerabilities:
on (#3BXA9)
In amessage to misc@,Tom Smyth wrote (in part):
on (#3A4YK)
In amessage to tech@,Theo de Raadt (deraadt@) provided some insights into ongoingwork on pledge(2):
on (#3A4YM)
arm64 is now anofficially supported platform for OpenBSD.As some readers will have noticed,there's nowsyspatch(8) support, too.Theo de Raadt (deraadt@) committed the following change:
on (#38FB5)
Another p2k17 hackathon report is just in, from Antoine Jacoutot (ajacoutot@), who writes:
on (#38BTJ)
Our dear friend Bob Beck (beck@) writes:
on (#37WKN)
A new p2k17 hackathon report has arrived, this one from Florian Obser, who writes:
on (#37T8K)
Landry Breuil (landry@) sent in our next report from the recent ports hackathon:
on (#37JYX)
The next p2k17 report comes from Anthony J. Bentley (bentley@):
on (#37JYY)
The next p2k17 report comes from Sebastian Reitenbach (sebastian@):
on (#37GDJ)
The latest hackathon report to come in today came from Christian Weisgerber (naddy@):
on (#37BHJ)
The p2k17 hackathon reports keep flowing in, here's one from Jeremy Evans (jeremy@):
on (#37AMT)
Here is a new p2k17 hackathon report from Paul Irofti (pirofti@), who writes:
on (#379Z4)
A new p2k17 hackathon report is in, from Marc Espie, who writes:
on (#377S7)
The p2k17 hackathon has concluded, and we have our first report.Matthias Kilian (kili@) wrote in:
on (#3539P)
In amessage to tech@,Theo de Raadt (deraadt@) wrote: