Today I got botan2 cross compiling for x86-64 Windows (from Linux x86-64).
Why? Because I want to cross compile keepassxc and this is getting in my way.
Why do I want to cross compile keepassxc? Because I want to use that code in the signet client to import keepass v4 databases
And I want my (Linux based) CI to be able to continue to crank out windows builds. That's why.
After Botan, I'm going after argon2, and then others.
Oh and I had to build my own compiler because mxe repos are way old. So I'll probably be hitting up their mailing list to find out if someone has the ./debian directory that produced that .deb file so I can give them an updated build. If nothing else, I'd like to at least built it and put it in my own apt repo.
Yeah, I'm way down the rabbit hole on this one. And if I manage to dig myself out, I'm going to do it all over again for i686!
And I don't want to wait those extra few seconds so I spin up a fresh qube and have it on standby, because I know I'm going to need it in a few minutes. As soon as I start using that one, I spin up another fresh one in the background. 😂
It has support for the passing through GPUs to Qubes, so if you have to have a Windows qube with direct access to a GPU, you can absolutely do that.
I haven't done it myself, but I have passed through other PCI devices.
Not sure what you mean about the user interface. It has a launcher menu in the corner to start apps in various qubes, ability to easily move files from one qube to another, USB passthrough, ability to change which networking gateway is used (Tor, VPN, clearnet, other, or none), and all this without ever touching a command line.
I am having so much fun with disposable VMs (DVM) in #Qubes, it should be illegal!
I'm doing #dev work again today and when I think I have the minimal commands to reproduce an issue, I'll spin up a DVM, paste the commands and make sure I hit the problem I expected. If not, I'll poke around to fix it (install a dependency, update the PATH, etc.) and then repeat.
Takes about 8 second to spin up a fresh VM. Very rapid #development!
📡 EFF launches Rayhunter — a $20 open-source tool that helps detect cell-site simulators (aka Stingrays) used for surveillance. Big win for privacy! 🔍 #Privacy #Surveillance #OpenSource #security #cloud #infosec #cybersecurity
https://www.eff.org/deeplinks/2025/03/meet-rayhunter-new-open-source-tool-eff-detect-cellular-spying
And it now can be installed from Debian without having to compile anything too!
OK, normally when I hear about someone who doesn't know crytpography or Rust writing Rust code and rolling their own cryptographic protocol, I'd almost certainly not going to use their code... but... Wang Lu seems to be the real deal, just picking up these skills along the way. Their highly experimental hardware password manager, which is not open source hardware nor software, sounds like it's a pretty decent design. If it actually does what is described, I am impressed.
It'll be interesting to follow along and see if it turns out to be an even more hardcore password manager than the #Signet. Of course, there's no proof that any of this code exists and works, so it could all be vaporware. We won't know unless it's released (in either source of binary form).
https://blog.wang-lu.com/2025/03/cardputer-as-hardware-password-manager.html
Honestly, just playing around with it has been what's worked best for me. Go to printables and find some cool stuff and then read their comments on recommended print settings.
When you run into problems (prints not sticking to the bed, warping or whatever), look for the answers with your search engine of choice.
Once you can print out models that are pre-made, next you can get into CAD if you're so inclined. There are tons of good videos on FreCAD on yewtu.be.
Productive day today!
#gardening - I mixed about a cubic yard of soil & rice hulls, put the rain barrel back in service, and took a first pass at fixingthe gutter
#signet - documented using the qt creator IDE, fixed all compiler warnings, and improved the Windows CI/CD build pipeline
Yup, that's the one. I'm about to finish a nicer looking case for it too.

That one is my personal device on account of the imperfection in the case.
Great episode with Joel Salatin. Just wind him up and let him go. Hell, you don't even have to wind him up.
https://fountain.fm/episode/X0QtYgaapycmhWNrtqtT
nostr:nevent1qvzqqqpxquqzqnma8krmfa3hhs3jyh4cfkr5kkz7vexfpardwl6v556hdfrvfa2e9ukzel
Joel Salatin...🤔 that name sounds familiar...
/me Checks the author of the "everything I want to do is illegal" book on the coffee table literally next to me.
Oh. That's why. 😂
You're likely talking about the issue where the keys for the SQLite database were stored in plaintext on disk.
That's been fixed reasonably well on Mac. On Windows & Linux they database keys are in the OSes keychain (or Secret Service or whatever they call it) but any app running as that user can just get them in plaintext, just like they could when they were on disk in plaintext.
Signal has a history of collecting everyone's phone numbers even after usernames were finally implemented, blocking open source clients from being in the stock F-droid repos, taking years to partially fix the plaintext keys thing, not actually having public code to run a server that actually works, not allowing 3rd party clients to connect to their centralized servers and so on...
Having said that, their crypto was still legit last time I looked at the code. Metadata protection is lacking, but that's going to be true of nearly every centralized service.
I make open source hardware password managers called nostr:nprofile1qqsf3vs4hphtnaqg6ekqxg3vfkhuhetnrejt696dn6l292jm9rjvntcpzpmhxue69uhkummnw3ezumt0d5hszrnhwden5te0dehhxtnvdakz7qgawaehxw309ahx7um5wghxy6t5vdhkjmn9wgh8xmmrd9skctc65awq5.
Oh, and I maintain Ansible roles/playbooks to make self-hosting things easier.
I also grow and preserve my own food, but that's not something I sell. That's just for me. No interest in selling any of that. I'll share my experience though.
I guess I do woodshop projects from time to time too. Again, those are just for me, but I'm willing to share what I learn.
Not much going on today.
No #meshtastic #solar node updates because I'm waiting on the lower gain antennas
No #Signet cross compiling updates because I'm busy doing house projects to get ready for gardening.
No #gardening updates because the tasks are uninteresting, like level the rain barrel stand and fix the gutter.
No production server updates because a.) I was waiting on RAM, and b.) it's boring.
No test server updates because I've been procrastinating fixing it ever since it literally blew up on me last time I tried to turn it on.
But in truth, all this completely unsexy grunt work is what enables the interesting work. So I soldier on. Getting stuff done. Like a boss.
Oops. Accidentally invited a journalist to a #signal group about war planning. 🤣
I now have a better understamding of why search engines aren't pulling up any guides on how to cross compile QT apps for macOS. People generally don't do this. Even the people who frequent the QT forums aren't sure if it's possible, and that doesn't even touch the question about compiling for ARM of an x86_64 machine.
https://forum.qt.io/topic/98510/cross-compile-qt-from-linux-to-macos
I didn't realize I was trying to do something so rare.
Cross compiling is usually difficult to get set up, but that's doubly true when the target is macOS, square that if it's QT and square it again is it's a different CPU architecture.
I'm trying to grind through it, but I think it might be grinding through me instead.
I'm attempting to start with the same CPU architecture (x86_64) to minimize the number of concurrent changes. One of us will be more stubborn, and I think I'll eventually outlast the build tool, as good of a fight as they may put up.
#development #mac #linux #foss
A buddy is playing wotb AI video and so I had him make some videos of nostr:nprofile1qqsrf5h4ya83jk8u6t9jgc76h6kalz3plp9vusjpm2ygqgalqhxgp9gpzfmhxue69uhk7enxvd5xz6tw9ec82cspp4mhxue69uhkummn9ekx7mqpzpmhxue69uhkummnw3ezumrpdejqd2970s
I big shout out to the person in AntPool who mined 888888. That was a tricky one to find. 😂
Anyone else excited for 888888? 🤓 Yeah, I'm a dork
