151–160 of 163 posts
Earlier quoted context omitted.
My guess is this part: The iwn(4) driver was added, providing support for the Intel® Centrino™ Wireless-N 105 and 135 chipsets. [r266770] from: https://www.freebsd.org/releases/11.0R/relnotes.html#drivers...
That driver was on OpenBSD for a long time. I put FreeBSD on a machine a year or so ago and really missed that driver. Maybe now I can get rid of the USB dongle I've been using instead.
Earlier quoted context omitted.
HardenedBSD is one of the bigger jokes in the BSD community. If you really care about the things it claims to do, I highly recommend using OpenBSD because it actually has competent and sustainable development.
Are you saying that the measures listed here http://hardenedbsd.org/content/easy-feature-comparison do not work properly?
Earlier quoted context omitted.
This is still geli+zfs, and not native zfs encryption that was recently presented in OpenZFS Developer Summit [0]. [0] https://www.youtube.com/watch?v=frnLiXclAMo
Correct, it is full disk encryption instead of dataset encryption. But on the other hand, if you install 11.0 from installer and chose Auto(ZFS) with EncryptedZFS and MBR(GPT) then you will get a GeliBoot installation. There is no boot pool anymore, instead the early boot stages decrypt the root zpool to load the rest of the boatloader, which then decrypts the pool to load the kernel. With bootloader-selectable boot…
Earlier quoted context omitted.
I use CURRENT on a Thinkpad X230. It works ok. Main gotchas: * No SSL CA certificates out of the box. FreeBSD security team has taken the curious posture of claiming that shipping no CAs is better than just shipping e.g. Mozilla's CA bundle.[0] * rc.d is like Linux init from 5 years ago. Dynamic network configuration is not handled well. * Intel GPU driver support for anything above Haswell is still waiting to be mer…
> No Xorg or session management out of the box. TrueOS Desktop is your friend. PC-BSD, now called TrueOS, has for years now been the place to go if one cannot hack getting X up and running onesself, as one has to do with FreeBSD. PC-BSD/TrueOS Desktop has X and GUI login pre-configured out of the box. > rc.d is like Linux init from 5 years ago. Linux init from 5 years ago was upstart in quite a few places. (Debian is…
Earlier quoted context omitted.
That driver was on OpenBSD for a long time. I put FreeBSD on a machine a year or so ago and really missed that driver. Maybe now I can get rid of the USB dongle I've been using instead.
iwn(4) has been present for a long time. I suspect you mean iwm(4)?
Earlier quoted context omitted.
Are you saying that the measures listed here http://hardenedbsd.org/content/easy-feature-comparison do not work properly?
I'm not GP, but yes. They do not work properly and likely introduce additional vulnerabilities.
FreeBSD is not 'just another OS out there' but an important piece of technology powering lots of things we often use: from Sony's PlayStation and WhatsApp, through Netflix and Yahoo, to Juniper and PFSense networking gear and EMC storage and FreeNAS appliance - and many, many more! So, have you donated yet? We need FreeBSD and FreeBSD needs your support! https://www.freebsdfoundation.org/donate/
What really makes me sad is that the BSD license allows corporate leeches like Sony to create incredibly successful and valuable products like the PS4 without ever having to give back to the project that produced the software they rely on. It's obvious that Sony picked FreeBSD over Linux because they don't have to publish their additions to FreeBSD, and can continue to integrate new and improved code from upstream wi…
When I do vagrant up, I see the following error:
No base MAC address was specified. This is required for the NAT networking to work properly (and hence port forwarding, SSH, etc.). Specifying this MAC address is typically up to the box and box maintainer. Please contact the relevant person to solve this issue.
If I do vagrant up again, it seems to be working, but then I see a lot of:
default: Warning: Remote connection disconnect. Retrying...
and it eventually times out.
Any ideas on how to solve this issue?
Thanks!
Earlier quoted context omitted.
I'm not GP, but yes. They do not work properly and likely introduce additional vulnerabilities.
Do you have any evidence for this? I've heard rumors here on HN and else where that HardenedBSD's code quality is lacking and that they didn't incorporate all the fixes and suggestions from the FreeBSD community during the various code reviews. But none of that is definitive, do you have any proof or evidence for this statement, "They do not work properly and likely introduce additional vulnerabilities."
https://github.com/HardenedBSD/secadm/commit/3dd7584b70804cf...
If this check did anything, it appears susceptible to time-of-check, time-of-use attack.
See also https://reviews.freebsd.org/D473 , where Shawn pretty cleary does not incorporate feedback from the FreeBSD community.
Earlier quoted context omitted.
Do you have any evidence for this? I've heard rumors here on HN and else where that HardenedBSD's code quality is lacking and that they didn't incorporate all the fixes and suggestions from the FreeBSD community during the various code reviews. But none of that is definitive, do you have any proof or evidence for this statement, "They do not work properly and likely introduce additional vulnerabilities."
Here's an example of poor code quality: https://github.com/HardenedBSD/secadm/commit/3dd7584b70804cf... If this check did anything, it appears susceptible to time-of-check, time-of-use attack. See also https://reviews.freebsd.org/D473 , where Shawn pretty cleary does not incorporate feedback from the FreeBSD community.