Hey everyone! I bring you my development journey on what I have discovered, accomplishments for this month, and the goals for next month!
Additionally, I will share some posts highlights on what post I am proud of sharing to Dev.to and my top 3 posts that stood out to me this month!
✨ Dev.to Posts Highlights! ✨
Here is one of the posts I am proud of for this month!
Finally shared my portfolio on dev.to and got a chance to see everyone's portfolio! It was great seeing different portfolio designs from all of you and got some feedback from my own portfolio!
Here is the top 3 posts that I have discovered that stood out to me!
@georgekobaidze If you are interested to see other great posts, check out George's post on his list of posts he want to showcase to the community!
@thomasbnt Made his own email weekly feed using an open model for more personalization.
@sanidhya_at_mlh A guide on not losing in a Hackathon. Although not guaranteed, it brings insights on how to make the most out of a hackathon in general.
Monthly Discovery 🔍
BREAKING NEWS: There is a critical vulnerability in PHP, Node, and simply HTTPS. It advise to update to the latest version if you are using any of them. Here is a copy of the email from Render for more insights:
What's potentially affected
- Any application that sends HTTPS requests to destinations over the internet
- Any application running Node.js, regardless of framework
- Any application running PHP, regardless of framework
What happened
eMudhra certificate compromise: On October 19, a public disclosure confirmed the compromise of private keys for eight intermediate certificates issued by eMudhra, a widely trusted certificate authority. Attackers can use these keys to impersonate websites and services to applications that still trust the affected certificates, circumventing the protection normally provided by HTTPS.
Node.js security release: On October 21, Node.js released patches for multiple vulnerabilities, including flaws that can bypass TLS certificate hostname checks and a flaw in Brotli decompression that can allow remote code execution. These releases also address the eMudhra certificate compromise.
PHP2Shell: On October 21, PHP released patches for two critical vulnerabilities discovered in the PHP runtime. These vulnerabilities can allow unauthenticated attackers to execute code on affected services or read sensitive information from memory, including passwords, tokens, and API keys. PHP applications can be affected regardless of which framework they use.
What you need to do
Update affected dependencies and rebuild your services. Follow our eMudhra advisory for instructions specific to your runtime. For all native runtimes, rebuilding your service updates its system certificate store. However, some languages and libraries bundle their own certificates and require separate updates. For Docker-based services, update the certificate store and affected dependencies in your image before redeploying.
If you run Node.js, update its version and redeploy every affected service. Update to 22.23.4, 24.22.1, or 26.12.1, or a later release in the same major version. These are the same versions recommended in our eMudhra advisory. For native runtimes, set your service's Node.js version. For Docker services, update Node.js in your image.
If you run PHP, update its version and redeploy every affected service. All PHP apps on Render use Docker. Follow our PHP2Shell advisory to update the PHP installation in your Docker image and confirm that your deployed services use a patched version.
We will update these advisories as additional fixes and guidance become available. Please refer to them for the latest instructions.
- 🔍 See more information on the Vulnerability
- 🔍 See more information on the Vulnerability here too
- 🔍 Anyway, reverse engineer anything with AI lol.
Accomplishments 🏆
- ✅ Shared my Portfolio on dev.to!
- ✅ Got the #a11y badge on dev.to!
- ✅ Got some badges on the Hacktoberfest event!
- ✅ Continued interacting with the Dev.to community.
Goals for Next Month 🎯
- 📝 Post one article every week.
- 📝 Going back to contribute to Forem.
- 📝 Continue interacting with the Dev.to community.
Feedback 💬
- What else should I do for November?
- Any questions/comments/advice or tips for the Monthly Report? Leave a comment below! I would love to hear from you!
Top comments (15)
Oooh 19/20 that soo cool! Actually I've got 17/20 :(
And I just received the automated email from DEV Digest about
Hacktoberfest Open-Source AI Challenge Week 3: Slow and Steady Submission 🦥
Stuck in the same dev.to topics? An open model fixed it.
Ayy looking nice.
@sylwia-lask Look it's you on his feed haha XD
Hahaha how cool is that 😂
But already read this post before this email! 😆
lol. What other posts showed up in your feed?
Thanks for featuring my post! ⭐
Anytime Giorgi!
php security updates be like
lol
A monthly report becomes more useful when each goal carries a falsifiable end state rather than only a theme. For the next month, a small table with the goal, the observable artifact, and the condition that would make you revise it would make progress easier to compare without turning the post into a productivity scorecard. The mix of portfolio work and community reading here already gives that reflection a solid base.
Lmao, and I thought I was crazy when I decided no Node.js, instead I'll just write a web server in rust 🤣
It's all fun and games until Rust is somehow affected too xd
Haha, true, though then I give up and will go back stone age raw assembly 😂
259 reactions on the portfolio piece, that's the month's proof.
Indeed. Thanks for the read!