-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add new (and better) wordlists #6
Comments
We need also wordlist for non-english users. |
Maybe the trustwords list used by pEp is an option. Sadly Volker does not support putting the trustwarts into a repo of its own: "Everybody shall use the pEpEngine" :-( |
So sorry, @htgoebel that I did not notice your hint before! These lists look really good, although they are not prefix codes. I will look deeper into them. The relevant CSV files can now be found on Thanks for the hint! |
More wordlists
We would like to provide more wordlists.
Although users can use any wordlist they want::
$ diceware mywordlist.txt $ cat /usr/share/dict/words | diceware -
we might offer some of them for convenience out-of-the-box. Typical candidates could be wordlists in other languages, the original 7776-terms wordlist from diceware.com, or others.
Register wordlists by name, not by language
As one can see from that list, it might not be convenient to offer/select wordlists by language as it is the case currently (yeah there is only one list built-in but we have a language selector at start).
Instead we could name each wordlist with arbitrary strings (something like "8k", "original", ...) and process these wordlist names in user interface.
The
--help
option should display all lists available (or we offer a special switch for that).An uncomplete collection of possible wordlist types:
Lists that provide only terms suitable for little children. These lists could be used by services that
generate passphrases for others and must make sure no one is offended by the words picked.
Support GPG-signed wordlists
Something else regarding wordlists one could consider: the wordlist format expected currently, is a file (or file-like object) with lines. All non-empty lines are treated as a word. This makes it hard for GPG-signatures or similar data sources to be processed. Especially GPG-signed files could be interesting, because we could check authenticity of a wordlist when we use it.
Support dynamic wordlists
Static files are one possibility to create a wordlist. It should be possible to create wordlists also from dynamic sources on the fly (this might even improve entropy). In that case we would need a mechanism to hide the real format of a wordlist from the core components.
Instead we would need some piece of API that allows something like
mygenerator = get_wordlist_generator(name)
and then retrieves words from this generator piece by piece.Collect wordlists from other packages by entry_points
A last thing we could support: third-party packages could provide their own wordlists for use with diceware. They might register their lists with some diceware component which, when called returns the lists. The registration and list lookup could again be done via entry points.
This last point is far from being urgent.
The text was updated successfully, but these errors were encountered: