Andrew Inggs retweeted
Interesting Netflix Performance investigation which began at a WebSocket and ended in the Linux kernel:
netflixtechblog.com/investig…
Andrew Inggs retweeted
My open source library - @springboot & @wiremock integration has been adopted by WireMock and is now THE official integration for these two projects:
github.com/wiremock/wiremock…
Andrew Inggs retweeted
What are your plans for Thursday evening?🤔
How about joining me at @virtualJUG to talk about production features and development practices for working with @GraalVM?😎
meetup.com/virtualjug/events…
Included: working demos, breaking demos, benchmarks, language jokes.
See you there!:)
Andrew Inggs retweeted
It's official: I'm going to be working on the async book (and other docs) for the next six months, supported by a Rust Foundation fellowship foundation.rust-lang.org/new… It's just a portion of my time, but I'm optimistic I can make an improvement to the async #rustlang experience 😀
Andrew Inggs retweeted
I am reading about Conflict-free Replicated Data Types (CRDT). And I came across these fantastic implementations by Evan Wallace!
It's interesting to see how real-world collaborative applications work with the help of these data structures and algorithms!
Links in 🧵
Andrew Inggs retweeted
it's only called reasoning if it's from the brain region of homo sapiens. otherwise, it's just sparkling auto-regression
Andrew Inggs retweeted
SpringOne is less than two weeks away! We are excited to provide the latests updates on all things happening in the portfolio! Be sure to register at springone.io ! #springone #tanzu @SpringOne
Andrew Inggs retweeted
The very first post-quantum standards from NIST are out: ML-KEM, ML-DSA, and SLH-DSA aka FIPS 203, 204, 205.
nvlpubs.nist.gov/nistpubs/fi…
nvlpubs.nist.gov/nistpubs/fi…
nvlpubs.nist.gov/nistpubs/fi…
Spotted by Matthias Kannwischer. linkedin.com/posts/mkannwisc…
Andrew Inggs retweeted
#Java developers:
☕️ The 14th #JVM Language Summit is next week
☕️ Speakers include @BrianGoetz @cl4es @headius @PaulSandoz & @RemiForaxOff
☕️ Topics include Babylon, JRuby & Leyden
☕️ I'll post links to recordings once available
☕️ Agenda openjdk.org/projects/mlvm/jv…
#JVMLS2024
Andrew Inggs retweeted
If you're worried someone knows what EDR you run, that's an admission you're worried that knowledge will explicitly help threat actors.
I seriously need to know your logic there...
The strangest thing from all this is people being worried attackers might know what EDR product a company runs.
Outside of Endgame I’m not sure any EDR products tried to hide their existence.
If you’re on a host simply listing files in C:\Windows\System32\Drivers is enough to determine what products are in play or the ever popular read job descriptions or employees LinkedIn profiles
Andrew Inggs retweeted
This is a really interesting vulnerability, but *the Internet is not on fire.* Please read the actual advisory before spreading FUD. If you can't understand the original advisory, please get someone to explain it to you.
In short, the exploit has only been proven against x86 versions - NOT x64. That's important because finding the right address to return to in x64 is exponentially harder in x64 than x86.
This is definitely a "don't delay patching" moment, but not a "OMG, get an outage window NOW" moment. Monitor for updates though, that could change (though highly unlikely IMO).
This is also a great time to talk about zero trust. The foundational principle here is "deny all, permit by exception." Most orgs don't need SSH open to the whole Internet. Yes, ACLs are a pain to use. But you're getting a lot back in security. That's true for times like these, but it's also makes credential compromises harder to meaningfully exploit.
As an aside, if you can't do IP ACLs for SSH (and everyone *can*, it's just a question of overhead to maintain), consider changing the default port for SSH. In some testing, that's dropped my failed login attempts by more than 95% (98%+ if you don't make it something obvious like 2200, 2222, or 2022).
Finally, let's talk monitoring. It took @qualys researchers about a week to get a root shell. And that's for the x86 version (which again, is infinitely easier to trigger than in x64). So even if you can't just allow list a few IP addresses, you can for sure block list IPs that are hammering your server with ~10,000 exploit attempts. And before someone says "but Jake, what if they use a distributed network" - okay, but still block the obviously malicious IPs?
Great work by the Qualys team. There aren't many that can turn something like this into RCE - even in controlled environments.
blog.qualys.com/vulnerabilit…
Andrew Inggs retweeted
The specific technologies in distributed systems may change rapidly, but I think the fundamentals are evergreen. We are going to be retrying, queueing, caching, load shedding, and sharding until the end of time.
Andrew Inggs retweeted
Such a great question -- now that things like Clickhouse and DuckDB exist, how do we think about retriever, our custom built storage engine?
Answer: it's a massive differentiator for us, and a huge competitive advantage. We LOVE it.
=> 🧵
Andrew Inggs retweeted
Universally:
“I am trying to do X. The documentation HERE says I should see result Y. I am instead seeing Z. Here is a minimal reproduction case.”
This will cause you to close a majority of cases before submitting them as you discover a mistake you’ve made.
What information should you include in your AWS Support case? 📝 re:Post has the details! 💬
repost.aws/knowledge-center/…
#AWSSupport #AWSrePost
Andrew Inggs retweeted
The brave man who took this iconic photo, one of the first 3 humans to ever leave Earth orbit and travel to the Moon, died yesterday. Bill Anders, I salute you.
Andrew Inggs retweeted
The obvious reaction a lot of people have to this is they imagine the failure modes. But one of the secrets of engineering management is that part of turning a 1x programmer into a 10x programmer is remembering that a joyless programmer is always a 1x programmer.
Andrew Inggs retweeted
The Spring Cloud team is happy to announce the general availability of Spring Cloud 2023.0.2 and Spring Cloud 2022.0.7. Spring Cloud 2023.0.2 introduces compatibility with @springboot 3.3.x.
spring.io/blog/2024/05/31/sp…
Andrew Inggs retweeted
Slides for my talk from GeeCon, 2024, May 18th: "OOMs... I did it again".
Feedback welcome, errors are my own ("how was I supposed to know, that something wasn't right?", right?), as are the horrible jokes.
drive.google.com/file/d/1cbX…
























