Dániel Buga

Disappointed that there are only 24 hours in a day. 🦀 Cyber janitor

[Scott Mabin @mabezzzzz]

I'm excited to announce the 1.0.0 beta release of esp-hal! Read more in the announcement blog post: https://t.co/Bp2VBEbhtM

[Dániel Buga @bugadani]

@imperioworld_ Editing* mistake sorry

[Dániel Buga @bugadani]

@imperioworld_ Nice article! You left in a slight edition mistake you might want to fix: "Why they require a new edition" contains "We will talk about why some doctests cannot be merged below." but comes after "How they were improved", which lists the reasons

[Guillaume Gomez @[email protected] @imperioworld_]

A major feature got merged in rustdoc: merged doctests. Currently, doctests are slow because they are all compiled individually. Merged doctests however are, well, merged into one file, compiled once and then each of them runs in its own process.

PR: https://t.co/3SCMicQyM7

1/3

[Dániel Buga @bugadani]

@jam_waffles Living the coder dream, i see. 👌

[Scott Mabin @mabezzzzz]

Check out the progress made in Q2 2024 using
@rustlang on @EspressifSystem microcontrollers!

https://t.co/GjeugGhqqG

#rustlang #rustembedded #rust #esp32 #espressif

@rustembedded

[Dániel Buga @bugadani]

@DJSnM nono, IFT4 is "Holy Shitballs! They landed after burning up!"

[Noah Huesser @yatekii]

👋@rustembedded we have a new probe-rs release for you https://t.co/2MBvraFTBY🎉
The changelog is massive thanks to all the contributors! We got rid of libusb in favor of nusb, good C support for the debugger and countless bugfixes and internal improvements!
Have fun =)

[Scott Mabin @mabezzzzz]

Check out the progress made in Q4 2023 using @rustlang on @EspressifSystem microcontrollers!

https://t.co/61R343r0MX

#rustlang #rustembedded #rust #esp32 #espressif @rustembedded

[Scott Chacon @chacon]

I've been frustrated by `git branch` for 15 years now, so I finally wrote a bash script that is what that command probably should be - ordered by last commit, ahead/behind info, descriptions. Download and set it up as an alias to live life how you deserve

https://t.co/aqAF9Vxtju

[Noah Huesser @yatekii]

We start 2024 with a release of https://t.co/XgoJWiZdgT 0.22.0🎉 For the first time in 3 years we have a new arch in alpha: Xtensa. New targets and even more bugfixes! A huge thank you to all the contributors in @rustembedded! Check it out at https://t.co/XuSSFaxnuK :-)

[Dániel Buga @bugadani]

@TheTmLev @BenKuchera @Wertandrew You don't tell a person who stood up that they did it wrong.

[Scott Manley @DJSnM]

I resynced the telemetry bar with the video of MECO & Hot Stage. Now it's more obvious the order of engine shut down, relight and failure on the boost back.
I suspect that booster failure is something like a fluid hammer effect given the stop and restart puts lots of stress on plumbing.

[Jesse D'Aguanno @0x30n]

Deadliest words in infosec:
“It’s better than nothing, right?”

Wrong

These words are the enabler of so many worthless “security solutions”. From phishing testing, to SAST, to “threat intel feeds”, to well, look around the floor of RSA…

Instead of identifying real problems and finding or engineering solutions that fix those problems, “security” continues to bolt on the cheapest “solution”, masking the real problem and kicking it down the road, saying “it’s better than nothing”.

It’s really not. Every organization has limited, finite resources, no matter how well funded. Wasting time, effort, and money implementing “solutions” because that’s what everyone else does is harmful. Those resources should be spent on identifying and addressing the root cause.

Making it so your users aren’t sure if they should open that attachment from their supervisor, or burying developers in false positive vulnerabilities _is not_ better than nothing. These are technical problems, they need engineering, not fairy dust and best practices.

The VC driven infosec — oops, I mean “cyber security” — startup world drives this world of worthless security “solutions”. There’s a perverse incentive to bring to market the weakest approach to a problem as quickly as possible. There’s absolutely _no_ incentive to solve hard problems. “The human is the weakest link, so let’s test if we can trick them”, not “let’s make it impossible for a person being tricked to result in a compromise, and also provide a great, usable UX”.

This is then enabled by security people that don’t actually understand the problem they’re trying to solve. Their view of security is entirely shaped by what vendors are trying to sell them, what their peers are doing, and what Gartner et al says is the best. Gartner and their peers are also just taking what the market is offering (junk) and comparing.

Platform providers are probably in the best position to address the underlying issues. They’re not incentivized in the same way. They’re not (usually) selling security, but security affects their bottom line. That’s why you see real work coming from them on Passkeys, etc. They do have other, sometimes competing incentives though, so it’s not a panacea.

My advice to security leaders:
- Before investing in a security product, ask yourself if you really understand the problem you are trying to address. Does this approach really address the issue? For instance, trying to stop phishing attacks against your users? Does TOTP MFA address that?
- If you find yourself, or someone saying to you “it’s better than nothing”, stop and reevaluate. Is it really better than nothing, or should your available resources be put to use on a real solution.
- Hire technical people that question the status quo.
- Train your people to be more technical and question the status quo
- Don’t let vendors tell you what the problem is, they’ll always have a solution to the problem they invented
- Identify the problem, then go to find a solution
- Don’t be afraid to build the solution (even though it’s not always the the best approach)

[Dániel Buga @bugadani]

Spellchokers are impontart

[FerrousSystems @FerrousSystems]

The ink is dried and the mail has arrived: Ferrocene is ISO 26262 and IEC 61508 qualified!

https://t.co/t8rWJd7vYX

#rustlang #embeddedsystems #opensource

[Dániel Buga @bugadani]

@teej_dv I'm not sure "You make me leak" is a good pickup line

[Dániel Buga @bugadani]

@ghidraninja hope that wire has no enamel on it