minisign VS mkp224o

There are alternatives, minisign and signify.

You don't have to attach identities to public and private keys. If all you need it for is signing, then check out minisign.

If you need signatures, minisign is a similar hard-to-misuse program.

In your case, use a tool such as https://jedisct1.github.io/minisign/ to do signing/verification. GPG is another choice which is very common. It will produce a "signature" which can be embedded alongside your posts verifying that the text of the post was endorsed by someone bearing the given public key.

Claiming it's not ancient because Linux desktop distributions still use it for signing packages is a very odd argument. Most Cryptography experts (note: I'm not talking about programmers, IT professionals or people who know a thing or two about cryptography, I mean actual cryptographers) would agree that we should start using something like signify or minisign instead of the bloated mess that is GPG for signing package repositories.

minisign\ (5 comments)

mkp224o has worked fine for me. Older tools like Shallot and Eschalot don't support v3 addresses, and so are no longer usable.

I’m hosting a site on a Raspberry Pi 4B (8GB Ram) with Nginx. I wanted to make it accessible on tor with a custom vanity address so I used a program called mkp224o to generate an address.

I thought that it would be cool to have a vanity v3 domain of some kind, so I've used mkp224o to generate one (bitcoinABC...DEF.onion, from now on I'll refer to this as .onion

https://gitlab.torproject.org/tpo/onion-services/onionmine based on https://github.com/cathugger/mkp224o/

Yup, https://github.com/cathugger/mkp224o was used. I'll props https://gitlab.torproject.org/tpo/onion-services/onionmine as well which is a new project to consolidate the entire minting process.

So I realized that I could give a custom private key to get a custom .onion address. Then I used mkp224o to brute force some

mkp224o