The project has released OpenBSD 6.2 which features many new drivers, particularly for the ARM architecture, and network packet handling performance improvements. Some key features have been added to the system installer too, including checking for security updates on the system’s first boot: “Installer improvements: The installer now uses the Allotment Routing Table (ART). A unique kernel is now created by the installer to boot from after install/upgrade. On release installs of architectures supported by syspatch, “syspatch -c” is now added to rc.firsttime. Backwards compatibility code to support the ‘rtsol’ keyword in hostname.if(5) has been removed. The install.site and upgrade.site scripts are now executed at the end of the install/upgrade process. More detailed information is shown to identify disks. The IPv6 default router selection has been fixed. On the amd64 platform, AES-NI is used if present.“

This license is recognized as free license, but is not copyleft.

P.S.

Creating a bootable USB key using a Un*x-like system:
Some older systems may not be able to boot from USB keys or require
changing boot priority. Check your BIOS settings if you run into
problems.
First, you will need to obtain a local copy of the bootable filesystem
image miniroot59.fs or install59.fs as described above.
You should use the signify(1) and sha256(1) commands to verify
the integrity of the images with the SHA256.sig file on the mirror site.
Next, use the dd(1) utility to copy the file to the USB storage device.
The command would likely be, under OpenBSD:
dd if=miniroot59.fs of=/dev/rsdNc bs=1m
where N is the device number. You can find the correct device number
by checking dmesg(8) when inserting the media.
If you are using another operating system, you may have to adapt
this to conform to local naming conventions for the USB key and
options suitable for copying to a "raw" disk image. The key
issue is that the device name used for the USB key *must* be one
that refers to the correct block device, not a partition or
compatibility mode, and the copy command needs to be compatible
with the requirement that writes to a raw device must be in
multiples of 512-byte blocks. The variations are endless and
beyond the scope of this document.
If you're doing this on the system you intend to boot the USB key on,
copying the image back to a file and doing a compare or checksum
is a good way to verify that the USB key is readable and free of
read/write errors.

The OpenBSD developers have announced the availability of a new stable release of their security-oriented operating system. The new release, OpenBSD 6.1, introduces bug fixes, several new or improved hardware drivers and security enhancements to the system installer. “Installer improvements: The installer now uses privilege separation for fetching and verifying the install sets. Install sets are now fetched over an HTTPS connection by default when using a mirror that supports it. The installer now considers all of the DHCP information in file name, boot file-name, server-name, tftp-server-name, and next-server when attempting to do automatic installs or upgrades. The installer no longer adds a route to an alias IP via 127.0.0.1, due to improvements in the kernel routing components.“

This license is recognized as free license, but is not copyleft.

P.S.

Creating a bootable USB key using a Un*x-like system:
Some older systems may not be able to boot from USB keys or require
changing boot priority. Check your BIOS settings if you run into
problems.
First, you will need to obtain a local copy of the bootable filesystem
image miniroot59.fs or install59.fs as described above.
You should use the signify(1) and sha256(1) commands to verify
the integrity of the images with the SHA256.sig file on the mirror site.
Next, use the dd(1) utility to copy the file to the USB storage device.
The command would likely be, under OpenBSD:
dd if=miniroot59.fs of=/dev/rsdNc bs=1m
where N is the device number. You can find the correct device number
by checking dmesg(8) when inserting the media.
If you are using another operating system, you may have to adapt
this to conform to local naming conventions for the USB key and
options suitable for copying to a "raw" disk image. The key
issue is that the device name used for the USB key *must* be one
that refers to the correct block device, not a partition or
compatibility mode, and the copy command needs to be compatible
with the requirement that writes to a raw device must be in
multiples of 512-byte blocks. The variations are endless and
beyond the scope of this document.
If you're doing this on the system you intend to boot the USB key on,
copying the image back to a file and doing a compare or checksum
is a good way to verify that the USB key is readable and free of
read/write errors.

The OpenBSD project has announced the release of OpenBSD 6.0. The OpenBSD project focuses on providing code and documentation that are correct and of high quality. This has lead to OpenBSD being regarded as a highly secure and reliable operating system. The new release features New/extended platforms: for armv7 – EFI bootloader added, kernels are now loaded from FFS instead of FAT or EXT filesystems, without U-Boot headers, a single kernel and ramdisk are now used for all SoCs, Miniroot installer images include U-Boot 2016.07 with support for EFI payloads, vax removed. Many new and improved hardware drivers and support for hardware-reduced ACPI implementations, for ACPI 5.0 implementations, initial support for MSI-X has been added, the xhci(4) driver now performs handoff from an xHCI-capable BIOS correctly, W^X is now strictly enforced by default etc.. Updated versions of LibreSSL and OpenSSH are included as well and feature several security enhancements.

This license is recognized as free license, but is not copyleft.

P.S.

Creating a bootable USB key using a Un*x-like system:
Some older systems may not be able to boot from USB keys or require
changing boot priority. Check your BIOS settings if you run into
problems.
First, you will need to obtain a local copy of the bootable filesystem
image miniroot59.fs or install59.fs as described above.
You should use the signify(1) and sha256(1) commands to verify
the integrity of the images with the SHA256.sig file on the mirror site.
Next, use the dd(1) utility to copy the file to the USB storage device.
The command would likely be, under OpenBSD:
dd if=miniroot59.fs of=/dev/rsdNc bs=1m
where N is the device number. You can find the correct device number
by checking dmesg(8) when inserting the media.
If you are using another operating system, you may have to adapt
this to conform to local naming conventions for the USB key and
options suitable for copying to a "raw" disk image. The key
issue is that the device name used for the USB key *must* be one
that refers to the correct block device, not a partition or
compatibility mode, and the copy command needs to be compatible
with the requirement that writes to a raw device must be in
multiples of 512-byte blocks. The variations are endless and
beyond the scope of this document.
If you're doing this on the system you intend to boot the USB key on,
copying the image back to a file and doing a compare or checksum
is a good way to verify that the USB key is readable and free of
read/write errors.

The OpenBSD project has announced the release of OpenBSD 5.9. The OpenBSD project focuses on providing code and documentation that are correct and of high quality. This has lead to OpenBSD being regarded as a highly secure and reliable operating system. The new release features W^X (write or execute) security for 32-bit x86 processors, many new and improved hardware drivers and support for installing OpenBSD on GPT partitioned hard drives. This release features a forked version of the “less” command and network stack improvements. Updated versions of LibreSSL and OpenSSH are included as well and feature several security enhancements.

This license is recognized as free license, but is not copyleft.

P.S.

Creating a bootable USB key using a Un*x-like system:
Some older systems may not be able to boot from USB keys or require
changing boot priority. Check your BIOS settings if you run into
problems.
First, you will need to obtain a local copy of the bootable filesystem
image miniroot59.fs or install59.fs as described above.
You should use the signify(1) and sha256(1) commands to verify
the integrity of the images with the SHA256.sig file on the mirror site.
Next, use the dd(1) utility to copy the file to the USB storage device.
The command would likely be, under OpenBSD:
dd if=miniroot59.fs of=/dev/rsdNc bs=1m
where N is the device number. You can find the correct device number
by checking dmesg(8) when inserting the media.
If you are using another operating system, you may have to adapt
this to conform to local naming conventions for the USB key and
options suitable for copying to a "raw" disk image. The key
issue is that the device name used for the USB key *must* be one
that refers to the correct block device, not a partition or
compatibility mode, and the copy command needs to be compatible
with the requirement that writes to a raw device must be in
multiples of 512-byte blocks. The variations are endless and
beyond the scope of this document.
If you're doing this on the system you intend to boot the USB key on,
copying the image back to a file and doing a compare or checksum
is a good way to verify that the USB key is readable and free of
read/write errors.

Noct is a 2D top-down multiplayer survival horror game that blends arcade combat with RPG survival elements. You are a survivor of the apocalyptic purge that formed the desolate wasteland now know as Noct.

In the 20th anniversary of the OpenBSD source tree, Theo de Raadt has announced the release of OpenBSD 5.8. The OpenBSD project focuses on providing code and documentation that are correct and of high quality. This has lead to OpenBSD being regarded as a highly secure and reliable operating system. The new release features several new or improved drivers, the sudo command has been replaced with doas and some of the system installer’s default settings have been changed. “We are pleased to announce the official release of OpenBSD 5.8. This is our 38th release on CD-ROM (and 39th via FTP/HTTP). We remain proud of OpenBSD’s record of twenty years with only two remote holes in the default install. As in our previous releases, 5.8 provides significant improvements, including new features, in nearly all areas of the system.“

This is the 37th release on CD-ROM (and 38th via FTP/HTTP). It remains proud of OpenBSD’s record of more than ten years with only two remote holes in the default install. As in our previous releases, 5.7 provides significant improvements, including new features, in nearly all areas of the system. Improved hardware support includes: new xhci(4) driver for USB 3.0 host controllers; new umcs(4) driver for MosChip Semiconductor 78×0 USB multiport serial adapters; new skgpio(4) driver for Soekris net6501 GPIO and LEDs; new uslhcom(4) driver for Silicon Labs CP2110 USB HID based UART….” The latest release of the security oriented flavour of BSD includes many changes such as the removal of SSLv3 support from base utilities and more strict enforcement of write-exclusive-or-execute (W^X) in the kernel.