Language Selection

English French German Italian Portuguese Spanish

Personal Computing - BSD Style

Filed under
Reviews
BSD
-s

A milestone was reached on April 29 and I couldn't let it pass without a look. I'm speaking of the release of PC-BSD 1.0, their very first stable release. Almost a year ago Tuxmachines tested 0.6 of PC-BSD, considered a beta release, and was quite impressed then as I recall. I saw .7, .8, .9 and increments get released, but I just had to revisit the user-friendly bsd again on this wonderful occasion. How did PC-BSD stack up on this their "new era of stability and simplicity?"

It all starts with a boot of the cd. The first image is a boot screen giving several choices for booting the system with extras of Escape to bootloader prompt, boot FreeBSD with usb keyboard, or Reboot. I just went with the default and hit <enter>. Next, one sees a beautiful silent splash screen featuring a close-up of pretty yellow flowers. It states one could Press Any Key to view startup details, but escape seems to be the only one that worked for me - or perhaps it was a question of timing. In any case, eventually one is brought to another screen with choices. They are: Start graphical install, Reset X to default VESA driver, Change Resolution to 800x600, System Utilities, and Reboot.

        

Choosing to start the graphical install ...you guessed it, starts the graphical install. Here begins a great looking professional quality install process. It looks nice, but it is also really easy. It asks where to install and then begins. My choices were limited to the primary partitions on my disk, but I had two blank ones at the beginning of this newest harddrive in the Master position. I simply chose hda1 (in linux speak) and let it install. The actuall system install was quite fast, taking about 15 minutes and then one is asked for a root password, to setup a user, and where to install the bootloader. You can choose to skip installing a boot loader with PC-BSD, and I did. Instead, I took a lesson learned from FreeBSD and edited my everyday lilo.conf as follows:
other=/dev/hda1
table=/dev/hda
label=PC-BSD

        

When setting up an user account, you are given the opportunity to select auto-login and X start if desired. I did and upon boot I was taken straight to a 1024x768 KDE 3.5.2 desktop. Sound was auto detected and setup as I was greeted by the default kde login sound as well as a really beautiful wallpaper. The wallpaper is a landscape of a lush green valley with a field of those same pretty yellow flowers all in front of a majestic mountain range. Other than a slightly customized panel and menu, the rest seems your basic default KDE.

        

        

On the desktop are two icons other than Trash. One opens the PC-BSD wiki in the default browser, Konqueror. This is an online documentation site with links to some other handy tools such as an user forum. The other icon is even more exciting. Again it opens up a browser, but where it takes you is an online repository of software. From this varying list, one can download software, and easily install onto their system. Installing is as easy as clicking the file. It reminded me of my windows days actually. Click the pbi file downloaded, an installation wizard opens and installs the software. Some of the applications available are kmplayer, firefox, opera, OpenOffice, java, and a coupla kde themes. I tested several packages and all went really well.

        

There is also an update application. Although at this time, there were no updates, so testing was limited.

My final thoughts: I found PC-BSD to be even better than the last time. It's prettier, easier, and more complete. Installation was smooth, hardware detection was good and performance was great. The system was stable and all applications tested worked fine. The only probably I had was finding the Flash browser plugin in their repository. If you've been wanting to try a BSD clone, you couldn't go wrong with PC-BSD. Again this time as with the last, I'm very impressed with all the work that has obviously gone into this system to make it so easy for anyone to have a BSD. I believe they have met their goals and then some.

PC-BSD Homepage.

Download or Purchase PC-BSD.

PC-BSD Screenshots.

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