Ten Years of Frinkiac: A Few Months of Modernization with AI It’s been just over ten years (February 2, 2016) since we launched Frinkiac to the public. In those first few months after release we added GIF support, some new sites (hello Morbotron ), and then we mostly stopped working on it. Everything worked well enough for us and the code sat unchanged on the same architecture we’d built in 2015.…
In the pyca/cryptography project we ostensibly write Python (and Rust), but in reality we are CI engineers doomed to spend 90% of all our development time building and maintaining our annoyingly large CI 1 . As part of that unwanted work we possess a self-hosted runner for macOS arm64 builds 2 . Self-hosted runners have one big drawback 3 – they lack build isolation. In the typical security model…
In 2019 and 2020 we did an analysis of memory unsafety bugs in Apple’s iOS and macOS releases. Another year has passed, so let’s run the numbers again 1 2 . If you’re interested in a deeper dive on what memory unsafety is and why it is Fish in a Barrel’s mission to rid the world of its scourge please read through the previous posts for more details. And, of course, follow @LazyFishBarrel on…
Last year we did an analysis of memory unsafety bugs in Apple’s iOS 12.x and macOS 10.14.x releases. We’re now at (nearly) the same point in the release cycle of iOS 13/macOS 10.15 so let’s run the numbers again 1 . If you’re interested in a deeper dive on what memory unsafety is and why it is Fish in a Barrel’s mission to rid the world of its scourge please read through last year’s post for the…
Buy Now! Fish in a Barrel ( @LazyFishBarrel ) is committed to ending the scourge of memory unsafety. It’s a well-known fact in the security engineering community that branded vulnerabilities are a key contributor to security. However, for too long, people who play defense have suffered from a dearth of quality signage. As part of our efforts, we set out to correct that. Fish in a Barrel has…
Over at @LazyFishBarrel we’ve been tweeting statistics about the proportion of memory unsafety related vulnerabilities in various software for a little over a year 1 . However, while Twitter is a great medium for dispensing this information on a per release basis, it’s not great for deeper analysis. Rather than just talking about a single release, what if we aggregated the total memory…
Yesterday Apple announced News+, “ an immersive magazine and news reading experience ”. This immersive experience is, for now, a US/Canada only product, with Apple noting: “Available in the US and Canada, Apple News+ presents the best and most relevant articles to meet any range of interests from renowned publications such as Vogue, National Geographic Magazine, People, ELLE, The Wall Street…
We’ve been quiet on the Frinkiac and Morbotron front for awhile, but today we’re introducing the newest member of the CompuGlobalHyperMegaCap family: Master of All Science . GIF and meme your way to happiness 1 with all the tools you’ve come to expect from our sites, but now with Rick & Morty! We’ve got every episode aired to date conveniently indexed so even an idiot like Jerry can find what…
pyca/cryptography 2.0 was been released today! This sounds like a big release, but it’s really just the 20th feature release we’ve done since starting the project 1 . But if it’s just a typical feature release then why the blog post? Well, coincidentally 2.0 actually is a huge release! In addition to adding support for ChaCha20Poly1305, AES-CCM, X25519 key exchange, Diffie-Hellman improvements,…
What platform do my users run on? How many users do I have? Is it okay to drop support for something ? Open source library developers have an analytics problem. How do you answer questions like this when people are embedding your software as a component of their own product? For example, you, the developer of the library frinkiac-iac would like to drop support for Python 2.6 because it is old,…