SMOLNET PORTAL home about changes
[root][parent][raw file]
bsdweekly.com.atom.xml - sfeed_tests - sfeed tests and RSS and Atom files
(URL) git clone git://git.codemadness.org/sfeed_tests (git://git.codemadness.org)
(DIR) Log
(DIR) Files
(DIR) Refs
(DIR) README
(DIR) LICENSE
---
bsdweekly.com.atom.xml (131297B)
---
1 <?xml version="1.0" encoding="UTF-8"?>
2 <feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
3 <id>tag:bsdsec.net,2005:/articles</id>
4 <link rel="alternate" type="text/html" href="https://bsdsec.net"/>
5 <link rel="self" type="application/atom+xml" href="https://bsdsec.net/articles.atom"/>
6 <title>BSDSec</title>
7 <updated>2020-10-29T17:09:15Z</updated>
8 <entry>
9 <id>tag:bsdsec.net,2005:Article/1223</id>
10 <published>2020-10-29T17:09:15Z</published>
11 <updated>2020-10-29T17:09:15Z</updated>
12 <link rel="alternate" type="text/html" href="https://bsdsec.net/articles/openbsd-errata-october-29th-2020-tmux"/>
13 <title>OpenBSD Errata: October 29th, 2020 (tmux)</title>
14 <content type="html">Errata patches for tmux have been released for OpenBSD 6.7 and 6.8.
15
16 tmux has a stack overflow in CSI parsing.
17
18 Binary updates for the amd64, i386, and arm64 platforms are available via
19 the syspatch utility. Source code patches can be found on the respective
20 errata page:
21
22 https://www.openbsd.org/errata67.html
23 https://www.openbsd.org/errata68.html
24 </content>
25 <tags>openbsd</tags>
26 <author>
27 <name>tb@openbsd.org</name>
28 </author>
29 </entry>
30 <entry>
31 <id>tag:bsdsec.net,2005:Article/1222</id>
32 <published>2020-10-28T17:36:48Z</published>
33 <updated>2020-10-28T17:36:48Z</updated>
34 <link rel="alternate" type="text/html" href="https://bsdsec.net/articles/openbsd-errata-october-29th-2020-icmp6"/>
35 <title>OpenBSD Errata: October 29th, 2020 (icmp6)</title>
36 <content type="html">Errata patches for the kernel have been released for OpenBSD 6.7 and 6.8.
37
38 When generating the ICMP6 response to an IPv6 packet, the kernel could
39 use mbuf memory after freeing it.
40
41 Binary updates for the amd64, i386, and arm64 platforms are available via
42 the syspatch utility. Source code patches can be found on the respective
43 errata page:
44
45 https://www.openbsd.org/errata67.html
46 https://www.openbsd.org/errata68.html
47
48 As these affect the kernel, a reboot will be needed after patching.
49 </content>
50 <tags>openbsd</tags>
51 <author>
52 <name>tb@openbsd.org</name>
53 </author>
54 </entry>
55 <entry>
56 <id>tag:bsdsec.net,2005:Article/1221</id>
57 <published>2020-10-27T23:24:21Z</published>
58 <updated>2020-10-27T23:24:21Z</updated>
59 <link rel="alternate" type="text/html" href="https://bsdsec.net/articles/freebsd-announce-freebsd-12-2-release-now-available"/>
60 <title>[FreeBSD-Announce] FreeBSD 12.2-RELEASE Now Available</title>
61 <content type="html">-----BEGIN PGP SIGNED MESSAGE-----
62 Hash: SHA256
63
64 FreeBSD 12.2-RELEASE Announcement
65
66 The FreeBSD Release Engineering Team is pleased to announce the
67 availability of FreeBSD 12.2-RELEASE. This is the third release of the
68 stable/12 branch.
69
70 Some of the highlights:
71
72 * Updates to the wireless networking stack and various drivers have
73 been introduced to provide better 802.11n and 802.11ac support.
74
75 * The ice(4) driver has been added, supporting Intel(R) 100Gb ethernet
76 cards.
77
78 * The jail(8) utility has been updated to allow running Linux(R) in a
79 jailed environment.
80
81 * OpenSSL has been updated to version 1.1.1h.
82
83 * OpenSSH has been updated to version 7.9p1.
84
85 * The clang, llvm, lld, lldb, compiler-rt utilities and libc++ have
86 been updated to version 10.0.1.
87
88 * And much more...
89
90 For a complete list of new features and known problems, please see the
91 online release notes and errata list, available at:
92
93 * https://www.FreeBSD.org/releases/12.2R/relnotes.html
94
95 * https://www.FreeBSD.org/releases/12.2R/errata.html
96
97 For more information about FreeBSD release engineering activities, please
98 see:
99
100 * https://www.FreeBSD.org/releng/
101
102 Availability
103
104 FreeBSD 12.2-RELEASE is now available for the amd64, i386, powerpc,
105 powerpc64, sparc64, armv6, and aarch64 architectures.
106
107 FreeBSD 12.2-RELEASE can be installed from bootable ISO images or over
108 the network. Some architectures also support installing from a USB memory
109 stick. The required files can be downloaded as described in the section
110 below.
111
112 SHA512 and SHA256 hashes for the release ISO, memory stick, and SD card
113 images are included at the bottom of this message.
114
115 PGP-signed checksums for the release images are also available at:
116
117 * https://www.FreeBSD.org/releases/12.2R/signatures.html
118
119 A PGP-signed version of this announcement is available at:
120
121 * https://www.FreeBSD.org/releases/12.2R/announce.asc
122
123 The purpose of the images provided as part of the release are as follows:
124
125 dvd1
126
127 This contains everything necessary to install the base FreeBSD
128 operating system, the documentation, debugging distribution sets,
129 and a small set of pre-built packages aimed at getting a
130 graphical workstation up and running. It also supports booting
131 into a "livefs" based rescue mode. This should be all you need if
132 you can burn and use DVD-sized media.
133
134 Additionally, this can be written to a USB memory stick (flash
135 drive) for the amd64 architecture and used to do an install on
136 machines capable of booting off USB drives. It also supports
137 booting into a "livefs" based rescue mode.
138
139 As one example of how to use the memstick image, assuming the USB
140 drive appears as /dev/da0 on your machine something like this
141 should work:
142
143 # dd if=FreeBSD-12.2-RELEASE-amd64-dvd1.iso \
144 of=/dev/da0 bs=1m conv=sync
145
146 Be careful to make sure you get the target (of=) correct.
147
148 disc1
149
150 This contains the base FreeBSD operating system. It also supports
151 booting into a "livefs" based rescue mode. There are no pre-built
152 packages.
153
154 Additionally, this can be written to a USB memory stick (flash
155 drive) for the amd64 architecture and used to do an install on
156 machines capable of booting off USB drives. It also supports
157 booting into a "livefs" based rescue mode. There are no pre-built
158 packages.
159
160 As one example of how to use the memstick image, assuming the USB
161 drive appears as /dev/da0 on your machine something like this
162 should work:
163
164 # dd if=FreeBSD-12.2-RELEASE-amd64-disc1.iso \
165 of=/dev/da0 bs=1m conv=sync
166
167 Be careful to make sure you get the target (of=) correct.
168
169 bootonly
170
171 This supports booting a machine using the CDROM drive but does
172 not contain the installation distribution sets for installing
173 FreeBSD from the CD itself. You would need to perform a network
174 based install (e.g., from an HTTP or FTP server) after booting
175 from the CD.
176
177 Additionally, this can be written to a USB memory stick (flash
178 drive) for the amd64 architecture and used to do an install on
179 machines capable of booting off USB drives. It also supports
180 booting into a "livefs" based rescue mode. There are no pre-built
181 packages.
182
183 As one example of how to use the memstick image, assuming the USB
184 drive appears as /dev/da0 on your machine something like this
185 should work:
186
187 # dd if=FreeBSD-12.2-RELEASE-amd64-bootonly.iso \
188 of=/dev/da0 bs=1m conv=sync
189
190 Be careful to make sure you get the target (of=) correct.
191
192 memstick
193
194 This can be written to a USB memory stick (flash drive) and used
195 to do an install on machines capable of booting off USB drives.
196 It also supports booting into a "livefs" based rescue mode. There
197 are no pre-built packages.
198
199 As one example of how to use the memstick image, assuming the USB
200 drive appears as /dev/da0 on your machine something like this
201 should work:
202
203 # dd if=FreeBSD-12.2-RELEASE-amd64-memstick.img \
204 of=/dev/da0 bs=1m conv=sync
205
206 Be careful to make sure you get the target (of=) correct.
207
208 mini-memstick
209
210 This can be written to a USB memory stick (flash drive) and used
211 to boot a machine, but does not contain the installation
212 distribution sets on the medium itself, similar to the bootonly
213 image. It also supports booting into a "livefs" based rescue
214 mode. There are no pre-built packages.
215
216 As one example of how to use the mini-memstick image, assuming
217 the USB drive appears as /dev/da0 on your machine something like
218 this should work:
219
220 # dd if=FreeBSD-12.2-RELEASE-amd64-mini-memstick.img \
221 of=/dev/da0 bs=1m conv=sync
222
223 Be careful to make sure you get the target (of=) correct.
224
225 FreeBSD/arm SD card images
226
227 These can be written to an SD card and used to boot the supported
228 arm system. The SD card image contains the full FreeBSD
229 installation, and can be installed onto SD cards as small as
230 512Mb.
231
232 For convenience for those without console access to the system, a
233 freebsd user with a password of freebsd is available by default
234 for ssh(1) access. Additionally, the root user password is set to
235 root, which it is strongly recommended to change the password for
236 both users after gaining access to the system.
237
238 To write the FreeBSD/arm image to an SD card, use the dd(1)
239 utility, replacing KERNEL with the appropriate kernel
240 configuration name for the system.
241
242 # dd if=FreeBSD-12.2-RELEASE-arm-armv6-KERNEL.img \
243 of=/dev/da0 bs=1m conv=sync
244
245 Be careful to make sure you get the target (of=) correct.
246
247 FreeBSD 12.2-RELEASE can also be purchased on CD-ROM or DVD from several
248 vendors. One of the vendors that will be offering FreeBSD 12.2-based
249 products is:
250
251 * FreeBSD Mall, Inc. https://www.freebsdmall.com
252
253 Pre-installed virtual machine images are also available for the amd64
254 (x86_64), i386 (x86_32), and AArch64 (arm64) architectures in QCOW2, VHD,
255 and VMDK disk image formats, as well as raw (unformatted) images.
256
257 FreeBSD 12.2-RELEASE amd64 is also available on these cloud hosting
258 platforms:
259
260 * FreeBSD/amd64 Amazon(R) EC2(TM):
261 AMIs are available in the following regions:
262
263 af-south-1 region: ami-0183ba5b381eb0baa
264 eu-north-1 region: ami-0821c256650690884
265 ap-south-1 region: ami-009471f6e29b012ef
266 eu-west-3 region: ami-0bfaf7527f637d64b
267 eu-west-2 region: ami-023d320201b8d06c5
268 eu-south-1 region: ami-08828d09ef0598bc8
269 eu-west-1 region: ami-02b1b6bc3cface0ac
270 ap-northeast-2 region: ami-03f41a1a8d06363a5
271 me-south-1 region: ami-0e1e55e0288018f35
272 ap-northeast-1 region: ami-0a352b6e005340d93
273 sa-east-1 region: ami-0b9c77455fbf5f3f0
274 ca-central-1 region: ami-0dbf9b82233b2b970
275 ap-east-1 region: ami-0f4732ac090ec2a7d
276 ap-southeast-1 region: ami-045943797617e690c
277 ap-southeast-2 region: ami-0cbc4c8a75ded8b2d
278 eu-central-1 region: ami-0d94faf9636228402
279 us-east-1 region: ami-00be86d9bba30a7b3
280 us-east-2 region: ami-075db5a7ecd8b1456
281 us-west-1 region: ami-0e54f016b55b7f6ce
282 us-west-2 region: ami-0c273f14bc9df57d1
283
284 AMIs are also expected to be available in the Amazon(R) Marketplace
285 once third-party validation is complete at:
286 https://aws.amazon.com/marketplace/pp/B07L6QV354/
287
288 FreeBSD/arm64 Amazon(R) EC2(TM):
289 AMIs are available in the following regions:
290
291 af-south-1 region: ami-0afe034012109b43b
292 eu-north-1 region: ami-04d3c1275757f20e9
293 ap-south-1 region: ami-07c0b1ad6978b7814
294 eu-west-3 region: ami-0bfc36baff5afe2a1
295 eu-west-2 region: ami-0276cf2663706fbb5
296 eu-south-1 region: ami-0fa854a53ca82be87
297 eu-west-1 region: ami-0aa22dfb10a633d26
298 ap-northeast-2 region: ami-0fb44fe96791af480
299 me-south-1 region: ami-000505dcbd78acc9e
300 ap-northeast-1 region: ami-066d14139dd815cda
301 sa-east-1 region: ami-03d75ceb6ca00c117
302 ca-central-1 region: ami-050385d1fdf3c70f2
303 ap-east-1 region: ami-00f184a5ec9b137ca
304 ap-southeast-1 region: ami-063ab54f54180837c
305 ap-southeast-2 region: ami-0903d6af1e37a63ff
306 eu-central-1 region: ami-02fcc489e80482d5f
307 us-east-1 region: ami-00eea2f51ee575a19
308 us-east-2 region: ami-00d07c574a09a4941
309 us-west-1 region: ami-03ad9a0a981f26542
310 us-west-2 region: ami-0fd803a9d8beb7d6d
311
312 AMIs are also available in the Amazon(R) Marketplace at:
313 https://aws.amazon.com/marketplace/pp/B081NF7BY7/
314
315 * Google(R) Compute Engine(TM):
316 Instances can be deployed using the gcloud utility:
317
318 % gcloud compute instances create INSTANCE \
319 --image freebsd-12-2-release-amd64 \
320 --image-project=freebsd-org-cloud-dev
321 % gcloud compute ssh INSTANCE
322
323 Replace INSTANCE with the name of the Google Compute Engine instance.
324
325 FreeBSD 12.2-RELEASE is also expected to be available in the
326 Google Compute Engine(TM) Marketplace once they have completed
327 third-party specific validation at:
328 https://console.cloud.google.com/launcher/browse?filter=category:os&amp;filter=price:free
329
330 * Hashicorp/Atlas(R) Vagrant(TM):
331 Instances can be deployed using the vagrant utility:
332
333 % vagrant init freebsd/FreeBSD-12.2-RELEASE
334 % vagrant up
335
336 Download
337
338 FreeBSD 12.2-RELEASE may be downloaded via https from the following site:
339
340 * https://download.freebsd.org/ftp/releases/ISO-IMAGES/12.2/
341
342 FreeBSD 12.2-RELEASE virtual machine images may be downloaded from:
343
344 * https://download.freebsd.org/ftp/releases/VM-IMAGES/12.2-RELEASE/
345
346 For instructions on installing FreeBSD or updating an existing machine to
347 12.2-RELEASE please see:
348
349 * https://www.FreeBSD.org/releases/12.2R/installation.html
350
351 Support
352
353 Based on the new FreeBSD support model, the FreeBSD 12 release series
354 will be supported until at least June 30, 2024. This point release,
355 FreeBSD 12.2-RELEASE, will be supported until at least three months after
356 FreeBSD 12.3-RELEASE. Additional support information can be found at:
357
358 * https://www.FreeBSD.org/security/
359
360 Please note that 12.1 will be supported until three months from the 12.2
361 release date, currently scheduled for January 31, 2021.
362
363 Acknowledgments
364
365 Many companies donated equipment, network access, or human time to
366 support the release engineering activities for FreeBSD 12.2 including:
367
368 The FreeBSD Foundation
369 Rubicon Communications, LLC (netgate.com)
370 Tarsnap
371 NetApp
372 Internet Systems Consortium
373 ByteMark Hosting
374 CyberOne Data
375 Sentex Data Communications
376 New York Internet
377 Juniper Networks
378 NetActuate
379 Department of Computer Science, National Chiao Tung University
380 NLNet Labs
381 iXsystems
382
383 The release engineering team for 12.2-RELEASE includes:
384
385 Glen Barber &lt;gjb@FreeBSD.org&gt; Release Engineering Lead,
386 12.2-RELEASE Release Engineer
387 Konstantin Belousov &lt;kib@FreeBSD.org&gt; Release Engineering
388 Antoine Brodin &lt;antoine@FreeBSD.org&gt; Package Building
389 Bryan Drewery &lt;bdrewery@FreeBSD.org&gt; Release Engineering, Package
390 Building
391 Marc Fonvieille &lt;blackend@FreeBSD.org&gt; Release Engineering, Documentation
392 Xin Li &lt;delphij@FreeBSD.org&gt; Release Engineering, Security Team
393 Liaison
394 Ed Maste &lt;emaste@FreeBSD.org&gt; Security Officer Deputy
395 Colin Percival &lt;cperciva@FreeBSD.org&gt; Release Engineering Deputy Lead
396 Hiroki Sato &lt;hrs@FreeBSD.org&gt; Release Engineering, Documentation
397 Gleb Smirnoff &lt;glebius@FreeBSD.org&gt; Release Engineering
398 Gordon Tetlow &lt;gordon@FreeBSD.org&gt; Security Officer
399
400 Trademark
401
402 FreeBSD is a registered trademark of The FreeBSD Foundation.
403
404 ISO Image Checksums
405
406 amd64 (x86_64):
407
408 SHA512 (FreeBSD-12.2-RELEASE-amd64-bootonly.iso) = de1a805cd7f2c740d0f42aa6d2f7439fd9470ee4a471dc2b8eb85314776e9fe5423d0576f099adda600c990885ffbb098bedcb4c13c132125f670919e499ea40
409 SHA512 (FreeBSD-12.2-RELEASE-amd64-bootonly.iso.xz) = 1ea2389e2c7dc4bdc889925cbffb49e066ed087678cff46197f17d15bbedb35a1021e88a858b040c8d7b041ab7f7b18b4ff8c38e97866bd2b97d5b9ad506d687
410 SHA512 (FreeBSD-12.2-RELEASE-amd64-disc1.iso) = bbf67945d244c76f1ef26029b2e1c2d30d30881b178881b92b657a3da66f54ff40c57e69f4bebeefe6071da8311f477e8d371a1b9a8d7f000dd32383b9cd7ca7
411 SHA512 (FreeBSD-12.2-RELEASE-amd64-disc1.iso.xz) = ba2990269cc73623b490c18541d04d4fc9f1d9d1639688d33c8108e09cae78daa6be774d6f40c86774070ab0b42815249a6754ab4135843f197b94bdc8d34268
412 SHA512 (FreeBSD-12.2-RELEASE-amd64-dvd1.iso) = 80e8c6804e0a965bc1be596b0c8d6dbdbbf9eef42bb4170761ec4094cc07b294fd4f17cd55d28aa7679b5d01c121fa15e6c24852f9307959af759254ebfceba1
413 SHA512 (FreeBSD-12.2-RELEASE-amd64-dvd1.iso.xz) = ab75d9cae6a4df12ecd9439a108601f8b7729684e711ea48b6784cac8072237e2a41500c1f3060b7680980a1c32545fb89444a936e9096aa6841c87d4bb236eb
414 SHA512 (FreeBSD-12.2-RELEASE-amd64-memstick.img) = 483b961fda9d48a6a59e128f32ece9054e49cd25c7a33987524f1535e0732d2f362829c25801e16336b5ea9ee35681ef1ae04cd027275d73c6bbf9fca5f35ca0
415 SHA512 (FreeBSD-12.2-RELEASE-amd64-memstick.img.xz) = 75219bd14c52efb9b670884d8dd67499a781f2e6242d84660525535c6eb334d11b50a3d5fb110e755aa1e9791cf5deb5c045eaefec036bd4b67cc4c15532a367
416 SHA512 (FreeBSD-12.2-RELEASE-amd64-mini-memstick.img) = 392d5bb81387b2639f59ac469d60e18d198f6e28d50c678f1154f86dbc583c16ec5461853ff66180b9405997ba8647efb740241794de18242a594241477a841c
417 SHA512 (FreeBSD-12.2-RELEASE-amd64-mini-memstick.img.xz) = 6f5c1e8e15597c86ab56e6ac457975d361ea8dec375abe77cfd9604ee54055a2100e6f5d46da7acf702042025c62c4e680a1279c2e84b7b3b424bf6081e7f4bb
418
419 SHA256 (FreeBSD-12.2-RELEASE-amd64-bootonly.iso) = f18412a1936d6f7df1e8e8857c98aeb53f752d43c732affee9c7a5615d4331b5
420 SHA256 (FreeBSD-12.2-RELEASE-amd64-bootonly.iso.xz) = 0eafcd6f17b8f87234f161d727b0f52b85f3f4415e9b36d3c93afb57f5da47d0
421 SHA256 (FreeBSD-12.2-RELEASE-amd64-disc1.iso) = 289522e2f4e1260859505adab6d7b54ab83d19aeb147388ff7e28019984da5dc
422 SHA256 (FreeBSD-12.2-RELEASE-amd64-disc1.iso.xz) = a4530246cafbf1dd42a9bd3ea441ca9a78a6a0cd070278cbdf63f3a6f803ecae
423 SHA256 (FreeBSD-12.2-RELEASE-amd64-dvd1.iso) = bc997989eafb41fcabd6ed55e379134c7322425391d1cd0e5eff37759fc7f865
424 SHA256 (FreeBSD-12.2-RELEASE-amd64-dvd1.iso.xz) = 221d6f9214de944bcdbbe61f030fdebccd43e285227c6b3796e0926e793c9bf7
425 SHA256 (FreeBSD-12.2-RELEASE-amd64-memstick.img) = c7fae987dc652aca219d8b1c4941a1ae48bccefa41b7d82a0656a6a3f9e04775
426 SHA256 (FreeBSD-12.2-RELEASE-amd64-memstick.img.xz) = 9422356d456f2b8a8226c6f51f8a9205456777cb57a023421cfd4a330d382dae
427 SHA256 (FreeBSD-12.2-RELEASE-amd64-mini-memstick.img) = 83ad7fab69f8d860e0f785ed3af16c19e84e32b3d4f6206fc8b31b83c4e6bfb5
428 SHA256 (FreeBSD-12.2-RELEASE-amd64-mini-memstick.img.xz) = 1e3fdefb660d9920f7d315591eeeeab1522670d5f122b9531064bf3b360701c9
429
430
431 i386 (x86):
432
433 SHA512 (FreeBSD-12.2-RELEASE-i386-bootonly.iso) = 2eea6122389c0553d9aa15c682f472dfb8b7fa9c74c25364323f51185320904dbe96770fc333bfa11992d98bf85200ee729db5b1ea3ea25879b0a0ddcc105fc9
434 SHA512 (FreeBSD-12.2-RELEASE-i386-bootonly.iso.xz) = 53b08ae31359f730fda8bbe9dc5cd19d76c7e1a672bb4b3ee69e731e2444825e8c8b6056e84a5c13195e81f1643eb793e65809aabd3d36e1a53844365a3b9485
435 SHA512 (FreeBSD-12.2-RELEASE-i386-disc1.iso) = 3436f9f94fe7d35d604e4bd8089f8c98619092797c04fb6cd2fa6bf866cd78d7d282e3c7ee052750ee152ba44a6320ba6b1b6a1c589b5fad4a2466fa7f952fee
436 SHA512 (FreeBSD-12.2-RELEASE-i386-disc1.iso.xz) = 18652842708c858e03cb2b62db15c0925f04f08cd3ef42bdc6723939d4ef0acb3cae70fd1c8ea601f81fd4d9ed7c463c532f1249d068a3225e404e2df577c5b2
437 SHA512 (FreeBSD-12.2-RELEASE-i386-dvd1.iso) = 07ac2f0f81a8a0d2370cd6e0650573c3ed78075d6e664262548f99d51ee7b7891a2e622633555e4545df90e2c329187c41ce7bf3e1f6899ecc2dd3edc06bb107
438 SHA512 (FreeBSD-12.2-RELEASE-i386-dvd1.iso.xz) = 1c89d73db19a9bcbda722f5362a16625c5dca906684ed80ee75ca7e95fd3393852da65c0a9ed1d09c564c05f1e5d4ccae9ce9937e3cacec045de64c6a052883a
439 SHA512 (FreeBSD-12.2-RELEASE-i386-memstick.img) = d2aac7e9ab2f733f8f052c3b7377c664be8addb76038ba3f8e738bae0c46c36e5e8966861668099e9c57f5ef761267b2b4e4e9b1604f22a3a6fd782ef7c0aec7
440 SHA512 (FreeBSD-12.2-RELEASE-i386-memstick.img.xz) = b00ad7ecd524601c74f43ccc54705db810be84e8880088a6fdb5a6b3afe8c882b28991c1117301af40fb3305d8cf5557364787852af4d6ee95605a3e47160bfb
441 SHA512 (FreeBSD-12.2-RELEASE-i386-mini-memstick.img) = 5bdabe7a44a2b9d2d65d15cd20158f8f6526bed9d459bbff3577c25900127b15900e0fda58cfc1d04640add87a65a800e418897cf2b3f17b71b2344d5a338a66
442 SHA512 (FreeBSD-12.2-RELEASE-i386-mini-memstick.img.xz) = b68c51ebc80858e604c8836b0566c936f17a6c48077bfae469cd15f1ca6e9720b1261bf761550aabc02617302ee1ec11792f4d77b964672ee51c1f85665c4b0a
443
444 SHA256 (FreeBSD-12.2-RELEASE-i386-bootonly.iso) = 38ebc253646fa304888c248c9066f3354fe9beaf9d0784086d4bc0d70b639b2a
445 SHA256 (FreeBSD-12.2-RELEASE-i386-bootonly.iso.xz) = aca3ea590b4dec58f964a489f99f57e6f1faecc2c249869179970404b2071036
446 SHA256 (FreeBSD-12.2-RELEASE-i386-disc1.iso) = b422b5f390f9bd05f5c71783099b2b9a925e7256d7907b9be613ece4a1fb4124
447 SHA256 (FreeBSD-12.2-RELEASE-i386-disc1.iso.xz) = a8761b1f6cef9d931c201bc5e041fcc1a9ae3705f2b407694206124fcfd276cb
448 SHA256 (FreeBSD-12.2-RELEASE-i386-dvd1.iso) = e7278d307966306fc5709a312ad07b801ac73ea2acb0fd9469c2274bb57f0c05
449 SHA256 (FreeBSD-12.2-RELEASE-i386-dvd1.iso.xz) = cf562f8f8514ae344450fd15bd756693a72b8e29453a6b3fda5fcd25bc3270bd
450 SHA256 (FreeBSD-12.2-RELEASE-i386-memstick.img) = 83a32f4f2b90f82fa205e481ab0068cd0c2fcdbbfa5fef81b99cc4b9b6f53b48
451 SHA256 (FreeBSD-12.2-RELEASE-i386-memstick.img.xz) = 78630d283f882116ce24161b4870884467e8c85385ed14f68ad36f5e4d727484
452 SHA256 (FreeBSD-12.2-RELEASE-i386-mini-memstick.img) = e1055b30960827734f290916afcd477a48464753996eec88a4d76067c7f5b03b
453 SHA256 (FreeBSD-12.2-RELEASE-i386-mini-memstick.img.xz) = 5087505d6823ec1f09c5e8620ad1d83dd8cce27334e3b15971c81aff881b469a
454
455
456 powerpc:
457
458 SHA512 (FreeBSD-12.2-RELEASE-powerpc-bootonly.iso) = 48308b77fda1c3edf0d5916587b70e1148291ff6ad211294c0425086fc82e29893cc6571868789b009f16144b2480d43b778ba14548428bfd18dcc322f39cc1d
459 SHA512 (FreeBSD-12.2-RELEASE-powerpc-bootonly.iso.xz) = 0f0785a6eef88e3c00b9c2af68355a5788d3db2e3419345f931860191ed360db5ab46a08e08d52c8b5c9619bb82af04be039148a083347146187135d5a60e135
460 SHA512 (FreeBSD-12.2-RELEASE-powerpc-disc1.iso) = eb7feb628946caf47c257596595e03864ffb4edb270c5a461708f5e30ce88c6e3044e19ee6014a0593597975d8b41bc0cf6a69f3e517a31485103bf4b1a42083
461 SHA512 (FreeBSD-12.2-RELEASE-powerpc-disc1.iso.xz) = 2983e759b5b3a58bf5e02a95ef4b69a889891ff35d6ac8d932a5e370361f31045f1cb48c11a4287fffb6fa2fd935da4b474d81162f72921fc6d332ba572e4acb
462 SHA512 (FreeBSD-12.2-RELEASE-powerpc-dvd1.iso) = 5b76131677aa998e7ff5488841722bdc7d796ada8ee8edf466059b74617e7baa89661ba089430de62e2804d7e7053336c07003b9e085f8e01cefbc086e82522b
463 SHA512 (FreeBSD-12.2-RELEASE-powerpc-dvd1.iso.xz) = 3a36fb3c512006d458a0afb1ca21aaaa475ca0a6b89b3fe499b4b8ecdb73ac84d835766c2633ab94648dd62eab6863a6dceaa55ce7bce4e5137cc9bf60693fd3
464 SHA512 (FreeBSD-12.2-RELEASE-powerpc-memstick.img) = 2d8175d46d4e9a1c35b4baf12d855fe2cdca8f31ac87c56a5ca7680441289459bacc55d3c13e742ccab64ad18ec09e741c520f192cbf5dc06e2164269e0de199
465 SHA512 (FreeBSD-12.2-RELEASE-powerpc-memstick.img.xz) = 819b8b5a14bc26152f6624f5d9638c2a57db38df6f831184b5b3cf4fdeee39cd190b360a1e7c4fd9ece0c5d638eff87759c878722390c6d9d23fc7dee59219e0
466 SHA512 (FreeBSD-12.2-RELEASE-powerpc-mini-memstick.img) = e214fdcabd64a545da57064c319516c41ba65b7cc6adc31d218a3fb7c09388f68cb9205ce8df70b32d54d11b05d4577137e151af57681a46a0a34318428a9526
467 SHA512 (FreeBSD-12.2-RELEASE-powerpc-mini-memstick.img.xz) = d115bedb3430d3b2c3b5a7dd8f4b0d78e185a91a4f600758f5d7c9420bc834a931445c38cf04f4eaf35558f6b42a0f6833e23943f8ec415193f80a247478325b
468
469 SHA256 (FreeBSD-12.2-RELEASE-powerpc-bootonly.iso) = a12775e330bd10857ebdbe7489e3496007b4dc556842fcf77db861b43ab73295
470 SHA256 (FreeBSD-12.2-RELEASE-powerpc-bootonly.iso.xz) = 3a60de08618b1cf0439533c9e9ad589e81e21b0ebd220dd6788728b7937a2aaf
471 SHA256 (FreeBSD-12.2-RELEASE-powerpc-disc1.iso) = ea75d83e7638e220849a2bee10175ec62f18393e87ca7d928d59995a951bddd6
472 SHA256 (FreeBSD-12.2-RELEASE-powerpc-disc1.iso.xz) = 375fbdf7d1c4b9365c6aae40c9ee8149edf71c51d541d1e9cc12f4f129beeaff
473 SHA256 (FreeBSD-12.2-RELEASE-powerpc-dvd1.iso) = a70df012ad49928a24586c89d888b9d088c5dc74ca635d1519446e81dcbe3d63
474 SHA256 (FreeBSD-12.2-RELEASE-powerpc-dvd1.iso.xz) = 94f2ad8bbf20e3baf303a7a5b2da49f1f6b22be8ae02be69017c3db8eadbc3a9
475 SHA256 (FreeBSD-12.2-RELEASE-powerpc-memstick.img) = 2768337b74dbc3064f838b81d98eac8c3314cf8a9b94708a6b121b52d367a2c5
476 SHA256 (FreeBSD-12.2-RELEASE-powerpc-memstick.img.xz) = d3b771b2a8a20d6bc38f4d865372d89d741ae049f54beedc1bf08915476db5f2
477 SHA256 (FreeBSD-12.2-RELEASE-powerpc-mini-memstick.img) = 922e51d46bf57e2cdeb2fa3ff5bc2fa8b56f4a4f61eea9911c6278c54b65f254
478 SHA256 (FreeBSD-12.2-RELEASE-powerpc-mini-memstick.img.xz) = ce6e6f183dc90a356041baf016a84b33368c82f36335f499282485e82e630145
479
480
481 powerpc64:
482
483 SHA512 (FreeBSD-12.2-RELEASE-powerpc-powerpc64-bootonly.iso) = 4fe2e31c78ccb3511c92f8095fc6809a5abbccff2dde87cba812615dee73a3ac056c3f3b3d9687d99605b38a0ab0f07fb516854d972d5ddf160d00be3ddec65a
484 SHA512 (FreeBSD-12.2-RELEASE-powerpc-powerpc64-bootonly.iso.xz) = df68b371e9acdcb38ac066ebc93f834a52045514b453309af1aeaa896de0c03476f1545ca721bec4d94744a43b053180ca3f61552dd68eaf35237e03accec757
485 SHA512 (FreeBSD-12.2-RELEASE-powerpc-powerpc64-disc1.iso) = 8de9a8da1de7cac22f97305ab6ac930e008241e5be11097c3f78a3c1a3253e0bbcff345b55216614f91ba5384f0fa5f7328815e0589aa753daa98fe2e4011595
486 SHA512 (FreeBSD-12.2-RELEASE-powerpc-powerpc64-disc1.iso.xz) = 7debd7d6273a0f19475d9b61bd1f57f29762c47ee58669c256f4b41b837cda9ba04953900867d88a540881568a6a4c708f79ef49c390ec283a534891cfb5fb11
487 SHA512 (FreeBSD-12.2-RELEASE-powerpc-powerpc64-dvd1.iso) = ab63a35ac490e4dc97f694253c699f491116a720cc345b3a32cb3a2ca0c8f26f8e5ea312e66c9be93207fb2db537e370d2ec2ae5468f3a7c7fc656bdf6630b9f
488 SHA512 (FreeBSD-12.2-RELEASE-powerpc-powerpc64-dvd1.iso.xz) = fdbb67ce6f78bf9384d5a7d0e23a80b38549034d29bfac9353fd1d65d682f600f17598102bedc858bb5a36a149ab49971b3ca3b0293dfce3ac9d175a6c3c8ea9
489 SHA512 (FreeBSD-12.2-RELEASE-powerpc-powerpc64-memstick.img) = 6ab2e469368bf8f011f845b431d8b433b3a7a525f6ef48b20fc8aedbe9a1d52a4d4a34610247e251ba7c3ebf0516cf8b1323a69fe01a63e19ef343f7b67b2419
490 SHA512 (FreeBSD-12.2-RELEASE-powerpc-powerpc64-memstick.img.xz) = bd78ad50d2a88871650a6fa59ad2f1556486c047e5b2bbaae73f01968e8a027eb0da633ecb6dd5e8b6487884b25b7d9fd13844ba21556044fe1492a0484f27c1
491 SHA512 (FreeBSD-12.2-RELEASE-powerpc-powerpc64-mini-memstick.img) = 689ddf5092437a7e51d41a9dc5fe5bb71f2d07ec6da221676cd04d4054c41d6f02fb98b860fef9a93f15c79d1c2606e52f72ec54fb142e9984f45297110fcf41
492 SHA512 (FreeBSD-12.2-RELEASE-powerpc-powerpc64-mini-memstick.img.xz) = 36c8c5fffee7439631150773b96392c2dc55b654cbe5e75d5cb6f03b1f166edc755f3929303ecfefc2f5934e23946efc0804df6e6c795482f5317f83872a17e6
493
494 SHA256 (FreeBSD-12.2-RELEASE-powerpc-powerpc64-bootonly.iso) = d1226567cd54f02dd4cf3ad98be6426c147d6bbb7922734993c2a7b9373f2d45
495 SHA256 (FreeBSD-12.2-RELEASE-powerpc-powerpc64-bootonly.iso.xz) = a1ec2e7cb9908cbc26158bdefce6f358aa3acbda871b1ad78ae6d6843479671c
496 SHA256 (FreeBSD-12.2-RELEASE-powerpc-powerpc64-disc1.iso) = 0a85c8b34c043a4147c6c175542435e1618b5d95590d6509a4c271cbd6f95b11
497 SHA256 (FreeBSD-12.2-RELEASE-powerpc-powerpc64-disc1.iso.xz) = f0a20b84ab1aba40d563d175df35811e8b5af32550b137b12c418551b668d427
498 SHA256 (FreeBSD-12.2-RELEASE-powerpc-powerpc64-dvd1.iso) = 016db608679c7e36666a0319439ca92386f40931480f4c2e6de2bd780edb81da
499 SHA256 (FreeBSD-12.2-RELEASE-powerpc-powerpc64-dvd1.iso.xz) = d02a44d105217a220fe9a5aa3dfc56d9497d6acc334a7648dfc845db59ccbcb3
500 SHA256 (FreeBSD-12.2-RELEASE-powerpc-powerpc64-memstick.img) = 0dfff2ec5d416a62badf4c9f09f9cdb236b796dde5385c22726d931f12892e95
501 SHA256 (FreeBSD-12.2-RELEASE-powerpc-powerpc64-memstick.img.xz) = c2cbc4785eaaee2e3f632815d69f14f2ba8986b447f95cb59cf85a2cdbe999f7
502 SHA256 (FreeBSD-12.2-RELEASE-powerpc-powerpc64-mini-memstick.img) = b8f623d7ebef36bf0bde305ccbef6abf1c4c6979cb8cef5d596bd12edb1dae3e
503 SHA256 (FreeBSD-12.2-RELEASE-powerpc-powerpc64-mini-memstick.img.xz) = c36d650841c77364f91db4bdca620e3b32690b3e978a6485bad270f4d2263a99
504
505
506 powerpcspe:
507
508 SHA512 (FreeBSD-12.2-RELEASE-powerpc-powerpcspe-bootonly.iso) = d44e218026f2790c2681197e59aed5475bc959a572245980c9fb98f11ea028a8ed6f04956d65bf38a15bc97fc70665e4773dc8147c8d7014d5633b88c634b651
509 SHA512 (FreeBSD-12.2-RELEASE-powerpc-powerpcspe-bootonly.iso.xz) = 240a26fdd1b82dfc4a8edf53af3947c7dd3d492eb06511afd748748afde9de757cec4bad0b9b26d796261ecfd63d69406223c5f0a233c220c2eb3ddcfcc574c4
510 SHA512 (FreeBSD-12.2-RELEASE-powerpc-powerpcspe-disc1.iso) = 16018c09eb22d03a144aca306387dd89e6729908695abdfde28926613418725bec2dab7337257de571c5d71870059033104f093a17003b48064db82058b781ca
511 SHA512 (FreeBSD-12.2-RELEASE-powerpc-powerpcspe-disc1.iso.xz) = 676823b4c748e56869a0801e6916ee1a7e0af380dc5760714efe6f59e89932288019408453da9b03d221c2ae9f344e8624a8474b8f4bf70de410948550e9bbf3
512 SHA512 (FreeBSD-12.2-RELEASE-powerpc-powerpcspe-dvd1.iso) = 613a646c9108f0e0d6782aa125612a7923cd0eec3b49d047d4f3893c6a6938c09251839e007b53db481b6733ae751cc78ef88f2440862bd4b15e16494eee8762
513 SHA512 (FreeBSD-12.2-RELEASE-powerpc-powerpcspe-dvd1.iso.xz) = 577d44f9af1e136894947da1a0d58ab0c862e6d9f5cc4727e0ab52b2f2745c14a9fdc03782e2c9edb094c697edc4d055b2e4b95f0e03fc0247a459b0072e144a
514 SHA512 (FreeBSD-12.2-RELEASE-powerpc-powerpcspe-memstick.img) = 547b9355aa6edb75d6c42e04f6dece6dd9a52964c044d88237ef08476bf16d0c3fec696e11d7360942cac2bff8bef8d677d5eaf9d8da97b97a41ce287e7f31df
515 SHA512 (FreeBSD-12.2-RELEASE-powerpc-powerpcspe-memstick.img.xz) = dc04385343748e9f1eaa52b0e162174a32563d17b875e3eabb0f225d1f7be2246dd8fbb9b41c31496e243b56424b16b11c3905405274f279d750ecf359fef47c
516 SHA512 (FreeBSD-12.2-RELEASE-powerpc-powerpcspe-mini-memstick.img) = b3c9eb36315b2b1c6ec0fa1df5a183f75df45b8b35c20b2cc3c1a3501ab560109578930f2eaeb7d5766111a1c2ba2a9fe982c6efc6ba830c81aaa66507c6eed9
517 SHA512 (FreeBSD-12.2-RELEASE-powerpc-powerpcspe-mini-memstick.img.xz) = 48faccd49f14317b84a432d5653a9e9382a0d0b92391e6e8232a13c4e22291060d7364b2593eeee48b5997ce178cbffe04efba3575a9f01311135696d18acb10
518
519 SHA256 (FreeBSD-12.2-RELEASE-powerpc-powerpcspe-bootonly.iso) = 6468c27b22ca32743f7edc0ed87c69c0621564cfe7aee0304bfa6158fc523d19
520 SHA256 (FreeBSD-12.2-RELEASE-powerpc-powerpcspe-bootonly.iso.xz) = d69a1cc7f000dbfdfffcddf4fb81227aa314af7d9adfe8091e443b796a69cdcc
521 SHA256 (FreeBSD-12.2-RELEASE-powerpc-powerpcspe-disc1.iso) = e76e2a08276efd46baf0b24ee164e892528165bfb302ba2e978ae04c530f172f
522 SHA256 (FreeBSD-12.2-RELEASE-powerpc-powerpcspe-disc1.iso.xz) = 739b877800f63d9730d5b6067e0a7ef9bd4bf276e32b924b90bae001c2c5132d
523 SHA256 (FreeBSD-12.2-RELEASE-powerpc-powerpcspe-dvd1.iso) = 5bda07e5bc727085368eff9cfd711fee6a7dc1c489c52fc5ce8d4489a7d947ff
524 SHA256 (FreeBSD-12.2-RELEASE-powerpc-powerpcspe-dvd1.iso.xz) = d87a6cf46f427bb3da974300b20e1d5084545f72ace04928229a852861c57c6c
525 SHA256 (FreeBSD-12.2-RELEASE-powerpc-powerpcspe-memstick.img) = 94a59f00bc2b70938e42d02891985a6c7314260ae6d9669f1444a9666fc7a236
526 SHA256 (FreeBSD-12.2-RELEASE-powerpc-powerpcspe-memstick.img.xz) = 26be2b200e11826753d6524ebe5c65e69357026a85f5e2bd66d28dbbcb6c53bf
527 SHA256 (FreeBSD-12.2-RELEASE-powerpc-powerpcspe-mini-memstick.img) = 7ebc8a976184eb21515c8e10de392a37e61868083ed3c0473b5d9fc24d29805f
528 SHA256 (FreeBSD-12.2-RELEASE-powerpc-powerpcspe-mini-memstick.img.xz) = 20337c824deac4aca6e34e53e3a46b252cac1ad87a006be97d6422d99b8783b3
529
530
531 sparc64:
532
533 SHA512 (FreeBSD-12.2-RELEASE-sparc64-bootonly.iso) = 11b80a1e09134c13e89c759327f6cf94731c4e95bfa10e22c107de7a2771f03f9699d77335f342b131dbce6cc09299035c465e3f77bd3038a477e9d562ce463b
534 SHA512 (FreeBSD-12.2-RELEASE-sparc64-bootonly.iso.xz) = 7c293e0c5533609357fd1fb8d04d3bda623f6382001644f325c1270a22c1b79f9bfd7c33dc8393b86db6d688b89b8804027f5de4e7804b49768ef43338bfc97e
535 SHA512 (FreeBSD-12.2-RELEASE-sparc64-disc1.iso) = 72a93fec891af9a731f65106d8bec9fdeb91b7c13737cbe85c721b45c52873a0ef911848c74b5a20dde2d08d4a9010b95deacf114542f4b71c3e6503b31e4a9d
536 SHA512 (FreeBSD-12.2-RELEASE-sparc64-disc1.iso.xz) = 4cdda67204c29fd0b35066ec39b9771e680800c178f2fb75728ba0e29164fd936475c249433acb382daad1c1d40c82578ebf0b6a131091dc9f6cb85971f3b9ea
537 SHA512 (FreeBSD-12.2-RELEASE-sparc64-dvd1.iso) = aff90155def4dab46676f87c0153ca5d0ab97e81a19d16bb342243abdc397ca6c251a5641d9075d2be810bbaa31bf921af1daff261c16cae0ebb6857f3def69d
538 SHA512 (FreeBSD-12.2-RELEASE-sparc64-dvd1.iso.xz) = 3b3aa8fafde8778c19242e12d1310866db6143a9a926d9e694d31583fd794e7c09e94351cc3d8cf81b2a5573974160b6b2329d44c6f99e0b780a821cacbb7270
539
540 SHA256 (FreeBSD-12.2-RELEASE-sparc64-bootonly.iso) = 33336bf0bfff8e74bccdd5a7ca73306154e62bfcc5cb154bb4d14eed45ee0b6a
541 SHA256 (FreeBSD-12.2-RELEASE-sparc64-bootonly.iso.xz) = 31504bb3c211818f8bbbd37f043190fcca1ef1da9e4c748655f0281330c65ff1
542 SHA256 (FreeBSD-12.2-RELEASE-sparc64-disc1.iso) = 485d756a8ec56c73601d13dd8a3356225e42c34df44ff37784dea00c127a54b8
543 SHA256 (FreeBSD-12.2-RELEASE-sparc64-disc1.iso.xz) = 5c637765409ac8c5bdaf2671b771f04ceabadfb64bcbcccb56ac60ac86a2720a
544 SHA256 (FreeBSD-12.2-RELEASE-sparc64-dvd1.iso) = ca21d77e7241b6b30a0fbb8f9e76d0ec29245e92929c4126a0a2f0054db0116d
545 SHA256 (FreeBSD-12.2-RELEASE-sparc64-dvd1.iso.xz) = a78421dbe2c203e8f8f7562455a73bfee6d837ae0d52968750872614c698a379
546
547
548 aarch64 GENERIC:
549
550 SHA512 (FreeBSD-12.2-RELEASE-arm64-aarch64-memstick.img) = 5df35108516e11253075b4008ce8f970d0541d6b51b136b1e7616a2354b8d216ef714c241fb99578e4468b13187d44dbb34b82ec6fed0b7f407a0afee7cb5b03
551 SHA512 (FreeBSD-12.2-RELEASE-arm64-aarch64-memstick.img.xz) = 003f4f19ca1276fce9943d8909ab26734ac0b4fae7ca42d582c2ab7269e99b28fd0de18e057e4c785de87248cbb3bbc27ae5d056fe25915af22bbdcc69b65a75
552 SHA512 (FreeBSD-12.2-RELEASE-arm64-aarch64-mini-memstick.img) = 5acdb5298b67a24aacd040674abb809315b6126b1017049b9431cd215f0152909898b1e554456e004364633609cd9caa41d120e1dfa91a521fe1c42579d4e587
553 SHA512 (FreeBSD-12.2-RELEASE-arm64-aarch64-mini-memstick.img.xz) = be9a569a1f450fd59edf6d8e75c0c0ac3fa65ba9c703f2a951593724f021070fcc21e30133db1558d32eb4e22337bdae9667d5cdf68e0db3612bc3ddfb31504c
554
555 SHA256 (FreeBSD-12.2-RELEASE-arm64-aarch64-memstick.img) = 59642a466f75b736c3ef7bc09ab818b3958943ee5b159a3750e2647dc1cd2a38
556 SHA256 (FreeBSD-12.2-RELEASE-arm64-aarch64-memstick.img.xz) = c9fb961372d9282073813eff38c09902a171285b50a8cbc59de036acf7fcdb84
557 SHA256 (FreeBSD-12.2-RELEASE-arm64-aarch64-mini-memstick.img) = 9499eb3d182f4e692e6fb0547b8f179a5b10c6121bea4f27056144a5270f5bc0
558 SHA256 (FreeBSD-12.2-RELEASE-arm64-aarch64-mini-memstick.img.xz) = 6d0b38f9d4a182a2a860e2b5b71994017a2bb654bd5990bb9377e7b6c56766e4
559
560
561 aarch64 RPI3:
562
563 SHA512 (FreeBSD-12.2-RELEASE-arm64-aarch64-RPI3.img.xz) = 8ae44c1cd4224cf34a830044d6c4d1439563ba308ae1096c968f1319d640c776c6b164170f4d916fc492474ee866619955d2ba6e6917c074aeaecd7f5ed1a0ea
564
565 SHA256 (FreeBSD-12.2-RELEASE-arm64-aarch64-RPI3.img.xz) = c11603f31f9736744946fb3125063fdf05e2abfcbfcd3b43be025ec85c493ef5
566
567
568 aarch64 PINE64:
569
570 SHA512 (FreeBSD-12.2-RELEASE-arm64-aarch64-PINE64.img.xz) = edccfbec870b18b566b0068f919f767b1c2146d3dc2ecd562332a2a7d5fe551e4ef3ed9b27fb0f6f343ba19bb457a11a2f052eebb14883094f441c62979b38a1
571
572 SHA256 (FreeBSD-12.2-RELEASE-arm64-aarch64-PINE64.img.xz) = 8d96f8d3cecca0e6036dc1bb8eb576b716b574b082705b0e784d4b68beeb4123
573
574
575 aarch64 PINE64-LTS:
576
577 SHA512 (FreeBSD-12.2-RELEASE-arm64-aarch64-PINE64-LTS.img.xz) = 987c1084cac75348d52a8d3f51e6d4b9d91b93a56d839e6346b9872111205ebb60f8d88aeee1308c92ae6b1e633fa0854848f50d1ec4b4e06f00229d9b773cae
578
579 SHA256 (FreeBSD-12.2-RELEASE-arm64-aarch64-PINE64-LTS.img.xz) = 9eedbd68029ee522fed9ebed6d664277b9b9dbd87229e33c51668375a45ca369
580
581
582 armv7 BANANAPI:
583
584 SHA512 (FreeBSD-12.2-RELEASE-arm-armv7-BANANAPI.img.xz) = 81393337057d10da85961fbcfd9a70547667d7019be3d760ebdf79c60527d1a9cf57c7acf7fa6addc9f8cac5e73e1dd000ee9fea757e334cd64b29c813b4344d
585
586 SHA256 (FreeBSD-12.2-RELEASE-arm-armv7-BANANAPI.img.xz) = 2120668375c8af906c7e8062c0a18cb4e99e4f102fa5ad408272974482a2f55f
587
588
589 armv7 CUBIEBOARD:
590
591 SHA512 (FreeBSD-12.2-RELEASE-arm-armv7-CUBIEBOARD.img.xz) = a275ea08e0b6df0db530bb477b496882c6ef61e06998a1fba119c6cbfa4f1f67ac92b0714df0ad27d3400bf762e3e467f0acf19a4dfc1fe7e7bbc0b593dc2c7b
592
593 SHA256 (FreeBSD-12.2-RELEASE-arm-armv7-CUBIEBOARD.img.xz) = 10d996025f40997fa1f857b9a6cb991a84f4faf4feee0d1679450818123505f3
594
595
596 armv7 CUBIEBOARD2:
597
598 SHA512 (FreeBSD-12.2-RELEASE-arm-armv7-CUBIEBOARD2.img.xz) = 0e08c60f3a119ad78c4bc081fb810fd91b2ba3b31ffc3e2eb75c4223d7ffd2e506241d205b877c16cf50916d92552c397c55336823f974f11f81a3af13d6a414
599
600 SHA256 (FreeBSD-12.2-RELEASE-arm-armv7-CUBIEBOARD2.img.xz) = edf76dd3e6fbfcf465466b2bf350a5616ec29a91695f6c14f14b35b922aaa923
601
602
603 armv7 CUBOX-HUMMINGBOARD:
604
605 SHA512 (FreeBSD-12.2-RELEASE-arm-armv7-CUBOX-HUMMINGBOARD.img.xz) = 3772cef45bcd4cda23fd10077683cdd122f378b4c3a5ae97ca39a9306599b602736ece948852312c53f17298052192888222fe4ac04c3073d90e24cd35e2b8c8
606
607 SHA256 (FreeBSD-12.2-RELEASE-arm-armv7-CUBOX-HUMMINGBOARD.img.xz) = 3603945478bed8aff378390df0eb69b31ffe008bcbcc498bbe079fc98a82c180
608
609
610 armv7 GENERICSD:
611
612 SHA512 (FreeBSD-12.2-RELEASE-arm-armv7-GENERICSD.img.xz) = 11ad4b999b641d3804f5c2f205aef3ed3732885f78e36636e931454cd48dac8420db4c6e66b7d8984e06eafb4428bb5db77c97fceeebc2da891635583ba6e13f
613
614 SHA256 (FreeBSD-12.2-RELEASE-arm-armv7-GENERICSD.img.xz) = 79b57227797d98d7d0d7b40144aec80fb85270b53ac047a4f066620844c1a119
615
616
617 armv6 RPI-B:
618
619 SHA512 (FreeBSD-12.2-RELEASE-arm-armv6-RPI-B.img.xz) = 5fc18ff8a7e27e26ca2971d3d85352124ae9e8e5189f3319782ca3f8d592055f67095c792733400471c41262c90eb364f1070f8469da0626acf4e800b75896ce
620
621 SHA256 (FreeBSD-12.2-RELEASE-arm-armv6-RPI-B.img.xz) = 207097afd24c41103caa2f0cc5992afe4d968abaad5f6828d7e6b6a065ca024e
622
623
624 armv7 RPI2:
625
626 SHA512 (FreeBSD-12.2-RELEASE-arm-armv7-RPI2.img.xz) = 8eb949dbc37aca12afd2236488632dc5d166dc09cdd2eedff19ab018ac583ffa99f2f6b537c0d59b3480af38fa6bed36d54e8a024ce2b42b1f540bc39baf47e3
627
628 SHA256 (FreeBSD-12.2-RELEASE-arm-armv7-RPI2.img.xz) = 95cdd6b7d9da49b85e2b85e53af75cdb8a1e08a4dc9ddd786196f44d4ded14a6
629
630
631 armv7 WANDBOARD:
632
633 SHA512 (FreeBSD-12.2-RELEASE-arm-armv7-WANDBOARD.img.xz) = d47df12567ce975759ffe76a534756f658247a9c3585bce4f1ec0396e1a2a738b5cab2e9776d41486b9ecd20a58abc04b9fd61b2b550b282be5fd1c8f8e599b0
634
635 SHA256 (FreeBSD-12.2-RELEASE-arm-armv7-WANDBOARD.img.xz) = 692b9e17baf5d14997a7a4dd2d5f2fe0edaa342ab2d01900f3e6e3ea580a0e53
636
637
638 Virtual Machine Disk Image Checksums
639
640 amd64 (x86_64):
641
642 SHA512 (FreeBSD-12.2-RELEASE-amd64.qcow2.xz) = 33c2352abbc926651491827a8496196c3d1f6f27ebd76d5611906a9f32a170020923d833de5e55d4daaafbf0a2b2050db7bc1415998eb7bff430c12a7b781a08
643 SHA512 (FreeBSD-12.2-RELEASE-amd64.raw.xz) = ead6a3ae3d9be2a7a459049dece82d7ed0d1f037de8bb9e1d8fb49e7cf225ffebd91d7fdb58a7b595b2a9fb3adf8455b71f2781fc9d26b2cd52e9d5226d48007
644 SHA512 (FreeBSD-12.2-RELEASE-amd64.vhd.xz) = b810f364c90eca105fcebeee8dd719023d399bc9c668b930ef53d210f5233f1ef41f3273c4239869cf60c0bc62ef1851493b2129ed1b4a0a1b68af2597f7a9dd
645 SHA512 (FreeBSD-12.2-RELEASE-amd64.vmdk.xz) = 54987c803fd75929012894763a4add6cef7b8da1bba2a52bf636a8eb52477a1d6dfa9d037bcea53bd625eb0463952d48b08805af544848f9efae422b3467faf5
646
647 SHA256 (FreeBSD-12.2-RELEASE-amd64.qcow2.xz) = a0c5769d9ff776aa8f01661cf4b95a9e30db9dd31839c6cc4d3e86cce730956a
648 SHA256 (FreeBSD-12.2-RELEASE-amd64.raw.xz) = 0f8593382b6833658c6f6be532d4ffbedde7b75504452e27d912a0183f72ab56
649 SHA256 (FreeBSD-12.2-RELEASE-amd64.vhd.xz) = 7c3346d448b1f7890f939f8cbe4710240d75482cdc53537dc1635f1cd9a7d4d2
650 SHA256 (FreeBSD-12.2-RELEASE-amd64.vmdk.xz) = 39439ff0dd31e48b62c20bee1e6c970bcbf672bf9b1fdef166368da3154ae43a
651
652
653 i386 (x86):
654
655 SHA512 (FreeBSD-12.2-RELEASE-i386.qcow2.xz) = 0ecee5d21df2998dc733b537233974d6a6005ee79aec2ab8c1e8991ef13faa1011dd150b323582942653ee6f88f2a032c216cf2f1ab83f38476f828471394cc2
656 SHA512 (FreeBSD-12.2-RELEASE-i386.raw.xz) = fc2034b279571648b05c4f6ec5f4a45bd83310e1f9511516919b3e61f97db77471719816275769e37aeb8608072a7c991a116682c0f0fc41d73ddb6d55750bce
657 SHA512 (FreeBSD-12.2-RELEASE-i386.vhd.xz) = a16da143aec710d9faa2dd39bdc64ea6024edb60de2f297fb5f65ac6343705400153d0333fe9467c814a8f6e529eddfc5b959482dd6a6c261a63ab793a160b23
658 SHA512 (FreeBSD-12.2-RELEASE-i386.vmdk.xz) = 50660f5615208a5a2a6e6a40661f5c649a4e6d0c3f5a86d5eaa169f44bb2239491a633d912c4b663a23d1c1d87db1cf856ae7ee9679b64fcd40534304298906f
659
660 SHA256 (FreeBSD-12.2-RELEASE-i386.qcow2.xz) = 9b4fdcda43f93accafc5a066d90aaf4143d8205c904e2f05051cb68bde3502cb
661 SHA256 (FreeBSD-12.2-RELEASE-i386.raw.xz) = 963ea53cc0deeafcfd6a1851d3d0c5baf4a661c3e3c682e4b3d4e6a40bad7f5a
662 SHA256 (FreeBSD-12.2-RELEASE-i386.vhd.xz) = 2cf2c392822c8d654a2c0b2854e80527309184984b002afcebe2d7269eab71ae
663 SHA256 (FreeBSD-12.2-RELEASE-i386.vmdk.xz) = ece59134fd93972375e93b5067cef4c0fe730973d3a349fadee40ff96130a5ef
664
665
666 aarch64 (arm64):
667
668 SHA512 (FreeBSD-12.2-RELEASE-arm64-aarch64.qcow2.xz) = ea14f57c3501d4ecafb17863b9f470f38d4b2a88c508999ac17d19f7f45aeb68ae8b15ebc368a3442e5ff8e9cfadd4c0837806232af7cd81f6de6e343c0c3849
669 SHA512 (FreeBSD-12.2-RELEASE-arm64-aarch64.raw.xz) = 65091e7355893e5b5a1ad2594046192ce8e57324679a20dd0e281337435974ec7567c8b1545db1c265397c6b4569f4991f2b0495697568d3031d70de54c081bb
670 SHA512 (FreeBSD-12.2-RELEASE-arm64-aarch64.vhd.xz) = f9df34a94c979eb33d210075888b9253662e1aeeac0685d5164b51e6423ba791c7820f6c954dda789cfa2840a0b5b816bfbf98feb2cea604aae7adeec05e3445
671 SHA512 (FreeBSD-12.2-RELEASE-arm64-aarch64.vmdk.xz) = 4d0c7cf14eef2b3093b3282ec1db69793e7ea84a867a299cbee28683251d375e19a5e6241907fc2cfa087cfdafa7aba90d204a5e1c27a5b421572ca1909c6341
672
673 SHA256 (FreeBSD-12.2-RELEASE-arm64-aarch64.qcow2.xz) = e9a4698d05adb7db2f0683b4bb8edeb71f8607eb94de902e3259e99785675d13
674 SHA256 (FreeBSD-12.2-RELEASE-arm64-aarch64.raw.xz) = 879201066c8ab142466eb9dd5921196742610b4226ac988aa8975ef26f120c03
675 SHA256 (FreeBSD-12.2-RELEASE-arm64-aarch64.vhd.xz) = e8b333f92708bde816996aefefd21bbc77c81027ba2dfb900899a1be6ecab18d
676 SHA256 (FreeBSD-12.2-RELEASE-arm64-aarch64.vmdk.xz) = b14fa9c8d98f9ecb7e67419ab84b8ed3ff8c9f5259fd7dcd4d05dc52ad0bf6e8
677
678
679 Love FreeBSD? Support this and future releases with a donation to The
680 FreeBSD Foundation! https://www.FreeBSDFoundation.org/donate/
681
682 -----BEGIN PGP SIGNATURE-----
683
684 iQIzBAEBCAAdFiEEjRJAPC5sqwhs9k2jAxRYpUeP4pMFAl+Yl1UACgkQAxRYpUeP
685 4pP/Dg//VCG7zAGfFGYjVSLb3OtnAa9KAyXV6ZT3em/bs+bcB9+OrcOAqJrYVRbc
686 BAYVqqbGIRcChI9Tr9Y1G0wLez+fOSvAk/wBjXm3iYGSFSeMIejFKXLEKl6PY3ny
687 /t/jVPU9YPg4P/Y7Pcbt7ts/S0xccPmwKyqWWPJ6IJTA6LY3AwndmtKsXe5eAbi9
688 2X2MV/FVQAhNGWOwVJJEkmTgvw11e49SCpS24EKLoKkdqDI4+u2WLjO+PKOEaTXE
689 bQp6TtxI4XEdgRkUroVAEGpsN9AsnQWd9NDxQrQP4hwndKQAVLYUUUz17JRmnSUn
690 WIZCaZe+PkL391h3nKT0GfUl41iWXIDDy/eMWSsOE8evZqs64TPtStvy/9ReQSg3
691 A5UK4rVty91Fwelbn/nD5D207g/p1KlVVC2JcuXXxRKaMbQfb1W62lj4WdMnBqS6
692 dgFvRuGO374C7RojGRFVNKj4xjV7MAI2pEE8EwVoZXFd719ytmeOFmICmYXXz4BH
693 j09CYmljn7S8AG/xmAT2H4h0xFMVLr4YYOq2eazSL7fXVDy2c3s3I+lE3pSNgbsZ
694 1oFwiHtkdAkYtdRGmioKF2kPT6SNKjQvwwC8A97eicvDatGiSE+eg+LBAcNyNf77
695 F4mEbRuSs6zvjWIvcvn2fq8r/ahiPDeq7GL5lvJF8f1rdefrfDQ=
696 =Cpal
697 -----END PGP SIGNATURE-----
698 _______________________________________________
699 freebsd-announce@freebsd.org mailing list
700 https://lists.freebsd.org/mailman/listinfo/freebsd-announce
701 To unsubscribe, send any mail to "freebsd-announce-unsubscribe@freebsd.org"</content>
702 <tags>freebsd</tags>
703 <author>
704 <name>gjb@FreeBSD.org</name>
705 </author>
706 </entry>
707 <entry>
708 <id>tag:bsdsec.net,2005:Article/1220</id>
709 <published>2020-10-27T21:13:23Z</published>
710 <updated>2020-10-27T21:13:23Z</updated>
711 <link rel="alternate" type="text/html" href="https://bsdsec.net/articles/openbsd-errata-october-29th-2020-bgpd"/>
712 <title>OpenBSD Errata: October 29th, 2020 (bgpd)</title>
713 <content type="html">Errata patches for OpenBGPD have been released for OpenBSD 6.7 and 6.8.
714
715 In bgpd, the roa-set parser could leak memory.
716
717 Binary updates for the amd64, i386, and arm64 platforms are available via
718 the syspatch utility. Source code patches can be found on the respective
719 errata page:
720
721 https://www.openbsd.org/errata67.html
722 https://www.openbsd.org/errata68.html
723 </content>
724 <tags>openbsd</tags>
725 <author>
726 <name>tj@openbsd.org</name>
727 </author>
728 </entry>
729 <entry>
730 <id>tag:bsdsec.net,2005:Article/1219</id>
731 <published>2020-10-21T22:06:17Z</published>
732 <updated>2020-10-21T22:06:17Z</updated>
733 <link rel="alternate" type="text/html" href="https://bsdsec.net/articles/freebsd-announce-freebsd-quarterly-status-report-third-quarter-2020"/>
734 <title>[FreeBSD-Announce] FreeBSD Quarterly Status Report - Third Quarter 2020</title>
735 <content type="html">
736 --6vqnfjaiktnxv5lf
737 Content-Type: text/plain; charset=iso-8859-1
738 Content-Disposition: inline
739 Content-Transfer-Encoding: quoted-printable
740
741 FreeBSD Project Quarterly Status Report - Third Quarter 2020
742 Introduction
743
744 This report covers FreeBSD related projects for the period between July
745 and September, and is the third of four planned reports for 2020.
746
747 This quarter brings a good mix of additions and changes to the FreeBSD
748 Project and community, from a diverse number of teams and people
749 covering everything from architectures, continuous integration,
750 wireless networking and drivers, over drm, desktop and third-party
751 project work, as well as several team reports, along with many other
752 interesting subjects too numerous to mention.
753
754 As the world is still affected by the epidemic, we hope that this
755 report can also serve as a good reminder that there is good work that
756 can be done by people working together, even if we're apart.
757
758 We hope you'll be as interested in reading it, as we've been in making
759 it. Daniel Ebdrup Jensen, on behalf of the quarterly team.
760 __________________________________________________________________
761
762 FreeBSD Team Reports
763
764 * FreeBSD Foundation
765 * FreeBSD Release Engineering Team
766 * Cluster Administration Team
767 * Continuous Integration
768 * Ports Collection
769 * FreeBSD Office team - 3rd quarter 2020 report
770 * FreeBSD Graphics Team status report
771
772 Projects
773
774 * FreeBSD on Microsoft HyperV and Azure
775 * Building FreeBSD on non-FreeBSD hosts
776 * Git Migration Working Group
777 * Linux compatibility layer update
778 * LLDB Debugger Improvements
779 * Lua usage in FreeBSD
780 * NFS over TLS implementation
781 * syzkaller on FreeBSD
782
783 Kernel
784
785 * DRM Drivers Update
786 * DTS Update
787 * DesignWare Ethernet adapter driver improvements
788 * Google Summer of Code'20 Project - eBPF XDP Hooks
789 * ENA FreeBSD Driver Update
790 * IPSec Extended Sequence Number (ESN) support
791 * NXP ARM64 SoC support
792 * Addition of PowerPC64LE Architecture
793 * ure - USB 3.0 Gigabit Ethernet Driver update
794 * Stateless hardware offloads for VXLANs
795 * Wireless updates
796 * ZSTD Compression in ZFS
797
798 Architectures
799
800 * CheriBSD 2020 Q3
801 * FreeBSD/RISC-V Project
802
803 Ports
804
805 * Update to grub-bhyve
806 * KDE on FreeBSD
807
808 Documentation
809
810 * DOCNG on FreeBSD
811
812 Third-Party Projects
813
814 * Potluck - Flavour &amp; Image Repository for pot
815 __________________________________________________________________
816
817 FreeBSD Team Reports
818
819 Entries from the various official and semi-official teams, as found in
820 the Administration Page.
821
822 FreeBSD Foundation
823
824 Contact: Deb Goodkin &lt;deb@FreeBSDFoundation.org&gt;
825
826 The FreeBSD Foundation is a 501(c)(3) non-profit organization dedicated
827 to supporting and promoting the FreeBSD Project and community
828 worldwide. Funding comes from individual and corporate donations and is
829 used to fund and manage software development projects, conferences and
830 developer summits, and provide travel grants to FreeBSD contributors.
831 The Foundation purchases and supports hardware to improve and maintain
832 FreeBSD infrastructure and provides resources to improve security,
833 quality assurance, and release engineering efforts; publishes marketing
834 material to promote, educate, and advocate for the FreeBSD Project;
835 facilitates collaboration between commercial vendors and FreeBSD
836 developers; and finally, represents the FreeBSD Project in executing
837 contracts, license agreements, and other legal arrangements that
838 require a recognized legal entity.
839
840 Here are some highlights of what we did to help FreeBSD last quarter:
841
842 COVID-19 Impact to the Foundation
843
844 Like other organizations, we put policies in place for all of our staff
845 members to work from home. We also put a temporary ban on travel for
846 staff members. We are continuing our work supporting the community and
847 Project, but some of our work and responses may be delayed because of
848 changes in some of our priorities and the impact of limited childcare
849 for a few of our staff members.
850
851 Partnerships and Commercial User Support
852
853 We help facilitate collaboration between commercial users and FreeBSD
854 developers. We also meet with companies to discuss their needs and
855 bring that information back to the Project. Not surprisingly, the stay
856 at home orders, combined with our company ban on travel during Q3 made
857 in-person meetings non-existent. However, the team was able to continue
858 meeting with our partners and commercial users virtually. These
859 meetings help us understand some of the applications where FreeBSD is
860 used.
861
862 We are currently scheduling Zoom company meetings for Q4, please reach
863 out if you would like to schedule a meeting with us.
864
865 Fundraising Efforts
866
867 Last quarter we raised $192,874.43! Thank you to the individuals and
868 organizations that stepped in, to help fund our efforts. We'd like to
869 thank Arm for their large contribution last quarter, which helped bring
870 our 2020 fundraising effort to $521k. We hope other organizations will
871 follow their lead and give back to help us continue supporting FreeBSD.
872
873 These are trying times, and we deeply appreciate every donation that
874 has come in from $5 to $150,000. We're still here giving 110% to
875 supporting FreeBSD!
876
877 We are 100% funded by donations, and those funds go towards software
878 development work to improve FreeBSD, FreeBSD advocacy around the world,
879 keeping FreeBSD secure, continuous integration improvements, sponsoring
880 BSD-related and computing conferences (even the virtual events!), legal
881 support for the Project, and many other areas.
882
883 Please consider making a donation to help us continue and increase our
884 support for FreeBSD.
885
886 We also have the Partnership Program, to provide more benefits for our
887 larger commercial donors. Find out more information about the
888 partnership program and share with your companies!
889
890 OS Improvements
891
892 A number of FreeBSD Foundation grant recipients started, continued
893 working on, or completed projects during the third quarter. These
894 include:
895 * Ongoing WiFi and Linux KPI layer improvements.
896 * Linuxulator application compatibility.
897 * DRM / Graphics driver updates.
898 * Zstd compression for OpenZFS.
899 * Online RAID-Z expansion.
900 * Modernized LLDB target support for FreeBSD.
901
902 You can find more details about most of these projects in other
903 quarterly
904
905 reports.
906
907 Staff members also worked on a number of larger projects, including:
908 * Run-Time Dynamic Linker (rtld) and kernel ELF loader improvements.
909 * Rewritten UNIX domain socket locking.
910 * Build infrastructure.
911 * Open system call path handling support for O_BENEATH,
912 O_RESOLVE_BENEATH.
913 * arm64 support.
914 * Migration to a Git repository.
915
916 Many of these projects also have detailed entries in other quarterly
917 report
918
919 entries.
920
921 Staff members also put in significant effort in many ways other than
922 larger, individual projects. These include assisting with code reviews,
923 bug report triage, security report triage and advisory handling,
924 addressing syzkaller reports, and ongoing maintenance and bug fixes in
925 functional areas such as the tool chain, developer tools, virtual
926 memory kernel subsystem, low-level x86 infrastructure, sockets and
927 protocols, and others.
928
929 University of Waterloo Co-op
930
931 With the transition to working from home, the Foundation decided to
932 again take on three University of Waterloo Co-op students for the Fall
933 2020 term (September to December). Tiger returns for a second term,
934 joined by new students Yang and Zac. Projects for the term include more
935 work on ELF Tool Chain, application of Capsicum to additional
936 utilities, testing and integration of FreePBX and Asterisk VOIP
937 software, pkgbase, and exploring containerization tooling.
938
939 Continuous Integration and Quality Assurance
940
941 The Foundation provides a full-time staff member and funds projects on
942 improving continuous integration, automated testing, and overall
943 quality assurance efforts for the FreeBSD project.
944
945 During the third quarter of 2020, Foundation staff continued improving
946 and monitoring the Project's CI infrastructure, and working with
947 experts to fix the failing builds and the regressions found by tests.
948 The setting up of dedicated VM host for running tests is completed. New
949 feature developments and the CI staging environment is in progress. We
950 are also working with other teams in the Project for their testing
951 needs. For example, tests of non-x86 architectures now run
952 periodically, and improve the CI of the embedded systems. We are also
953 working with many external projects and companies to improve the CI
954 between their products and FreeBSD.
955
956 See the FreeBSD CI section of this report for completed work items and
957 detailed information.
958
959 Supporting FreeBSD Infrastructure
960
961 The Foundation provides hardware and support to improve the FreeBSD
962 infrastructure. Last quarter, we continued supporting FreeBSD hardware
963 located around the world. We coordinated efforts between the new NYI
964 Chicago facility and clusteradm to start working on getting the
965 facility prepared for some of the new FreeBSD hardware we are planning
966 on purchasing. NYI generously provides this for free to the Project. We
967 also worked on connecting with the new owners of the Bridgewater site,
968 where most of the FreeBSD infrastructure is located.
969
970 Some of the purchases we made for the Project last quarter to support
971 infrastructure includes:
972 * Spamhaus spam filtering software to limit the amount of spam on the
973 mailing lists.
974 * 5 application servers to run tasks like bugzilla, wiki, website,
975 cgi, Phabricator, host git, etc.
976 * 1 server to replace the old pkg server and provide a lot more IOPS
977 to avoid the slowdowns seen during peak times of the day where the
978 disks just cannot keep up with the request volume.
979 * 1 server for exp-runs to make them faster.
980 * 1 server to build packages more frequently.
981
982 FreeBSD Advocacy and Education
983
984 A large part of our efforts are dedicated to advocating for the
985 Project. This includes promoting work being done by others with
986 FreeBSD; producing advocacy literature to teach people about FreeBSD
987 and help make the path to starting using FreeBSD or contributing to the
988 Project easier; and attending and getting other FreeBSD contributors to
989 volunteer to run FreeBSD events, staff FreeBSD tables, and give FreeBSD
990 presentations.
991
992 The FreeBSD Foundation sponsors many conferences, events, and summits
993 around the globe. These events can be BSD-related, open source, or
994 technology events geared towards underrepresented groups. We support
995 the FreeBSD-focused events to help provide a venue for sharing
996 knowledge, to work together on projects, and to facilitate
997 collaboration between developers and commercial users. This all helps
998 provide a healthy ecosystem. We support the non-FreeBSD events to
999 promote and raise awareness of FreeBSD, to increase the use of FreeBSD
1000 in different applications, and to recruit more contributors to the
1001 Project. As is the case for most of us in this industry, COVID-19 has
1002 put our in-person events on hold. In addition to attending virtual
1003 events, we are continually working on new training initiatives and
1004 updating our selection of how-to guides to facilitate getting more
1005 folks to try out FreeBSD.
1006
1007 Check out some of the advocacy and education work we did last quarter:
1008 * Launched our FreeBSD Fridays series of 101 classes. Topics included
1009 an Introduction to FreeBSD, FreeBSD Installfest, Introduction to
1010 Security, Introduction to ZFS and more. Videos of the past sessions
1011 and a schedule of upcoming events can be found here.
1012 * Attended and presented at OSI's State of the Source conference. The
1013 event was held virtually, September 9-11, 2020.
1014 * Launched the redesign of the FreeBSD Foundation Website.
1015 * Announced the 20th Anniversary of the FreeBSD Foundation.
1016 * Participated as an Admin for Google Summer of Code 2020
1017 * Continued to promote the FreeBSD Office Hours series including
1018 holding our own Foundation led office hours. Videos from the one
1019 hour sessions can be found on the Project's YouTube Channel. You
1020 can watch ours here.
1021 * Interviewed members of the outgoing FreeBSD Core Team to get their
1022 thoughts on their term.
1023 * Began working with the FreeBSD Vendor Summit planning committee on
1024 the November 2020 Vendor Summit.
1025 * Promoted the Foundation's 20th Anniversary and our work to support
1026 the FreeBSD Project in the It's FOSS Article. FreeBSD Foundation
1027 Celebrates 20 Years of Promoting and Supporting FreeBSD Project.
1028 * Authored a Beginners Guide to FreeBSD for Fosslife.
1029 * Committed to sponsoring All Things Open as a media Sponsor.
1030 * Committed to sponsoring the OpenZFS Developers Summit at the Bronze
1031 level.
1032 * Became an International RISC-V Member.
1033 * Committed to giving a FreeBSD talk at the nerdear.la conference on
1034 October 20th.
1035
1036 Keep up to date with our latest work in our
1037
1038 monthly newsletters.
1039
1040 Netflix provided an update on how and why they use FreeBSD in our
1041 latest Contributor Case Study.
1042
1043 We help educate the world about FreeBSD by publishing the
1044 professionally produced FreeBSD Journal. As we mentioned previously,
1045 the FreeBSD Journal is now a free publication. Find out more and access
1046 the latest issues at https://www.FreeBSDfoundation.org/journal/.
1047
1048 You can find out more about events we attended and upcoming events at
1049 https://www.FreeBSDfoundation.org/news-and-events/.
1050
1051 Legal/FreeBSD IP
1052
1053 The Foundation owns the FreeBSD trademarks, and it is our
1054 responsibility to protect them. We also provide legal support for the
1055 core team to investigate questions that arise. We updated our Trademark
1056 Usage Terms and Conditions on July 1, 2020.
1057
1058 Go to the FreeBSD Foundation's web site to find out how we support
1059 FreeBSD and how we can help you!
1060
1061 ### Other
1062
1063 We welcomed Andrew Wafaa and Kevin Bowling to our board of directors,
1064 to help govern the Foundation and guide us with our strategic
1065 direction. We have more information about our new board members on our
1066 website.
1067 __________________________________________________________________
1068
1069 FreeBSD Release Engineering Team
1070
1071 Links
1072 FreeBSD 12.2-RELEASE schedule=20
1073 URL: https://www.freebsd.org/releases/12.2R/schedule.html
1074 FreeBSD 12.2 test builds=20
1075 URL: https://www.freebsd.org/where.html#helptest
1076 FreeBSD development snapshots=20
1077 URL: https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/
1078
1079 Contact: FreeBSD Release Engineering Team &lt;re@FreeBSD.org&gt;
1080
1081 The FreeBSD Release Engineering Team is responsible for setting and
1082 publishing release schedules for official project releases of FreeBSD,
1083 announcing code freezes and maintaining the respective branches, among
1084 other things.
1085
1086 During the third quarter of 2020, the Release Engineering Team started
1087 work on the 12.2-RELEASE cycle, the third release from the stable/12
1088 branch.
1089
1090 As of this writing, two BETA builds have been released, with the
1091 expectation there will be a third BETA build currently remaining on the
1092 schedule.
1093
1094 The 12.2-RELEASE cycle will continue throughout October, with two RC
1095 builds currently planned, and RC3 scheduled on an as-needed basis. The
1096 12.2-RELEASE is so far scheduled for final release on October 27.
1097
1098 In addition to the 12.2-RELEASE, Glen Barber of the Release Engineering
1099 Team finished work to the release build tools and scripts to prepare
1100 for the conversion from Subversion to Git for the 13.0-RELEASE cycle.
1101 There are no plans to merge these changes to stable branches at this
1102 time; as discussed within the Git working group, we feel such a change
1103 on a stable branch would be too intrusive to our user base as well as
1104 downstream FreeBSD consumers. Development snapshot builds for
1105 13.0-CURRENT have recently been built from the Git tree within the
1106 project, and further snapshot builds for 12.x and 11.x will continue to
1107 be built from Subversion.
1108
1109 Additionally throughout the quarter, several development snapshots
1110 builds were released for the head, stable/12, and stable/11 branches.
1111
1112 Finally, the Release Engineering Team would like to thank Marius Strobl
1113 for his time serving on the team; he had recently stepped down from the
1114 Deputy RE Lead role due to constraints on his time. The Team welcomes
1115 Colin Percival, who has accepted fulfilling this role.
1116
1117 Much of this work was sponsored by Rubicon Communications, LLC
1118 (netgate.com) and the FreeBSD Foundation.
1119 __________________________________________________________________
1120
1121 Cluster Administration Team
1122
1123 Links
1124 Cluster Administration Team members=20
1125 URL: https://www.freebsd.org/administration.html#t-clusteradm
1126
1127 Contact: Cluster Administration Team &lt;clusteradm@FreeBSD.org&gt;
1128
1129 The FreeBSD Cluster Administration Team consists of the people
1130 responsible for administering the machines that the Project relies on
1131 for its distributed work and communications to be synchronised. In this
1132 quarter, the team has worked on the following:
1133 * Work with the FreeBSD Foundation on hardware update for web
1134 services, mirror and package building servers.
1135 * Disable directory indexing on the package mirrors to resolve
1136 performance issues of the machine.
1137 + This was later relaxed to allow indexing of the parent
1138 directories but still disallow the large package directories.
1139 * Ongoing systems administration work:
1140 + Accounts management for committers.
1141 + Backups of critical infrastructure.
1142 + Keeping up with security updates in 3rd party software.
1143
1144 Work in progress:
1145 * Setup Malaysia (KUL) mirror.
1146 * Setup Brazil (BRA) mirror.
1147 * Review the service jails and service administrators operation.
1148 * Infrastructure of building aarch64 and powerpc64 packages.
1149 + NVMe issues on PowerPC64 POWER9 blocking dual socket machine
1150 from being used as pkg builder.
1151 + Drive upgrade test for pkg builders (SSDs) courtesy of the
1152 FreeBSD Foundation.
1153 + Boot issues with Aarch64 reference machines.
1154 * New NYI.net sponsored colocation space in Chicago-land area.
1155 * Work with git working group for the git repository.
1156 * Searching for more providers that can fit the requirements for a
1157 generic mirrored layout or a tiny mirror.
1158 __________________________________________________________________
1159
1160 Continuous Integration
1161
1162 Links
1163 FreeBSD Jenkins Instance=20
1164 URL: https://ci.FreeBSD.org
1165 FreeBSD Hardware Testing Lab=20
1166 URL: https://ci.FreeBSD.org/hwlab
1167 FreeBSD CI artifact archive=20
1168 URL: https://artifact.ci.FreeBSD.org
1169 FreeBSD CI weekly report=20
1170 URL: https://hackmd.io/@FreeBSD-CI
1171 FreeBSD Jenkins wiki=20
1172 URL: https://wiki.freebsd.org/Jenkins
1173 Hosted CI wiki=20
1174 URL: https://wiki.freebsd.org/HostedCI
1175 3rd Party Software CI=20
1176 URL: https://wiki.freebsd.org/3rdPartySoftwareCI
1177 Tickets related to freebsd-testing@=20
1178 URL: https://preview.tinyurl.com/y9maauwg
1179 FreeBSD CI Repository=20
1180 URL: https://github.com/freebsd/freebsd-ci
1181
1182 Contact: Jenkins Admin &lt;jenkins-admin@FreeBSD.org&gt;
1183 Contact: Li-Wen Hsu &lt;lwhsu@FreeBSD.org&gt;
1184
1185 Contact: freebsd-testing Mailing List
1186 Contact: IRC #freebsd-ci channel on EFNet
1187
1188 The FreeBSD CI team maintains the continuous integration system of the
1189 FreeBSD project. The CI system firstly checks the committed changes can
1190 be successfully built, then performs various tests and analysis over
1191 the newly built results. The artifacts from those builds are archived
1192 in the artifact server for further testing and debugging needs. The CI
1193 team members examine the failing builds and unstable tests and work
1194 with the experts in that area to fix the codes or adjust test
1195 infrastructure. The details of these efforts are available in the
1196 weekly CI reports.
1197
1198 During the third quarter of 2020, we continued working with the
1199 contributors and developers in the project to fulfill their testing
1200 needs and also keep collaborating with external projects and companies
1201 to improve their products and FreeBSD.
1202
1203 Important changes:
1204 * All !x86 -test builds now trigger a new build on 22:00 UTC daily;
1205 this was not running very often because running all the tests in
1206 qemu takes lots of time. The work on improving the test execution
1207 speed and parallelism is in progress. The following is a list of
1208 the jobs affected:
1209 + Test build for FreeBSD HEAD on ARMv7.
1210 + Test build for FreeBSD HEAD on AArch64.
1211 + Test build for FreeBSD HEAD on MIPS64.
1212 + Test build for FreeBSD HEAD on PowerPC64.
1213 + Test build for FreeBSD HEAD on RISC-V64.
1214 * The build and test results will be sent to the dev-ci mailing list
1215 soon. Feedback and help with analysis is very appreciated!
1216 + A builder dedicated to run jobs using provisioned VMs is
1217 setup, this improves the stableness and reduces the execution
1218 time.
1219 + The result of FreeBSD-head-amd64-test_zfs is changed after
1220 OpenZFS importing; we encourage everyone to check and fix the
1221 failing and skipped test cases.
1222
1223 New jobs added:
1224 * CI build for FreeBSD HEAD on PowerPC64LE.
1225
1226 Work in progress:
1227 * Collecting and sorting CI tasks and ideas here.
1228 * Testing and merging pull requests in the the FreeBSD-ci repo.
1229 * Designing and implementing pre-commit CI building and testing,
1230 * Reduce the procedures of CI/test environment setting up for
1231 contributors and developers.
1232 * Setting up the CI stage environment and putting the experimental
1233 jobs on it.
1234 * Setting up public network access for the VM guest running tests.
1235 * Implementing automatic tests on bare metal hardware.
1236 * Adding drm ports building tests against -CURRENT.
1237 * Planning to run ztest and network stack tests.
1238 * Adding more external toolchain related jobs.
1239 * Improving the hardware lab to be more mature and adding more
1240 hardware.
1241 * Helping more 3rd software get CI on FreeBSD through a hosted CI
1242 solution.
1243 * Working with hosted CI providers to have better FreeBSD support.
1244
1245 Please see freebsd-testing@ related tickets for more WIP information,
1246 and don't hesitate to join the effort!
1247
1248 Sponsor: The FreeBSD Foundation
1249 __________________________________________________________________
1250
1251 Ports Collection
1252
1253 Links
1254 About FreeBSD Ports=20
1255 URL: https://www.FreeBSD.org/ports/
1256 Contributing to Ports=20
1257 URL: https://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/=
1258 ports
1259 -contributing.html
1260 FreeBSD Ports Monitoring=20
1261 URL: http://portsmon.freebsd.org/index.html
1262 Ports Management Team=20
1263 URL: https://www.freebsd.org/portmgr/index.html
1264
1265 Contact: Ren=C3=A9 Ladan &lt;portmgr-secretary@FreeBSD.org&gt;
1266 Contact: FreeBSD Ports Management Team &lt;portmgr@FreeBSD.org&gt;
1267
1268 The Ports Management Team is responsible for overseeing the overall
1269 direction of the Ports Tree, building packages, and personnel matters.
1270 Below is what happened in the last quarter.
1271
1272 We passed the landmark of 40,000 ports in the Ports Collection and are
1273 now around 40,400 ports. The last quarter saw 9335 commits to the HEAD
1274 branch and 481 commits to the 2020Q3 branch by respectively 167 and 63
1275 committers. There are currently 2525 open problem reports of which 595
1276 are unassigned. Compared to last quarter, this means a slight decrease
1277 in activity and also a slight increase in open PRs.
1278
1279 During the last quarter we welcomed Rainer Hurling (rhurlin@) and said
1280 goodbye to Kevin Lo (kevlo@) and Grzegorz Blach (gblach@).
1281
1282 The last three months saw new default versions for Perl (5.32),
1283 PostgreSQL (12) and PHP (7.4). Various packages also got updated:
1284 Firefox to 81.0.1, Chromium to 84.0.4147.135, Gnome to 3.36, Xorg to
1285 1.20.9, Qt5 to 5.15.0, Emacs to 27.1, KDE Frameworks to 5.74.0 and pkg
1286 itself to 1.15.8.
1287
1288 Never tired, antoine@ ran 30 exp-runs to test port version updates, on
1289 such diverse matters as:
1290 * Updating byacc in base to 20200330.
1291 * Check balancing of sed "y" command.
1292 * Use of brackets.
1293 * Removing the now redundant "port" argument from USES=3Dreadline.
1294 __________________________________________________________________
1295
1296 FreeBSD Office team - 3rd quarter 2020 report
1297
1298 Links
1299 The FreeBSD Office project=20
1300 URL: https://wiki.freebsd.org/Office
1301
1302 Contact: FreeBSD Office team ML &lt;office@FreeBSD.org&gt;
1303 Contact: Dima Panov &lt;fluffy@FreeBSD.org&gt;
1304 Contact: Li-Wen Hsu &lt;lwhsu@FreeBSD.org&gt;
1305
1306 The FreeBSD Office team works on a number of office-related software
1307 suites and tools such as OpenOffice and LibreOffice.
1308
1309 Work during this quarter focused on providing the latest stable release
1310 of LibreOffice suite and companion apps to all FreeBSD users.
1311 * Alongside with updating old stable branch to latest 6.4.x releases,
1312 current ports-tree now have a full-featured cutting-edge 7.0.1
1313 bundle.
1314 * Conservative users can keep 6.4.x stable version by switching to
1315 use all-in-one editors/libreoffice6 port and even with i18n
1316 language pack (off by default). It will be kept updated at least
1317 till 7.1.0 version is released.
1318
1319 We are looking for people to help the project.
1320
1321 All unstable work with LibreOffice snapshots is staged in our WIP
1322 repository.
1323 The open bugs list contains all filed issues which need some attention.
1324 Patches, comments and objections are always welcome in the mailing list
1325 and bugzilla.
1326 __________________________________________________________________
1327
1328 FreeBSD Graphics Team status report
1329
1330 Links
1331 Project GitHub page=20
1332 URL: https://github.com/FreeBSDDesktop
1333
1334 Contact: FreeBSD Graphics Team &lt;x11@freebsd.org&gt;
1335 Contact: Niclas Zeising &lt;zeising@freebsd.org&gt;
1336
1337 The FreeBSD X11/Graphics team maintains the lower levels of the FreeBSD
1338 graphics stack. This includes graphics drivers, graphics libraries such
1339 as the MESA OpenGL implementation, the X.org xserver with related
1340 libraries and applications, and Wayland with related libraries and
1341 applications.
1342
1343 There have been several updates to the FreeBSD graphics stack and
1344 related libraries since the last report.
1345
1346 Most notably, MESA related ports were changed to use the meson build
1347 system, instead of the autotools based one. This was needed since mesa
1348 upstream has deprecated and removed the autotools build system, and
1349 this paved the way for further mesa updates. While there was a need for
1350 a few minor corrections after the initial update, this update has been
1351 successful and made it possible to further update and improve the
1352 FreeBSD mesa port.
1353
1354 There have also been several security fixes for xorg-server and libX11,
1355 so these ports have been updated to fix these issues.
1356
1357 During the period, FreeBSD 12 was changed to improve the compatibility
1358 with input devices using udev/evdev and libinput. This change removes
1359 the need for local configuration and makes most mice, touchpads and
1360 keyboards work out of the box. This change will be in the upcoming
1361 FreeBSD 12.2 release.
1362
1363 There have also been several updates to various libraries, both in the
1364 graphics and input stacks, and several userland drivers have been
1365 updated. Libraries such as libdrm and libevdev have been updated to
1366 include new FreeBSD support, developed by team members and added
1367 upstream.
1368
1369 There has also been ongoing work to keep the various drm-kmod ports and
1370 packages up to date, mostly in response to changes in various FreeBSD
1371 versions.
1372
1373 We have also continued our regularly scheduled bi-weekly meetings.
1374
1375 People who are interested in helping out can find us on the
1376 x11@FreeBSD.org mailing list, or on our gitter chat. We are also
1377 available in #freebsd-xorg on EFNet.
1378
1379 We also have a team area on GitHub where our work repositories can be
1380 found.
1381 __________________________________________________________________
1382
1383 Projects
1384
1385 Projects that span multiple categories, from the kernel and userspace
1386 to the Ports Collection or external projects.
1387
1388 FreeBSD on Microsoft HyperV and Azure
1389
1390 Links
1391 Microsoft Azure article on FreeBSD wiki =20
1392 URL: https://wiki.freebsd.org/MicrosoftAzure
1393 Microsoft HyperV article on FreeBSD wiki=20
1394 URL: https://wiki.freebsd.org/HyperV
1395
1396 Contact: FreeBSD Integration Services Team &lt;bsdic@microsoft.com&gt;
1397 Contact: Wei Hu &lt;whu@FreeBSD.org&gt;
1398 Contact: Li-Wen Hsu &lt;lwhsu@FreeBSD.org&gt;
1399
1400 Li-Wen is working on the FreeBSD release code related to Azure for the
1401 -CURRENT, 12-STABLE and 11-STABLE branches. The work-in-progress is
1402 available here. The 11.4-RELEASE image on Azure Marketplace is
1403 published. We are testing the releng/12.2 branch and 12.2-RELEASE image
1404 will be published to Azure Marketplace soon after released.
1405
1406 This project is sponsored by The FreeBSD Foundation, with resources
1407 provided by Microsoft.
1408 __________________________________________________________________
1409
1410 Building FreeBSD on non-FreeBSD hosts
1411
1412 Links
1413 Wiki=20
1414 URL: https://wiki.freebsd.org/BuildingOnNonFreeBSD
1415
1416 Contact: Alex Richardson &lt;arichardson@freebsd.org&gt;
1417
1418 Until recently FreeBSD could only be built on a FreeBSD host. However,
1419 many popular free CI tools only allow building on Linux or macOS and
1420 therefore can not be used for building the FreeBSD base system.
1421 Furthermore, it is sometimes useful to cross-build FreeBSD for a remote
1422 machine or an emulator even if the build machine is not running
1423 FreeBSD. The goal of this project is to allow building the base system
1424 on Linux and macOS hosts.
1425
1426 I started this project in 2017 to allow building CheriBSD on the Linux
1427 servers and desktops that many of us working on the CHERI project use.
1428 The first few patches were upstreamed in 2018 (see the 2018q3 report)
1429 and I merged the full set of patches to CheriBSD shortly after. Over
1430 the past two years I have slowly been upstreaming the remaining patches
1431 and finally committed the last required change in time for this report.
1432
1433 As of September 2020 it should be possible to use the buildworld and
1434 buildkernel make targets to build a fully-functional FreeBSD
1435 installation on macOS and Linux hosts. We use this in our continuous
1436 integration system to build and test CheriBSD disk images for multiple
1437 architectures. I have also committed a GitHub Actions configuration
1438 upstream that takes approximately 10 minutes to build an amd64 kernel.
1439 This will ensure that changes that break crossbuilding from Linux/macOS
1440 can be detected easily.
1441
1442 Upstreaming the crossbuilding changes has resulted in various build
1443 system cleanups. For example, we now no longer need to use lorder.sh
1444 when building libraries which speeds up the linking step a bit. The
1445 portability and bootstrapping changes should also make it easier to
1446 upgrade from older versions since we no longer rely on host headers in
1447 /usr/include matching those of the target system (e.g. when
1448 bootstrapping localedef, etc.).
1449
1450 While this support for building on Linux and macOS should still be
1451 considered experimental, it should work in many cases. If you would
1452 like to give it a try, the following command line should successfully
1453 build an amd64 world on Linux and macOS systems that have packages for
1454 LLVM 10 (or newer) installed: MAKEOBJDIRPREFIX=3D/somewhere
1455 ./tools/build/make.py TARGET=3Damd64 TARGET_ARCH=3Damd64 buildworld Buil=
1456 ds
1457 must be performed using the ./tools/build/make.py wrapper script since
1458 most Linux and macOS systems do not ship an appropriate version of
1459 bmake. Please let me know if you encounter any issues.
1460
1461 Sponsor: DARPA
1462 __________________________________________________________________
1463
1464 Git Migration Working Group
1465
1466 Links
1467 Git conversion tooling repo=20
1468 URL: https://github.com/freebsd/git_conv
1469 FreeBSD-git mailing list=20
1470 URL: https://lists.freebsd.org/mailman/listinfo/freebsd-git
1471 Beta doc git repo=20
1472 URL: https://cgit-beta.FreeBSD.org/doc
1473 Beta ports git repo=20
1474 URL: https://cgit-beta.FreeBSD.org/ports
1475 Beta src git repo=20
1476 URL: https://cgit-beta.FreeBSD.org/src
1477
1478 Contact: Ed Maste &lt;emaste@FreeBSD.org&gt;
1479 Contact: Warner Losh &lt;imp@FreeBSD.org&gt;
1480 Contact: Ulrich Sp=C3=B6rlein &lt;uqs@FreeBSD.org&gt;
1481
1482 Work continues on FreeBSD's migration from Subversion to Git. Ulrich
1483 has addressed all known issues with svn2git and has been able to work
1484 around the inconsistent metadata and forced commit issues in the
1485 Subversion history.
1486
1487 We still have additional documentation to write, and need to finish
1488 installing commit hooks (e.g. restricting branch creation, or ensuring
1489 appropriate data exists on cherry-pick commits).
1490
1491 We expect to open the beta repository to test commits before the end of
1492 October. This is to allow testing of the commit hooks, and to allow
1493 developers to test access and become familiar with git operation.
1494 Commits in this repository will be deleted and the repository will be
1495 recreated at least once prior to the final migration.
1496
1497 Those with an interest in the migration to Git are encouraged to
1498 subscribe to the FreeBSD-git mailing list and test out the beta src,
1499 ports, and/or doc repositories.
1500
1501 You are also welcome check out the wiki, issues, README and other
1502 documentation at the Git conversion tooling repo.
1503
1504 We currently expect to transition the src and doc repositories in
1505 mid-November. Additional investigation and experimentation with the
1506 ports repository is still underway.
1507
1508 Sponsor: The FreeBSD Foundation (in part)
1509 __________________________________________________________________
1510
1511 Linux compatibility layer update
1512
1513 Contact: Edward Tomasz Napierala &lt;trasz@FreeBSD.org&gt;
1514 Contact: Mark Johnston &lt;markj@FreeBSD.org&gt;
1515
1516 Earlier Linuxulator work focused on code cleanups and improving
1517 diagnostic tools. Work has now shifted from cleanups to fixing actual
1518 applications. Current status is being tracked at Linux app status Wiki
1519 page. Initial focus was on applications that don't involve X11, mostly
1520 because they tend to be easier to test and debug, and the bug fixes are
1521 not application-specific.
1522
1523 Foundation-sponsored work during this quarter included implementing a
1524 devfs(5) workaround to fix gettynam(3) inside jail/chroot, and
1525 workaround for the missing splice(2) syscall, which caused problems for
1526 grep and autotools. The Linux version reported to userspace was bumped
1527 to 3.10.0, which matches the kernel shipped with RHEL 7 and is
1528 neccessary for IBM's DB2 database installation to succeed. The
1529 BLKPBSZGET ioctl neccessary for Oracle database is supported now. There
1530 is now support for kcov(4), neccessary for syzcaller; as well as a
1531 number of fixes for issues reported by syzcaller, such as futex lock
1532 leaks. There were also more cleanups, including moving some
1533 Linuxulator-specific functionality related to error handling off from
1534 the syscall's fast code paths. The sysutils/debootstrap port, which
1535 provides an easy way to create Debian or Ubuntu jail, was updated to
1536 version 1.0.123. Finally there were some improvements to the
1537 documentation.
1538
1539 Most of those changes have been merged to FreeBSD 12-STABLE, in order
1540 to ship with 12.2-RELEASE.
1541
1542 There is increased involvement from other developers; this includes
1543 termios performance fixes, improved memfd support, implementing
1544 CLOCK_MONOTONIC_RAW required for Steam, madvise improvements, new
1545 compat.linux.use_emul_path sysctl. There is also ongoing work on
1546 tracking down the causes of failures related to Steam and WebKit, with
1547 fixes being first implemented in linuxulator-steam-utils.
1548
1549 Sponsor: The FreeBSD Foundation
1550 __________________________________________________________________
1551
1552 LLDB Debugger Improvements
1553
1554 Links
1555 Moritz Systems Project Description=20
1556 URL: https://www.moritz.systems/blog/lldb-debugger-improvements-for-fre=
1557 ebsd/
1558 Git Repository=20
1559 URL: https://github.com/moritz-systems/llvm-project
1560
1561 Contact: Kamil Rytarowski &lt;kamil@moritz.systems&gt;
1562 Contact: Michal G=C3=B3rny &lt;mgorny@moritz.systems&gt;
1563
1564 FreeBSD includes LLDB, the debugger in the LLVM family, in the base
1565 system. At present it has some limitations in comparison with the GNU
1566 GDB debugger, and does not yet provide a complete replacement. It
1567 relies on an obsolete plugin model in LLDB that causes growing
1568 technical debt. This project aims to bring LLDB closer to a fully
1569 featured replacement for GDB, and therefore for FreeBSD to feature a
1570 modern debugger for software developers.
1571
1572 The legacy monolithic target supports the executed application being
1573 debugged in the same process space as the debugger. The modern LLDB
1574 plugin approach, used on other supported targets, executes the target
1575 process under a separate lldb-server process. This improves reliability
1576 and simplifies the process / thread model in LLDB itself. In addition,
1577 remote and local debugging will both be performed using the same
1578 approach.
1579
1580 After the migration to the new process model is complete, the project
1581 will include reviewing the results of LLDB's test suite and fixing
1582 tests as time permits. The work is expected to be complete in 2020.
1583
1584 The project schedule is divided into three milestones, each taking
1585 approximately one month:
1586
1587 1. Introduce new FreeBSD Remote Process Plugin for x86_64 with basic
1588 support and upstream to LLVM. 2. Ensure and add the mandated features
1589 in the project (process launch, process attach (pid), process attach
1590 (name), userland core files, breakpoints, watchpoints, threads, remote
1591 debugging) for FreeBSD/amd64 and FreeBSD/i386. 3. Iterate over the LLDB
1592 tests. Detect, and as time permits, fix bugs. Ensure bug reports for
1593 each non-fixed and known problem. Add missing man pages and update the
1594 FreeBSD Handbook.
1595
1596 We are nearing the completion of the first milestone. The new plugin is
1597 getting into shape, and it can already run simple single-threaded
1598 programs. The supported features include single-stepping, breakpoints,
1599 memory and register I/O on amd64. Both plugins are supported
1600 simultaneously. The new plugin is used if FREEBSD_REMOTE_PLUGIN
1601 environment variable is set to any value, or if lldb-server is spawned
1602 directly. Otherwise, the old plugin is used for compatibility. Once the
1603 new plugin matures, we are planning to enable it unconditionally on the
1604 architectures that it is ported to.
1605
1606 Sponsor: The FreeBSD Foundation
1607 __________________________________________________________________
1608
1609 Lua usage in FreeBSD
1610
1611 Contact: Ed Maste &lt;emaste@FreeBSD.org&gt;
1612 Contact: Kyle Evans &lt;kevans@FreeBSD.org&gt;
1613 Contact: Ryan Moeller &lt;freqlabs@FreeBSD.org&gt;
1614
1615 During this quarter, flua (FreeBSD Lua) was taught where to find base
1616 .lua modules in order to support require of .lua modules to be provided
1617 by the base system. flua also gained support for require of binary
1618 modules.
1619
1620 A review for libjail bindings has also been submitted, pending review.
1621 libjail is an essential component if one wants to be able to write jail
1622 management utilities in flua.
1623
1624 People interested in working with Lua in FreeBSD are welcome to get in
1625 contact to discuss other project ideas. To name a couple of potential
1626 projects, some interesting modules that have not been started but could
1627 prove useful (listed in no particular order):
1628 * libcrypt
1629 * libexpat
1630 * libnv
1631 * libxo
1632
1633 There is also a small list of scripts that would do well with a port to
1634 flua:
1635 * certctl(8)
1636 __________________________________________________________________
1637
1638 NFS over TLS implementation
1639
1640 Contact: Rick Macklem &lt;rmacklem@freebsd.org&gt;
1641
1642 In an effort to improve NFS security, an internet draft which I expect
1643 will become an RFC soon specifies the use of TLS 1.3 to encrypt all
1644 data traffic on a Sun RPC connection used for NFS.
1645
1646 Although NFS has been able to use sec=3Dkrb5p to encrypt data on the
1647 wire, this requires a Kerberos environment and, as such, has not been
1648 widely adopted. It also required that encryption/decryption be done in
1649 software, since only the RPC message NFS arguments are encrypted. Since
1650 Kernel TLS is capable of using hardware assist to improve performance
1651 and does not require Kerberos, NFS over TLS may be more widely adopted,
1652 once implementations are available.
1653
1654 The coding for this project has now been completed. All required
1655 changes to the NFS and kernel RPC code have been committed to -CURRENT.
1656 The daemons are now believed to be complete, but will remain in
1657 base/projects/nfs-over-tls until -CURRENT has an OpenSSL library with
1658 the kernel TLS support incorporated in it. If this does not happen for
1659 FreeBSD-13, hopefully the patched OpenSSL and the daemons can become
1660 ports.
1661
1662 To support clients such as laptops, the daemons that perform the TLS
1663 handshake may optionally handle client X.509 certificates from a site
1664 local CA. There are now exports(5) options to require client(s) to
1665 provide a valid X.509 certificate.
1666
1667 While setting up system(s) for testing is still a little awkward, the
1668 documentation is now available for those who want to help with testing.
1669
1670 The main limitation in the current implementation is that it uses
1671 TLS1.2 and not TLS1.3. This should change once the KERN_TLS rx patch
1672 includes TLS1.3 support.
1673
1674 Third party testing would be appreciated.
1675 __________________________________________________________________
1676
1677 syzkaller on FreeBSD
1678
1679 Contact: Mark Johnston &lt;markj@FreeBSD.org&gt;
1680
1681 See the syzkaller entry in the 2019q1 quarterly report for an
1682 introduction to syzkaller.
1683
1684 syzkaller, especially the public syzbot instance, continues to find
1685 bugs in the FreeBSD kernel. A number of these bugs have been fixed in
1686 subsystems such as the VFS name cache, the TCP and SCTP stacks, pf(4),
1687 the unix domain socket implementation, and the Linuxulator.
1688
1689 The FreeBSD Foundation sponsored some work to enable cross-OS fuzzing.
1690 This makes it possible to fuzz the Linuxulator using syzkaller's Linux
1691 target. This effort quickly found several bugs; once the support is
1692 committed upstream we will hopefully be able to leverage syzbot to gain
1693 continuous testing of the Linux system call interface in addition to
1694 the native and 32-bit compatibility interfaces.
1695
1696 Some work was also done to enable running syzkaller in a FreeBSD jail,
1697 with the eventual aim of making it easy to distribute binary images
1698 containing everything required to immediately start running syzkaller
1699 on a new host. Currently a number of setup steps are required, making
1700 deployment somewhat painful.
1701
1702 Sponsor: The FreeBSD Foundation
1703 __________________________________________________________________
1704
1705 Kernel
1706
1707 Updates to kernel subsystems/features, driver support, filesystems, and
1708 more.
1709
1710 DRM Drivers Update
1711
1712 Links
1713 drm-kmod=20
1714 URL: https://github.com/freebsd/drm-kmod/
1715
1716 Contact: Emmanuel Vadot &lt;manu@FreeBSD.Org&gt;
1717
1718 The drm drivers for FreeBSD 13-CURRENT have been updated to match Linux
1719 5.4.62 Then graphics/drm-current-kmod have been updated to follow this
1720 LTS release of Linux.
1721
1722 For now graphics/drm-devel-kmod is also tracking this release but will
1723 be updated to a later revision of Linux drm drivers in the near future.
1724
1725 A lot of linuxkpi code was removed from the ports or replaced with a
1726 BSD licenced implementation.
1727
1728 Sponsor: The FreeBSD Foundation
1729 __________________________________________________________________
1730
1731 DTS Update
1732
1733 Contact: Emmanuel Vadot &lt;manu@FreeBSD.org&gt;
1734
1735 DTS files (Device Tree Sources) were updated to be on par with Linux
1736 5.8 for HEAD and 5.6 for the 12-STABLE branch.
1737 __________________________________________________________________
1738
1739 DesignWare Ethernet adapter driver improvements
1740
1741 Links
1742 WIP branch=20
1743 URL: https://github.com/gonzoua/freebsd/tree/rk_eth
1744
1745 Contact: Oleksandr Tymoshenko &lt;gonzo@FreeBSD.org&gt;
1746
1747 DesignWare Ethernet adapter IP is used in Rockchip and Allwinner SoCs.
1748 The driver was updated with following fixes:
1749 * Initialize clocks instead of relying on u-boot to do the right
1750 thing.
1751 * Sense media type and adjust controller configuration accordingly.
1752 * Add support for RMII PHY mode.
1753
1754 Yet uncommitted changes include performance optimisation by adding
1755
1756 support for multi-segment mbuf transmission. The next step is to try to
1757 get more performance boost by using interrupt coalescence.
1758 __________________________________________________________________
1759
1760 Google Summer of Code'20 Project - eBPF XDP Hooks
1761
1762 Links
1763 Github diff link=20
1764 URL: https://github.com/Ankurk99/freebsd/tree/ebpf-import
1765 Project wiki =20
1766 URL: https://wiki.freebsd.org/SummerOfCode2020Projects/eBPFXDPHooksl
1767
1768 Contact: Ankur Kothiwal &lt;ankur@freebsd.org&gt;
1769
1770 The eBPF eXpress Data Path (XDP) allows eBPF programs to be run to
1771 filter received packets as early as possible, avoiding unnecessary
1772 processing overhead before the filter is run. The goal of this project
1773 is to extend an existing FreeBSD network driver (a virtual NIC like a
1774 VirtIO if_vtnet) to be able to call into an eBPF program when
1775 processing a newly received packet. In short, with XDP the driver must
1776 PASS (accept and process normally), DROP, TX or REDIRECT the packet as
1777 specified by the program. eBPF helper functions and maps for aiding in
1778 packet filtering will also be implemented.
1779
1780 Implemented:
1781 * Register a eBPF probe when an interface is registered with pfil.
1782 * Activating eBPF probe.
1783 * Create hooks and link them to the pfil head when the eBPF XDP probe
1784 is activated and successfully list the XDP probes.
1785 * Create a xdp_rx function which will pass the received packets to
1786 the eBPF program where the packets can be further processed. This
1787 function will return XDP actions: DROP and PASS.
1788 * Register the xdp hook and link it to the pfil head.
1789 * Write an eBPF program to process (currently drop and pass) ICMP
1790 traffic - This is to test that the hook is working properly.
1791 * Write a loader function to load the ICMP filter program to the
1792 kernel.
1793
1794 Future Work:
1795 * Currently we can only attach the XDP hook to PASS and DROP the
1796 packets - The work on detaching the hook is left.
1797 * The XDP action to "TX" and "REDIRECT" the packets.
1798
1799 Final Deliverables:
1800 * Implemented XDP hook to pass and drop packets.
1801 * Created a loader program to attach the eBPF program to the kernel.
1802 * A test program to DROP ICMP filter.
1803
1804 This code was done under the Google Summer of Code 2020 under the
1805 guidance
1806
1807 of Ryan Stone (rstone@). The eBPF implementation for FreeBSD is still a
1808 work in progress and FreeBSD doesn't support eBPF yet. The basic
1809 implementation for eBPF was a GSoC'18 project, and is still under
1810 development. This project is based on that implementation so the XDP
1811 implementation for FreeBSD can only be merged into the FreeBSD source
1812 code once it supports eBPF.
1813
1814 Currently this code is a work in progress and is merged to Ryan Stone's
1815 branch with support for the eBPF implementation.
1816
1817 Sponsor: Google Summer of Code
1818 __________________________________________________________________
1819
1820 ENA FreeBSD Driver Update
1821
1822 Links
1823 ENA README=20
1824 URL: https://github.com/amzn/amzn-drivers/blob/master/kernel/fbsd/ena/R=
1825 EADME
1826
1827 Contact: Michal Krawczyk &lt;mk@semihalf.com&gt;
1828 Contact: Artur Rojek &lt;ar@semihalf.com&gt;
1829 Contact: Marcin Wojtas &lt;mw@semihalf.com&gt;
1830
1831 ENA (Elastic Network Adapter) is the smart NIC available in the
1832 virtualized environment of Amazon Web Services (AWS). The ENA driver
1833 supports multiple transmit and receive queues and can handle up to 100
1834 Gb/s of network traffic, depending on the instance type on which it is
1835 used.
1836
1837 Completed since the last update:
1838 * Fix ENA compilation in case it is integrated into the kernel
1839 binary.
1840 * MFC of the ENA v2.2.0 driver to the FreeBSD 12.2.
1841
1842 Work in progress:
1843 * Add feature that allows reading extra ENI (Elastic Network
1844 Interface) metrics about exceeding BW/pps limits.
1845 * Introduce full kernel RSS API support.
1846 * Allow reconfiguration of the RSS indirection table and hash key.
1847 * Evaluation and prototyping of the driver port to the iflib
1848 framework.
1849
1850 Sponsor: Amazon.com Inc
1851 __________________________________________________________________
1852
1853 IPSec Extended Sequence Number (ESN) support
1854
1855 Contact: Grzegorz Jaszczyk &lt;jaz@semihalf.com&gt;
1856 Contact: Patryk Duda &lt;pdk@semihalf.com&gt;
1857 Contact: Marcin Wojtas &lt;mw@semihalf.com&gt;
1858
1859 Extended Sequence Number (ESN) is IPSec extension defined in RFC4303
1860 Section 2.2.1. It makes possible to implement high-speed IPSec
1861 implementations where standard, 32-bit sequence number is not
1862 sufficient. A key feature of the ESN is that only low order 32 bits of
1863 sequence number are transmitted over the wire. High-order 32 bits are
1864 maintained by sender and receiver. Additionally high-order bits are
1865 included in the computation of Integrity Check Value (ICV) field.
1866
1867 Extended Sequence Number support contains following:
1868 * Modification of existing anti-replay algorithm to fulfil ESN
1869 requirements.
1870 * Trigger soft lifetime expiration at 80% of UINT32_MAX when ESN is
1871 disabled.
1872 * Implement support for including ESN into ICV in cryptosoft engine
1873 in both encrypt and authenticate mode (eg. AES-CBC and SHA256 HMAC)
1874 and combined mode (eg. AES-GCM).
1875 * Implement support for including ESN into ICV in AES-NI engine in
1876 both encrypt and authenticate mode and combined mode.
1877
1878 Completed since the last update:
1879 * Adjust implementation of crypto part to the reworked Open Crypto
1880 Framework.
1881 * Move the core ESN implementation from the crypto drivers to
1882 netipsec layer.
1883 * Make use of the newly introduced crp_aad mechanism for combined
1884 modes.
1885 * Introduce minor fixes and improvements.
1886
1887 TODO:
1888 * Complete review process in Phabricator and merge patches in the
1889 tree.
1890
1891 Sponsor: Stormshield
1892 __________________________________________________________________
1893
1894 NXP ARM64 SoC support
1895
1896 Contact: Marcin Wojtas &lt;mw@semihalf.com&gt;
1897 Contact: Artur Rojek &lt;ar@semihalf.com&gt;
1898 Contact: Dawid Gorecki &lt;dgr@semihalf.com&gt;
1899
1900 The Semihalf team initiated working on FreeBSD support for the NXP
1901 LS1046A SoC
1902
1903 LS1046A are quad-core 64-bit ARMv8 Cortex-A72 processors with
1904 integrated packet processing acceleration and high speed peripherals
1905 including 10 Gb Ethernet, PCIe 3.0, SATA 3.0 and USB 3.0 for a wide
1906 range of networking, storage, security and industrial applications.
1907
1908 Completed since the last update:
1909 * Upstreaming of the QorIQ SDHCI driver (r365054).
1910
1911 With above the current Semihalf upstreaming activity is complete.
1912
1913 The major out-of-tree supported components:
1914 * DPAA network controller support.
1915 * QSPI controller support.
1916
1917 They work on 11.2-RELEASE, but still require significant
1918
1919 effort to adopt to FreeBSD-CURRENT.
1920
1921 Sponsor: Alstom Group
1922 __________________________________________________________________
1923
1924 Addition of PowerPC64LE Architecture
1925
1926 Links
1927 Early notes=20
1928 URL: https://lists.freebsd.org/pipermail/freebsd-ppc/2020-August/012043=
1929 =2Ehtml
1930 Announcement=20
1931 URL: https://lists.freebsd.org/pipermail/freebsd-ppc/2020-September/012=
1932 098.h
1933 tml
1934
1935 Contact: Brandon Bergren &lt;bdragon@freebsd.org&gt;
1936
1937 As of r366063, experimental support for little-endian PowerPC64
1938 (PowerPC64LE) is available in -CURRENT for POWER8 and POWER9 machines.
1939
1940 In 2010, when FreeBSD was ported to PowerPC64, the average user would
1941 have been using a G5 PowerMac, a purely big-endian machine.
1942
1943 While, at the time, a 32-bit PowerPC machine could run in
1944 little-endian, as well as POWER6 and POWER7, in practice, the
1945 complexities involved in managing it at the kernel level and lack of
1946 firmware support made it infeasible to support.
1947
1948 When IBM designed POWER8, one main focus was to improve little-endian
1949 support, and bring it up to parity with big-endian.
1950
1951 This improved support makes it practical to support a little-endian
1952 operating environment on what is traditionally a primarily big-endian
1953 platform.
1954
1955 In 2020, with POWER9 being affordable for many users thanks to the
1956 Raptor Blackbird, semi-easy access to surplus POWER8 hardware, IBM
1957 having a major future focus on POWER little-endian, and the decay of
1958 big-endian support in modern video cards and graphical environments,
1959 there is demand for a little-endian version of FreeBSD on POWER.
1960
1961 With FreeBSD/PowerPC64's transition in 2019 to the ELFv2 ABI as part of
1962 the 2019q4 PowerPC on Clang effort, the last major barrier to a
1963 little-endian port was eliminated.
1964
1965 Since nobody else was working on it, and I had the skillset required to
1966 do the port, I decided to experiment one weekend with a little-endian
1967 kernel to see how difficult it would be to port.
1968
1969 It turned out to be a lot more trivial than I was expecting. Three days
1970 later I had console support in qemu, and after another week of
1971 debugging, I had it fully up and running on hardware.
1972
1973 FreeBSD PowerPC64LE is now an experimental MACHINE_ARCH in base, and is
1974 continuing to evolve at a rapid pace.
1975
1976 Big-endian PowerPC64 is still the preferred platform for the
1977 foreseeable future, and will not be deprecated.
1978
1979 Sponsor: Tag1 Consulting, Inc.
1980 __________________________________________________________________
1981
1982 ure - USB 3.0 Gigabit Ethernet Driver update
1983
1984 Links
1985 svn commit: r365648=20
1986 URL: https://svnweb.freebsd.org/changeset/base/365648
1987 FreeBSD-SA-20:27.ure=20
1988 URL: https://www.freebsd.org/security/advisories/FreeBSD-SA-20:27.ure.a=
1989 sc
1990 D25809 major update to if_ure=20
1991 URL: https://reviews.freebsd.org/D25809
1992
1993 Contact: John-Mark Gurney &lt;jmg@FreeBSD.org&gt;
1994
1995 The ure is a driver for handling the RealTek ethernet adapters,
1996 including the RTL8153 USB 3.0 Gigabit ethernet adapters. It is used in
1997 many ethernet dongles and docking stations.
1998
1999 Previous to this update, the driver was limited in speed. In my
2000 testing, I was only able to get ~91Mbps. This limit was due to one
2001 packet per USB transfer. USB has a limit of 8000 transfers per second
2002 (1500 bytes/pkt * 8000 pkts/sec * 8bits/byte =3D=3D 96 Mbps). This was
2003 acceptable for fast ethernet (RTL8152, 100Mbps), but with the
2004 additional support for Gigabit ethernet, it became a bottleneck.
2005
2006 The updates add sending and receiving multiple packets in a single USB
2007 transfer, VLAN hardware tagging, and enable TCP and UDP checksum
2008 offloading. This increased the speed on gigabit ethernet to ~940 Mbps.
2009
2010 In doing this work, a security vulnerability was discovered in the
2011 driver. Due to improper setting of a device register, on some devices,
2012 it caused packets to be fragmented when they shouldn't be and the
2013 driver was unable to handle them correctly. This allowed an attacker,
2014 who could generate large frames (say, ping packets, or large TCP
2015 transfers), to inject arbitrary packets into the network stack. This
2016 could allow the attacker to spoof traffic from other machines, and
2017 bypass VLAN protections. See the SA for more information.
2018
2019 As part of this work, a script was created to run tests to validate
2020 that basic functionality of the driver (w/o options) work properly, and
2021 then iterate over each option to make sure that they function properly.
2022 This will be released at some point in the future.
2023
2024 If you're interested in helping out, or testing it, let me know.
2025 __________________________________________________________________
2026
2027 Stateless hardware offloads for VXLANs
2028
2029 Links
2030 r365867=20
2031 URL: https://svnweb.freebsd.org/base?view=3Drevision&amp;revision=3Dr365867
2032 r365868=20
2033 URL: https://svnweb.freebsd.org/base?view=3Drevision&amp;revision=3Dr365868
2034 r365869=20
2035 URL: https://svnweb.freebsd.org/base?view=3Drevision&amp;revision=3Dr365869
2036 r365870=20
2037 URL: https://svnweb.freebsd.org/base?view=3Drevision&amp;revision=3Dr365870
2038 r365871=20
2039 URL: https://svnweb.freebsd.org/base?view=3Drevision&amp;revision=3Dr365871
2040 RFC6935=20
2041 URL: https://tools.ietf.org/html/rfc6935
2042
2043 Contact: Navdeep Parhar &lt;np@FreeBSD.org&gt;
2044
2045 VXLAN (Virtual eXtensible LAN) is a tunneling protocol in which Layer 2
2046 traffic for a virtual LAN is encapsulated in UDP and transferred over
2047 Layer 3 networks between VTEPs (VXLAN Tunnel End Points). Traffic on
2048 the wire has two sets of networking headers: the headers for the
2049 encapsulation and the headers of the traffic being encapsulated. VXLANs
2050 are supported by if_vxlan(4) on FreeBSD.
2051
2052 Modern NICs commonly support header checksum insertion and
2053 verification, TSO (TCP Segmentation Offload) on transmit, and RSS for
2054 load distribution on receive. But the default is to operate on the
2055 outermost headers. Some NICs can operate on the inner encapsulated
2056 frames as well. The commits listed above allow if_vxlan(4) to take
2057 advantage of such NICs.
2058
2059 r365867 and r365868 add new mbuf checksum flags and ifnet capabilities.
2060 r365870 implements the kernel parts of the new capabilities and updates
2061 if_vxlan(4) to make use of them. r365871 implements driver support for
2062 the new capabilities in cxgbe(4).
2063
2064 VXLAN and other tunneling protocols that use UDP explicitly allow zero
2065 checksum in the outer UDP header, even with IPv6. r365869 adds support
2066 for configuring one UDP/IPv6 port where zero checksums are allowed.
2067
2068 This work was sponsored by Chelsio Communications and was implemented
2069 and tested using T6 (Terminator 6) NICs supported by cxgbe(4). It is
2070 available in 13.0-CURRENT (head) right now and will be available in
2071 12-STABLE in the future.
2072
2073 VXLANs can be created as usual and will automatically have checksum and
2074 TSO capabilities if the underlying physical interface supports VXLAN
2075 stateless offloads. Use ifconfig to list, disable, and enable checksum
2076 capabilities on the VXLAN interface. Use
2077 https://bugs.freebsd.org/bugzilla/ to report bugs.
2078
2079 Future work:
2080 * Direct call into a vxlan input routine from the driver's receive
2081 routine.
2082 * LRO support in if_vxlan(4).
2083 * GENEVE support.
2084
2085 Sponsor: Chelsio Communications
2086 __________________________________________________________________
2087
2088 Wireless updates
2089
2090 Links
2091 The freebsd-wireless mailing list=20
2092 URL: https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
2093 athp github repository=20
2094 URL: https://github.com/erikarn/athp
2095
2096 Contact: Adrian Chadd &lt;adrian@FreeBSD.org&gt;
2097 Contact: Bjoern A. Zeeb &lt;bz@FreeBSD.org&gt;
2098
2099 The following works happened in FreeBSD HEAD (some already in Q2) and
2100 were merged for 12.2-BETA2 and include net80211 and driver updates for
2101 better 11n and upcoming 11ac support.
2102
2103 In more detail, this includes an ath(4) update, some run(4) 11n
2104 support, 11n for otus(4), A-MPDU, A-MSDU, A-MPDU+A-MSDU and Fast frames
2105 options, scanning fixes, enhanced PRIV checks for jails, restored
2106 parent device name printing, improvements for upcoming VHT support,
2107 lots of under-the-hood infrastructure improvements, new device IDs, and
2108 debug tools updates.
2109
2110 If you have a chance please test before the release.
2111
2112 Atheros 11ac driver athp
2113
2114 In the last three months the athp(4) port of the ath10k driver has
2115 progressed well. Adrian reports the following important changes:
2116 * Per-node transmit buffering was implemented, required for correct
2117 hostap and QCA6174 behaviour.
2118 * Issues with ignoring sending some management frames got fixed;
2119 null-data frames were being filtered out and this caused
2120 undesirable hostap behaviour.
2121 * Transmit path refactoring reduced code duplication.
2122 * A fix on firmware start / VAP running tracking no longer stops the
2123 first VAP from coming active after VAP creation / ifconfig up.
2124 * Correcting hostap mode PHY configuration now allows non-VHT
2125 stations to associate and correctly exchange data with a VHT AP.
2126 * Addition of a crypto key configuration cache in the driver ensures
2127 the ieee80211_key details are available after the key is deleted;
2128 net80211 would reuse or free the state before the driver task would
2129 finish the firmware command.
2130
2131 Newer Intel Wireless device support
2132
2133 Initial work was done to integrate net80211 support in the LinuxKPI
2134 compat layer to get the wireless parts going. In addition, upstreaming
2135 code changes and working through problems and review started on two
2136 sides. One was trying to get mostly compile time changes upstreamed to
2137 the iwlwifi driver. The other is sorting out conflicting LinuxKPI
2138 changes to not break the DRM graphics drivers. Bjoern hopes that with
2139 some of that sorted out, he can soon go back to focus on the wireless
2140 parts and produce a new snapshot.
2141
2142 rtw88 and brcmfmac
2143
2144 As the Intel driver port and LinuxKPI advance, both the rtw88, and to a
2145 lower degree the brcmfmac, ports benefit from that. Bjoern lately also
2146 got a brcmfmac PCIe card and started to port support for that. This for
2147 the moment remains a free-time project.
2148
2149 Work by Bjoern was sponsored by: Rubicon Communications, LLC (d/b/a
2150 "Netgate") and The FreeBSD Foundation
2151 __________________________________________________________________
2152
2153 ZSTD Compression in ZFS
2154
2155 Contact: Allan Jude &lt;allanjude@freebsd.org&gt;
2156
2157 Zstandard (ZSTD) is a modern high-performance compression algorithm
2158 designed to provide the compression ratios of gzip while offering much
2159 better performance. ZSTD has been adopted in FreeBSD for a number of
2160 other uses, including compressing kernel crash dumps, as a replacement
2161 for gzip or bzip for compressing log files, and for future versions of
2162 pkg(8).
2163
2164 This effort to complete the integration of ZSTD into ZFS is funded by
2165 the FreeBSD Foundation.
2166
2167 During the third quarter the integrating of ZSTD into OpenZFS was
2168 completed in the upstream OpenZFS repository, and the new OpenZFS 2.0
2169 codebase was imported into 13-CURRENT. Completed milestones in this
2170 project:
2171 * Importing ZSTD 1.4.5 into OpenZFS, using the recent upstream zstd
2172 features that make it easier to embed zstd in other projects.
2173 * Changing the way compression levels are tracked and inherited.
2174 * Save and restore the compression level via an embedded block
2175 header.
2176 * Also store the version of zstd used in the embedded block header,
2177 for future-proofing. The checksum of a block may not match if zstd
2178 is upgraded, since it may compress the block more.
2179 * Add tests to ensure zstd compression and metadata survive ZFS
2180 replication.
2181 * Resolve possible negative interactions with L2ARC and ZFS Native
2182 Encryption.
2183 * Fix bug with L2ARC if the Compressed ARC feature is disabled.
2184 * Improve the ZFS feature activation code, so that zstd cannot create
2185 pools that will panic older versions of ZFS.
2186
2187 With these changes, upgraded pools can compress data with zstd
2188
2189 or zstd-fast, across a wide range of different compression levels. This
2190 will allow the storage administrator to select the
2191 performance-vs-compression tradeoff that best suits their needs.
2192
2193 Tasks remaining to be completed:
2194 * Add a section to the FreeBSD Handbook ZFS chapter about zstd
2195 * Create more documentation around selecting a suitable compression
2196 level
2197 * Finish support for ZSTD in the FreeBSD boot loader (Warner Losh
2198 imp@freebsd.org)
2199
2200 Sponsor: The FreeBSD Foundation
2201 __________________________________________________________________
2202
2203 Architectures
2204
2205 Updating platform-specific features and bringing in support for new
2206 hardware platforms.
2207
2208 CheriBSD 2020 Q3
2209
2210 Links
2211
2212 Contact: Alex Richardson &lt;arichardson@FreeBSD.org&gt;
2213 Contact: Andrew Turner &lt;andrew@FreeBSD.org&gt;
2214 Contact: Brooks Davis &lt;brooks@FreeBSD.org&gt;
2215 Contact: Edward Tomasz Napierala &lt;trasz@FreeBSD.org&gt;
2216 Contact: George Neville-Neil &lt;gnn@FreeBSD.org&gt;
2217 Contact: Jessica Clarke &lt;jrtc27@FreeBSD.org&gt;
2218 Contact: John Baldwin &lt;jhb@FreeBSD.org&gt;
2219 Contact: Robert Watson &lt;rwatson@FreeBSD.org&gt;
2220 Contact: Ruslan Bukin &lt;br@FreeBSD.org&gt;
2221
2222 CheriBSD extends FreeBSD to implement memory protection and software
2223 compartmentalization features supported by the CHERI instruction-set
2224 extensions. There are three architectural implementations of the CHERI
2225 protection model: CHERI-MIPS, CHERI-RISC-V, and Arm's forthcoming
2226 experimental Morello processor (due late 2021). CheriBSD is a research
2227 operating system with a stable baseline implementation into which
2228 various new research features have been, or are currently being,
2229 merged:
2230 * Arm Morello - We are preparing to open source our adaptation of
2231 CheriBSD to Arm's Morello architecture. The Morello branch is being
2232 updated to the most recent CheriBSD baseline, and patches are in
2233 review for upstreaming to our open-source repository. CheriBSD
2234 currently boots and runs statically linked CheriABI binaries on the
2235 Morello simulator, and dynamic linking support is in progress, with
2236 OS and toolchain bugs being worked on. We aim to make a first
2237 CheriBSD/Morello snapshot available alongside other open-source
2238 Morello software in mid-October 2020, however, our target for a
2239 more mature and usable implementation is December 2020.
2240 * Kernel spatial memory safety (pure-capability kernel) - The current
2241 CheriBSD kernel is a hybrid C program where only pointers to
2242 userspace are CHERI capabilities. This ensures that the kernel
2243 follows the intent of the application runtime and cannot be used to
2244 defeat bounds on application pointers. We have developed and will
2245 soon merge a pure-capability kernel where all pointers in the
2246 kernel are appropriately bounded capabilities. This vastly reduces
2247 the opportunity for buffer overflows. This spatial memory safety
2248 lays the groundwork for future work such as device driver
2249 compartmentalization and kernel temporal safety.
2250 * Userspace heap temporal memory safety (Cornucopia) - CHERI
2251 capabilities provide the necessary features to enable robust and
2252 efficient revocation of freed pointers. With Cornucopia we have
2253 implemented a light-weight revocation framework providing
2254 protection from use-after-reallocation bugs with an average cost
2255 below 2%. We aim to bring these overheads down further over the
2256 next year and merge this functionality into the mainline CheriBSD.
2257 * We have been working on updating the arm64 bhyve from Politehnica
2258 University of Bucharest to have it committed to FreeBSD. We have
2259 been upstreaming initial changes to help support this.
2260 * Baseline FreeBSD improvements - We are upstreaming (to FreeBSD)
2261 various bug fixes and tweaks for PCIe support, and support for the
2262 System MMU (SMMU) that will be present on the N1SDP and Morello
2263 SoCs. We have upstreamed support for cross-building FreeBSD from
2264 macOS and Linux (with some limitations; see separate entry on
2265 crossbuilding). We have also fixed implementation bugs in the
2266 RISC-V ABI.
2267
2268 CHERI Documentation and Exercises
2269
2270 * We have released [Capability Hardware Enhanced RISC Instructions:
2271 CHERI Instruction-Set Architecture (Version
2272 8)](https://www.cl.cam.ac.uk/techreports/UCAM-CL-TR-951.pdf).
2273 Notable changes include promotion of CHERI-RISC-V to
2274 non-experimental and discussion of Arm's Morello prototype.
2275 * We have developed a set of [Adversarial CHERI Exercises and
2276 Missions](https://ctsrd-cheri.github.io/cheri-exercises) to
2277 introduce security researchers to CHERI protections.
2278 __________________________________________________________________
2279
2280 FreeBSD/RISC-V Project
2281
2282 Links
2283 Wiki=20
2284 URL: https://wiki.freebsd.org/riscv
2285
2286 Contact: Mitchell Horne &lt;mhorne@FreeBSD.org&gt;
2287
2288 Contact: freebsd-riscv Mailing List
2289 Contact: IRC #freebsd-riscv on freenode
2290
2291 The FreeBSD/RISC-V project is providing support for running FreeBSD on
2292 the RISC-V Instruction Set Architecture.
2293
2294 This quarter saw several important bug fixes. A number of hangs in the
2295 system were identified and addressed, and a bug in QEMU's
2296 implementation of the Platform Level Interrupt Controller was fixed.
2297 This fix is included in the new devel/qemu50 and devel/qemu-devel
2298 ports.
2299
2300 The end result of these fixes is that the test suite can now be
2301 reliably run to completion in QEMU. The entire run takes several hours,
2302 so CI has been configured to run the job once a day. There is active
2303 effort into reducing the time it takes to run the entire test suite.
2304
2305 A new u-boot port was created: sysutils/u-boot-qemu-riscv64. This
2306 variant can be used as a secondary bootloader alongside OpenSBI to load
2307 and launch FreeBSD's loader(8) from an EFI System Partition.
2308
2309 Next quarter will likely bring further fixes to address some of the
2310 failing test cases.
2311 __________________________________________________________________
2312
2313 Ports
2314
2315 Changes affecting the Ports Collection, whether sweeping changes that
2316 touch most of the tree, or individual ports themselves.
2317
2318 Update to grub-bhyve
2319
2320 Links
2321 grub-bhyve Git Repository=20
2322 URL: https://gitlab.com/ctuffli/grub
2323
2324 Contact: Chuck Tuffli &lt;chuck@freebsd.org&gt;
2325
2326 bhyve is the hypervisor included in FreeBSD and other operating systems
2327 used to run virtual machines. When not using a boot ROM (i.e. UEFI),
2328 the user must load the guest operating system for bhyve. For
2329 non-FreeBSD guests, the loader is a version of GNU GRUB (a.k.a the GNU
2330 GRand Unified Bootloader) modified to interface with bhyve. This work
2331 is an effort to both update the base GRUB code to the latest version as
2332 well as improve the usability on FreeBSD.
2333
2334 The current grub-bhyve is based on an older version of GRUB (circa
2335 2015) and thus is missing more recent additions such as XFS file system
2336 and syslinux support. With the update, installing CentOS, for example,
2337 now does not require the extra step of changing the default file system
2338 to something other than XFS.
2339
2340 Internally, the code has been restructured to be its own "platform"
2341 which should make it easier to keep in sync with upstream development.
2342 The major improvement is the ability to automatically find and load the
2343 GRUB configuration file from the guest disk image. With this change, it
2344 is not necessary to create a device map file or specify which Linux
2345 kernel or initrd image to use. More importantly, if the guest image
2346 updates its GRUB configuration, for example after updating the kernel,
2347 no changes are needed when invoking grub-bhyve. Note, this feature
2348 requires a new "disk" option:
2349
2350 # grub-bhyve --disk=3D/zroot/vms/u18-mini/disk0.img --vm=3Du18-mini
2351
2352 The automatic configuration file detection works with both GRUB
2353 configuration files (e.g. CentOS, Ubuntu) as well as syslinux
2354 configuration (e.g. Alpine). For the adventurous, there is experimental
2355 support for Fedora's BootLoaderSpec (a.k.a. blscfg) on the blscfg
2356 branch of the grub-bhyve Git repository.
2357
2358 The code has been tested on a few Linux variants, but it would benefit
2359 from wider testing (and bug reports!). The new version does not have a
2360 Port but is easily built on FreeBSD. After cloning / downloading the
2361 source, run:
2362
2363 $ PYTHON=3Dpython3.7 ./bootstrap $ MAKE=3Dgmake ./configure
2364 --with-platform=3Dbhyve $ gmake
2365
2366 The resulting binary, grub-bhyve, will be in the grub-core/ directory.
2367 If you have success or troubles with it, please let me know.
2368 __________________________________________________________________
2369
2370 KDE on FreeBSD
2371
2372 Links
2373 KDE FreeBSD =20
2374 URL: https://freebsd.kde.org/
2375 KDE Community FreeBSD=20
2376 URL: https://community.kde.org/FreeBSD
2377
2378 Contact: Adriaan de Groot &lt;kde@FreeBSD.org&gt;
2379
2380 The KDE on FreeBSD project aims to package all of the software produced
2381 by the KDE Community for the FreeBSD ports tree. The software includes
2382 a full desktop environment called KDE Plasma, an IDE with the name
2383 KDevelop, a PIM suite known as Kontact and hundreds of other
2384 applications that can be used on any FreeBSD machine.
2385
2386 With the continuation of the ever-so-peculiar era of
2387 almost-only-online, the KDE community has shifted gears and also gone
2388 for online events. The yearly conference, Akademy, was conducted online
2389 over video calls. Meanwhile, software continues to be released, so this
2390 quarter the kde@ team:
2391 * Put the beta of the next version of KDE Plasma, scheduled for
2392 official release in October 2020, into the Area51 development tree.
2393 Area51 is a fork of the FreeBSD ports tree where new development
2394 for KDE ports happens.
2395 * The monthly regular updates to the KDE Plasma desktop landed
2396 on-time and safely.
2397 * With three months in a quarter, there were also three releases of
2398 KDE Frameworks 5, including a new framework for handling DAV jobs.
2399 * The June applications update and its .1 release landed a bit late,
2400 but brings with it the usual raft of updates to KDE applications
2401 and libraries,
2402 * A new Digikam release, which arrived in the ports tree on the day
2403 of its release.
2404 * A new KDevelop release arrived a day after its release. This update
2405 contains a number of crash fixes for refactoring support.
2406 * Qt was updated to Qt 5.15, the last in the Qt5 series and an LTS
2407 version. Bugfix releases are expected, but the next major Qt will
2408 be Qt 6.
2409
2410 On the infrastructure front, August saw some minor updates to CMake and
2411 ninja.
2412
2413 As usual, kde@ continues to support the work of xorg@ and gnome@ in
2414 maintaining the Free Desktop stack on FreeBSD, including XOrg, poppler,
2415 and xdg-utils. A new MAINTAINER group, desktop@, has been created to
2416 provide shared ownership of that shared stack.
2417
2418 With Python2 deprecation looming, the build system for QtWebEngine --
2419 itself a fork of Chromium -- is becoming a pressing issue in Q4 and
2420 will no doubt chew up a lot of time in the coming months.
2421 __________________________________________________________________
2422
2423 Documentation
2424
2425 Noteworthy changes in the documentation tree, in manpages, or in
2426 external books/documents.
2427
2428 DOCNG on FreeBSD
2429
2430 Links
2431 DOCNG Website Repo=20
2432 URL: https://gitlab.com/carlavilla/freebsd-hugo-website
2433 DOCNG Documentation Repo=20
2434 URL: https://gitlab.com/carlavilla/freebsd-hugo-documentation
2435 DOCNG Share Repo=20
2436 URL: https://gitlab.com/carlavilla/freebsd-hugo-data
2437
2438 Contact: Sergio Carlavilla &lt;carlavilla@FreeBSD.org&gt;
2439
2440 The Doc New Generation project aims to convert the website and all
2441 existing documentation to Hugo/AsciiDoctor. Right now almost everything
2442 is converted as you can see in the repositories.
2443
2444 The objective of using Hugo and AsciiDoctor is to reduce the learning
2445 curve and let people to start quickly with our documentation system.
2446 Other benefits of using Hugo is that we can use other technologies
2447 aside from AsciiDoctor, like MarkDown, RST, Pandoc, etc.
2448
2449 The remaining tasks include:
2450 * Finish the conversion of some books to AsciiDoctor.
2451 * Get some tweaks in the CSS to be responsive.
2452 * Add AsciiDoctor extensions to create an index of tables and
2453 figures.
2454 * Make a general review.
2455
2456 The dates for making the migration have yet to be discussed.
2457
2458 Patches, comments and objections are always welcome.
2459 __________________________________________________________________
2460
2461 Third-Party Projects
2462
2463 Many projects build upon FreeBSD or incorporate components of FreeBSD
2464 into their project. As these projects may be of interest to the broader
2465 FreeBSD community, we sometimes include brief updates submitted by
2466 these projects in our quarterly report. The FreeBSD project makes no
2467 representation as to the accuracy or veracity of any claims in these
2468 submissions.
2469
2470 Potluck - Flavour &amp; Image Repository for pot
2471
2472 Links
2473 Potluck Repository &amp; Project=20
2474 URL: https://potluck.honeyguide.net/
2475 Potluck on github =20
2476 URL: https://github.com/hny-gd/potluck
2477 pot project =20
2478 URL: https://pot.pizzamig.dev
2479
2480 Contact: &lt;&gt;
2481
2482 pot is a jail management tool that also supports orchestration through
2483 nomad.
2484
2485 Potluck aims to be to FreeBSD and pot what Dockerhub is to Linux and
2486 Docker: A repository of pot flavours and complete images for usage with
2487 pot.
2488
2489 In the last quarter, an initial set of Nomad, Consul and Traefik images
2490 has been created that are sufficient to run a simple virtual datacenter
2491 out of the box.
2492 A three-part article series explaining how to set this up is also
2493 available now.
2494
2495 Furthermore, ready-made images suitable for scheduling via Nomad and
2496 Consul in such an environment have been created, e.g. a BackupPC or a
2497 Postfix Backup MX service.
2498
2499 Future plans include additional images and exposing more configuration
2500 options in the existing images to allow a more flexible usage.
2501
2502 Beside general feedback and tests, additional flavours and patches are
2503 very welcome!
2504
2505 Sponsors: Honeyguide GmbH &amp; Honeyguide Group (Pty) Ltd ## Puppet
2506 Puppet Puppet's FreeBSD slack channel Bolt Choria Puppet Team
2507 puppet@FreeBSD.org
2508
2509 Since out last status report a few years ago, the puppet@ team
2510 regularly updated the various Puppet ports to follow upstream releases
2511 of Puppet 4, Puppet 5 and Puppet 6. Puppet 4 was removed when it
2512 reached EOL.
2513
2514 More recently, an effort was made to enhance Facter 4 so that it can be
2515 used as a drop-in replacement of Facter 3 on FreeBSD. Facter 4 is a
2516 Ruby rewrite of Facter 3, the C++ rewrite of Facter 2 which was
2517 initially in Ruby. As a consequence we have two ports for Facter:
2518 sysutils/facter is the C++ implementation (Facter 3) and
2519 sysutils/rubygems-facter is the Ruby implementation (updated from
2520 Facter 2 to Facter 4 a few weeks ago). The Puppet 5 and Puppet 6 ports
2521 already allow to choose which version of Facter to use. Facter 4 will
2522 be the default version of Facter with Puppet 7 which is expected to be
2523 released soon.
2524
2525 We are getting ready to add a port for Puppet 7 as sysutils/puppet7
2526 when it is available, along with PuppetServer 7
2527 (sysutils/puppetserver7), and PuppetDB 7 (databases/puppetdb7).
2528
2529 Regarding orchestration, most Marionette Collective ports have been
2530 deprecated for a long time, and the last component sysutils/mcollective
2531 is expected to be deprecated soon: Marionette Collective was not
2532 shipped anymore with Puppet 6 and Bolt has been made available as a
2533 lightweight replacement.
2534
2535 Bolt is already available in the ports tree as sysutils/rubygems-bolt),
2536 but if you are using Marionette Collective, you are invited to look
2537 into Choria which will reach the ports tree soon as sysutils/choria.
2538 Choria is a direct evolution of Marionette Collective allowing a smooth
2539 transition from MCollective. Once Choria is available in the ports
2540 tree, Marionette Collective will be deprecated.
2541 __________________________________________________________________
2542
2543 News Home | Status Home
2544 Site Map | Legal Notices | =C2=A9 1995-2020 The FreeBSD Project. All rig=
2545 hts
2546 reserved.
2547
2548 --6vqnfjaiktnxv5lf
2549 Content-Type: application/pgp-signature; name="signature.asc"
2550
2551 -----BEGIN PGP SIGNATURE-----
2552
2553 iQGTBAABCgB9FiEEDonNJPbg/JLIMoS6Ps5hSHzN87oFAl+QsKhfFIAAAAAALgAo
2554 aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDBF
2555 ODlDRDI0RjZFMEZDOTJDODMyODRCQTNFQ0U2MTQ4N0NDREYzQkEACgkQPs5hSHzN
2556 87op1gf/YOFz9WlcOqrMZp+qGKEc8I6Z/JvH3hxazWTuuWAP/4k7zlXVSqx3LwR9
2557 TNt3pXGwgCUEbZ5HEOOBnSpB/tTRiS30Dfpu0XjCeoZ8Rg4WWZM6V5zLUVnLSZNJ
2558 X8pW65P28ErK12poVKwgJbGUxDjpRQiowA4UrfzBJL7FhDPNwDKBp5OmRmG0np4f
2559 yZ9Sy2Ux0CYyWZaL+BV6Cdz4VgEUbeseAFRD9afE7NIboE3gif4brIMdVHbdM+Az
2560 3+kkg7tSUYl1PF4vitPszRQRlb+u2UJwcclwSKyCPU/sV8emPJaGR5yjddCu5JM3
2561 p4LZgTSbnBK9VN8UUb0tPoKoCupGGw==
2562 =U8JA
2563 -----END PGP SIGNATURE-----
2564
2565 --6vqnfjaiktnxv5lf--</content>
2566 <tags>freebsd</tags>
2567 <author>
2568 <name>debdrup@FreeBSD.org</name>
2569 </author>
2570 </entry>
2571 <entry>
2572 <id>tag:bsdsec.net,2005:Article/1218</id>
2573 <published>2020-10-21T01:29:49Z</published>
2574 <updated>2020-10-21T01:29:49Z</updated>
2575 <link rel="alternate" type="text/html" href="https://bsdsec.net/articles/netbsd-9-1-available"/>
2576 <title>NetBSD 9.1 available!</title>
2577 <content type="html">The NetBSD Project is pleased to announce NetBSD 9.1, the first
2578 feature and stability update for the netbsd-9 release branch.
2579
2580 Over the last months many changes have been made to the NetBSD 9 stable
2581 branch. As a stable branch the release engineering team and the NetBSD
2582 developers are conservative with changes to this branch and many users
2583 rely on the binaries from our regular auto-builds for production use.
2584
2585 The new release features (among various other changes) many bug fixes,
2586 a few performance enhancements, stability improvements for ZFS and LFS
2587 and support for USB security keys in a mode easily usable in Firefox
2588 and other applications.
2589
2590 For more details and instructions see the 9.1 announcement at
2591
2592 https://www.NetBSD.org/releases/formal-9/NetBSD-9.1.html</content>
2593 <tags>netbsd</tags>
2594 <author>
2595 <name>martin@NetBSD.org</name>
2596 </author>
2597 </entry>
2598 <entry>
2599 <id>tag:bsdsec.net,2005:Article/1217</id>
2600 <published>2020-10-20T18:30:14Z</published>
2601 <updated>2020-10-20T18:30:14Z</updated>
2602 <link rel="alternate" type="text/html" href="https://bsdsec.net/articles/rpki-client-6-8p0-released"/>
2603 <title>rpki-client 6.8p0 released</title>
2604 <content type="html">rpki-client 6.8p0 has just been released and will be available in the
2605 rpki-client directory of any OpenBSD mirror soon.
2606
2607 rpki-client is a FREE, easy-to-use implementation of the Resource
2608 Public Key Infrastructure (RPKI) for Relying Parties (RP) to
2609 facilitate validation of the Route Origin of a BGP announcement. The
2610 program queries the RPKI repository system and outputs Validated ROA
2611 Payloads in the configuration format of OpenBGPD, BIRD, and also as
2612 CSV or JSON objects for consumption by other routing stacks.
2613
2614 See RFC 6811 for a description of how BGP Prefix Origin Validation
2615 secures the Internet's global routing system.
2616
2617 rpki-client was primarily developed by Kristaps Dzonsons, Claudio
2618 Jeker, Job Snijders, and Sebastian Benoit as part of the OpenBSD
2619 Project and gets released as a base component of OpenBSD every six
2620 months, and follows the OpenBSD release numbering scheme.
2621
2622 This is the first release based on OpenBSD 6.8. It includes the following
2623 changes to the previous release:
2624
2625 * Improve how repositories are downloaded: do not fetch symlinks and
2626 clean extraneous files in the repositories after download using the
2627 cryptographically signed RPKI manifest listings.
2628
2629 * Fix a bug where rpki-client could hang after calling rsync.
2630
2631 * Remove the -f option, no longer needed.
2632
2633 * Improved validation of the trust anchors.
2634
2635 * Add new option '-s timeout' to make rpki-client automatically
2636 terminate after a timeout (default 1 hour). This helps when
2637 rpki-client is run via cron to prevent a hanging process to cause
2638 problems.
2639
2640 Portability improvements:
2641
2642 * Replace warnc() with warnx() + strerror()
2643
2644 * Replace b64_pton() with code using the libcrypto EVP_Decode*
2645 functionality.
2646
2647 * Adjust for OpenSSL 1.1.x compatible use of the EVP_ENCODE_CTX
2648 struct.
2649
2650 rpki-client is known to compile and run on at least the following
2651 Linux distributions: Alpine 3.12, Debian 9, Debian 10, Fedora 31,
2652 Fedora 32, Fedora 33, RHEL/CentOS 7, RHEL/CentOS 8.
2653 It is our hope that packagers take interest and help adapt
2654 OpenBGPD-portable to more distributions.
2655
2656 The mirrors where rpki-client can be found are on
2657 https://www.rpki-client.org/portable.html
2658
2659 Reporting Bugs:
2660 ===============
2661
2662 General bugs may be reported to tech@openbsd.org
2663
2664 Portable bugs may be filed at https://github.com/rpki-client/rpki-client-portable
2665
2666 We welcome feedback and improvements from the broader community.
2667 Thanks to all of the contributors who helped make this release
2668 possible.
2669 </content>
2670 <tags>openbsd</tags>
2671 <author>
2672 <name>benoit-lists@fb12.de</name>
2673 </author>
2674 </entry>
2675 </feed>
Response: application/gopher-menu
Original URLgopher://codemadness.org/1/git/sfeed_tests/file/input/sfe...
Content-Typeapplication/gopher-menu; charset=utf-8