You can download a pre-compiled build from the GitHub Releases page.

Or you can build it from source:

go install github.com/innix/shrek/cmd/shrek@latest

This will place the compiled Shrek binary in your $GOPATH/bin directory.

Shrek is a single binary that is normally used via the CLI. The program takes 1 or more filters as arguments.

# Generate an address that starts with "food":
shrek food

# Generate an address that starts with "food" and ends with "xid":
shrek food:xid

# Generate an address that starts with "food" and ends with "xid", or starts with "barn":
shrek food:xid barn

# Generate an address that ends with "2ayd".
shrek :2ayd

# Shrek can search for the start of an onion address much faster than the end of the
# address. Therefore, it is recommended that the filters you use have a bigger start
# filter and a smaller (or zero) end filter.

To see full usage, use the help flag -h:

shrek -h

You can run Shrek in Docker by pulling a pre-built image from Docker Hub or by building an image locally.

There's no need to run docker pull directly, because docker run will automatically download the image from Docker Hub if it isn't found locally. So you can save a step and run Shrek with a one-liner:

docker run --rm -it \
    -v "$PWD/generated":/app/generated \
    innix/shrek:latest \
    -n 3 food:ad barn:yd

Build the Docker image locally using the Dockerfile:

docker build -t shrek:latest .

Then run a new container using the locally built image:

docker run --rm -it \
    -v "$PWD/generated":/app/generated \
    shrek:latest \
    -n 3 food:ad barn:yd

When running Shrek in a container, you pass arguments to it by placing them at the very end of the docker run command. In the example commands above, the arguments -n 3 food:ad barn:yd are passed to the Shrek binary.

The Docker image configures Shrek to save found .onion addresses to the directory /app/generated/ in the container's file system. To access that directory from the host, you need to create a shared volume using Docker's -v argument. In the above examples, the -v argument will allow the host to access the container's directory by browsing to $PWD/generated.

If you're getting a permission error when trying to access the generated directory on the host, take a look at this FAQ.

You can use Shrek as a library in your Go code. Add it to your go.mod file by running this in your project root:

go get github.com/innix/shrek

Here's an example of using Shrek to find an address using a start-end pattern and saving it to disk:

package main

import (
	"context"
	"fmt"

	"github.com/innix/shrek"
)

func main() {
	// Brute-force find a hostname that starts with "foo" and ends with "id".
	addr, err := shrek.MineOnionHostName(context.Background(), nil, shrek.StartEndMatcher{
		Start: []byte("foo"),
		End:   []byte("id"),
	})
	if err != nil {
		panic(err)
	}

	// Save hostname and the public/secret keys to disk.
	fmt.Printf("Onion address %q found, saving to file system.\n", addr.HostNameString())
	err = shrek.SaveOnionAddress("output_dir", addr)
	if err != nil {
		panic(err)
	}
}

More comprehensive examples of how to use Shrek as a library can be found in the examples directory.

This project is under active development and hasn't reached v1.0 yet. Therefore the public API is not fully stable and may contain breaking changes as new versions are released. If you're using Shrek as a package in your code and an update breaks it, feel free to open an issue and a contributor will help you out.

Once Shrek reaches v1.0, the API will stabilize and any new changes will not break your existing code.

Shrek is the fastest .onion vanity address generator written in Go (at time of writing), but it's still slow compared to the mature and highly optimized mkp224o program. There are optimizations that could be made to Shrek to improve its performance. Contributions are welcome and encouraged. Feel free to open an issue/discussion to share your thoughts and ideas, or submit a pull request with your optimization.

The primary goal of Shrek is to be an easy to use CLI program for regular users and library for Go developers, not to be the fastest program out there. It should be able to run on every major platform that Go supports. Use of cgo or other complicated build processes should be avoided.

No. They were already deprecated at the time Shrek was first released, so there didn't seem any point supporting them. There are no plans to add them as a feature.

Sure. Use the --format basic flag when running the program to keep things simple. You can also run shrek --help to see a list of all possible formatting options; maybe you'll find one you like.

There are example projects that show how to use Shrek and Bine together.

But to put it simply, all you need to do is convert Shrek's OnionAddress into Bine's KeyPair. See this code example:

package main

import (
    "github.com/cretz/bine/tor"
    "github.com/cretz/bine/torutil/ed25519"
    "github.com/innix/shrek"
)

func main() {
    // Generate any address, the value doesn't matter for this demo.
    addr, err := shrek.GenerateOnionAddress(nil)
    if err != nil {
        panic(err)
    }

    // Or read a previously generated address that was saved to disk with SaveOnionAddress.
    // addr, err := shrek.ReadOnionAddress("./addrs/bqyql3bq532kzihcmp3c6lb6id.onion/")
    // if err != nil {
    //     panic(err)
    // }

    // Take the private key from Shrek's OnionAddress and turn it into an ed25519.KeyPair
    // that the Bine library can understand.
    keyPair := ed25519.PrivateKey(addr.SecretKey).KeyPair()

    // Now you can use the KeyPair in Bine as you normally would, e.g. with ListenConf:
    listenConf := &tor.ListenConf{
        Key: keyPair,
    }
}

If the directory (or any of the sub-directories) were created by the Shrek process running in the Docker container, they will be owned by the root user that is running the Shrek process. You need to change ownership of the directory back to your user, which can be done by running the chown command:

sudo chown -R $USER "$PWD/generated"

Onions have layers, ogres have layers.

This project has no affiliation with the creators of the Shrek franchise. It's just a pop culture reference joke.

Shrek is distributed under the terms of the MIT License (see LICENSE).