Eindhoven, the Netherlands
See my homepage at https://proycon.anaproy.nl for further details and contact info.
on ~mil/sxmo-tickets
On 2024-11-07 18:33, ~proycon wrote:
Thanks, sorry it took a while. This looks good to me. I sent the patch to the mailing list for a last round of scrutiny, hopefully we can merge it quickly then: https://lists.sr.ht/~mil/sxmo-devel/patches/55861
Thanks for your replay. there is one bug in this patch! when there exists a WEP secured wifi, it will not be able to connect. the correct and tested line to fix all the trouble is:
NAMES=$(echo "$SSID" | awk -F ' ' '{ $NF=""; print $0 }' | sed 's/[[:space:]]*$//' | sed 's/ WPA\w//g')
Comment by ~proycon on ~mil/sxmo-tickets
REPORTED
RESOLVED IMPLEMENTEDComment by ~proycon on ~mil/sxmo-tickets
Good find and sorry for the late reaction again. I suppose it would also work in a one liner right? Or is the down step crucial?
nmcli device wifi hotspot ifname wlan0 con-name "Hotspot $SSID" ssid "$SSID" channel "$channel" band bg password "$key" 802-11-wireless-security.pmf 1 wifi-sec.pmf disable
Did you happen to try that?
I guess we could make a SXMO_WIFI_PMF_DISABLE parameter to toggle this functionality. Disabling security measures by default might be a bit risky (and you say it does work for some devices), though I must admit I don't know at all what PMF does.
Comment by ~proycon on ~mil/sxmo-tickets
Thanks, sorry it took a while. This looks good to me. I sent the patch to the mailing list for a last round of scrutiny, hopefully we can merge it quickly then: https://lists.sr.ht/~mil/sxmo-devel/patches/55861
bug added by ~proycon on ~mil/sxmo-tickets
Comment by ~proycon on ~mil/sxmo-tickets
On Sat Oct 26, 2024 at 7:48 PM CEST, ~aren wrote:
Yes, that sounds quite feasible and a good idea. (I don't think the rc suffix is common in Alpine but we can just do a less advertised v1.17 and a final v1.18)
We basically do this already, there always seem to be a few bugs that turn up after making a release, which tend to get fixed in 1.X.1 or 1.X.2. So perhaps the thing to do is to make a 1.17 release sooner rather than later, and plan on a couple of point releases to clean up the loose ends?
Agreed, would be good to really something soonish once all the important parts we want in are in place (e.g. peanutbutter).
Comment by ~proycon on ~mil/sxmo-tickets
One more for the list:
- ensure lswt is added as a dependency for sxmo-utils
Comment by ~proycon on ~mil/sxmo-tickets
One more for the release todo-list:
- ensure latest svkbd is released (at suckless) and packaged (in aports)
Comment by ~proycon on ~mil/sxmo-tickets
On Sun Oct 27, 2024 at 7:33 AM CET, ~stacyharper wrote:
I'm also a bit against making wofi the default, without strong argument. Just they are different, with different pros and cons.
Yes, but for the out-of-the-box experience I think wofi now provides the most intuitive/comfortable experience. I guess we should just let more people try and weigh in on what they prefer as default.