What in that act says OpenWrt would be made illegal? If anything, OpenWrt would roll out automated security updates for a supported branched release to comply with these regulations.
Also, if you actually read it, there are exceptions for open source software!
WSL 2 runs a full Linux kernel under Hyper-V. There are some out-of-tree or staging drivers included in Microsoft's Linux kernel derivative and they publish their kernel sources at https://github.com/microsoft/WSL2-Linux-Kernel.
What makes this card powerful, lies in the way it changes how NFC behaves on your device when it's set as a default transit card:
Your device stops randomizing the UID on each tap;
Your device begins responding to all NFC readers as if they were express-transit enabled, just like on Android;
Also this card does not change its serial number and UID when moving to other devices, unlike most other ones.
I guess what I am saying is: it doesn’t explain the problem it is solving very well. It doesn’t say what the default behavior is for other cards set as transit cards do (I would expect it to work the same way-ish) and how transit providers are supposed to match people to tickets, etc. then why this particular card is special. It assumes you know.
That whole "The solution" section does explain this.
"what the default behavior is for other cards set as transit cards" statement is countered by the article "Your device stops randomizing the UID on each tap". Granted, I know this part because in the past Google Pay on Android would randomize the UID on each read and on Apple devices transferring cards between devices would reinitialize the UID but would keep some application-specific (like a Suica card identifier) static, thus making these virtual cards unsuitable for UID-based identification for access control.
"how transit providers are supposed to match people to tickets" is not relevant to the premise of "This repository describes general status on the topic and a possible solution to allow you to use your device as an access card in UID-based access systems." In general, these are stored fare cards so they do not store a ticket and instead store an available balance.
If you are using `wg-quick`, then you need `Table = off` to disable adding routes to the system route table automatically. After that, then you can add routes manually.
Maybe MediaTek has shipped some modified versions of OpenWRT using this "wappd" thing to their B2B customers (as part of the SDK perhaps?) and are now advertising those as vulnerable.
Yes, I'm assuming that's exactly why OpenWrt is mentioned but it's very misleading.
The OpenWrt folks generally have good enough taste not to ship any drivers or userspace junk from vendor SDKs, though they do have a fair-sized set of backport patches on top of the (somewhat elderly) mainline kernels they do ship.
I'm running up-to-date mainline on my routers, not OpenWrt kernels. The mt76 support in 6.11 (and previously in 6.9 and 6.10) is complete enough that I don't need to carry any patches at all over what's in Linus' tree.
I agree with all of your points here. I also noticed that the iOS notifications got an "upgrade" recently with photo previews and user avatar icons now being present in the notifications.
On the note of mobile, I do know plenty of people I talk to on Discord with Android devices dislike the native Android to React Native update which slowed down Discord to the point where people risk bans by modding the older native Android client to continue working with modern Android.
reply