Language Selection

English French German Italian Portuguese Spanish

BSD

Security and BSD Leftovers

Filed under
Security
BSD
  • Security updates for Wednesday

    Security updates have been issued by Arch Linux (go, go-pie, pacman, and xpdf), CentOS (java-1.7.0-openjdk, java-1.8.0-openjdk, java-11-openjdk, and patch), openSUSE (gcc7), Red Hat (firefox, kernel, and qemu-kvm-rhev), Slackware (mozilla), SUSE (kernel, libcaca, openconnect, python, sysstat, and zziplib), and Ubuntu (libxslt, linux-azure, and linux-lts-xenial, linux-aws).

  • os-release file appears

    There’s now (well, for DragonFly 5.7 users) an /etc/os-release file to show the installed DragonFly version.

  • samsung ativ book 9

    Physically, it’s in the ultraportable category with a 12 inch screen and weighing about two pounds. It’s a completely fanless design, using an M-5Y31 CPU (Broadwell generation). My model came with 8GB RAM and 256GB SSD, but it’s possible to find some with half that. Everything is a bit tiny and compromised, so in my opinion it wouldn’t make for a good all around machine (like the Carbon X1), but if space and weight is at a premium, it’s a good substitute.

    I immediately installed OpenBSD 6.6 when it arrived and have been using it for a few days. I have a few complaints, and I’m not confident in recommending it, but no regrets.

FreeBSD 12.1-RC2 Now Available

Filed under
BSD

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

The second RC build of the 12.1-RELEASE release cycle is now available.

Installation images are available for:

o 12.1-RC2 amd64 GENERIC
o 12.1-RC2 i386 GENERIC
o 12.1-RC2 powerpc GENERIC
o 12.1-RC2 powerpc64 GENERIC64
o 12.1-RC2 powerpcspe MPC85XXSPE
o 12.1-RC2 sparc64 GENERIC
o 12.1-RC2 armv6 RPI-B
o 12.1-RC2 armv7 BANANAPI
o 12.1-RC2 armv7 BEAGLEBONE
o 12.1-RC2 armv7 CUBIEBOARD
o 12.1-RC2 armv7 CUBIEBOARD2
o 12.1-RC2 armv7 CUBOX-HUMMINGBOARD
o 12.1-RC2 armv7 RPI2
o 12.1-RC2 armv7 PANDABOARD
o 12.1-RC2 armv7 WANDBOARD
o 12.1-RC2 armv7 GENERICSD
o 12.1-RC2 aarch64 GENERIC
o 12.1-RC2 aarch64 RPI3
o 12.1-RC2 aarch64 PINE64
o 12.1-RC2 aarch64 PINE64-LTS

Note regarding arm SD card images: For convenience for those without
console access to the system, a freebsd user with a password of
freebsd is available by default for ssh(1) access.  Additionally,
the root user password is set to root.  It is strongly recommended
to change the password for both users after gaining access to the
system.

Installer images and memory stick images are available here:

    https://download.freebsd.org/ftp/releases/ISO-IMAGES/12.1/

The image checksums follow at the end of this e-mail.

If you notice problems you can report them through the Bugzilla PR
system or on the -stable mailing list.

If you would like to use SVN to do a source based update of an existing
system, use the "releng/12.1" branch.

A summary of changes since 12.1-RC1 includes:

o The loader.efi had been updated to use ioalign for compliance with
  UEFI specification 2.7A.

o A null pointer dereference bug had been fixed.

o A fix to SCTP to reset local variables to their initial values had
  been added.

o The ixgbe(4) driver had been updated to prevent a system crash when
  configuring EEE on X500EM_X devices.

o The sdhci(4) driver had been updated to fix a boot issue on Beaglebone
  SoCs.

A list of changes since 12.0-RELEASE is available in the releng/12.1
release notes:

    https://www.freebsd.org/releases/12.1R/relnotes.html

Please note, the release notes page is not yet complete, and will be
updated on an ongoing basis as the 12.1-RELEASE cycle progresses.

=== Virtual Machine Disk Images ===

VM disk images are available for the amd64, i386, and aarch64
architectures.  Disk images may be downloaded from the following URL
(or any of the FreeBSD download mirrors):

    https://download.freebsd.org/ftp/releases/VM-IMAGES/12.1-RC2/

The partition layout is:

    ~ 16 kB - freebsd-boot GPT partition type (bootfs GPT label)
    ~ 1 GB  - freebsd-swap GPT partition type (swapfs GPT label)
    ~ 20 GB - freebsd-ufs GPT partition type (rootfs GPT label)

The disk images are available in QCOW2, VHD, VMDK, and raw disk image
formats.  The image download size is approximately 135 MB and 165 MB
respectively (amd64/i386), decompressing to a 21 GB sparse image.

Note regarding arm64/aarch64 virtual machine images: a modified QEMU EFI
loader file is needed for qemu-system-aarch64 to be able to boot the
virtual machine images.  See this page for more information:

    https://wiki.freebsd.org/arm64/QEMU

To boot the VM image, run:

    % qemu-system-aarch64 -m 4096M -cpu cortex-a57 -M virt  \
	-bios QEMU_EFI.fd -serial telnet::4444,server -nographic \
	-drive if=none,file=VMDISK,id=hd0 \
	-device virtio-blk-device,drive=hd0 \
	-device virtio-net-device,netdev=net0 \
	-netdev user,id=net0

Be sure to replace "VMDISK" with the path to the virtual machine image.

=== Amazon EC2 AMI Images ===

FreeBSD/amd64 EC2 AMIs are available in the following regions:

  eu-north-1 region: ami-0186d6a5fbc8766f2
  ap-south-1 region: ami-0b6bef3551f1b0f70
  eu-west-3 region: ami-062495360178ede5e
  eu-west-2 region: ami-0ccfe49c85e5f8cc0
  eu-west-1 region: ami-0e2730782e7462f98
  ap-northeast-2 region: ami-053ddd72fc1feb00a
  ap-northeast-1 region: ami-06cd2e1981334f254
  sa-east-1 region: ami-08acf6b9b1df41f34
  ca-central-1 region: ami-064249d804369c668
  ap-east-1 region: ami-020c406cb2f52030b
  ap-southeast-1 region: ami-08264f040bf980098
  ap-southeast-2 region: ami-0da02f500e46cac8f
  eu-central-1 region: ami-05458e84d05b820e8
  us-east-1 region: ami-06f6cbd134064befb
  us-east-2 region: ami-0cfe92105f4fee6a8
  us-west-1 region: ami-0bb63fac9c5ec153a
  us-west-2 region: ami-00a29b19544968928

FreeBSD/aarch64 EC2 AMIs are available in the following regions:

  eu-north-1 region: ami-0ea4448b9b547107c
  ap-south-1 region: ami-07a9fd713466fe63f
  eu-west-3 region: ami-02e84241865e90f54
  eu-west-2 region: ami-0b707024f9aadb94f
  eu-west-1 region: ami-0abf12b852be4e776
  ap-northeast-2 region: ami-086547036e5a47816
  ap-northeast-1 region: ami-038017fcbf85e7669
  sa-east-1 region: ami-0da52f30dd7d86ef5
  ca-central-1 region: ami-092ee6a89213c15a2
  ap-east-1 region: ami-0db28099cf79bf65d
  ap-southeast-1 region: ami-0852402b94d58adf8
  ap-southeast-2 region: ami-01f869cc877cef54f
  eu-central-1 region: ami-04d008006fdb7e720
  us-east-1 region: ami-0411db3e8715d4352
  us-east-2 region: ami-01e68c35d7ddcac3e
  us-west-1 region: ami-02dcdcd99bf7fde1f
  us-west-2 region: ami-09ce8334b595dff30

=== Vagrant Images ===

FreeBSD/amd64 images are available on the Hashicorp Atlas site, and can
be installed by running:

    % vagrant init freebsd/FreeBSD-12.1-RC2
    % vagrant up

=== Upgrading ===

The freebsd-update(8) utility supports binary upgrades of amd64 and i386
systems running earlier FreeBSD releases.  Systems running earlier
FreeBSD releases can upgrade as follows:

	# freebsd-update upgrade -r 12.1-RC2

During this process, freebsd-update(8) may ask the user to help by
merging some configuration files or by confirming that the automatically
performed merging was done correctly.

	# freebsd-update install

The system must be rebooted with the newly installed kernel before
continuing.

	# shutdown -r now

After rebooting, freebsd-update needs to be run again to install the new
userland components:

	# freebsd-update install

It is recommended to rebuild and install all applications if possible,
especially if upgrading from an earlier FreeBSD release, for example,
FreeBSD 11.x.  Alternatively, the user can install misc/compat11x and
other compatibility libraries, afterwards the system must be rebooted
into the new userland:

	# shutdown -r now

Finally, after rebooting, freebsd-update needs to be run again to remove
stale files:

	# freebsd-update install

Read more

Also: FreeBSD 12.1-RC2 Has Update For UEFI 2.7A, Various Bug Fixes

GhostBSD Reaffirms To Being TrueOS+BSD Desktop OS With Official MATE Desktop

Filed under
BSD

With Project Trident moving away from a TrueOS/FreeBSD base to instead Void Linux, if you are looking for a good BSD-based desktop operating system it largely comes down to the likes of MidnightBSD and GhostBSD providing good out-of-the-box setups. As for GhostBSD, they are reaffirming their commitment to using TrueOS/FreeBSD and MATE as their official desktop.

The project reaffirmed on Wednesday that they are sticking to their TrueOS with FreeBSD 12-STABLE base while being a "slow-moving rolling release' that will eventually migrate to TrueOS with FreeBSD 13-STABLE after it is available.

Read more

Direct: Dealing with the misunderstandings of what is GhostBSD

Also: Codebase: Neck Deep | BSD Now 320

OpenBSD 6.6 Released

Filed under
BSD
  • OpenBSD 6.6

    This is a partial list of new features and systems included in OpenBSD 6.6. For a comprehensive list, see the changelog leading to 6.6.

  • OpenBSD 6.6 Arrives: Disables GCC In Base For ARMv7/i386, SMP Improvements, AMDGPU Added

    Theo de Raadt released OpenBSD 6.6 today as the newest feature update to this popular BSD operating system known for its security focus.

    OpenBSD 6.6 has moved to disabling GCC in its base packages for i386 and ARMv7, LLVM Clang platform support has been expanded, various SMP improvements and more system calls being unlocked, improved Linux compatibility with ACPI interfaces, a number of new hardware drivers, wired and wireless networking stack improvements, various installation enhancements, and the never-ending work on improving the security. OpenBSD 6.6 ships with OpenSSH 8.1, LibreSSL 3.0.2, OpenSMTPD 6.6, and other updated packages.

Project Trident 2020 OS Migration

Filed under
OS
GNU
Linux
BSD

After several months of examination and testing of the various operating systems that are available right now, we have reached a conclusion. Project Trident will rebasing with Void Linux.

Read more

Also: Project Trident Switching From TrueOS/FreeBSD Distribution To Basing On Void Linux

FreeBSD 12.1-RC1 Now Available

Filed under
BSD

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

The first RC build of the 12.1-RELEASE release cycle is now available.

Installation images are available for:

o 12.1-RC1 amd64 GENERIC
o 12.1-RC1 i386 GENERIC
o 12.1-RC1 powerpc GENERIC
o 12.1-RC1 powerpc64 GENERIC64
o 12.1-RC1 powerpcspe MPC85XXSPE
o 12.1-RC1 sparc64 GENERIC
o 12.1-RC1 armv6 RPI-B
o 12.1-RC1 armv7 BANANAPI
o 12.1-RC1 armv7 BEAGLEBONE
o 12.1-RC1 armv7 CUBIEBOARD
o 12.1-RC1 armv7 CUBIEBOARD2
o 12.1-RC1 armv7 CUBOX-HUMMINGBOARD
o 12.1-RC1 armv7 RPI2
o 12.1-RC1 armv7 PANDABOARD
o 12.1-RC1 armv7 WANDBOARD
o 12.1-RC1 armv7 GENERICSD
o 12.1-RC1 aarch64 GENERIC
o 12.1-RC1 aarch64 RPI3
o 12.1-RC1 aarch64 PINE64
o 12.1-RC1 aarch64 PINE64-LTS

Note regarding arm SD card images: For convenience for those without
console access to the system, a freebsd user with a password of
freebsd is available by default for ssh(1) access.  Additionally,
the root user password is set to root.  It is strongly recommended
to change the password for both users after gaining access to the
system.

Installer images and memory stick images are available here:

    https://download.freebsd.org/ftp/releases/ISO-IMAGES/12.1/

The image checksums follow at the end of this e-mail.

If you notice problems you can report them through the Bugzilla PR
system or on the -stable mailing list.

If you would like to use SVN to do a source based update of an existing
system, use the "releng/12.1" branch.

A summary of changes since 12.1-BETA3 includes:

o A NULL pointer dereference that could lead to a system crash had been
  fixed.

o A fix to correctly implement pmap_page_is_mapped() on arm64 and riscv.

o A fix to tun(4) and tap(4) when destroying interfaces had been added.

o A fix to krping to notify sleeping threads of device removal had been
  added.

o Several updates to mlx5core, mlx5en(4), and mlx5ib(4).

o Several fixes in libusb(3) and xhci(4) have been added.

o Several SCTP and TCP fixes have been added.

A list of changes since 12.0-RELEASE is available in the releng/12.1
release notes:

    https://www.freebsd.org/releases/12.1R/relnotes.html

Please note, the release notes page is not yet complete, and will be
updated on an ongoing basis as the 12.1-RELEASE cycle progresses.

=== Virtual Machine Disk Images ===

VM disk images are available for the amd64, i386, and aarch64
architectures.  Disk images may be downloaded from the following URL
(or any of the FreeBSD download mirrors):

    https://download.freebsd.org/ftp/releases/VM-IMAGES/12.1-RC1/

The partition layout is:

    ~ 16 kB - freebsd-boot GPT partition type (bootfs GPT label)
    ~ 1 GB  - freebsd-swap GPT partition type (swapfs GPT label)
    ~ 20 GB - freebsd-ufs GPT partition type (rootfs GPT label)

The disk images are available in QCOW2, VHD, VMDK, and raw disk image
formats.  The image download size is approximately 135 MB and 165 MB
respectively (amd64/i386), decompressing to a 21 GB sparse image.

Note regarding arm64/aarch64 virtual machine images: a modified QEMU EFI
loader file is needed for qemu-system-aarch64 to be able to boot the
virtual machine images.  See this page for more information:

    https://wiki.freebsd.org/arm64/QEMU

To boot the VM image, run:

    % qemu-system-aarch64 -m 4096M -cpu cortex-a57 -M virt  \
	-bios QEMU_EFI.fd -serial telnet::4444,server -nographic \
	-drive if=none,file=VMDISK,id=hd0 \
	-device virtio-blk-device,drive=hd0 \
	-device virtio-net-device,netdev=net0 \
	-netdev user,id=net0

Be sure to replace "VMDISK" with the path to the virtual machine image.

=== Amazon EC2 AMI Images ===

FreeBSD/amd64 EC2 AMIs are available in the following regions:

  eu-north-1 region: ami-0c2caa354f54dcc8e
  ap-south-1 region: ami-011f6d0b22b4179ae
  eu-west-3 region: ami-0e633b1e66b94dc5e
  eu-west-2 region: ami-06f77908c8875b5ce
  eu-west-1 region: ami-07d5b3d4ffa682d66
  ap-northeast-2 region: ami-0a0d9969831c99d3f
  ap-northeast-1 region: ami-092398d1a41a67f27
  sa-east-1 region: ami-023dd6db41165f441
  ca-central-1 region: ami-0cf9fd10259cf4eb2
  ap-east-1 region: ami-0e255d1bb4a1f76f4
  ap-southeast-1 region: ami-0404212cff3236606
  ap-southeast-2 region: ami-0fea81c67debcba8b
  eu-central-1 region: ami-08e32f4e90fd250f4
  us-east-1 region: ami-0e6e401d0ffebd916
  us-east-2 region: ami-0d094195cae5bf901
  us-west-1 region: ami-04c1e10d06064e68d
  us-west-2 region: ami-02d0010139a9a494e

FreeBSD/aarch64 EC2 AMIs are available in the following regions:

  eu-north-1 region: ami-022e4644320e82ac1
  ap-south-1 region: ami-0e421a1864d53d226
  eu-west-3 region: ami-0bffb1c264a4b8d09
  eu-west-2 region: ami-0f596a538918dc9c8
  eu-west-1 region: ami-063c017d8b9086b55
  ap-northeast-2 region: ami-0b34ed283d7dd41ae
  ap-northeast-1 region: ami-0071602b3e78a8de0
  sa-east-1 region: ami-07986820662819e67
  ca-central-1 region: ami-0d9ee49739059957b
  ap-east-1 region: ami-00ae1e2b897eb6230
  ap-southeast-1 region: ami-0018127ce245410e0
  ap-southeast-2 region: ami-02fa0380052cd268f
  eu-central-1 region: ami-01836dc7a9f273243
  us-east-1 region: ami-0018654c0af06d99d
  us-east-2 region: ami-06a4203b93836b927
  us-west-1 region: ami-09c5010072b44bd96
  us-west-2 region: ami-063fae5c2ec327807

=== Vagrant Images ===

FreeBSD/amd64 images are available on the Hashicorp Atlas site, and can
be installed by running:

    % vagrant init freebsd/FreeBSD-12.1-RC1
    % vagrant up

=== Upgrading ===

The freebsd-update(8) utility supports binary upgrades of amd64 and i386
systems running earlier FreeBSD releases.  Systems running earlier
FreeBSD releases can upgrade as follows:

	# freebsd-update upgrade -r 12.1-RC1

During this process, freebsd-update(8) may ask the user to help by
merging some configuration files or by confirming that the automatically
performed merging was done correctly.

	# freebsd-update install

The system must be rebooted with the newly installed kernel before
continuing.

	# shutdown -r now

After rebooting, freebsd-update needs to be run again to install the new
userland components:

	# freebsd-update install

It is recommended to rebuild and install all applications if possible,
especially if upgrading from an earlier FreeBSD release, for example,
FreeBSD 11.x.  Alternatively, the user can install misc/compat11x and
other compatibility libraries, afterwards the system must be rebooted
into the new userland:

	# shutdown -r now

Finally, after rebooting, freebsd-update needs to be run again to remove
stale files:

	# freebsd-update install

Read more

Announce: OpenSSH 8.1 released

Filed under
Security
BSD

OpenSSH 8.1 has just been released. It will be available from the mirrors listed at http://www.openssh.com/ shortly.

Read more

Project Trident 19.10 Now Available

Filed under
BSD

This is a general package update to the CURRENT release repository based upon TrueOS 19.10

Read more

FreeBSD 12.1-BETA3 Now Available

Filed under
BSD

The third BETA build of the 12.1-RELEASE release cycle is now available.

Installation images are available for:

o 12.1-BETA3 amd64 GENERIC
o 12.1-BETA3 i386 GENERIC
o 12.1-BETA3 powerpc GENERIC
o 12.1-BETA3 powerpc64 GENERIC64
o 12.1-BETA3 powerpcspe MPC85XXSPE
o 12.1-BETA3 sparc64 GENERIC
o 12.1-BETA3 armv6 RPI-B
o 12.1-BETA3 armv7 BANANAPI
o 12.1-BETA3 armv7 BEAGLEBONE
o 12.1-BETA3 armv7 CUBIEBOARD
o 12.1-BETA3 armv7 CUBIEBOARD2
o 12.1-BETA3 armv7 CUBOX-HUMMINGBOARD
o 12.1-BETA3 armv7 RPI2
o 12.1-BETA3 armv7 PANDABOARD
o 12.1-BETA3 armv7 WANDBOARD
o 12.1-BETA3 armv7 GENERICSD
o 12.1-BETA3 aarch64 GENERIC
o 12.1-BETA3 aarch64 RPI3
o 12.1-BETA3 aarch64 PINE64
o 12.1-BETA3 aarch64 PINE64-LTS

Note regarding arm SD card images: For convenience for those without
console access to the system, a freebsd user with a password of
freebsd is available by default for ssh(1) access.  Additionally,
the root user password is set to root.  It is strongly recommended
to change the password for both users after gaining access to the
system.

Installer images and memory stick images are available here:

    https://download.freebsd.org/ftp/releases/ISO-IMAGES/12.1/

The image checksums follow at the end of this e-mail.

If you notice problems you can report them through the Bugzilla PR
system or on the -stable mailing list.

If you would like to use SVN to do a source based update of an existing
system, use the "releng/12.1" branch.

A summary of changes since 12.1-BETA2 includes:

o An issue with imx6-based arm boards had been fixed.

o An issue with 64-bit long double types leading to link failures had
  been fixed.

o An overflow logic error had been fixed in fsck_msdosfs(8).

o An issue in destruction of robust mutexes had been fixed.

o Support for the '-vnP' flags to the zfs send subcommand had been
  added for bookmarks.

o The ixgbe(4) driver had been updated to prevent a potential system
  crash with certain 10Gb Intel NICs.

o A regression with the zfs send subcommand when using the '-n', '-P',
  and '-i' flags had been fixed.

o The freebsd-update(8) utility had been updated to include two new
  subcommands, updatesready and showconfig.

o Support for 'ps -H' had been added to kvm(3).

o An issue when compiling certain ports targeting Intel Atom CPUs had
  been fixed.

o A use-after-free in SCTP had been fixed.

o A regression that could lead to a system crash when using vmxnet3 had
  been fixed.

A list of changes since 12.0-RELEASE is available in the releng/12.1
release notes:

    https://www.freebsd.org/releases/12.1R/relnotes.html

Please note, the release notes page is not yet complete, and will be
updated on an ongoing basis as the 12.1-RELEASE cycle progresses.

=== Virtual Machine Disk Images ===

VM disk images are available for the amd64, i386, and aarch64
architectures.  Disk images may be downloaded from the following URL
(or any of the FreeBSD download mirrors):

    https://download.freebsd.org/ftp/releases/VM-IMAGES/12.1-BETA3/

The partition layout is:

    ~ 16 kB - freebsd-boot GPT partition type (bootfs GPT label)
    ~ 1 GB  - freebsd-swap GPT partition type (swapfs GPT label)
    ~ 20 GB - freebsd-ufs GPT partition type (rootfs GPT label)

The disk images are available in QCOW2, VHD, VMDK, and raw disk image
formats.  The image download size is approximately 135 MB and 165 MB
respectively (amd64/i386), decompressing to a 21 GB sparse image.

Note regarding arm64/aarch64 virtual machine images: a modified QEMU EFI
loader file is needed for qemu-system-aarch64 to be able to boot the
virtual machine images.  See this page for more information:

    https://wiki.freebsd.org/arm64/QEMU

To boot the VM image, run:

    % qemu-system-aarch64 -m 4096M -cpu cortex-a57 -M virt  \
	-bios QEMU_EFI.fd -serial telnet::4444,server -nographic \
	-drive if=none,file=VMDISK,id=hd0 \
	-device virtio-blk-device,drive=hd0 \
	-device virtio-net-device,netdev=net0 \
	-netdev user,id=net0

Be sure to replace "VMDISK" with the path to the virtual machine image.

=== Amazon EC2 AMI Images ===

FreeBSD/amd64 EC2 AMIs are available in the following regions:

  eu-north-1 region: ami-07085de4e26071c9e
  ap-south-1 region: ami-095bd806d8acfffb1
  eu-west-3 region: ami-0314542b8d7579bdd
  eu-west-2 region: ami-06ec921eb87ef4d7b
  eu-west-1 region: ami-0f0051c800be4091e
  ap-northeast-2 region: ami-0f109258a463177bb
  ap-northeast-1 region: ami-0224a1cb8e19333b8
  sa-east-1 region: ami-0536a86bff5f33356
  ca-central-1 region: ami-06709921360dccfa3
  ap-east-1 region: ami-0142af9336f6e529c
  ap-southeast-1 region: ami-0c439e0bc0c567dd3
  ap-southeast-2 region: ami-0fa770b7f07583b48
  eu-central-1 region: ami-0dfca49cf2ba89c43
  us-east-1 region: ami-06884b4e2e511590f
  us-east-2 region: ami-06c687665309d8b17
  us-west-1 region: ami-0dce597e8b07a6c6d
  us-west-2 region: ami-0e1f5ccdd2221b1d6

FreeBSD/aarch64 EC2 AMIs are available in the following regions:

  eu-north-1 region: ami-0914805810f9fcca2
  ap-south-1 region: ami-0862409434d8089f2
  eu-west-3 region: ami-08e6dc501b060fa7c
  eu-west-2 region: ami-000f2362fef121710
  eu-west-1 region: ami-0c7a18e2b216a1b0c
  ap-northeast-2 region: ami-047bc72d91ab47b95
  ap-northeast-1 region: ami-082dcca6b9ac52f3f
  sa-east-1 region: ami-0a9fd8ffffc889430
  ca-central-1 region: ami-0d513e584801de3fa
  ap-east-1 region: ami-089a6b231886f692f
  ap-southeast-1 region: ami-09c6f305a761c8712
  ap-southeast-2 region: ami-0ee5e02b85aecbef3
  eu-central-1 region: ami-08321cbac28d28d71
  us-east-1 region: ami-0a9c2fdd733536b50
  us-east-2 region: ami-0a5b46f4260ed9ca5
  us-west-1 region: ami-01aca4de517a623fe
  us-west-2 region: ami-0ac8b561fb3597d89

=== Vagrant Images ===

FreeBSD/amd64 images are available on the Hashicorp Atlas site, and can
be installed by running:

    % vagrant init freebsd/FreeBSD-12.1-BETA3
    % vagrant up

=== Upgrading ===

The freebsd-update(8) utility supports binary upgrades of amd64 and i386
systems running earlier FreeBSD releases.  Systems running earlier
FreeBSD releases can upgrade as follows:

	# freebsd-update upgrade -r 12.1-BETA3

During this process, freebsd-update(8) may ask the user to help by
merging some configuration files or by confirming that the automatically
performed merging was done correctly.

	# freebsd-update install

The system must be rebooted with the newly installed kernel before
continuing.

	# shutdown -r now

After rebooting, freebsd-update needs to be run again to install the new
userland components:

	# freebsd-update install

It is recommended to rebuild and install all applications if possible,
especially if upgrading from an earlier FreeBSD release, for example,
FreeBSD 11.x.  Alternatively, the user can install misc/compat11x and
other compatibility libraries, afterwards the system must be rebooted
into the new userland:

	# shutdown -r now

Finally, after rebooting, freebsd-update needs to be run again to remove
stale files:

	# freebsd-update install

Read more

Programming, Open Hardware and BSD

Filed under
Development
BSD

                           

  • The rise of open-source computing

                             

                               

    is a set of open-source designs for microchips that was initially developed a decade ago at the University of California, Berkeley. These days it is attracting attention from many big technology firms, including Google, Nvidia and Qualcomm (see article). In August IBM made its Power chip designs open-source. These moves are welcome, for two reasons.

  • A Message to Our Readers

    We ask for your help in getting the word out (in addition to hopefully buying the issue when it's released). We know there are many thousands out there who no longer have bookstores that carry 2600 in their neighborhoods or who live in parts of the world where getting our publication has always been, at best, a challenge.

    Please show your support and buy this issue which you can then enjoy forever - and let everyone know what we're doing. Because if this is a success, we will be able to invest more into the magazine (paper and digital) to make it even better, as well as support more projects like HOPE.

  • Binary Hardening in IoT products

    Unfortunately, with few exceptions (notably Synology) we see there is very little coverage, and even Synology struggles to adopt basic hardening features like ASLR and stack guards.

    A perfect score, where all binaries had all 5 basic safety features, would result in a chart that looks like a regular pentagon. Instead, in most vendors’ cases, they struggle to achieve polygon status at all.

  •                

  • Milky Way v0.3 release

                     

                       

    Added
    LibreSSL as the default provider of SSL and TLS protocols
    Xenocara as the default provider of display server for the X Window System

  •                

  • sysupgrade(8) Added to OpenBSD 6.5

                     

                       

    In a move bound to be greeted with great enthusiasm, the newly-released Patch 012 for OpenBSD 6.5 adds sysupgrade(8) to the system.

Syndicate content

More in Tux Machines

Red Hat Enterprise Linux 7 and CentOS 7 Get Important Kernel Security Update

Marked as important by Red Hat Product Security, the new Linux kernel security patch is here to fix a use-after-free flaw (CVE-2018-20856) discovered in the __blk_drain_queue() function in block/blk-core.c, as well as a heap overflow issue (CVE-2019-3846) discovered in the mwifiex_update_bss_desc_with_ie function in marvell/mwifiex/scan.c. It also addresses a heap overflow issue (CVE-2019-10126) discovered in the mwifiex_uap_parse_tail_ies function in drivers/net/wireless/marvell/mwifiex/ie.c and a Bluetooth flaw (CVE-2019-9506) that may lead to BR/EDR encryption key negotiation attacks (KNOB). Read more

Purism: Supplying the Demand

Thank you all for the continued support and remarkable demand for the Librem 5. As we’ve shared earlier, we are iterating through shipping batches. The purpose of doing so is to increment and improve with each batch toward mass production and share that story publicly. As a result, these earlier batches are limited in quantity as we move toward mass production. Publicly releasing iterated hardware at this level of transparency is extremely uncommon, but in nearly everything we do we try to lead by example. Forming as a Social Purpose Corporation, open sourcing all our software, having PureOS be FSF endorsed, securing the lower layers of computing, or manufacturing a revolutionary mobile phone from scratch… all have required sacrifice but are well worth it to provide people with a values-driven alternative to Big Tech. Read more Also: Purism Provides Update On Librem 5 Shipping, Known Issues

KDE Plasma 5.17 Desktop Environment Gets First Point Release with 40 Bug Fixes

Released last week on October 15th, the KDE Plasma 5.17 desktop environment introduces Night Color support on X11, fractional scaling on Wayland, HiDPI and multi-screen improvements, as well as the ability to support for managing and configuring Thunderbolt devices in System Settings. It also improves the notification system with a new Do Not Disturb mode that automatically detects presentations, Breeze GTK theme support for the Google Chrome and Chromium web browsers, Nvidia GPU stats in System Settings, and color scheme support for GTK and GNOME apps in the Breeze GTK theme. Read more

Ubuntu Touch OTA-11 Release

Ubuntu Touch is the privacy and freedom respecting mobile operating system by UBports. Today we are happy to announce the release of Ubuntu Touch OTA-11! OTA-11 is immediately available for all supported Ubuntu Touch devices. You can skip to How to get OTA-11 to get it right away if you're impatient, or read on to learn more about this release. We were calling this a "small release" originally. Our plan was to cover the backlog of pull requests that weren't quite ready for OTA-10. It turns out, that made this "small" update not small at all. Read more Also: Ubuntu Touch OTA-11 for Ubuntu Phones Brings Smarter Keyboard, Better Browsing UBports' Ubuntu Touch OTA-11 Released