nottelling
Yeah, just make sure you don't make that known during jury selection or you won't get to help.
I think the thing in this case is that it is the job of police to pull over a box truck full of human cargo. The implication here is so you think they'd have let a truck they knew was full of immigrants just drive away?
It's a combination, but mostly the risk of loss and inconvenience outweighs the cost for most passengers.
Not really. If DOS was Windows command line, this would be more like executing a series of jobs from the bootloader and waiting for output or errors to appear on the terminal or printer.
The only thing something like GMOS would have controlled is hardware resources and I/O. The "very specific program like a calculator" is accurate, but is loaded into memory via tape or punch cards or the like by the operator at runtime, alongside whatever other software was needed for the job batch.
Check the link I posted above, or you can look at the 802.15.4 wiki for an overview.
https://en.m.wikipedia.org/wiki/IEEE_802.15.4, scroll to the security section.
No apology needed, one thing about security is that paranoia is good. One problem with security is that paranoia leads to assumptions and misinformation, rather than understanding.
Symmetric key encryption is much faster than asymmetric, and can use much larger keys with less compute penalty. So we use acPU intensive asymmetric TLS handshakes to safely exchange the keys, and then switch to the faster method for the data.
So when ZigBee use AES 128, you can be reasonably sure the data packets are safe. The next question to ask is "do they exchange their keys safely?"
Which in this case would be "no" if you just leave the ZigBee controller in pairing mode all the time. However, you only allow pairing when you want it, and only pair with devices you explicitly allow. Unauthorized devices never get your network key.
That's fair, since it's possible these chips have some backdoored bootloader or something, I've never personally analyzed them with an electron microscope, but the architecture and wire traces are published, so you could start a chip fabrication plant and roll your own silicon.
The actual running code on them is usually GitHub hosted though, or you can write it yourself and just import the libraries you need, again usually from GitHub or the platform specific repositories.
If you're worried about Chinese chips in your open source though, I have some real bad news for you.
If you're using FOSS specifically as a control against Chinese spying, and not analyzing the commit logs of every package you download, I have more bad news for you.
Your Https connections are also symmetric, so that's a silly thing to dislike.
The handshake and key exchange are asymmetric, and used to establish a symmetric session key.
ZigBee encryption is fine for the use case, because you're only adding devices you know are being added. You inherently trust that your physical ZigBee device is the device it claims to be.
There's potentially an opportunity to hijack the key exchange between devices at network join, but you'd have to approve the listening device to your network in the first place.
https://development.libelium.com/zigbee-networking-guide/security-and-data-encryption
There is an entire ecosystem of open SoC devices, code, platforms, development boards, etc. One of the most popular is the ESP32/8266 boards, which is a pretty good place to start.
Part of what a tattoo is is the ephemerality. The art dies with the owner. Do what you want with your family's remains, but this is just dumb hubris.
The problem is that plenty of smart people are conservative. Because conservatism is fundamentally a grift, and the smart ones use the dumb ones to get richer.
Swift just has enough empathy to realize she's already rich.