Titanous
BIMI logo and verified checkmark are spoofable in Gmail
Fish in a Barrel Memory Safety Bounty Program
https://docs.google.com/spreadsheets/d/1dXtv2wnutujfXWUHB9Bm...
Firefox TLMC Response to Dark Matter Root Inclusion Request Appeal
ZombieLoad: Cross Privilege-Boundary Data Leakage on Intel CPUs
https://code.visualstudio.com/docs/remote/faq#_why-arent-the...
>This censorship occurs despite the fact that when in China a cell phone using a foreign SIM is not subject to the firewall restrictions (all traffic is tunneled back to your provider first), so Google, Twitter, Facebook, et al all work fine on a non-mainland China SIM even though you’re connected via China Mobile or China Unicom’s network.
Tesla says its factory is safer. But it left injuries off the books
How I exploited TLS-SNI-01 to issue Let's Encrypt certs using shared hosting
Introducing Nested Virtualization for Google Compute Engine
(edited for clarity)
Also, log shipping and Let's Encrypt support are coming soon.
Distributed communication should work fine, feel free to ping us on IRC or GitHub if you run into any trouble or have any questions!
Flynn is designed to be an end-to-end solution for production deployment, and all of our components are created to work together. The whole system is self-bootstrapping and self-hosting, so installation is easy, and the same APIs are used to manage the whole platform as are used to manage apps deployed on it.
In addition to the twelve-factor stateless webapps that Deis Workflow supports, Flynn also includes highly available database appliances with safe, automatic failover (currently PostgreSQL, MySQL, and MongoDB with more coming in the future). We also have a bunch of security features coming over the next few months like Let's Encrypt support and flexible user authentication with 2FA and very granular access control.
If you don't need or want our database appliances and you are comfortable with Kubernetes and happy to install and operate it, then Deis Workflow is a good option. If you don't care about using Kubernetes specifically, Flynn is a good pick as it is easier to get up and running with.
Compliance is a really interesting vertical. As we make progress on our security roadmap, Flynn will become a very compelling option for environments like HIPAA, PCI, etc. especially when combined with clouds like AWS that are also compliant.
So far no one is using Flynn in a fully disconnected environment, and we're aware of this limitation. My take on this is that we need a replacement for buildpacks that allows for repeatable/functional builds (think Nix for app deployment).