I've run into some strange issues with hex encoded passphrases.
Maybe it is an iwm driver issue, but on some connections if I had
any hex string passphrases in the hostname.if file, it would
absolutely fail to connect.
On 11/25/23 07:42, Stefan Sperling wrote:
On Sat, Nov 25, 2023 at 08:20:47AM
On 2023/11/25 16:00, Thomas Nemeth wrote:
> join mywifi wpakey 'B22c-2&0%snOy7!l+6vmpH#QT2BN1RPdeImAb0/
btw: it's hard to guess at the real complexity of your SSID, but it's
used as a salt for the WPA paasword, so if it isn't already, it's a good
idea to make this fairly complex too.
On Sat, Nov 25, 2023 at 08:20:47AM -0700, Theo de Raadt wrote:
> What you are asking for is too difficult to do.
>
> netstart is a shell script. shell script arguments are not 8 bit clean,
> because the the sh language has many meta & escape characters.
>
> Your configuration exceeds what can
Le samedi 25 novembre 2023, 16:20:47 CET Theo de Raadt a écrit :
> What you are asking for is too difficult to do.
>
> netstart is a shell script. shell script arguments are not 8 bit clean,
> because the the sh language has many meta & escape characters.
>
> Your configuration exceeds what can
What you are asking for is too difficult to do.
netstart is a shell script. shell script arguments are not 8 bit clean,
because the the sh language has many meta & escape characters.
Your configuration exceeds what can be done.
>Synopsis: /etc/netstart fails to parse complex wpa2 passphrases
>Category: system
>Environment:
System : OpenBSD 7.4
Details : OpenBSD 7.4 (GENERIC.MP) #2273: Tue Oct 10 09:45:06
MDT 2023
dera...@arm64.openbsd.org:/usr/src
