The #eff made a wonderful project called rayhunter. It detects modern cell site simulators (aka #stingrays, fake cell towers).
But it doesn't work out of the box on Debian and when I offered a fix (commands to compile a version for Debian), they didn't like it, suggesting that everyone who uses Debian or #Ubuntu 22.04 should set up a rust development environment & compile it themselves.
The beauty of #OpenSource is that I don't have to accept that answer. I'm forking it & adding a #Debian release
https://gitlab.hax0rbana.org/public-repos/rayhunter
I'm not familiar with #Microsoft's #GitHub CI/CD system, so I'm making automated jobs to do it in #GitLab's CI. I **will** accept pull requests to also implement it in GitHub's CI/CD, and I can mirror my fork over there after I get the feature implemented.
Hopefully the upstream maintainers will accept my feature so the project is more accessible to people, especially #journalists and #activists who might not know how to get the bleeding edge #Rust toolchain.
And if it is not accepted, then people who find out about my repo can choose between downloading a release from my CI/CD or compiling it themselves.
And that's OK. Letting people choose is a good thing. When there is a difference of opinion, spinning up another fork is great.
Who knows, maybe I'll add a #Windows release as well. 😁
I just can't say enough about how amazing it is to be able to detect #stingray style attacks for $20.
#security #privacy #cyber #cybersecurity #infosec
The #eff made a wonderful project called rayhunter. It detects modern cell site simulators (aka #stingrays, fake cell towers).
But it doesn't work out of the box on Debian and when I offered a fix (commands to compile a version for Debian), they didn't like it, suggesting that everyone who uses Debian or #Ubuntu 22.04 should set up a rust development environment & compile it themselves.
The beauty of #OpenSource is that I don't have to accept that answer. I'm forking it & adding a #Debian release
https://gitlab.hax0rbana.org/public-repos/rayhunter
I'm not familiar with #Microsoft's #GitHub CI/CD system, so I'm making automated jobs to do it in #GitLab's CI. I **will** accept pull requests to also implement it in GitHub's CI/CD, and I can mirror my fork over there after I get the feature implemented.
Hopefully the upstream maintainers will accept my feature so the project is more accessible to people, especially #journalists and #activists who might not know how to get the bleeding edge #Rust toolchain.
And if it is not accepted, then people who find out about my repo can choose between downloading a release from my CI/CD or compiling it themselves.
And that's OK. Letting people choose is a good thing. When there is a difference of opinion, spinning up another fork is great.
Who knows, maybe I'll add a #Windows release as well. 😁
To follow up from my previous post: I got it working!
My fork of the EFF's Rayhunter adds support for Debian 12, Ubuntu 22.04, and macOS (x86_64). Get it from the latest job in pipeline https://gitlab.hax0rbana.org/public-repos/rayhunter/-/pipelines
I've submitted the improvements upstream and hope they will be accepted: https://github.com/EFForg/rayhunter/pull/172
But you can get this from me whether it's accepted there or not. I couod use help testing (I don't own a mac, for example). Please comment on the MR if you test and have a GitHub account.
Every time I use clang I think of "Aerosol Can" by Major Lazer. 🤣
#iykyk
The #eff made a wonderful project called rayhunter. It detects modern cell site simulators (aka #stingrays, fake cell towers).
But it doesn't work out of the box on Debian and when I offered a fix (commands to compile a version for Debian), they didn't like it, suggesting that everyone who uses Debian or #Ubuntu 22.04 should set up a rust development environment & compile it themselves.
The beauty of #OpenSource is that I don't have to accept that answer. I'm forking it & adding a #Debian release
https://gitlab.hax0rbana.org/public-repos/rayhunter
I'm not familiar with #Microsoft's #GitHub CI/CD system, so I'm making automated jobs to do it in #GitLab's CI. I **will** accept pull requests to also implement it in GitHub's CI/CD, and I can mirror my fork over there after I get the feature implemented.
Hopefully the upstream maintainers will accept my feature so the project is more accessible to people, especially #journalists and #activists who might not know how to get the bleeding edge #Rust toolchain.
And if it is not accepted, then people who find out about my repo can choose between downloading a release from my CI/CD or compiling it themselves.
And that's OK. Letting people choose is a good thing. When there is a difference of opinion, spinning up another fork is great.
Who knows, maybe I'll add a #Windows release as well. 😁
Right now I have rayhunter releases building for:
- Debian 12 (bookworm)
- Debian latest (also currently bookwork)
- Ubuntu 22.04 (jammy)
- Ubuntu 24.04 (noble)
- Ubuntu latest (also currently noble)
I do not yet have a macOS build, but I am working on that right now. Once that's working the gitlab CI job will be more full featured than the GitHub build in the upstream repo.
The #eff made a wonderful project called rayhunter. It detects modern cell site simulators (aka #stingrays, fake cell towers).
But it doesn't work out of the box on Debian and when I offered a fix (commands to compile a version for Debian), they didn't like it, suggesting that everyone who uses Debian or #Ubuntu 22.04 should set up a rust development environment & compile it themselves.
The beauty of #OpenSource is that I don't have to accept that answer. I'm forking it & adding a #Debian release
https://gitlab.hax0rbana.org/public-repos/rayhunter
I'm not familiar with #Microsoft's #GitHub CI/CD system, so I'm making automated jobs to do it in #GitLab's CI. I **will** accept pull requests to also implement it in GitHub's CI/CD, and I can mirror my fork over there after I get the feature implemented.
Hopefully the upstream maintainers will accept my feature so the project is more accessible to people, especially #journalists and #activists who might not know how to get the bleeding edge #Rust toolchain.
And if it is not accepted, then people who find out about my repo can choose between downloading a release from my CI/CD or compiling it themselves.
And that's OK. Letting people choose is a good thing. When there is a difference of opinion, spinning up another fork is great.
Who knows, maybe I'll add a #Windows release as well. 😁
Yes, I'm stirring up trouble again. No, you can't stop me.
The #eff made a wonderful project called rayhunter. It detects modern cell site simulators (aka #stingrays, fake cell towers).
But it doesn't work out of the box on Debian and when I offered a fix (commands to compile a version for Debian), they didn't like it, suggesting that everyone who uses Debian or #Ubuntu 22.04 should set up a rust development environment & compile it themselves.
The beauty of #OpenSource is that I don't have to accept that answer. I'm forking it & adding a #Debian release
https://gitlab.hax0rbana.org/public-repos/rayhunter
I'm not familiar with #Microsoft's #GitHub CI/CD system, so I'm making automated jobs to do it in #GitLab's CI. I **will** accept pull requests to also implement it in GitHub's CI/CD, and I can mirror my fork over there after I get the feature implemented.
Hopefully the upstream maintainers will accept my feature so the project is more accessible to people, especially #journalists and #activists who might not know how to get the bleeding edge #Rust toolchain.
And if it is not accepted, then people who find out about my repo can choose between downloading a release from my CI/CD or compiling it themselves.
And that's OK. Letting people choose is a good thing. When there is a difference of opinion, spinning up another fork is great.
Who knows, maybe I'll add a #Windows release as well. 😁
Do you still use the official version of Firefox (not a fork) now that their new ToS have dropped?
https://video.nostr.build/e9031da420a9609a1d2b236fb54f4901e71051006200098763aff42d16324049.mp4
Wow, everyone who responded has left Mozilla's Firefox, either after the ToS drop, or earlier.
I mean, I get it, there is good reason and I'm bailing on them too, but it still sucks to see an organization that I've liked since at least Firefox 3.x go down the crapper.
I'm glad to hear people are largely going to community maintained browsers though, again, at least of the people who responded.
Do you still use the official version of Firefox (not a fork) now that their new ToS have dropped?
https://video.nostr.build/e9031da420a9609a1d2b236fb54f4901e71051006200098763aff42d16324049.mp4
More footage: https://sora.com/g/gen_01jn7fyjgweq5v1j2rhbdedw8w
Last night at Kreative House was wild
Here's a thought for you. QA jobs are going to become more important as more people jump on the vibe coding trend.
How could one demonstrate that they are more effective and efficient at doing QA than sold random person who just claims to be a talented QA engineer?
How could consumers determine who has quality QA before adopting a new technology?
What is this? I feel like I missed some big new feature that just dropped... is this in the stable channel of Graphene?
Earlier this week I had to pick a couple locks out of necessity. That's why I always have my emergency picks in my wallet. They are very small and there are only 3 picks, but if these are ever called for, despiration makes up for the lack of quality. It's amazing what you can accomplish when you have no other choice.
It's been a few years since I needed to do that.
nostr:npub16v82nr4xt62nlydtj0mtxr49r6enc5r0sl2f7cq2zwdw7q92j5gs8meqha , I may be calling on you for consult …
https://guggero.github.io/cryptography-toolkit/#!/hd-wallet
☝️ Fantastic tool. I used it a lot when I was writing tools to do these key derivations (just to confirm I fully understand the process). That'll let you do everything except use a xpub to generate more addresses.
A quick search turns up https://github.com/swan-bitcoin/xpub-tool to do that.
Use these tools to understand the concepts and then you'll be all set to implement it in your language of choice (or better yet, find a library that has already done so).
Hey nostr:nprofile1qqsplqcdmp63xzcnf7ln7faxnmkdscf6fxt53fcmtgn35uvlawhpfmgprpmhxue69uhhyetvv9ujuumwdae8gtnnda3kjctvqy28wumn8ghj7un9d3shjtnyv9kh2uewd9hszyrhwden5te0dehhxarj9emkjmn9lek5n7, you still sell hardware, yeah? I might be looking for some sticks of DDR4 (ECC, 2667MHz).
Used is fine (kinda preferred to save money, honestly). 4x16 and 2x32. Possibly more if the price is right, but probably just adding 128GB will be enough.
I want to support people like you, selling things on Nostr for bitcoin. I have my own hosting, but I'd be happy for you to be my hardware supplier. 😎
Oh, and if you wanted an air gapped key generation, you could use a seed signer to do that part.
Again, it should be simple modifications to already existing standards and code.
If you want to use bip32 to solve this problem, see this fork of this thread:
You would get a unique key for each client and could rotate keys anytime you want. For a proof of concept, the only things that should need implemented in the client are:
1. Cryptographically verifying a sub-account's identity, and
2. Auto-following new identities that pop up
That would demo the concept and then, if it gains traction, you could make the key generation more user friendly.
First, that's circular logic. Saying we're not going to implement it because other people might not implement it is just silly.
Second, using a seed and xpub does not require all clients to change their code. In fact, you could do this today with standalone tools and absolutely no code changes (example below).
Third, using an xpub would provide all the features with **less complexity**, backward compatibility, and you get a seed phrase for your identity.
Example that you could do today: Using standalone tools, generate an identity keypair and then generate sub-keys for each client. Each client gets its own unique key. Put the xpub, path, and a link to the identity npub in the profile for each client. Those who support programatically verifying the link can do so and all other clients can verify the link in the same way they do now: post a note with each authorized key on the identity account.
Imposters can claim they're sub-accounts of someone else, but the xpub won't check out and there won't be any note on the identity account saying that's a legit sub-account.
While this doesn't require any code changes, obviously it would be a better UX to have the software verify the link, auto-follow sub-accounts, and so on.
You can also choose to have multiple personalities that are linked. Maybe you use one sub-account to talk politics, one to talk about your mad ping pong skills, and another to talk about gardening. There could even be an indicator in the profile to indicate that following this sub account should not follow all the others automatically. The possibilities are only limited by our imagination.