I continue to hold the view that Tesla's success is because they are really a software company, not a car company.
1,282 karma · joined July 25, 2012
I continue to hold the view that Tesla's success is because they are really a software company, not a car company.
* HTTP/2 (3?) (on the roadmap) * a refresh of the dyno line-up - at least pass on some of the cost savings of removing/supporting free tier by reducing dyno pricing or preferably bumping specs * auto-scale for all dyno tiers * rebuild security team with reputable lead * edge / multi region active-active DX * edge ssl termination * iterate on chat ops (underrated feature) * more metrics * more alerting (e.g. crashed apps) * better user/access team management (default app roles) * enhanced secrets management in env (2 layers of env view/roles - config vs secrets) * DDOS protection * Treat CI env vars as secrets!
This is the most concerning part of that email, as it implies more than an "out of an abundance of caution", but rather that they suspect their password DB has been compromised.
Thinking about it, it does sound the most likely as they were probably the same DB the customer oAuth tokens were stored in that were used to access Github repositories. But if they already knew the data was stored together why wait till now to reset passwords?
I like how it just glosses over access to all the other tools which often contain a treasure trove of data. Just Slack can give an attacker worst case credentials pasted into channels and best case loads of information for more targeted social engineering attacks. LAPSUS$ even stated they had access to over 8K channels.
https://www.mylondon.news/whats-on/whats-on-news/gallery/lon...
1. Don't use strict (adkim=s; aspf=s) if you expect your emails to be forwarded (https://www.dmarcanalyzer.com/forwarding-within-dmarc/).
2. Microsoft (Outlook/Office365) ignores DMARC p=reject by default (https://docs.microsoft.com/en-us/microsoft-365/security/offi...)
Their choice as partner for the Oxford vaccine was purely political. Merck were originally the preferred choice (and they have a lot of vaccine experience) and a deal was almost done, but the UK vetoed it because all production would be in the US and they wouldn't offer the guarantees the UK had gotten from Oxford as part of their funding of the Vaccine development.
https://www.theguardian.com/society/2021/jan/29/we-had-to-go...
https://www.uber.com/legal/en/document/?name=general-terms-o...
E.g. like this one https://about.ads.microsoft.com/en-us/resources/policies/cla...
Current value January 4, 2021 - $2,238 billion
https://www.microstrategy.com/en/company/company-videos/micr...
The only place you get stuck and need an intermediary vps is if you are behind CGNAT. I came across this recently that helps set all that up. https://github.com/erikespinoza/v4raider
Which is a problem right? Now it emerges what has been breached. Including credit card data. Surely the prudent thing would have been to warn all their customers immediately to allow them to be on the lookout for malicious use of their data (phishing, etc.) and not wait until they have concluded their investigation.
vs
> The GDPR introduces a duty on all organisations to report certain types of personal data breach to the relevant supervisory authority. You must do this within 72 hours of becoming aware of the breach, where feasible.
So either EasyJet was delayed in their reporting of the breach, or the ICO didn't feel it was urgent to notify 9 million people that their data had been compromised. But it is now 4 months later?