bri3d

28 ms·

481.
by bri3d 1y ago
Also take a look at 74/61/EEC. Some form of “immobilizer” has been required in Europe since 1998, and between actual ECE/UN directives and insurance partnerships, the standard increases every few years.
482.
by bri3d 1y ago
Yes, remote start breaks the model… which is why drive off release and remote start are separate systems. On modern European cars with automatic transmissions, the TCU will not release Park until the immobilizer (short range, challenge resp
483.
by bri3d 1y ago
Hitag2, while broken, is worlds better than rolling code. All modern European cars that I’m aware of now use AES.
484.
by bri3d 1y ago
UN/ECE 116
485.
by bri3d 1y ago
As far as I know no vehicles use this kind of rolling code algorithm for push button start, only key fob functions. Certainly not in Europe (due to immobilizer regulations) but I don’t believe anywhere else either. Generally, long range key
486.
by bri3d 1y ago
They definitely appear to use beamforming internally. It appears that the satellite uses knowledge of receiver location (or at least receiver density) to select beamforming codebooks. It's less likely they use this in their mobile cove
487.
by bri3d 1y ago
The user terminals use both; there’s a switch to enable the user terminal to ignore GPS if it’s inaccurate (for example in conflict areas where it is often spoofed or denied).
488.
by bri3d 1y ago
It's the level above; it's the thing that hosts the "grid of apps" you see on unifi.ui.com or on a Dream Machine, for example. The Network / Controller app is just one "app" in the "grid of apps.&quot
489.
by bri3d 1y ago
You're probably running what's currently called, I think, UniFi Network Server (at one point it was UniFi Controller?). That lets you configure networking devices but it isn't the "full" Ubiquiti ecosystem (Identity
490.
by bri3d 1y ago
That's the simplest and most obvious way I can think of. I know the Mill folks were deeply into this space and probably invented something more clever but I haven't kept up with their research in many years.
491.
by bri3d 1y ago
I disagree; Itanium was fundamentally flawed for general purpose computing and especially time-shared generally purpose computing. VLIW is not practical in time-sharing systems without completely rethinking the way cache works, and Itanium
492.
by bri3d 1y ago
They were pretty common for the first few years of Starlink, but it looks like the last global coordinated outage was on May 28, 2024.
493.
by bri3d 1y ago
Mac OS has "Private Frameworks" - shared libraries that are used by the system but don't ship with headers by default. It's trivial to produce these headers from the libraries, and then make wrappers for them like OpenMu
494.
by bri3d 1y ago
No, it’s like saying there is a link between putting locks on your door and making sure the lock can’t be replaced with one that takes someone else’s key, or worse one that copies the key that’s put into it. The threat models directly overl
495.
by bri3d 1y ago
I think they _might_ have thought a little farther than this; as far as I can tell this tool was _supposed_ to only boot images with the same security checks as the actual fused state of the console, and the issue was that the section heade
496.
by bri3d 1y ago
This reminds me a lot of the PSP Pandora's Battery: a special factory "boot from external flash" system with exploitable vulnerabilities - on PSP, the special Pandora's Battery "JigKick" serial number 0xFFFFFFF
497.
by bri3d 1y ago
Yes, that Acurite sensor and the one I have connected to my weather setup (Shenzhen Fine Offset / Ambient Weather) are all AS3935 based. I also have an Aliexpress "JMCU" AS3935 breakout/antenna board that I bought to pla
498.
by bri3d 1y ago
I was recently introduced to fully integrated lightning sensor ICs: https://www.digikey.com/en/product-highlight/a/ams/as3935-fr... - supply it a repurposed RFID coil and it will tell you when it detects
499.
by bri3d 1y ago
I’ve also seen this pattern at a pervasive rate but I think it’s mostly shady overemployment / outsourcing agencies, with NK as a tag along. It doesn’t matter either way since the countermeasures are the same (besides the stupid meme K
500.
by bri3d 1y ago
The design is both better and worse: * The list of officially trusted companies and root certificates is stored on a blockchain, for whatever reason, but at least this way it's a fairly open list and it's supposed to be shared equ
501.
by bri3d 1y ago
> Dev mode seems like such a nonstarter. I don't know what dev mode entails, ... what? All it means is that the "commissioner" (broker which attaches Matter devices to your Fabric) ignores the chaining of the device attest
502.
by bri3d 1y ago
This is correct; the hand-wringing in this thread is fair in that Matter does have a central governing authority who determine which devices are trusted, but completely unjustified insofar as that making a DIY Matter fabric/network is
503.
by bri3d 1y ago
I disagree that there’s zero chance for a homebrew scheme; it’s pretty easy to enable development mode and commission self-made devices using Google Home or Apple Home on both iOS and Android.
504.
by bri3d 1y ago
Shrug. I think this is a good illustration: it’s not the language that’s the issue, it’s the DOM. The DOM was and continues to be a terrible UI abstraction for applications. What we really needed was Flex or XAML or Swing or even XUL, for t
505.
by bri3d 1y ago
If you know the inverse function for SHA-1, that’s really quite something :) That project is indeed SHA-1 and not SHA256, but the implementation is much more clever and did a very good job utilizing some very ancient FPGAs back in the day.
506.
by bri3d 1y ago
You're forgetting Unisoc/Spreadtrum and ZTE in 5G, and in 4G there are also a bunch of "lower-end" Chinese basebands that are heavily copied from / derivative of one another. > Utterly unbelievable that no Wester
507.
by bri3d 1y ago
It's just a UART; you can use the UART to debug the device in various ways. On Pixel devices, the UART is not configured or brought up by default in locked production mode (as things should be), but by unlocking the device and then usi
508.
by bri3d 1y ago
> Most of those boards have a separate physical JTAG connector (at least in development kits, this article indicates JTAG over USB is disabled in production systems anyways so no difference there There's generally an entire phase of
509.
by bri3d 1y ago
In the interest of completeness I looked deeper and there are a few more patches to the kernel and SEP OS done at emulation time: https://github.com/ChefKissInc/QEMUAppleSilicon/blob/6eff3ab... but really not
510.
by bri3d 1y ago
The eShard thing and this GitHub are fairly different, as far as I know. The eShard people found an earlier version of this repository and set about patching one billion parts of the iOS kernel, library cache, and userland to make it run on

More ›