Skip to content
/ dictpw Public

Generate password from dictionary with BSD licensing and practices

License

Notifications You must be signed in to change notification settings

guijan/dictpw

Repository files navigation

Dictpw - generate password from dictionary

Dictpw randomly picks 5 words off a 7776-word dictionary and prints them with a dot between each word. This is the Diceware method of password generation from the command line.

Which of the following 2 passwords is easier to memorize?

computer.stuffy.dexterity.carve.wife
J#2%Q*PDfNI

Analysis

There are 7776^5 or 28430288029929701376 possible passwords using dictpw's default word count. There are (23+23+10+10)^10 or 1568336880910795776 possible passwords in a random 10 character password composed of uppercase characters, lowercase characters, digits, and the symbols on top of each digit on the keyboard, or 18 times less possible passwords. Dictpw sits between a 10 and 11 character long password of such a scheme by default.

Build instructions

Dictpw depends on Meson, a C compiler, and a POSIX-like or Windows operating system.

Install Meson, and follow the build instructions:

meson setup build
meson compile -C build

By default, dictpw will use the system's BSD functions if they are present, attempt to link against an installed libbsd if they're not present, or fall back to building and statically linking libobsd if all else fails.

The binary will be in build/dictpw.

Custom dictionary

By default, dictpw uses the EFF's long word list. You can specify a custom dictionary by setting the dict option with Meson. A dictionary is a file with one word per line.

Example

foo@bar ~
$ build/dictpw
canary.gnat.uncross.waking.expose
foo@bar ~
$ build/dictpw -n4
chummy.iguana.outsider.yearling

Windows support

Build from MSYS2

Install MSYS2 and follow the installation instructions; make sure to read the MSYS2-Introduction page after completing the installation instructions-failure to do so may break your MSYS2 installation.

The rest of this section describes a MINGW64 build.

Install the dependencies:

foo@bar MSYS ~
$ pacman --noconfirm -S git groff mingw-w64-x86_64-gcc mingw-w64-x86_64-meson \
    mingw-w64-x86_64-ninja mingw-w64-x86_64-nsis mingw-w64-x86_64-dos2unix

Now start the MINGW64 environment, and enter the directory to which you downloaded the dictpw sources. Produce the installer for a release build:

foo@bar MINGW64 ~/dictpw
$ meson setup build
foo@bar MINGW64 ~/dictpw
$ sh dictpw_installer.sh

MSYS environment build instructions

Building releases with the MSYS compatibility layer is also supported. The process is the same, except the dependencies are different:

foo@bar MSYS
$ pacman --noconfirm -S dos2unix git groff gcc meson ninja mingw-w64-x86_64-nsis

Obviously, you don't need to enter a different environment to build the MSYS version.

CLANG64 environment build instructions

The CLANG64 build process, too, only differs from the MINGW64 build process in the dependency list:

foo@bar MSYS
$ pacman --noconfirm -S git groff mingw-w64-clang-x86_64-clang \
    mingw-w64-clang-x86_64-dos2unix mingw-w64-clang-x86_64-meson \
    mingw-w64-clang-x86_64-ninja mingw-w64-x86_64-nsis

Make sure to enter the CLANG64 environment after installing the dependencies and before following the build instructions.

Notice that no matter the MSYS2 environment you're building dictpw in, the dependencies are always the environment's version of the same packages-except you must install the MINGW64 NSIS for environments missing a NSIS package.

Others

Dictpw builds on all of MSYS2's environments. MINGW64 and MINGW32 are the most stable MSYS2 environments, therefore they are the only supported environments. The build is kept in working order in all the others purely for the sake of portability.

Build from Visual Studio

Native build

Open up cmd and install the dependencies via Chocolatey:

C:\Users\foo>choco install -y groff strawberryperl nsis meson
C:\Users\foo>refreshenv

cd into the directory to which you downloaded the sources and build the project:

C:\Users\foo\dictpw>meson setup --backend=vs build
C:\Users\foo\dictpw>meson compile -C build

Make the installer:

C:\Users\foo\dictpw>makensis dictpw.nsi

The Windows on Arm64 installer can't be compiled natively because NSIS doesn't support Arm64 installers.

Additionally, please note that NSIS doesn't distribute 64-bit builds of makensis, so you have to compile your own. There's no support for installing the 64-bit version with a 32-bit installer.

Cross compile to Arm64 from x64

This is the only way to make an Arm64 installer. The installer is x64 and runs on Arm64 through Windows' x64 emulation, but the binaries it installs are native.

Change the build step to this:

C:\Users\foo\dictpw>meson setup --backend=vs ^
    --cross-file=.github/workflows/meson-vs-aarch64.txt build
C:\Users\foo\dictpw>meson compile -C build

Windows example

Unfortunately, Microsoft hasn't provided a proper way to install command line utilities to Windows. The installer registers the .exe in the Windows Registry which allows running the program from cmd using the start command:

C:\Users\foo>start /b /wait dictpw
unusual.skewer.swirl.whinny.rogue

Keep in mind the /b and /wait flags are necessary: they tell cmd.exe not to start another cmd.exe, and to wait for the program's exit.

Windows documentation

The installer also installs the manual. Check dictpw.txt inside the installation directory.