The question is more what this really solves. They said they built all this because DNS propagation was too slow. But secondary dns servers by e.g. your isp will still have old records when you change something. So what did they earn? Every is correct within their network pretty fast. But for a normal user there isnt any difference because 8.8.8.8 or 1.1.1.1 still cache old records?
That has also been implemented recently. With staged publishing the author must verify a new release with 2FA so automated attacks dont work anymore. Some human in the loop must verify a release.
I am wondering about the last part of glibc malloc. Isnt that exactly the problem reported for the last 10+ years with glibc? And the common solution is to use tcmalloc or jemalloc which hasnt these problems?
I would love to have a mode that I must use my long password to unlock my mac for security purposes. But when unlocked, use touchid as an alternative to my password for convenience.
So just the normal TouchID mode but not for unlocking the mac.
Oh there will be a lot of issues in the future because Germany says thst your company is in Germany because you work from there. So you have to do taxes in Estonia and in Germany. And prepare for a lot of tax issues if you dont have a good tax advisor.
I do understand why all these steps are required. And they are good. But how should zero-trust architecture solve that? You‘re still authenticated what the core problem is.
When you have a custom domain you can list @mydomain.com as sending domain allowing you every string before the at character. So that means you could use 50 different domains with infinite adresses on these domains.