Practical Security Strategist, Engineer, Architect and Technical Debt Advisor.
Interested in effective cybersecurity. No snake oil. No checkbox security.
To make a mistake is human but to really fuck things up you need a computer.
| github | https://github.com/securitym0nkey |
| codeberg | https://codeberg.org/securitym0nkey |
if you update your mikrotik on 7.22 today, do not forget to enable the new RA Guard in the bridge settings.
It help to block some ipv6 router advertising attack.
change log don't say if there is fix to airsnitch or not tough
more info:
#mikrotik @mikrotik #update #upgrade #security #ipv6 #airsnitch #wifi #bridge #raguard #slaac
RE: https://tldr.nettime.org/@tante/116082694984669549
I am just so tired of this "AI" shit. Truly. Not just the extra maintenance burden on my but the constant discussions that lead nowhere. I can keep making the same arguments against using "AI" for anything relevant from here till the cows come home but it's not gonna change people's opinion. Because they are "on AI" or their bosses force it upon them or whatever.
But honestly. It's all been said. Neither does the tech change significantly (regardless of what the boosters tell you) nor do the other facts at hand, the brain and skill atrophy, the exploitation, the ecological impact, etc. etc. etc.
Dunno. It's hard to keep doing this whole "keep making your point and maybe some people will change their mind thing" when the facts are all on the table and people just have made decisions I find morally questionable.
Maybe I am just tired. Will keep doing the same shit tomorrow. Keep running against that concrete wall hoping that it will somehow crumble.
AI is making us write more code. That's the problem.
I analyzed research papers on AI-generated code quality. The findings:
→ 1.7x more issues than human-written code
→ 30-41% increase in technical debt
→ 39% increase in cognitive complexity
→ Initial speed gains disappear within a few months
We're building the wrong thing faster and calling it productivity.
Sometimes figuring out whats happening over time in the Mikrotik changelogs isn't as easy as it should be..... I made a tool to display changelog entries and data in different ways, as well as searching all changelogs for keywords. (MLAG for instance is a good search keyword).
This is still in really early public availability, but its been useful for 2 out of 2 people I shared it with and so I expect it will be useful for a wider audience.
When countries get hooked on US tech, their governments are constrained in reining in tech’s harms while most of the economic benefits accrue to the United States.
It’s time to break out of that trap — but that means challenging the Silicon Valley model, not creating our own digital colonizers.
https://disconnect.blog/escaping-the-trap-of-us-tech-dependence/
hey fellow #MikroTik enthusiasts,
Lately i have consolidated some network infrastructure. Mainly removing dedicated firewall systems where they did not much more than filtering traffic. A task a RouterOS system can do with ease. But when it comes to High-Availability setups there is a caveat: the old systems kept ruleset, VRRP interfaces, virtual IPs, etc. in-sync. Using a more flexible system, like RouterOS, it's up to YOU to keep the configurations working with each other.
To tackle this challenge I’ve created MikroSync - https://codeberg.org/securitym0nkey/MikroSync
- a tool to synchronize RouterOS configurations
- can run directly on the Router (as a container)
- OpenSource - MIT license
Consider #MikroSync early beta - though I’ve started to use it in a simple production environment.
Happy for any feedback and contributions.
LΞX/NØVΛ 🇪🇺
Eugen Rochko
tante
Mark Levison
fancysandwiches
Theo Baschak 
Paris Marx
Volker Quaschning