My course about Ruby on Rails security is out of pre-sale. All of the content, videos and text is published now. I will likely add an extra AI section soon as an extra.
https://t.co/Q7jTGKGcoj
Hi everyone!!!
Who is excited about the first Euruko in Italy? 🇮🇹
We started planning and we will share more information in the next weeks, in the meantime you can subscribe on https://t.co/ccezlZ0OLx to receive further updates!
On Monday I'm launching Chat with Work: AI bots that run on triggers, and one place where you decide what they do. Here's the gist. Monday it's on Product Hunt, come say hi. https://t.co/o4eP45HKVI
I'm not shotgun applying to every Rails job out there. I'm looking for work that means something to me, on a team I'd be proud to be part of.
Slower, but it feels right.
For all Omarchy enthusiasts.
This week’s newsletter is out.
A bit of Friday reading:
https://t.co/UFZsUvcn11
Some things you might have missed: local AI on more hardware, new homelab tools, and 46 fixes on the way.
@5katkov My 8 year old is also about to figure out it. She wrote a letter to Santa and asked him to come and meet her. And she said she wants me to be there too, to make sure I am not the one dressed as Santa :D I need to hire someone for the job I guess.
@JM97_79 Not sure what makes him an Emperor. Not having the balls to confront Merab(much smaller than him) on his own? The jumping of the cage when his brother got knocked out? Or the failed drug test?
As I mentioned above, there is a current example, but since the fix is not public yet, I won't share it yet.
But as an example, you replaced a dependency with an in-house implementation, so you never need to upgrade it again. For that old dependency, someone finds a vulnerability that also effects your implementation. You will never know about it and will stay vulnerable. There are multiple tools for the same job an most eco-systems, and quite often, there is a vulnerability found in one of them and the same issue is present in the others. The beauty of open-source is that maintainers pick these up and patch, so you just need to upgrade.
@raggi And you potentially introduced 100 vulnerabilities in your app and when a new technique comes out in the future and it affects your implementation, you will likely not hear about it and will never patch. I have a really good recent example for this, but it isn't public yet.
We harvested a few giant sweet potatoes recently. It is one of my favorite crops. Pretty easy to grow and the whole plant is edible, although we feed the greens to the animals only.
Do you mind to share the numbers? But regardless of those, if you believe a stack is better for security than another one, you might be surprised one day. It is easy to write insecure code in any language and you can write secure code in any. Vulnerable dependencies happen in each stack regularly, there is tooling to handle those in pretty much all stacks.
@raggi Your initial tweet implied that you are glad you ditched the ruby stack because of the CVE and my response was for that. Go might be much better for your use case, but not because of the security aspect.
How is cybersecurity a threat though? Cybercrime is a threat. And he is totally wrong. There were always easy and hard to exploit vulnerabilities and it is the same now, although you can get an exploit done faster. If it would be just down to the tokens, it would be easy to secure the systems, just ask AI to do it.
I don't have a ruby person identity, but ruby is my choice of scripting language for sure. But I think it is silly to believe a language will make your stack more secure than another. As for the maintenance burden, see the screenshot in my other reply. You should've upgraded go more than ruby this year so far due to security releases.
I don't know about the whole past decade, but if you just look at this year, you should've upgraded go more often due to a security issue than Ruby.
And your experience is one in many, I also have close to 20 years of experience as a developer, a decade as a pentester and in my experience, choosing a language for security reasons is not a wise thing to do.