Introduce 'auto-join' to the [OpenBSD] wifi 802.11 stack
reddit / BSD

----------------------------------------------------------------------
jcunningham10 · 2018-07-12 21:50

OpenBSD doesn’t use WPA supplicant to do this?

----------------------------------------------------------------------
phessler · 2018-07-12 22:00

No, OpenBSD only uses wpa_supplicant to do the 802.1X supplicant
negotiation.  Everything else is in base.

----------------------------------------------------------------------
jcunningham10 · 2018-07-12 22:14

Just curious, but what are the motivations for doing a separate
implementation?

----------------------------------------------------------------------
techsnapp · 2018-07-13 02:08

Have you never met puffy before?

Have a look here: [https://www.openbsd.org/innovations.html](https://w
ww.openbsd.org/innovations.html)

Have you not heard of doas? openNTD? openSMTPD? openBGPD? iked2? tmux?

----------------------------------------------------------------------
jcunningham10 · 2018-07-13 02:19

I’m familiar with some of the OpenBSD projects that make it into
Linux, but don’t have much other insight. Is there a goal to avoid 3rd
party daemons?

----------------------------------------------------------------------
techsnapp · 2018-07-13 14:15

\>  Is there a goal to avoid 3rd party daemons?

Aside from being a user, I'm not associated with the project. I
imagine they would rather know the code well and simplify it for
better auditing and improvements, rather than forking a third party
app and hacking on it.

I think doas is a perfect example in this case. The maintainer of sudo
is an openbsd developer/committer and yet, the developer community of
openBSD wanted something simpler and with fewer configuration options.
Once doas was in base, sudo was out. Apache http was in base for many
years, but they became displeased with it and replaced it with their
own httpd server.

----------------------------------------------------------------------
ts574 · 2018-07-13 20:16

No, it’s more about avoiding large, complex daemons. Simpler programs
are easier to reason about, easier to work with, and easier to audit.