<unnamed>

Public Key

npub1nzeptwrwh86q34nvqv3zcnd0e0jhx8nyh5t5m8475249k28yexhsmdnum9

Profile Code

nprofile1qqsf3vs4hphtnaqg6ekqxg3vfkhuhetnrejt696dn6l292jm9rjvntcpp4mhxue69uhkummn9ekx7mqppamhxue69uhkummnw3ezumt0d5q3camnwvaz7tmwdaehgu3wvf5hgcm0d9hx2u3wwdhkx6tpdsvpw6kj

Publishing to

nos.lol

nostr.mom

nostr.bitcoiner.social

Last Notes

2026-09-03 21:51:01 UTC

Just got accepted to present at @[email protected] this year. It's a case study of the theory that FOSS projects are unstoppable.
https://blossom.primal.net/b393286d1e0fca8e5d961ce210a24cdfb4570d6f3b8d6f1f0e831d152f772b25.jpg
https://blossom.primal.net/2e32eed144ff0fe6f58faba0afafbd1495360011d5de68c5f96dc852fa83c7b8.jpg
And this is my kind of conference. It's all about freedom and privacy. For example, no need to give your name & credit card details. You don't even have to register! You can just show up.
This is the cypherpunk spirit the world needs, and I'm proud to be a part of that.
https://SeaGL.org/
#freedom #FOSS #OpenHardware #OpenSource

2026-08-16 19:27:34 UTC

- reply

Disclosure: AI did not find this bug, did not fix it, and did not verify that the fix was correct and complete. I did.

2026-08-16 19:27:11 UTC

There's a new firmare update for Signet available. This one fixes a vulnerability that would allow an attacker with access to an unlocked device to add/overwrite password entries without a physical button press.
To be clear, there's no impact to the confidentality, and no impact if you never use your device on a compromised machine.
Download and updating guide links:
https://hax0rbana.org/signet/downloads.html
https://hax0rbana.org/signet/guides.html#update-firmware

2026-08-04 02:45:14 UTC

The past few years have given me a better understanding why manufacturers are seldom also retailers. And why advertising/marketing is frequently outsourced.
I mean, it makes sense on paper, but actually living it makes it crisp.
Focus, time and energy are already split between research, development, parts inventory, assembly & flashing, and product inventory.
Adding in marketing/outreach (an entire field of its own), shop setup/maintenance/fees, order fulfillment, returns and exchanges... it's a lot.
It makes more sense to focus on what you love and are good at, and do that. For some people, that's the social aspect, talking to people and such.
For me, it's engineering and NOT talking to people.
If I ever come across a fellow freedom lover who doesn't want to get bogged in technical details and just wants to put #FreedomTech into as many hands as possible, we'll make an amazing team.

2026-07-19 07:30:24 UTC

#nevent1q…9c2g
💯

2026-07-16 03:11:14 UTC

- reply

Yep, the firmware is reproducible from the published source.
Of course, if users don't compile it themselves, they'll never see that it matches. And if they do compile it, then they might as well flash their binary on there (even if it is the same as mine).
In any case, I'm doing my part. 🤓

2026-07-15 23:35:42 UTC

- reply

I do. 👋
Happy to help people level up their security. And it's all open source: hardware, firmware, and software.
https://www.takemysats.com/open-source-gadgets/products/signet-password-manager
And the page for the project is here:
https://hax0rbana.org/signet/

2026-06-15 01:32:37 UTC

About a year ago, I was considering seeing if there were any podcasts (or similar) who would be interested in open source hardware, sustainable tech, or security tools that are more practical and easier to use.
I never got around to it. Between my day job and community solidarity projects that I've become more involved in, I just never made time.
Given the choice again, I'd do the same thing, but it's a shame people don't know about, nor benefit from Signet. I don't have answers here, just thinking out loud.
I can say that my lack of public speaking doesn't indicate that the project is dead, or in jeopardy. Quite the opposite. In that same timeframe, we shipped the biggest update we've ever had: KeePass v4 database support, support for importing custom fields, and lots of behind the scenes changes (more automated builds, switched to the new KeePassXC as the importing library). None of it required anyone to buy any new hardware, as always. And there's more planned too.
I do find it interesting to better understand why software companies are constantly bolting on features and changing the user interface seemingly just to change it.
It gives them a reason to tell people about their stuff. It gives their existing users something to tell their friends. They get to make headlines and ride the social media buzz.
Projects that only change things when there's a real need and don't add a bunch of features nobody asked for... those projects don't get noticed
Fortunately, I maintain this project primarially for me, so I'm not inclined to try to keep up with the rate race. I don't have to play those games. I can play by my own rules. I can take a low time preference approach and focus on good engineering instead of marketing, outreach and public relations. And I likely will. If others like what I'm doing, I'd be happy to collaborate. If someone "steals" the design and starts selling them, more power to 'em. I'm not afraid of competition.

2026-05-02 02:24:40 UTC

New Signet client release is now available on https://hax0rbana.org/signet/downloads.html
Notable changes include:
- Supoort for importing extra fields from KeePass databases
- Support for importing KeePass v4.x database files
The other changes are things like the Windows executable being compiled automatically by my CI/CD system, so I don't have to manually go to a Windows box to compile it.

2026-04-25 03:29:07 UTC

I've got the deb building issues solved for Debian. There's an Ubuntu release (Jammy) that upgraded libbotan2 but not libgcrypt so the Debian 11 has one library that is too old and another that is too new and I think it's reversed with the .deb from Debian 12. At least something like that, I'm tooting from memory.
The solution is to build it on Jammy so it'll pick the library versions that match. I should get that done after the weekend. And I'll add in some more testing for more releases too.

2026-04-24 20:52:01 UTC

As the years march on, maintaining support for older distros becomes more complex. One version of a library is required on one release, and a different one on the next.
Most projects shy away from putting the work, even huge projects with large communities and/or corporate funding. It's a lot easier to just support the latest release.
Not Signet. I support Debian 11, both i386 and amd64. At a minimum, I will match Debian's Long Term Support commitments.
I'd like to go beyond this and match the Extended Long Term Support (ELTS), but this is challenging.
Docker doesn't keep images around forever, which is a problem for my CI/CD environment.
Debian doesn't keep their apt repos around, which is a problem for installing dependencies and build tools.
ELTS is 3rd party paid support.
While it'd be possible to run my own apt mirror and docker registry, it's a lot of work for something nobody is asking for. So for now, I match Debian's LTS policy: 5 years, then you need to upgrade your O/S and I'll keep on supporting you. 🫶

2026-04-23 15:59:02 UTC

- reply

I was able to reproduce the issue outside the CI environment. I think I know what needs to be done to clean all this up now, but I ran out of time before I got it done.
Plus I made a change to the CI runners which should prevent the Docker caching issue from recurring. Just need to get that into the Ansible scripts so it will never regress. THEN I can call it done.

2026-04-22 03:25:46 UTC

- reply

Resolved that, now on to trying to figure out why there are CMakeCache folders that are breaking the .deb build process.
This related to the new keepassxc project (in place of keepassx)
And frustratingly, this only seems to happen in the CI environment. Running the same commands on a fresh VMworks fine. So I expect it'll probably turn out to be more Docker issues. Time & effort will reveal all.

2026-04-21 05:08:45 UTC

I spent all day trying to track down some alarming PGP signature problems.
In the end, it was docker caching some file that was downloaded from the internet, as if there's no chance something online could possibly change...
Frustrating to waste time on Docker nonsense, but at least the explanation wasn't that it was detecting a compromise.
Onward.

2026-04-09 23:22:07 UTC

I've also made progress on the hardware side of the house. The current hardware is effectively USB-A only, and the new revision aims to fix that. I feel like the details are somewhat interesting on this. Perhaps that isn't true for hardware developers, but I think everyone else will enjoy, so it's story time!
I took on maintenance at hardware v1.2. It relied on a voltage regulated that was not available anymore. The journey begins...
I taught myself KiCAD and updated the design to use a different voltage regulator. The pins were reversed from the previous component, so this spawned v1.3. Exact same thing as v1.2 except it used components which were actually available.
That was OK, but the board had components on both sides, which made assembly tedious and error prone. Plus people were asking about native USB-C support. Between my desire to make these devices easier for people to build at home (myself included) and the USB-C thing, v1.4 was born.
This put all the components on the front of the board and added a USB-C connector. After a few attempts, I decided the surface-mounted USB-C connector was going to be too tedious for people to assemble, and I settled on the through-hole version.
After making a huge batch of these new boards, I discovered I made two errors:
1. I didn't connect the data pins from the A-side to the B-side. The result, you can't plug it in either way. Awkward for a USB-C connector!
2. More importantly is would ONLY work with USB-A to USB-C cables. I had wired it per the USB spec for legacy mode because the MCU only supports USB 2.0. It was only later I realized that legacy mode was referencing the cables, not the protocol.
The net result is that v1.4 hardware is basically still USB-A only. Yeah, you can put both USB ends on, but it's not going to work as most people expect.
This brings us to v1.41, which is nearly identical to v1.4, except a 56K Ω resistor was swapped out for a pair of 5.1K Ω resistors and slightly different wiring. I've hand soldered this on a prototype board and can confirm that it works properly. I updated the board and published it, but I haven't had new boards made yet. So the story continues. I'm pretty sure that they'll work as my prototype did, but there's still some chance I made a mistake in KiCAD and will have to make yet another revision before it has real USB-C support. Time will tell.
So there you have it. A behind the scenes look at hardware development and how I'm pushing to make this tech more accessible to people and adding native support for USB-C.

2026-04-09 05:09:35 UTC

I've been grinding away, doing the completely unglamorous work of maintenance and cross platform compatibility, but I did add in one little improvement.
- Switched from KeePass to KeePassXC library
- Added support for importing KeePass v4 databases
- Added support for importing extra fields from all KeePass files
All these changes were in the client software, not firmware nor hardware changes.

2026-03-18 20:34:52 UTC

I think I recently found a better way to explain the security that Signet offers:
1. Can unplug it when not in use to know your data is safe
2. Passwords are only released when the physical button is pressed
3. Lost devices can't be used w/o the device password
You don't have to be a cryptogrpher to understand these benefits.
I **am** a huge geek so I get excited to talk about the cool technical features, but I'm trying to get better at giving people the punchline instead of a huge pile of details. How'd I do?

2025-12-29 04:00:57 UTC

Finally got keepass v4 database importing working on Windows in addition to Linux.
I'd like to get some bugs fixed in MXE (the cross compiler I use to build .exe files), but I have a solution to hold me over until that happens (which may be "never").
Anyways, on to getting it to compile on macOS and then I can wrap up this feature.

2025-11-16 19:00:50 UTC

Reason #25630 that I don't get things done faster: The MXE scripts to build .deb packages are broken and after dozens of hours trying to resolve it, I haven't been able to figure it out.
I opened a ticket about it a couple weeks ago, but no replies.
https://github.com/mxe/mxe/issues/3264
This is blocking my ability to fix the CI jobs that build the Windows releases of the Signet client, which is holding up a release.
In this case, I don't think anyone who knows about these scripts is still around.
The moral of the story here is that if you can afford to help with open source software, we could really use it!
I'm not talking about money. I'm talking about project management, learning how to reproduce issues, debug them, working towards a resolution and not just being able to do these, bit actually doing them in practice.
It takes time and effort. It means being part of a community. And the reward is that the world is a better place. It's not the riches tech bros promise.

2025-11-16 07:45:36 UTC

Reason #25628 why I don't get things done faster. I had to set aside my tasks to patch reprepro so it could handle control.tar.xz files which is what are created by all of Debian's modern tools to create .deb files.
I submitted a merge request 2 weeks ago, but it hasn't been commented on, let alone reviewed or accepted.
But I've got the .deb for it on my apt repo and you can see the change and compile my version here if you want it. https://salsa.debian.org/debian/reprepro/-/merge_requests/14
Reason #25629 why I don't get things done faster. I spend time trying to get my patches upstreamed so more people can benefit from my work.
But just like my multi-year effort to get a patchlevel change in pam-u2f (from the original author and an official release, not a patch I wrote), it seems I'm being ghosted again.
Last time around, I reached out to the maintainer via email, the former maintainer, another person in auth, the maintainer via IRC, tried to get a mentor in IRC... all failed.

2025-10-30 23:41:33 UTC

Today I helped a user compile the #signet client for an #ARM based version of #MacOS.
It required changing a couple library paths, and I've already upstreamed those changes to the latest copy of the repo.
This was something I've been wanted to test for a long time now, but I don't have the hardware and it's hard to get the time of someone who does. But we did it. Together.
Hardware secured encryption is #cipherpunk meets #cyberpunk ✊
signet - And physical access is within our threat model!
Contrast that to the way hardware security work when made by Intel, AMD or ARM:
https://infosec.exchange/@dangoodin/115459944536890363

2025-09-13 21:27:36 UTC

- reply

There's going to be another bugfix I plan on testing, hopefully in the next week or two. I'll post pics and the results, even if the fix doesn't work.
#nevent1q…jtnw

2025-09-10 08:16:59 UTC

Well, that was... educational. Not only does v1.4 require plugging in the USB-C cable the right way, but it also only works with USB-A to USB-C cables (not C-to-C).
Everything related to the USB-A connector is fine, and previous revisions didn't have a USB-C connector at all, so this version is still an improvement, but not as much of an improvement as I was aiming for.
I've read a lot about USB-C cables and USB 3.1 and I think the next rev will fix both problems. Version 1.41, here we come.

2025-09-10 02:51:02 UTC

This is what #patching a #bug in #hardware looks like.
First attempt: I made things worse
Second attempt (not pictured): it's as if I did nothing
Third attempt: fixed!
https://image.nostr.build/19323510a7724fa6f88943b274e562c2afe1bb097d0290b8d2cc3c6012ce653e.jpg
https://image.nostr.build/e3c5d1d52302ada5f6fff9168140dfd3b8de4e232c59570267b31ee442a96a69.jpg
https://image.nostr.build/4f6a81327c9525f0bae4ef1a1a162a931805fba656d541a02234181537c4bd80.jpg
If you don't know how big a US dime is, the punchline here is that these wires are very small, tedious to work with and will probably come loose at the slightest provocation. #USBC
And a shout out to those who know exactly what happened here without any explanation required. I goofed. Next rev will be better. #OpenHardware #electronics #diy

2025-08-31 23:13:40 UTC

- reply

Also, if someone wants to just rip off my design and make and sell Signets themselves, there's nothing stopping you. The license allows for it, and I'm not going to shy away from competition.
Of course, if you do, it's on you to deal with fuck ups in manufacturing, soldering on USB connectors, flashing, testing each unit, setting up one or more stores, and the worst thing of all: marketing.
If that sounds good to you, go for it. If you want to share these burdens, partner with me.

2025-08-31 23:10:00 UTC

BTW, I am still looking for a reseller in Europe. If you or someone you know is there and wants to make open source security hardware available to people, reach out to me.
The cost of shipping is Europeans €25-30 per order, but beyond that, there's a risk with every single order that something will go wrong in customs (on either end), and that cost would double just to give it a second attempt!
That's why I don't offer international shipping. Because I end up losing money if 1 out of 10 orders requires re-shipping. Meanwhile the customer has to pay almost as much for shipping as the device. I want to slash that cost dramatically, and obviously I'll pass those savongs onto the user.
Here's what I want to do:
A.) Ship a batch of signets to someone in Europe, maybe 10x to start
B.) Orders to europeans ship from there
I'd prefer the reseller sells them, but I could enable shipping in my store if that's preferable.
We can work out something to balance the risk of me shipping off signets and never hearing anything from them again, and the reseller buying these from me and then being stuck with them if they're not selling. We can work it out, and a return/exchange process too. We got this, I just need a little help.

2025-08-30 20:22:13 UTC

- reply

The only other change in v1.4 is making assembly easier by making it a single sided board. It's just that and the USB-C, everything else is functionally identical.
#nevent1q…xj0t

2025-08-30 05:38:14 UTC

New #hardware revision is in the works... #Signet v1.4
https://image.nostr.build/f85d5700f0242966b35f188a39d9f79c81b6893934a8ae8953961533eac987ff.jpg
Native USB-C connector. No more need for those A-to-C adapters.
I just ordered more parts to make more of them. I'm excited. #OpenHardware for life, yo!

2025-08-03 21:43:02 UTC

- reply

The reason this helps the Signet project is because it means being able to develop the code without having to wait for hours to compile the cross compiler and cross compile the libraries. Instead, we have a fast, reproducible way to get the the libraries that are either grossly outdated in the official repo, or don't have any package at all in that repo.
#SelfSufficency #OpenSource #dev
#nevent1q…elru

2025-08-03 21:31:47 UTC

Last night I found a lua script in the MXE repo that allows me to create .deb packages. This is something I asked for a couple months ago and never got any reply.
This is a huge deal, not just for me, but for everyone who uses the MXE cross compiler to make Windows executables from Linux because the official repos have not been updated in a decade and they won't compile some modern software.
Soon, I will have an update version of gcc in my apt repo for everyone.
I am also going to be adding documentation on how people can compile the .deb packages themselves. The ones in my repo will be signed by me, but trusting me should not be a requirement.

2025-06-08 05:00:08 UTC

Trying out Plebian Market. The censors won't let me call the signet a password manager. Password is a forbidden word. But I can say password on nostr all day long. Password password password! Take that censors!
https://plebeian.market/products/30018:86419b2979bbe726b8bc966e8e6402da4509d64ed15a3a6b12abc14b0c29d124:signet-be5bw8oj89

2025-04-29 21:53:29 UTC

I finally have a partial answer to the question "how long will a #Signet last?"
Previously, we had never seen one wear out, but after 7.5 years, most of which was daily use, my 2017 Signet started having intermittent problems with the USB connector. I had to jiggle it to get it to work.
7+ years is better than you'll get from any commercial company, but here's the real kicker...
I replaced the USB connector and it works reliably again! 💯
The part of the question about how long it will last which is left unanswered is: how long will it last after one simple repair?
Any #Makerspace or #Hackerspace can help you make this #repair, even if you don't have any experience with #electronics. The USB connector costs less than a dollar and the space might even have some lying around they'd be willing go give it to you for free.
This is how gadgets should be. Not disposable, but long lasting AND repairable.
#environmentalism #sustainability #RightToRepair #FOSS #OpenHardware #sustainible

2025-04-27 21:40:18 UTC

Achievement unlocked: get an ad in the back of the latest 2600 magazine.
May all the cypherpunks have the tools they want, not merely the tools companies are willing to sell to them. 🤘😈

2025-04-12 22:54:30 UTC

I am happy to announce the release of a new #signet case (and more colors)! All the same hardware inside, it's just a new look.
There are a couple slight variations:
- snap together vs screw together, and
- I have one without a keyloop
What do you think? Prefer the cleaner look to the more functional option of having a keyloop? Want other colors? Let me know.
More pics are available on the Artisans Cooperative's store:
https://artisans.coop/products/signet
I'm going to update my personal store soon, but I am going to spin up my own #nostr relay so it will be more stable. Had someone send money into a black hole because a relay timed out.
At some point I will probably also update the store to DM me the secret *before* having the person send money. That way this can't happen again, regardless of any timeouts. I think the personal nostr notification already happens after payment, so that should already be good.

2025-03-29 00:14:41 UTC

Working on an update to the #signet client so it can import the Keepass 4.x databases (currently it can do up to and including 3.
x).
It compiles and works on Linux, but in order to be accepted it also needs to do so on macOS and Windows, and cross compiling the Windows executables from Linux needs to work for both 32- and 64-bit versions.
The keepassxc project has a bunch of dependencies, which is making this difficult. The libraries aren't packaged up elsewhere like they are on Debian. 🫤

2025-03-03 04:03:09 UTC

- reply

It feels so good to have this pipeline going. It's like a burden has been lifted.
macOS is on my list for the future. Looks like osxcross is the tool people are gravitating towards. 🧐

2025-03-02 06:49:28 UTC

Just managed to get a cross compiler set up so I can build #Windows executables from #Linux.
While it's unlikely that anyone else will care about this #development, it means I can have Windows builds in the CI/CD. This will save me a ton of time when cutting releases.
https://gitlab.hax0rbana.org/signet/signet-client
Currently in it's own branch, but if it builds correctly, and passes manusl testing on a Windows machine, I'll merge it into trunk. Steal it as an example if you wish.
#devops #OpenSource #security #FOSS

2025-02-25 00:01:12 UTC

We now have a FAQ on the main Signet page.
https://hax0rbana.org/signet
Thanks to the people who have asked questions. I'll continue to try to improve the documentation and make the hardware and software easier to use.

2025-02-24 06:18:04 UTC

Good news: we are helping to get a bug fixed in #QubesOS. It looks like the upcoming 4.3 will allow attaching a hidraw device on the first try.
That means no workarounds required to use Signet on Qubes, and it'll likely fix other devices too.
(I've been using mine with Qubes for years, but it'll be nice to not have to enable usb-reset-on-attach anymore)

2025-01-06 21:24:52 UTC

Thinking about checking out #podcasts who might like to have me on as a guest.
Anyone have any recommendations?
Any podcasts out there who cater to people getting interested in #privacy or #security? Or maybe an #OpenSource podcast where I could tell the story of how #unstoppable this project has been?
#signet #FreedomTech

2024-12-31 05:44:50 UTC

Signet finally has it's own account. Now you can follow this account any just get Signet updates and not have to wade through all @nprofile…uctz's posts about meshtastic, preserving homegrown food and whatnot. 😂
#OpenSource #hardware #FOSS #OpenHardware #FLOSS #security #privacy #electronics