Language Selection

English French German Italian Portuguese Spanish

BSD

FreeBSD 11.0 Officially Released

Filed under
BSD

Following the recent delays, FreeBSD 11.0-RELEASE is now officially available.

FreeBSD 11.0-RELEASE was announced this morning as the latest major update to this BSD operating system.

Among the many changes for FreeBSD 11 is 802.11n WiFi support, better WiFi/wireless support in general, native graphics support for the Bhyve hypervisor, official support for ARM 64-bit / AArch64, vastly improved/updated DRM graphics driver code, and much more.

FreeBSD 11.0 can be downloaded from the FreeBSD.org announcement.

Read more

First pfSense 2.3.2 Update Adds OpenSSL Security Fixes to the BSD-Based Firewall

Filed under
OSS
Security
BSD

Today, October 6, 2016, Jim Thompson from the pfSense project has had the great pleasure of announcing the release and immediate availability of the pfSense 2.3.2-p1 maintenance update to the open source BSD-based firewall distro.

Read more

OpenBSD 6.0 - an exercise in precision

Filed under
Reviews
BSD

The OpenBSD project is well known for its strong focus on security and for its precise documentation. The OpenBSD operating system generally gives preference to security and properly behaving software over features. OpenBSD is lightweight, sparse and relatively locked down by default. This makes the platform particularly popular among administrators who need a firewall or other minimal and stable platform.

OpenBSD 6.0 introduces many small changes and a handful of important ones. Looking through the release notes we find support for the VAX platform has been dropped. There have been several security updates to the OpenSSH secure shell service. Perhaps one of the more interesting security features in the operating system is strict enforcement of W^X: "W^X is now strictly enforced by default; a program can only violate it if the executable is marked with PT_OPENBSD_WXNEEDED and is located on a file system mounted with the wxallowed mount option. Because there are still too many ports which violate W^X, the installer mounts the /usr/local file system with wxallowed. This allows the base system to be more secure as long as /usr/local is a separate file system. If you use no W^X violating programs, consider manually revoking that option."

I decided to play with the 64-bit x86 build of OpenBSD which is 226MB in size. Booting from this ISO presents us with a text console where we are asked if we would like to install OpenBSD, upgrade an existing copy of the operating system or perform an auto-install. I chose to perform a normal installation.

Read more

Also: OpenBSD and NetBSD machines at Open Source Conference 2016 Nagaoka

FreeBSD 11.0 Comes Up Short In Ubuntu 16.04 vs. macOS Sierra Benchmarks

Filed under
Graphics/Benchmarks
BSD
Ubuntu

Yesterday I published some macOS 10.2 vs. Ubuntu 16.04 LTS benchmarks from a Mac Mini and MacBook Air systems. For those curious if BSDs can outperform macOS Sierra on Apple hardware, I tested the MacBook Air with FreeBSD 11.0 compared to the Linux and macOS results on that Core i5 system. Here are those results.

Read more

FreeBSD Delaaays and OpenBSD Founder Theo de Raadt Upset

Filed under
BSD
  • FreeBSD 11.0-RELEASE Needs To Be Respun Due To Security Issues

    The delayed FreeBSD 11.0 release just suffered another last-minute set-back. While "FreeBSD 11.0-RELEASE images" were distributed to FTP mirrors and the official announcement expected today, these images need to be re-spun to contain some security fixes and thus pushing back the official release.

    Glen Barber noted today on the mailing list, "Although the FreeBSD 11.0-RELEASE has not yet been officially announced, many have found images on the Project FTP mirrors. However, please be aware the final 11.0-RELEASE will be rebuilt and republished on the Project mirrors as a result of a few last-minute security fixes we feel are imperative to include in the final release."

  • FreeBSD 11.0 Operating System Lands October 5 Due to Last-Minute Security Issues

    A few minutes ago, Glen Barber informed the FreeBSD community that they should not hurry and install the ISO images of the FreeBSD 11.0 operating system made available a few days ago on the official FTP mirrors.

    These images aren't safe to use and contain various security vulnerabilities that need to be fixed before the FreeBSD Project will officially unveil the final release of the FreeBSD 11.0 operating system in the coming days. According to the release schedule, FreeBSD 11.0 should hit the streets later today, September 29, 2016.

    However, until then the FreeBSD development team is hard at work patching those nasty security issues and rebuilding the final ISO images, which will be made available on the respective FTP mirrors later today as FreeBSD 11.0-RELEASE-p1. If you're already running FreeBSD 11.0-RELEASE, you will soon be provided with instructions to safely update your system

  • OpenBSD Founder Calling For LLVM To Face A Cataclysm Over Its Re-Licensing

    For over one year there's been talk of LLVM pursuing a mass relicensing from its University of Illinois/NCSA Open Source License, which is similar to the three-clause BSD license, to the Apache 2.0 license with explicit mention of GPLv2 compatibility. As mentioned in that aforelinked article, this re-licensing is moving ahead.

FreeBSD 11.0 Final Release ISO Images Available For Download

Filed under
BSD

The Final Release of FreeBSD 11.0 is scheduled for Wednesday, September 28, 2016. However, the release builds have started to appear on FreeBSD’s FTP mirrors and you can download the final ISO right now.

Read more

FreeBSD 11.0 Gets One Last Release Candidate Build, Final Version Is Coming Soon

Filed under
BSD

FreeBSD's Glen Barber announced the other day that the third, and hopefully the last Released Candidate (RC) build of the upcoming FreeBSD 11.0 operating system is now available for public testing.

Read more

FreeBSD 11.0 RC3

Filed under
BSD

BSD Leftovers

Filed under
BSD

Trying Out Eight BSDs On A Modern PC: Some Are Smooth, Others Troublesome

Filed under
BSD

Following the seven-way Linux distribution benchmark comparison published earlier this week, on the same system I set out to test a variety of BSD distributions on the same system and ultimately benchmark their out-of-the-box performance too. Those performance benchmark results will be published later this week while today were a few remarks I wanted to share when trying out TrueOS, DragonFlyBSD, GhostBSD, FreeBSD, OpenBSD, NetBSD, MidnightBSD, and PacBSD (Arch BSD) on this modern Intel Xeon system.

All of my testing was done on an Intel Xeon E5-2509 v4 Broadwell-EP system with MSI X99A WORKSTATION motherboard, NVIDIA GeForce GTX TITAN X, 16GB of DDR4 memory, and an OCZ TRION 150 120GB SATA 3.0 SSD. With the seven Linux distributions tested in recent days they all worked fine on the system: Ubuntu, Clear Linux, Scientific Linux, openSUSE Tumbleweed, Fedora, Antergos, and Sabayon Linux.

Below are my various brief remarks when testing the different BSDs on this Intel Xeon system. These are my thoughts with admittedly being a Linux enthusiast while just touching BSD, Solaris, and others only on a semi-frequent basis. I am by no means a diehard "Linux fan boy" and have no fundamental objections to BSD, I simply prefer the operating system that best fits my needs and for benchmarking where I can get my tests done in a reliable, reproducible, and timely manner. I at least prefer my operating systems have a clean and quick install process with sane defaults; working generally ~100 hour weeks, I don't have time in 2016 if an OS cannot easily install and boot properly on a modern PC. I enjoy testing out the various BSDs and have no strong bias to any of them. This is the largest BSD testing comparison I've done in the past 12 years on Phoronix at the same time and on the same hardware.

Read more

Syndicate content

More in Tux Machines

Leftovers: BSD

Security Leftovers

  • Stop using SHA1 encryption: It’s now completely unsafe, Google proves
    Security researchers have achieved the first real-world collision attack against the SHA-1 hash function, producing two different PDF files with the same SHA-1 signature. This shows that the algorithm's use for security-sensitive functions should be discontinued as soon as possible. SHA-1 (Secure Hash Algorithm 1) dates back to 1995 and has been known to be vulnerable to theoretical attacks since 2005. The U.S. National Institute of Standards and Technology has banned the use of SHA-1 by U.S. federal agencies since 2010, and digital certificate authorities have not been allowed to issue SHA-1-signed certificates since Jan. 1, 2016, although some exemptions have been made. However, despite these efforts to phase out the use of SHA-1 in some areas, the algorithm is still fairly widely used to validate credit card transactions, electronic documents, email PGP/GPG signatures, open-source software repositories, backups and software updates.
  • on pgp
    First and foremost I have to pay respect to PGP, it was an important weapon in the first cryptowar. It has helped many whistleblowers and dissidents. It is software with quite interesting history, if all the cryptograms could tell... PGP is also deeply misunderstood, it is a highly successful political tool. It was essential in getting crypto out to the people. In my view PGP is not dead, it's just old and misunderstood and needs to be retired in honor. However the world has changed from the internet happy times of the '90s, from a passive adversary to many active ones - with cheap commercially available malware as turn-key-solutions, intrusive apps, malware, NSLs, gag orders, etc.
  • Cloudflare’s Cloudbleed is the worst privacy leak in recent Internet history
    Cloudflare revealed today that, for months, all of its protected websites were potentially leaking private information across the Internet. Specifically, Cloudflare’s reverse proxies were dumping uninitialized memory; that is to say, bleeding private data. The issue, termed Cloudbleed by some (but not its discoverer Tavis Ormandy of Google Project Zero), is the greatest privacy leak of 2017 and the year has just started. For months, since 2016-09-22 by their own admission, CloudFlare has been leaking private information through Cloudbleed. Basically, random data from random sites (again, it’s worth mentioning that every site that used CloudFlare in the last half year should be considered to having fallen victim to this) would be randomly distributed across the open Internet, and then indefinitely cached along the way.
  • Serious Cloudflare bug exposed a potpourri of secret customer data
    Cloudflare, a service that helps optimize the security and performance of more than 5.5 million websites, warned customers today that a recently fixed software bug exposed a range of sensitive information that could have included passwords and cookies and tokens used to authenticate users. A combination of factors made the bug particularly severe. First, the leakage may have been active since September 22, nearly five months before it was discovered, although the greatest period of impact was from February 13 and February 18. Second, some of the highly sensitive data that was leaked was cached by Google and other search engines. The result was that for the entire time the bug was active, hackers had the ability to access the data in real-time by making Web requests to affected websites and to access some of the leaked data later by crafting queries on search engines. "The bug was serious because the leaked memory could contain private information and because it had been cached by search engines," Cloudflare CTO John Graham-Cumming wrote in a blog post published Thursday. "We are disclosing this problem now as we are satisfied that search engine caches have now been cleared of sensitive information. We have also not discovered any evidence of malicious exploits of the bug or other reports of its existence."

Security Leftovers

  • Change all the passwords (again)
    Looks like it is time to change all the passwords again. There’s a tiny little flaw in a CDN used … everywhere, it seems.
  • Today's leading causes of DDoS attacks [Ed: The so-called 'Internet of things' (crappy devices with identical passwords) is a mess; programmers to blame, not Linux]
    Of the most recent mega 100Gbps attacks in the last quarter, most of them were directly attributed to the Mirai botnet. The Mirai botnet works by exploiting the weak security on many Internet of Things (IoT) devices. The program finds its victims by constantly scanning the internet for IoT devices, which use factory default or hard-coded usernames and passwords.
  • How to Set Up An SSL Certificate on Your Website [via "Steps To Secure Your Website With An SSL Certificate"]
  • SHA-1 is dead, long live SHA-1!
    Unless you’ve been living under a rock, you heard that some researchers managed to create a SHA-1 collision. The short story as to why this matters is the whole purpose of a hashing algorithm is to make it impossible to generate collisions on purpose. Unfortunately though impossible things are usually also impossible so in reality we just make sure it’s really really hard to generate a collision. Thanks to Moore’s Law, hard things don’t stay hard forever. This is why MD5 had to go live on a farm out in the country, and we’re not allowed to see it anymore … because it’s having too much fun. SHA-1 will get to join it soon.
  • SHA1 collision via ASCII art
    Happy SHA1 collision day everybody! If you extract the differences between the good.pdf and bad.pdf attached to the paper, you'll find it all comes down to a small ~128 byte chunk of random-looking binary data that varies between the files.
  • PayThink Knowledge is power in fighting new Android attack bot
    Android users and apps have become a major part of payments and financial services, carrying an increased risk for web crime. It is estimated that there are 107.7 million Android Smartphone users in the U.S. who have downloaded more than 65 million apps from the Google App Store, and each one of them represents a smorgasbord of opportunity for hackers to steal user credentials and other information.
  • Red Hat: 'use after free' vulnerability found in Linux kernel's DCCP protocol IPV6 implementation
    Red Hat Product Security has published details of an "important" security vulnerability in the Linux kernel. The IPv6 implementation of the DCCP protocol means that it is possible for a local, unprivileged user to alter kernel memory and escalate their privileges. Known as the "use-after-free" flaw, CVE-2017-6074 affects a number of Red Hat products including Red Hat Enterprise Linux 6, Red Hat Enterprise Linux 7 and Red Hat Openshift Online v2. Mitigating factors include the requirement for a potential attacker to have access to a local account on a machine, and for IPV6 to be enabled, but it is still something that will be of concern to Linux users. Describing the vulnerability, Red Hat says: "This flaw allows an attacker with an account on the local system to potentially elevate privileges. This class of flaw is commonly referred to as UAF (Use After Free.) Flaws of this nature are generally exploited by exercising a code path that accesses memory via a pointer that no longer references an in use allocation due to an earlier free() operation. In this specific issue, the flaw exists in the DCCP networking code and can be reached by a malicious actor with sufficient access to initiate a DCCP network connection on any local interface. Successful exploitation may result in crashing of the host kernel, potential execution of code in the context of the host kernel or other escalation of privilege by modifying kernel memory structures."

Android Leftovers