just did a quick readthrough. looks like you've covered my use cases (for my home network at least). looking forward to seeing how it integrates into my stack.
forgive me if you go over these questions, I didn't find them covered anywhere.
how lightweight are the endpoints/sensors compared to opencanary?
is there any way to do a log export? I saw several siem integrations and more on the roadmap but I personally always appreciate the ability to do this.
yes, iirc phones still advertise periodically. best to switch it off when not in use.
Debian users should receive their news 6-12 months after everyone else, change my mind
/s
this is the dark theme variant
harder to sell our data if just anyone can waltz in and steal it
this is shockingly ambitious from the flipper team. wow.
I don't have experience with ARM development, but IMO that seems like the field that would benefit the most from this project. its also where I see the most pushback occurring.
very happy they're opening this up. they built a good community with the first flipper, I'm sure there are tons of qualified people willing to contribute to this one.
makes sense that they'd remove it from their forums if it has nothing to do with graphene. not a single point relevant to the OS
i only did a quick readthrough so my understanding of how it works is probably flawed. that said:
you could consider split-tunneling a browser outside of your normal stack for fauxx to pollute. that way your real activity remains as close to "ghost" as possible, and gives your device a fake fingerprint that will fool anyone not directly targeting you.
the reason I'd suggest doing it that way is that nobody's personal device hygiene is perfect. flooding with synthetic data is a great way to help conceal when you slip up.
clone, star, fork. we can all help out.
almost like its not about security
Ah, the researchers finally got around to playing Expedition 33 huh?
Jokes aside, isn't this also a phenomenon with finishing books and TV shows?
there's no fucking way