As many of you know, I recently added Github OAuth sign-in. It's super slick BTW now that parties exist. Logging in to another location is just two clicks and no typing.
Click here if you want to bind your account to your Github.

But the advantages and disadvantages of different types of sign-ins came up, and the weaknesses of passwords. Passwords require you to trust that the site administrator is storing hashes correctly with something like bcrypt or hashing at all. You also have to come up with unique passwords for all of your sites, which basically requires an external password manager if you are doing it right regardless.

I had coded into the sign-in system I use for all of my sites support for sign-in in with bitcoin signatures. The resolvable downside is that since I wrote that code back when bitcoin was new, bitcoin wallets have gone from the direction of everyone having a single bitcoin address to having hundreds of rotating addresses. This isn't ideal for maintaining an address that represents your identity.

So the solution was to create a Bitcoin non-wallet. It has some of the features of a Bitcoin wallet, while lacking 90% of them. It's only job is signing, managing your identities if you want more than one, and keeping your private keys secure. It doesn't need to know what a transaction is, know what Merkle trees are, or touch a blockchain.

The application sits somewhere between a bitcoin wallet and a password manager.

Here is the Linux version:
https://submatrix.net/z/bitcoinsigner-1.0.0.AppImage

I'll add the Windows version the second I get that compiled.

I need to add the UI here to use bitcoin sign-in. I'm honestly hoping more sites adopt it. It also has advantages over Oauth in that it doesn't give trust to a third party to continue to allow you to use your other accounts, and doesn't cause a potential exchange of permissions across sites, or tell any site who you are on another site. It makes it impossible for a website to mismanage or leak your password. It operates on zero-trust.