5 ms·
> There were two strings printed with labels “SSID” and “Pwd”. I froze in horror. They wouldn’t dare. It is literally 3 meter distance. These are embedded devic
by kelnos 3y ago
> There were two strings printed with labels “SSID” and “Pwd”. I froze in horror. They wouldn’t dare. It is literally 3 meter distance. These are embedded devices, they do not need this complexity…
Not surprising at all. I would expect that a lot of these are bought as retrofits, and not as a part of new construction. Running wires through existing walls can be annoying, and they don't want to put that barrier to sale in front of them. And you can get a good-enough WiFi chipset for a few bucks these days.
> I need a 3A fuse [...] After installation, I checked the temperature of the fuse multiple times during the day to get at least some indication that things are not going to get worse. It worked fine for a more than a week now, but I still do not recommend experiments like this to anyone.
Probably don't need to be so worried here. If it's a 3A fuse, the entirety of your apartment's mains power is not running through it. A 3A fuse would burn out in a fraction of a second if you tried to do that.
Also, oh, man, Jazelle. I'd forgotten about that. Hardware support for Java bytecode... that did not pan out well.
- inetknght 3y ago> Probably don't need to be so worried here. If it's a 3A fuse, the entirety of your apartment's mains power is not running through it. If it's a "3A fuse" that doesn't blow at 6A or worse, then it will get very hot (fire hazard) if/when there's a short regardless of the distance to the mains power. If it truly is a 3A fuse, then great. If it's bought from Amazon then I doubt it's truly a 3A fuse.
- naitgacem 3y agoLouis Rossman over at YouTube has been going over this fuses thing from Amazon. All the fuses he tried from top-results didn't blow until he put 4x or 5x the current rating through them.
- stavros 3y agoReally? What the hell? That seems extremely unsafe, why are people doing this? Are 12A fuses cheaper to make than 3A fuses?
- kevincox 3y agoProbably not. But precision is expensive. A 3A +- 0.1A fuse will be more expensive to make them a 3A +- 6A fuse. And of course a customer will be upset with a 3A - 2A = 1A fuse so they really make a 9A +- 6A fuse and sell it as 3A. So if you are "lucky" you can pass 12A though it no problem. (Numbers make up for illustration.)
- SoftTalker 3y agoFuse needs to protect against 2 main things: 1) a dead short in the circuit. Fuse will blow pretty much instantly. 2) an overload on the circuit. Fuse will blow sooner or later depending on how great the load excess is. If the fuse is rated at 3A, it's not going to be fine at 2.9A and then instantly blow at 3.1A. You'd need actual current monitoring to do that. And some fuses are "delayed" to allow an overload for a few moments, such as when starting a motor. None of this disputes that Amazon is well known to sell garbage, and not just limited to fuses. That's why I don't buy anything there.
- ssl-3 3y agoAlso, too: Wifi has inherent galvanic isolation with a wide gap. It isn't strictly necessary, as anyone here obviously knows, but it can be a cost-effective way to isolate the [electrical] pokey-bits from the [meat-based] pokey-bits, and to avoid loops when things go wrong. Wireless has uses beyond just eliminating wires.
- mcbishop 3y ago> it can be a cost-effective way to isolate This never occurred to me, thanks.
- xerox13ster 3y ago> A 3A fuse would burn out in a fraction of a second if you tried to do that. he bought it on Amazon. He has every reason to be worried that it won't burn out. Louis Rossman did a video[0] where he put 8 amps through a 2 amp fuse and left the room for quite a long time, I think it was several minutes with 8a going through a 2a fuse. [0]: https://www.youtube.com/watch?v=B90_SNNbcoU https://www.youtube.com/watch?v=B90_SNNbcoU
- userbinator 3y agoFuses are notoriously imprecise, even "fast blow" ones: https://www.youtube.com/watch?v=WG11rVcMOnY https://www.youtube.com/watch?v=WG11rVcMOnY
- dns_snek 3y agoI'm not going to watch the whole video but it doesn't seem like it supports the point you're trying to make. > How long does it take for your 400mA multimeter fuse to blow at 600mA? > The amazing unpredictability of fusing current ratings at low overloads. It makes a point of saying that fuses are imprecise, i.e. that a fuse likely won't blow when 600mA of current passes through a 400mA fuse for a few seconds. What Rossmann discovered was that fuses from Amazon took 4x the rated current for minutes. That's many orders of magnitude out of spec.
- B1FF_PSUVM 3y ago> 4x the rated current > That's many orders of magnitude An order of magnitude is 10 times, in my timeline.
- dns_snek 3y agoThe relationship between the amount of overload and how fast the fuse is supposed to blow is quadratic, not linear. As an example with somewhat made-up numbers, at 1x it might take hours to blow, at 2x it might take a minute or two, at 3x it shouldn't take more than a second and at 4x it should be nearly instant. If it's supposed to blow in 0.1 seconds when overloaded by 4x, then taking 10 minutes is many orders of magnitude in my book. While that fuse is taking its sweet time, wiring or other components are being heated out of spec (16x more heat at 4x the current), potentially posing a fire hazard or damaging the device it's supposed to be protecting.
- AnthonyMouse 3y ago> Running wires through existing walls can be annoying, and they don't want to put that barrier to sale in front of them. It also makes it more convenient to compromise the device from across the street (or across town with a directional antenna). Though of course that's not a problem if your security is up to par and the device continues to receive regular security updates, and we can only surmise that the author has discovered a rare outlier in this space where that is not the case.
- inetknght 3y ago> Though of course that's not a problem if your security is up to par and the device continues to receive regular security updates Just remember that the S in IoT stands for security :)
- injidup 3y agoSecure Home
- b112 3y agodevice continues to receive regular security updates Have to reply to this, and my response was covered a bit by your statement of "security up to par". Nothing should be considered secure. All those bug bounties are to entice black hats, into giving up juicy pre-0day vulnerabilities. So just because a device is up to date with security updates, we all must understand, there are countless bugs unknown, needing to be patched, and often, being discovered by those that will never tell, never disclose, never report, and only use them for nefarious purposes. This is why security is nothing without monitoring. And why nothing is ever "safe", only likely "more safe" due to a security update. Consider everything that is network connected as compromised. Everything.
- AnthonyMouse 3y ago> Consider everything that is network connected as compromised. Everything. This doesn't seem like useful advice. If you know something is compromised, you're going to want to stop using it and build a clean system etc. You can't just do that continuously the instant you've built the new system. Likewise, how does monitoring even work? Every device and app wants to phone home to some random server. The connection will be encrypted and even if it wasn't it could be some arbitrary custom protocol you'd have to spend several hours to reverse engineer. You could just block them all but that will cause massive breakage and possibly impair security when the thing you're blocking is whatever thing's security update mechanism. What's a solution someone can actually use?
- AceJohnny2 3y ago> Also, oh, man, Jazelle. I'd forgotten about that. Hardware support for Java bytecode... that did not pan out well. I'd love someday to learn more about why Jazelle failed. The first SoC I worked on almost 20 years ago was built around an ARM926EJ-S, just like in the story. It was built for Nokia, who used Symbian OS [1], and supported user-installable apps written against Java Micro Edition [2]. The utter mess of Symbian's app discovery and installation, I suspect, was a prime reason Apple created their App Store for the iPhone. Nevertheless, the fundamental concept of HW-accelerated Java apps doesn't sound crazy. What happened? Were they just stuck with a sinking ship, Symbian? [1] https://en.wikipedia.org/wiki/Symbian https://en.wikipedia.org/wiki/Symbian [2] https://en.wikipedia.org/wiki/Java_Platform,_Micro_Edition https://en.wikipedia.org/wiki/Java_Platform,_Micro_Edition
- alexambarch 3y ago> Also, oh, man, Jazelle. I'd forgotten about that. Hardware support for Java bytecode... that did not pan out well. As someone who was too young to be paying any attention during this time, what were some of the reasons this didn’t pan out? Java seems so dominant looking back that I’m surprised something like this wouldn’t have been a success.
- vanderZwan 3y agoI have also wondered this for years, and always was told "because JITs work better", but that felt a bit handwavy. Luckily for both of us David Chisnall just published an article on ACM about designing ISAs that properly explains the reasoning behind Jazelle and why it did not work in the long run: > Small code is also important [for a simple single-issue in-order core]. A small microcontroller core may be as small as 10KB of SRAM (static random access memory). A small decrease in encoding efficiency can dwarf everything when considering the total area cost: If you need 20 percent more SRAM for your code, then that can be equivalent to doubling the core area. Unfortunately, this constraint almost directly contradicts the previous one [about decoder complexity]. This is why Thumb-2 and RISC-V focused on a variable length encoding that is simple to decode: They save code size without significantly increasing decoder complexity. > This is a complex tradeoff that is made even more complicated when considering multiple languages. For example, Arm briefly supported Jazelle DBX (direct bytecode execution) on some of its mobile cores. This involved decoding Java bytecode directly, with Java VM (virtual machine) state mapped into specific registers. A Java add instruction, implemented in a software interpreter, requires at least one load to read the instruction, a conditional branch to find the right handler, and then another to perform the add. With Jazelle, the load happens via instruction fetch, and the add would add the two registers that represented the top of the Java stack. This was far more efficient than an interpreter but did not perform as well as a JIT (just-in-time) compiler, which could do a bit more analysis between Java bytecodes. > Jazelle DBX is an interesting case study because it made sense only in the context of a specific set of source languages and microarchitectures. It provided no benefits for languages that didn't run in a Java VM. By the time devices had more than about 4MB of RAM, Jazelle was outperformed by a JIT. Within that envelope, however, it was a good design choice. > Jazelle DBX should serve as a reminder that optimizations for one size of core can be incredibly bad choices for other cores So: a decent JIT works better if you can afford the overhead of the JIT. Jazelle was only a good idea in a very brief period of time when this wasn't true, and even then only if you insist on running a Java VM. [0] https://queue.acm.org/detail.cfm?id=3639445 https://queue.acm.org/detail.cfm?id=3639445
- madaxe_again 3y ago>> To be honest, the whole thing was a bit scary, since I was very close to the mains I laughed at this. Changing a fuse is… a bit scary? They literally teach this in elementary school in the U.K. - or they did. As you say, no need to fretfully check the fuse - either it blows or it doesn’t, and you’ll know when it does. At least he didn’t find the receptacle holding a dead fuse, carefully wrapped in the ceremonial aluminium shroud of eternal life and certain death, which is a crime I may have committed in my younger, more fire-prone years. I find it interesting how uncomfortable some people are outside of their comfort zones - but then I am a person who spends his life sticking his nose in stuff he has no business with.
- kelnos 3y agoI don't know how old the author is, but I'm not surprised when people even 10-15 years younger than I am (I'm in my 40s) shy away from digging into the guts of how things work. I feel like I was at the tail end of when it was ok to experiment with technology as a kid and teen. The early '00s brought much more in the way of disposable, locked-down devices. Kids growing up today (despite the educational push of orgs like the Raspberry Pi Foundation) are presented with hermetically-sealed devices that present a sanitized interface. Manufacturers explicitly don't want their customers taking things apart, discovering how they work, or tinkering with them in any way... and often even try to put legal barriers in place to keep people from doing stuff like this. This is a far cry from when I was very young (and before I was born) when computers and kits would come with full schematics and datasheets!
- mixmastamyk 3y agoI remember my uncle replacing tubes in the back of the TV, which was actually dangerous.
- ThrowawayTestr 3y agoI honestly find it pretty sad
- Symbiote 3y agoSecondary school, but it's still in the revision guide so I assume they still teach it. https://www.bbc.co.uk/bitesize/guides/z6r37nb/revision/6 https://www.bbc.co.uk/bitesize/guides/z6r37nb/revision/6
- pmontra 3y agoYeah, the author makes this pun > C in IoT stands for “cost-effective” I guess but it's actually C for cableless.