51–60 of 265 posts
Not surprised, many of these vendors are doing crazy things, insane defaults, broken security, hardcoded values. Security is not a priority, I get that, but at the very least some baseline check would be nice (no hardcoded credentials for starting)
I bought some ambient room lighting recently. You cannot control them without a proprietary app. This bugged me ... so I grabbed an APK from the Google store, unpacked it, and found essentially keys to the kingdom: api keys for the backend, api keys for shopify, etc. Haven't done anything with this knowledge yet.
Earlier quoted context omitted.
Yet another thing ipv6 solves. Yeah you can do the officially supported fdXX:XXXX:XXXX:... but you can also just pick something like 1::1 and it's unlikely to conflict with the current global range. If you're gonna do that, though, it's better if you use fd00:... or one of the other assigned ranges so it's still in the standard range. OSes use this as a heuristic for source address selection.
> Yet another thing ipv6 solves. ... it's unlikely to conflict with the current global range I'm not familiar with IPv6's details, could you elaborate on this? To me, this reads like you're saying that IPv6 solves the problem by having low adoption rates rather than an actual function of the protocol.
The point of IPv6 was to make the addresses so long they are easy to manage.
Earlier quoted context omitted.
> Yet another thing ipv6 solves. ... it's unlikely to conflict with the current global range I'm not familiar with IPv6's details, could you elaborate on this? To me, this reads like you're saying that IPv6 solves the problem by having low adoption rates rather than an actual function of the protocol.
The argument is that IPv6 addresses are UUIDs and any random block is unlikely to collide with any other random address. It's not about low adoption, it's that there are unimaginably many IPv6 addresses. ...which is a major reason for why it has low adoption
Earlier quoted context omitted.
Yet another thing ipv6 solves. Yeah you can do the officially supported fdXX:XXXX:XXXX:... but you can also just pick something like 1::1 and it's unlikely to conflict with the current global range. If you're gonna do that, though, it's better if you use fd00:... or one of the other assigned ranges so it's still in the standard range. OSes use this as a heuristic for source address selection.
"all that 192 stuff was silly and too complicated... but this fd00: stuff is easy peasy!"
LLMs have truly killed obfuscation. It only worked previously by making things extremely tedious but AI doesn't care about that.
On the bright side, even a small local LLM can easily improve garbage code like that.
The US Department of War IP adresses baked into the firmware is the bigger story here. Note to self: never buy a Korean security product.
just buy stuff you can put your own firmware/os on because it's either just the worst security in the world (aka anything not from china) or, well... china. and while i currently don't hate china as much as i do US rn (because canadian; sorry) i can also say -- due to being an aforementioned leaflandian -- that due to very personal experience i have zero faith in anything from china that has the ability to connect to…
I bet someone returned that security camera.