OpenBSD 6.6 • Hacker News Board

Re: OpenBSD 6.6

#61

Post by chousuke » Thu, Oct 17, 2019, 7:14 PM UTC

sigjuice wrote: post #45

The OpenBSD developers are not too thrilled to hear about these sorts of issues, but looks like sysupgrade installed sets I didn't have before (x*66.tgz, game66.tgz).

It does that. You can hack the script to only install partial sets, but you're encouraged to install all the sets. I've seen at least one mention on the mailing list about merging the sets because the recommendation is to always install all of them anyway. They're just files on disk if you're not using them.

Re: OpenBSD 6.6

#62

Post by floatboth » Thu, Oct 17, 2019, 7:25 PM UTC

oil25 wrote: post #55

floatboth wrote: post #48

Earlier quoted context omitted.

I'm not sure why U2F would be "disabled for security". I guess it's just that nobody has implemented all the required things. For the USB tokens, you need userspace USB HID access and hotplug notifications. I did that in Firefox for FreeBSD :)

When I asked in IRC, I was told U2F was not implemented in browsers on OpenBSD because, "do you really want browsers to have full access to your USB stack?"

"full access to your USB stack" is not very meaningful (and honestly sounds like a WebUSB criticism, maybe someone thought U2F required WebUSB?!)

You only have access to the devices which you have permission to access. On FreeBSD, we have a devd config that sets the u2f group on U2F tokens.

Re: OpenBSD 6.6

#63

Post by floatboth » Thu, Oct 17, 2019, 7:27 PM UTC

brynet wrote: post #60

floatboth wrote: post #51

Earlier quoted context omitted.

How is Apache non-permissive? It deals with more things (like patents) and it's a bit complex, but it's not viral I'm pretty sure.

The last time it came up. https://news.ycombinator.com/item?id=21020024

Ah. Whatever. The common meaning of "non-permissive" is "copyleft", not "has patent clauses the OpenBSD project has weird concerns about".

Re: OpenBSD 6.6

#64

Post by sn » Thu, Oct 17, 2019, 7:41 PM UTC

prgmr.com has an updated netboot installer: https://prgmr.com/blog/2019/10/17/openbsd.html

Re: OpenBSD 6.6

#65

Post by dTal » Thu, Oct 17, 2019, 9:28 PM UTC

wahern wrote: post #38

messe wrote: post #27

Earlier quoted context omitted.

> Bluetooth [is] disabled in OpenBSD for security A clarification on that point: OpenBSD's bluetooth stack was unmaintained and removed due to code rot; it's not that bluetooth as a protocol is inherently insecure.

> it's not that bluetooth as a protocol is inherently insecure Bluetooth is a ridiculously complex protocol. Complexity is the enemy of security. There's no fixed threshold beyond which complexity makes something "insecure", and Wi-Fi and even USB aren't exactly simple (both have had their share of implementation exploits across operating systems), but AFAIU there's a strong sentiment that Bluetooth is far too comple…

Course, now we have Bluetooth: Wired Edition with USB-C layering many different optional protocols over the base transport. I understand the rationale, but I fear it means the days of "just works" USB may be coming to an end...

Re: OpenBSD 6.6

#66

Post by ectospheno » Thu, Oct 17, 2019, 10:45 PM UTC

sigjuice wrote: post #45

The OpenBSD developers are not too thrilled to hear about these sorts of issues, but looks like sysupgrade installed sets I didn't have before (x*66.tgz, game66.tgz).

I suppose you could just keep posting this until they follow through with their idea of having only one set to prevent people like you from complaining about this non issue. Or do you think being passive aggressive on hacker news is going to change their collective, long held stance on this issue?

Re: OpenBSD 6.6

#67

Post by sigjuice » Fri, Oct 18, 2019, 12:38 AM UTC

ectospheno wrote: post #66

sigjuice wrote: post #45

The OpenBSD developers are not too thrilled to hear about these sorts of issues, but looks like sysupgrade installed sets I didn't have before (x*66.tgz, game66.tgz).

I suppose you could just keep posting this until they follow through with their idea of having only one set to prevent people like you from complaining about this non issue. Or do you think being passive aggressive on hacker news is going to change their collective, long held stance on this issue?

No, what will happen is that sooner rather than later “people like you” will kill my casual interest in this stuff with personal attacks.

Re: OpenBSD 6.6

#68

Post by pnako » Fri, Oct 18, 2019, 1:09 AM UTC

sigjuice wrote: post #45

The OpenBSD developers are not too thrilled to hear about these sorts of issues, but looks like sysupgrade installed sets I didn't have before (x*66.tgz, game66.tgz).

OpenBSD developers have not really made it official but basically you're supposed to install them all. Theo has hinted at merging them before.

syspatch(8) also assumed them to be installed IIRC.

Re: OpenBSD 6.6

#69

Post by efiecho » Fri, Oct 18, 2019, 1:19 AM UTC

Can't wait to try if this release will improve wireless performance when configured as an AP, until now I have never been able to get speeds above 10 Mbps with OpenBSD.

Re: OpenBSD 6.6

#70

Post by snvzz » Fri, Oct 18, 2019, 3:34 AM UTC

asveikau wrote: post #3

I read about the "sysupgrade" tool and concluded that the upgrade to 6.7 in another 6 months will be awfully seamless... But I see from this that they backported the tool as a syspatch for 6.5! So from 6.5 we will be able to do syspatch && sysupgrade to get to 6.6. Sounds nice.

>So from 6.5 we will be able to do syspatch && sysupgrade to get to 6.6. Sounds nice.

Do note the steps before starting and the config file changes in the release notes need to be run through manually, before sysupgrade.

And after the new version boots, pkg_add -u.