Should I use BSD? reddit / BSD ---------------------------------------------------------------------- nextnextbaby · 2018-01-13 21:17 I am primarily a linux user but was thinking of switching to BSD (probably openbsd) because of its well known stability and security. I use a pretty basic range of programs like web browsers, torrent clients, audio playback, video playback, ftp clients, light video editing. Would I have trouble switching to BSD? Do I have justification to for security and stability reasons? ---------------------------------------------------------------------- PhiloPolyMath · 2018-01-13 21:28 I would say yes, give it a shot. Check my comment history and you will see me answering this question a few times, usually with links for people setting up an OpenBSD workstation/desktop (I’m on mobile now or I would link it myself). I’ve used linux in some capacity since about 2006. I’ve used Ubuntu, Mint, Fedora, Arch, Debian, Slackware, and now Void for some gaming and Nvidia support. But I mostly boot into OpenBSD on my desktop, laptop, and a couple VPS. I find it to be stable and clean with sane security defaults. I would so as I did. If you can go buy a cheap ssd and throw it in a system to give it a shot on some bare metal. Tried it on my x220 first and then I started in other places. Check the man pages, faq, and maybe the links I mentioned first. If you have a question try reddit or the irc channels. ---------------------------------------------------------------------- wareotie · 2018-01-13 21:29 It's quite hard to find something that, coming from Linux, does not work on any BSD. You can, for example, run full GNOME or KDE desktops. If you want to switch, do not hesitate :) ---------------------------------------------------------------------- blackhaz2 · 2018-01-13 22:41 Chromecast isn't working if that's your thing. Only with scripts. Couldn't get Chromiun to find the device. Check software availability in ports first. ---------------------------------------------------------------------- VampyrBit · 2018-01-14 00:07 For starting I would recommend TrueOS, you can check a FreeBSD base quick and with good defaults. Then if you want to explore other BSD's I really like OpenBSD defaults and ideology, and NetBSD organization and scope :) ---------------------------------------------------------------------- daemonpenguin · 2018-01-14 01:40 You will probably be fine, application-wise. And the BSDs are great, I definitely recommend giving them a try. I really like their conservative development style, documentation and file system organization. You might want to start with GhostBSD. It's a desktop-oriented flavour of FreeBSD and probably the easiest of the BSDs to get started with. It's a lot like setting up a desktop Linux system. Someone else suggested trying TrueOS, but it's a development project geared toward devs who want to be on the cutting edge. GhostBSD is desktop user oriented. From a security and stability standpoint, there probably isn't an argument to switch to BSD. Don't get me wrong, the BSDs are generally secure and stable, but not really any different from a stable, well maintained Linux distro such as CentOS, Debian or Ubuntu LTS. You mentioned using OpenBSD for the security. And OpenBSD is secure by default, but only the base OS is secure. The applications (ports) you run, for example desktop environments, torrent clients, web browsers, etc, have no extra security. For a desktop system you're not really any more (or less) secure running OpenBSD than you are FreeBSD or a well maintained Linux distro. OpenBSD's well-earned security reputation is for the base OS, not the applications which run on it. This might all sound like I'm discouraging you from switching. I'm not, I really like the BSDs and run FreeBSD myself. I want to dispel the idea that running, say Firefox, on OpenBSD is more secure than running Firefox on something like Debian. ---------------------------------------------------------------------- Nanosleep · 2018-01-14 01:46 I would say, as long as you think you can survive on f/oss software alone, you're probably fine using OpenBSD. The biggest gotcha that's still present today when it comes to desktop usage is Flash and browser DRM. My youtube movie purchases refuse to play, and I'd imagine the same is true for netflix. Another thing that stung me a bit that I wasn't expecting was their FUSE API mimics a much older version of Linux's FUSE API, so modern language support for FUSE is out, which means stuff like upspin won't work. Another thing worth mentioning, and maybe the only real thing holding me back from switching to OpenBSD on my workstation is virtualization support. vmm/vmd seems to be coming along, but I think it'll take another couple years at least before it's on par with bhyve, let alone KVM/Xen. Regarding Stability: I've personally seen a lot more kernel panics on openbsd (~10+ in 5-6 years) than I have on linux (~5? in 10+ years). Granted, it's always when doing weird stuff like restarting X with different Driver/DDX options... or resuming from a suspend without my wireless dongle (or some other device that was there when it suspended). I've never seen a kernel panic on a server, just in weird desktop situations.. That being said, it feels less Q/Aed in those edge cases than Linux does. Regarding Security: The (mis)handling of meltdown and spectre proves that when a big hardware vuln is embargoed, the little guys get completely screwed. Weigh the potential of getting caught with your pants down for an extended period of time against OpenBSD's track record of exploitable remote vulnerabilities and make your own decision about security. ---------------------------------------------------------------------- jaypatelani · 2018-01-14 05:39 Yesss ---------------------------------------------------------------------- MaskedCoward · 2018-01-14 06:00 I'd recommend FreeBSD (or GhostBSD if you're interested in easier initial setup) for desktop/laptop usage. Make sure your hardware is supported if you're using a laptop. A Thinkpad that's a couple of years old is usually a good bet. I have full support for suspend/resume, touchpad features, all that. ---------------------------------------------------------------------- ProfessorSexyTime · 2018-01-14 06:09 > From a security and stability standpoint, there probably isn't an argument to switch to BSD. Don't get me wrong, the BSDs are generally secure and stable, but not really any different from a stable, well maintained Linux distro such as CentOS, Debian or Ubuntu LTS. > You mentioned using OpenBSD for the security. And OpenBSD is secure by default, but only the base OS is secure. These points times 100%. Don't get me wrong; I hope to dual boot GhostBSD and Void Linux some day. But I think people miss the point that using Unix systems like BSD and Linux *set you up to be more secure right out of the gate*. But you can still be a moron and install a bunch of shit you don't know what it does or how it works or if it's secure. I like BSD and Linux both; I'm using Void right now and it's fantastic, and GhostBSD on Virtualbox is pretty awesome too. I think the contingency between BSD and Linux is stupid; this isn't Windows vs Mac. I can agree with all you BSD folk that systemd is awful, and there are some aspects of GNU being so integrated with Linux that are kind of annoying and counter what GNU is about. One thing I don't get about the BSD community is the statements about BSD's codebase being "more correct". If anyone could actually provide examples I might understand, but I've yet to see any tangible examples. It's mostly just parroting stuff people have read in blogs. Anyway if you're using Void/a non-systemd Linux like me and minimizing your use of GNU stuff (as much as you can), Linux is still good and enjoyable to use. BSD (for me) is no more or less enjoyable to use. But to say one is "more secure" than the other is a little misguided. It's not inaccurate, but it's not totally absolute. Both are great and both have different aspects and goals, but ultimately when it comes to desktop use it's about preference and what you want/need. ---------------------------------------------------------------------- slainthejabberwock · 2018-01-14 07:02 > The applications (ports) you run, for example desktop environments, torrent clients, web browsers, etc, have no extra security. Stack protector, free guard, libc randomisation, W\^X enforcement, heap canaries, and so on all apply to software from ports. Not to mention ports that have been pledged. > I want to dispel the idea that running, say Firefox, on OpenBSD is more secure than running Firefox on something like Debian. Firefox on OpenBSD will blow up if it violates W\^X, on Debian it will continue running. If Firefox does a use-after-free (which is the cause of a lot of exploitable Firefox vulnerabilities), if the allocation was bigger than one page, it will die on OpenBSD due to free unmap, and will always die if freecheck is enabled, while on Debian it will continue on and be exploitable. Your whole post makes me question if you understand how typical vulnerabilities work and how OpenBSD's mitigations make them harder/impossible to exploit. ---------------------------------------------------------------------- bit_of_hope · 2018-01-14 08:36 Do you want to use BSD? Yes? Go for it. Who'd you have to justify it to? Your mom? ---------------------------------------------------------------------- geheimnisse · 2018-01-14 08:40 Depending on your needs, look at FreeBSD as well. Don't get me wrong, I used OpenBSD as my primary OS for a long time and still love it today, at least on servers. But, FreeBSD performs better for a home PC, and I am able to get about 2 more hours out of my laptop battery over OpenBSD. As for pieces of software, check the ports collection of each to see if what you use is there: http://freshports.org for FreeBSD ports http://ports.su for OpenBSD ports And no, you would not have trouble switching to BSD. I used Linux from 2001 to 2014. Then switched to BSD with no problem. And yeah, security and stability-wise, you won't look back if you make the switch. ---------------------------------------------------------------------- UninsuredGibran · 2018-01-14 10:12 Excellent point. Running Chromium should be even more secure than Firefox because it was easier to pledge() more tightly (due to Google designing it with privilege separation from the beginning). DragonFly has some interesting notes on browser security: https://www.dragonflybsd.org/docs/docs/handbook/RunSecureBrowser/ ---------------------------------------------------------------------- [deleted] · 2018-01-14 14:59 I have used FreeBSD for about a year. The best parts were that the documentation was available offline and useful, and the system was truly integrated. The only other software system I have that experience in is Emacs. In many Linux-based distros it's hard to find an authoritative source of information for all the base system, and the whole fragmentation of the distro ecosystem can create lots of confusion. What made me leave FreeBSD was, I couldn't get suspend/resume working. I tried OpenBSD on various hardware, but especially WiFi drivers seemed to be rather limited (in comparison to say Linux or FreeBSD), so you should take that into consideration. If you're not programming at all (even shell scripts for your use, etc.), it might not be worth the switch, or to put it better, both systems might end up being about equivalent, if most of what you'll interact with will be the desktop environment and your application software. But if you're doing multimedia editing, AFAIK the Linux sphere has better support that sort of workflow. WRT security and stability, well I'd guess that most users' security problems stem from *how* they use their operating systems, not which one of them they use. WRT stability, again, rather than the OS stability, the stability of the apps you will use is what should interest you, and that does not depend (for the most part) on the operating system. ---------------------------------------------------------------------- Xerxero · 2018-01-14 16:39 Even on a desktop suspend and resume is flaky at best on FreeBSD. ---------------------------------------------------------------------- [deleted] · 2018-01-14 17:08 Many times people have told me around the Interwebz that they've gotten it working, but I've never managed to... I wonder if sth. like GhostBSD or TrueOS has it working. ---------------------------------------------------------------------- Xerxero · 2018-01-14 17:29 It worked better with an old amd card then with a 960 NVIDIA. But still find it very frustrating that this does not work. Next to sound this should work out of the box. ---------------------------------------------------------------------- [deleted] · 2018-01-14 18:22 I'm no security expert but I'd guess these are not the means the attacks on individuals employ most often. The most vulnerable stuff is data you transmit over the wire and data you voluntarily or involuntarily store in remote locations. OpenBSD on my laptop can't protect me from attacks on this data. It also can't protect me from phishing or social engineering. It's counterproductive to confuse the security a user needs and the security a server or a multi-user system needs. ---------------------------------------------------------------------- gumnos · 2018-01-14 18:49 On OpenBSD, ~~both Firefox and~~ Chromium (likewise Python & Ruby) need to be installed in a `wxallowed` mount-point because they do JIT that expects to do W\^X. $ find /usr/ports/www -name Makefil\* -print0 | xargs -0 grep USE_WXNEEDED /usr/ports/www/chromium/Makefile:USE_WXNEEDED= Yes /usr/ports/www/iridium/Makefile:USE_WXNEEDED= Yes /usr/ports/www/phantomjs/Makefile:USE_WXNEEDED = Yes /usr/ports/www/ruby-capybara-webkit/Makefile:USE_WXNEEDED = Yes /usr/ports/www/webkit/Makefile:USE_WXNEEDED = Yes /usr/ports/www/webkitgtk4/Makefile:USE_WXNEEDED = Yes *edit: Firefox no longer needs W\^X. Thanks, /u/slainthejabberwock for the update* ---------------------------------------------------------------------- gumnos · 2018-01-14 18:55 not to let this disparage any of the other OpenBSD protections, as all the other mitigations (stack protection, free guard, libc randomization, heap canaries, etc) all still apply. But W\^X has to be disabled for certain ports (change the `/usr/ports/www` to just `/usr/ports` in that previous `find` command to find all of them, not just the `www`-related ones) ---------------------------------------------------------------------- slainthejabberwock · 2018-01-14 19:17 Firefox's JIT was changed over a year ago to not map WX memory. Firefox isn't tagged WXNEEDED, hence it's not in your list. ---------------------------------------------------------------------- jeremiahs_bullfrog · 2018-01-14 19:18 Yup, and it's free in all senses of the word. ---------------------------------------------------------------------- gumnos · 2018-01-14 19:38 Somehow I'd missed that change coming through. Still seems to have issues on certain platforms such as macppc/powerpc but I'll have to update my OpenBSD config on i386/amd64. Thanks for the terrific news. ---------------------------------------------------------------------- slainthejabberwock · 2018-01-14 20:19 > I'd guess these are not the means the attacks on individuals employ most often Browser vulnerabilities aren't used as often as they used to be because they're rarer and more valuable than they used to be. Google/Mozilla/Microsoft/Apple have spent loads of time and money trying to prevent them. Which is why Chromium shipped with a multi- process architecture, why IE/Edge copied that and why Firefox is slowly moving there. Firefox is also having its rendering engine rewritten in a new language that was designed specifically to make it harder for use-after-frees and buffer/heap overflows to occur; the exact things OpenBSD already mitigates. They all did this because these vulnerabilities happen, because they get used and because RCE vulnerabilities in a browser are devastating. If you want an example, CVE-2016-9079 was a Firefox one that was actively exploited before it was patched, and would have been mitigated by OpenBSD. > The most vulnerable stuff is data you transmit over the wire and data you voluntarily or involuntarily store in remote locations. The most sensitive files are the ones no one is stupid enough to store on someone else's computer. Which is why the likes of CVE-2015-4495 -- another Firefox one which was actively used and delivered by ad networks to sites people visited regularly and trusted -- get used to steal them from the local machine. > OpenBSD on my laptop can't protect me from attacks on this data. It also can't protect me from phishing or social engineering. A guard dog at your home can't stop someone from robbing your bank. It also can't protect your car from being stolen while it's parked at work. Therefore, why have a guard dog, right? > It's counterproductive to confuse the security a user needs and the security a server or a multi-user system needs. What's counterproductive is security defeatism. X can't stop Y therefore there's no point in doing X. Defence in depth exists for a reason. If anything, ordinary, regular users need more protection from drive- by vulnerabilities than anyone. Browser vendors clearly agree, since they haven't spent all that time and effort hardening their software for fun. ---------------------------------------------------------------------- johnklos · 2018-01-14 21:01 A point worth making when it comes to OS comparisons is that generalizations aren't necessarily NOT true just because they're generalizations, but people often unknowingly or sometimes purposely twist them to make the generalizations seem untrue. For example, as /u/daemonpenguin and /u/ProfessorSexyTime point out, running software on either family of OSes isn't necessarily any more or less secure than the other because the security implications have 95% to do with the software itself, and then 99% to do with the user's actions. If a user is going to do dumb things, a user is going to do dumb things. But that's trying to compare families of OSes using the metrics outside of the OS programmers' control. When we ask the question differently, we should get more meaningful answers. Is BSD, generally speaking, more secure as an OS as GNU/Linux? Different people will have different answers, and here's mine. I hate systemd. GNU/Linux has gone from being a very capable Unix-like OS that generally worked well alongside of other Unix-like OSes to becoming a special snowflake that now has many components which are poorly understood, poorly documented, idiosyncratic, inconsistent, and outright counterintuitive. Some people make the mistake of thinking that their lack of understand about something has little to do with their evaluation of that something. I agree - there MIGHT be some people out there who understand systemd and can explain the philosophy in a way where the light bulb springs on and we all finally get it. But I have yet to find that. I've looked. I've asked. I've tried to engage systemd fans to learn. I assert, perhaps somewhat controversially, that this philosophy doesn't exist, and I invite the world to educate me. If it does exist, I want to learn it. When procedure and practice can be derived from concepts, you have a much better system than when you have to memorize exceptions and workarounds. Therefore, I think GNU/Linux is becoming more like Windows - we're supposed to just trust them, and we're not expected to understand what they're doing, else they'd explain, discuss and document their rationale with regards to changes in the system. Do a default install of a BSD, and do a default install of Debian or Ubuntu and count the number of daemons and services running and ask: Which has a larger attack surface? Which would be easier to examine and understand should we have a reason or desire to learn about the purpose and reasoning behind the running of each and every daemon and service? I feel more secure with BSD because normal humans can understand it. If normal humans can understand systemd, please point me to documentation :) ---------------------------------------------------------------------- [deleted] · 2018-01-14 21:03 > The most sensitive files are the ones no one is stupid enough to store on someone else's computer. That's an assumption not a fact. And a false assumption. First of all, personal data is quite sensitive, but it is stored on many remote computing systems, and is regularly retrieved by third parties (e.g. the Equifax incident, many other database leaks in the last months). I do concur to most your points, but still, none of these are arguments to make end-users move to OpenBSD for security reasons. They are valid for everybody, but the "security" they are looking for is not security at this level. And I want to underline that I'm not trying to suggest this a counterargument for OpenBSD (on the contrary, it's clearly a "pro" of it), but just that it's not that big of a plus when comparing it with systems that are not considerably *too insecure* from a casual computer user perspective. A better selling point of OpenBSD might be the sheer quality of the documentation it provides, the rather polished and minimal base system, a community of smart users, and the many high-quality tools such community has been able to create. Nobody moves to a rotting house because the quarter is safe, and they are not protected at all even if the house is a study castle, if they're sleeping outside and with doors and windows open, and the guard dog tied to a short leash around the backyard. ---------------------------------------------------------------------- daemonpenguin · 2018-01-14 22:46 I think you make good points about attack surface. One of the things I appreciate about the BSDs is the small nature and relatively few daemons being run. However, you seem to making the assumption that installing Linux means running systemd. But for many users that is not the case. Some Linux distros run OpenRC (like TrueOS), some still use Upstart, many still run SysV init. While most mainstream projects may have switched to systemd, it doesn't follow that running Linux means running systemd too. ---------------------------------------------------------------------- Hinulog · 2018-01-15 00:59 Broadly speaking, BSD & Linux were both Unix clones with Linux kernel having better device support. The gap in device support is narrowing. Several years ago a program of massive architectural change in Linux was initiated. Linux is rapidly becoming less Unix like and more Micro$oft like now. Chief amongst these changes is a purported init system replacement that is rapidly subsuming the entire OS. This purported init system known as 'systemd' has a lead developer at Red Hat who is arrogant & extremely cavalier in design implementation leading to *grave* security concerns for any system implementing his franken-init. Moreover, it is now, for all practical purposes, impossible to run Linux *without* systemd installed *even if* you choose to use a traditional or other init system. The feature creep & creation of more dependency upon systemd continues to accelerate. The systemd developer has frequently ignored concerns over poor design compromising security & has been caught on several occasions making silent changes. If all this sounds like a recipe for security Armageddon in Linux, you are not alone! In comparison BSD is run by adults who *gasp* document things clearly. For servers, I'd say it's high time to switch to a BSD. No question about it. OpenBSD is a *command line* BSD with great security posture. FreeBSD is also an excellent choice. For desktop, GhostBSD would be a good choice for a GUI BSD or many folks use command line OpenBSD alternatively. Device support in BSD, although improved is still an issue so investigate & see for yourself. Overall there are many paper cuts in desktop use of BSD but it doesn't stop many folks. YMMV. The other BSD's available I would classify as niche *or* experimental. Hope this helps. ---------------------------------------------------------------------- [deleted] · 2018-01-15 04:14 [deleted] ---------------------------------------------------------------------- johnklos · 2018-01-15 04:39 True - I did neglect to differentiate distros that haven't gone systemd. I do like that there are still some non-systemd choices :) ---------------------------------------------------------------------- UninsuredGibran · 2018-01-15 05:11 A few people came up with different rules, in different order. Which ones are you talking about? OpenBSD is probably the closest thing to UNIX nowadays. Linux not so much. It's been contaminated by GNUism which is a completely different ideology (coming from MIT and Lisp machines, where applications are really powerful but complex; think Emacs). ---------------------------------------------------------------------- UninsuredGibran · 2018-01-15 05:13 I don't want to troll but... [FreeBSD developers meeting](http://www.ee.pw.edu.pl/wp- content/uploads/2014/10/conference-32865.jpg) Don't be surprised that it doesn't work very well as a desktop system. It's a great server OS though. ---------------------------------------------------------------------- [deleted] · 2018-01-15 05:20 [deleted] ---------------------------------------------------------------------- VampyrBit · 2018-01-15 05:56 I'm a daily Linux user too, it's my main work and media machine, BSD's are getting there really quick, if you try TrueOS you can see it's almost like Linux daily use. But loving Linux as I love, and with their history and how it helps everyone start a better computer life with Open Souce, I still feel BSD's are more free for everyone, companies and users, from the system perspective and license. ---------------------------------------------------------------------- UninsuredGibran · 2018-01-15 12:58 1 and 2 is mostly about userland programs like grep, tail, etc. There is no huge difference between Linux and *BSD except that Linux generally comes with the GNU tools, which tend to have more of a kitchen sink approach with many options and extensions. But back in the days Unix purists already complained that BSD was adding too many extensions, so... ---------------------------------------------------------------------- piglit3 · 2018-01-15 13:32 splitting up things is often insane for release engineering. e.g. libc can immediately use new kernel features instead of checking every time, because you are not expected to update libc without updating kernel. and we can handle major bumps without needing to tuck them under the carpet and pretend they didn't happen. also, linux gets away with things by having orders of magnitude more people and money to throw at the problem. ---------------------------------------------------------------------- devnexen · 2018-01-15 13:47 Not much trouble eventhough the migration will be "smoother" with FreeBSD (and its siblings) than OpenBSD (I use both but prefer OpenBSD). The best is to try yourself though. ---------------------------------------------------------------------- nextnextbaby · 2018-01-15 18:16 UPDATE: the feedback from the bsd community has been overwhelmingly amazing. I've learned a lot about BSD this past week. After messing with some vm's I've decided to put TrueOS on hardware (my laptop for now). I plan to continue to learn more about bsd, freebsd seeming more ideal for me at the moment now that I've learned the differences. In the near future i may switch my server to bsd seeing as it looks to be able to host most of the applications I need it to. ---------------------------------------------------------------------- nextnextbaby · 2018-01-15 21:24 Aaaaaaaaand there's no touchpad or wifi support ---------------------------------------------------------------------- [deleted] · 2018-01-16 20:33 Last time I tried FreeBSD Firefox would segfault unless I put 'dbus_enable="YES"' in /etc/rc.conf. I needed to install devcpu-data from ports or packages to get the Intel microcode updates, and set a value in /boot/loader.conf to get sound working, and if I Ctrl-Alt- Fn'd out of an X session I wouldn't be able to get back into it... Granted, most of this was documented in the appropriate place, but it was a huge pain. All of these problems are fixable, but hardly worth the trouble for a desktop. The annoyances pile up. FreeBSD is almost exclusively a server BSD. OpenBSD users are more likely to dogfood their OS on the desktop, so OpenBSD just works with no problems. The downside is that OpenBSD doesn't have WINE or a Linux compatibility layer. ---------------------------------------------------------------------- geheimnisse · 2018-01-18 19:25 I found FreeBSD 11 about as easy to get set up as Arch Linux. Easier install process than Arch, but slightly more complicated post-install tweaking than Arch. > dbus_enable="YES" is no longer required. Sound works out of the box now. I can navigate to console then back to X without issue. FreeBSD has improved greatly on the desktop. I used FreeBSD 9 on the desktop, found it too much trouble, went back to OpenBSD, now FreeBSD has matured a bit more making it viable for the desktop. It also works flawlessly on my Thinkpad X240. The only thing I had to do really was install powerdxx and set up the flags and have i915kms and if_iwm get loaded in a kldlist entry in /etc/rc.conf rather than in /boot/loader.conf because of crashing. One plus over OpenBSD on the X240 is OpenBSD doesn't include iwm in the base install, so you have to hook up an ethernet cable and run *fw_update* before you can use wifi. Not necessary with FreeBSD, just kldload if_iwm after you have the appropriate entries to set up wifi in /etc/rc.conf. >X240 /etc/rc.conf >kldlist="i915kms if_iwm" >wlans_iwm0="wlan0" >ifconfig_wlan0="WPA DHCP" then the usual wpa_supplicant deal. ---------------------------------------------------------------------- geheimnisse · 2018-01-25 02:24 Void Linux still piques my interest these days - created by a former NetBSD guy. No systemd, etc. It uses runit for init. ---------------------------------------------------------------------- johnklos · 2018-01-25 04:15 Oooh! I'm going to check that out. Thanks :) ---------------------------------------------------------------------- geheimnisse · 2018-01-25 05:14 no problemo ese ---------------------------------------------------------------------- rigorousmortis · 2018-02-07 01:20 This comment is highly underrated