looking forward to the unwritten details / future posts too, particularly:
- How to handle network and IP duplicates on cloned VMs
and
- Turning a Dockerfile into a rootfs for the MicroVM (quickly)
451 karma · joined October 9, 2014
looking forward to the unwritten details / future posts too, particularly:
- How to handle network and IP duplicates on cloned VMs
and
- Turning a Dockerfile into a rootfs for the MicroVM (quickly)
but i'd love to know the series of changes that goes into something like this if its not just hype, potentially unpicking a giant complex system from the bottom up to remove attack surface.. interesting challenge!
Kind of funny the govt shipped the feature even with the spam risk and our more commercially oriented competitor product didn’t. You’d Hope they would be raising the bar for security not lowering it.
https://www.bloomberg.com/news/articles/2019-05-15/disney-wo...
But api gw is 10mb, not for lambda tho, confuse: https://docs.aws.amazon.com/apigateway/latest/developerguide...
Use s3 object lambda and have no limit to push to s3 with logic, adds a bit of latency tho https://aws.amazon.com/blogs/aws/introducing-amazon-s3-objec...
All historical but hard to understand the limits as a poor user..
Ended up going with cloudflare workers for s3 uploads with extra logic just to avoid the unknown, workers are great btw.
(Edit: I realize most of those aren’t statically linked, better description might be “things copied straight into container, not installed”)
I guess the secure enclave having storage introduces another attack too, wiping/corrupting/replacing that storage somehow, thus efuses, simpler and more straightforward.
I must be missing something, either the bootloader execution is trusted and should be able to store state securely, Secure Enclave style, or it’s not and melting things doesn’t solve the problem as compromise of the code means the fuses can be ignored..
Homelab would be fine =)
7000+ threads does seem like a lot though and agree there is the general lack of caring about resource consumption in all forms, eg Electron apps. At this point having lots of threads seems almost expected by various OSs and something they solve for to reduce the cost of it so the user doesn't have to worry about it.
I've often thought about what interesting findings you would get back if time and people were infinite and all those little things you thought, 'huh? thats weird' and put it in a queue somewhere and a few days later it had been thoroughly investigated and findings documented by some smart person. I'd expect you'd find some weird networking problems for why ssh hangs sometimes, misconfigurations, waste, security vulns etc. So many things we skip over day to day bc it would be a distraction.
Quote from related issue:
The NGINX ingress controller does not uses Services to route traffic to the pods. Instead it uses the Endpoints API in order to bypass kube-proxy to allow NGINX features like session affinity and custom load balancing algorithms. It also removes some overhead, such as conntrack entries for iptables DNAT.
I can imagine the delay between updating the GCP global load balancer service from GKE would be much higher than nginx-ingress reacting to changes in pod health/endpoints.
Either way I guess the takeaway is there is a race there between endpoints being updated and those updates propagating, and seems like that isn't handled as perfectly as people assume, and this likely gets worse with node contention and Kube API performance problems.
A multi tiered tree of repositories sounds very complex though, and would require its own effort, amazing it worked at all.
The information (in the form of chemicals etc) is there we just can't sense it via machine or otherwise, puts the idea of technological superiority into perspective.