Using a service like Have I Been Pwned, could companies like 23andMe proactively invalidate credentials that are known to be leaked? The next time those customers try to log in, they're forced to update their credentials through something like an email-based password reset?
Yes, this is exactly what could have been (and in my opinion, should have been) done to prevent this kind of "credential stuffing" attack. By taking known corpus of exposed passwords and comparing the hashed values against existing user password hashes, the company could have proactively locked accounts and forced password resets for users who had previously chosen weak passwords, and prevented new weak passwords from being chosen as well. This is quickly becoming an industry standard practice, and 23andMe likely knows that and is trying to make the argument that it's not their problem and has nothing to do with them (wrong).
Completely changed my approach to the gym. I used to never know what to do when I arrived in the morning. I’d usually do some cardio and then go shower.
FitBod now has me consistently doing hour-long workouts 4 days a week. I’ve used equipment I’ve never touched before and seen fantastic improvements in my fitness and strength.
As far as I know, Crossrail is the name of the project whilst the Elizabeth line is the name of the actual line. The Elizabeth line seems to be not quite an extension of the underground.
If a domain that you share your certificate with has their certificate revoked or is blacklisted for any reason this could have a negative impact on you.
I can confirm. My gran still has (she's not using it) her original TV bought around the time. From the stories my parents tell the SABC (think BBC) initialy broadcast a test signal and the early adopters would crowd around their TVs just to watch that.
I was one of the C.H.I.P. kickstarter backers. I actually have two. I've been quite pleased with them. Apart from the issue with early C.H.I.P.s not booting[1], I've been had very few issues with mine.
I really like the idea of these small, cheap, hackable and ubiquitous computers that we can assign to a project and not worry about the cost. One issue with the multitude of different companies making these things (Raspberry Pi, Beagleboard, Next Thing, etc.) is that some systems garner large communities (and subsequently lots of support) whilst others seem to remain small. Most of my endeavours with these computers has been software related but I imagine that the size of the community comes into effect when it comes to hardware support. Is there something that can be done do try to minimize this difference?
Open drivers, open documentation. Trying to work with these cheap SoCs is like pulling teeth, because their manufacturers are completely indifferent to the open source community. Video drivers are a particular sticking point.
They're working on it. The company behind C.H.I.P seems to be paying someone to develop drivers for it and get them into upstream Linux, including non-accelerated video drivers. A lot of the hardware on this era of Allwinner SoC actually already has support thanks to community efforts, too.
https://mailbrew.com/