An encrypted, self-repairing archiver with post-quantum protection and optional limits on how long and how often an archive can be opened.
giz packs files and folders into a single encrypted archive (a .giz file), much as zip or 7-Zip do, but built around security first and size second.
A restricted archive depends on the giz service at api.gen.uk, which holds one piece of its key and enforces the limits. An unrestricted archive never contacts anything.
giz is designed to resist a future quantum computer, including an attacker who records everything today and decrypts it later.
api.gen.uk cannot be reached, a restricted archive cannot be opened until it can.AaaaaaAaAaAaaA! is refused while a passphrase of four unrelated words is accepted. Generated passwords (160 random bits) are always accepted.The encryption in giz is far stronger than any password people are likely to choose, so in practice an archive is exactly as safe as its passwords and the way they are passed on.
Let giz choose the extract password. --extract-pass-gen produces 160 random bits as 32 characters in groups of four, such as 4JAP-DASE-ZG4B-XF2B-8DYG-3KPA-XXZJ-6M66. It leaves out the easily confused letters I, L, O and U, so it can be read aloud a group at a time.
Strength comes from randomness, not appearance. What matters is how many possibilities an attacker would have to try, and that depends on how the password was chosen. Cracking tools model people: they try slogans, names, dates, common phrases, keyboard runs, letter-for-symbol swaps, and capitals, symbols and small numbers in the usual places. A password a person chose is guessed by guessing the person.
| Password | How it was chosen | Strength |
|---|---|---|
test | By a person | About 7 bits: guessed instantly |
Password123! | By a person | About 15 bits |
EveryLittleHelps!26 | By a person: a slogan plus decoration | About 25 bits |
AaaaaaAaAaAaaA! | By a person: long, but a pattern | About 32 bits |
| 10 random keyboard characters | By a computer | About 66 bits |
5 random words, such as harbour violet tumble lantern meadow | By a computer | About 65 bits |
| A giz-generated password | By giz | 160 bits |
Dictionary words are only weak when a person picks them. Five words drawn at random from a list of 7,776 are as strong as ten random keyboard characters, even when the attacker knows the list, and far easier to say and type. If you use words, they must be picked at random (dice work) and used exactly as drawn: rearranging them into a sentence or swapping one for a nicer word brings human choice back.
The weaker password decides. Either password opens the archive, so a strong create password does nothing for an archive with a weak extract password. giz refuses any password you choose yourself whose estimated strength is below 50 bits. Treat that as a safety net, not a guarantee: the estimate catches the obviously weak, but it does not know every common phrase and can rate a person's clever invention more highly than an attacker would.
Keep the two passwords apart. The create password is yours alone. Use a different extract password for each archive and each recipient, so one careless recipient exposes only one archive.
Never send the password the same way as the archive. If the archive goes by email, the password goes by phone, video call, text message or in person. Someone who intercepts one channel then has only half of what they need.
Use a restricted archive for anything that matters. Nothing in a restricted archive can confirm a guess on its own: every guess has to go to the giz service, which slows repeated attempts down to a few dozen a day and records each one in the archive's log. A short lifetime and a low extraction limit (--days 7 --extractions 2, say) mean that a password which is intercepted, overheard or carelessly forwarded soon opens nothing at all.
On a call:
Ask the recipient to use it, not keep it. They should not forward it by email, paste it into a shared document or leave it on a note. With a low extraction limit, once they have opened the archive the password is spent anyway.
Agreeing references in advance works too. People who already share context can pass a password without ever stating it: "the date we agreed", the last line of an email that means something only to the recipient. This is sound, provided the agreement itself was made in person or by another route, and the exact form (2000-08-17, not 17/08/2000) is settled in advance, because every byte must match.
If you suspect interception, check giz log for failed attempts (bad_token). An archive cannot be withdrawn once made, so send a new archive with a new extract password, and rely on the original's limits to close it. This is another reason to keep lifetimes short.
Download the giz binary for your platform from the giz product page and copy it onto your path, for example /usr/local/bin on macOS or Linux. To create archives, install your licence once:
giz licence install --licence-file licence.txt
giz licence show
giz create reports.giz reports/ --create-pass-gen --extract-pass-gen
This stores the reports folder and prints two generated passwords. Keep the create password; send the extract password to the recipient by a different route from the archive itself.
A folder named with a trailing slash (reports/) stores its contents; without one (reports) it is stored under its own name. Without password options, giz prompts for each password twice.
giz create contract.giz contract.pdf --days 14 --extractions 3 --receipt contract.rcpt
The archive can be opened at most 3 times in the next 14 days, whichever runs out first. The optional receipt is a small file that, with the create password, lets you check the status and log after you have sent the archive away. It cannot open the archive.
giz list contract.giz
giz extract contract.giz -d out/
giz extract contract.giz -d out/ contract.pdf # just one entry
giz asks for "password": either password works. Existing files are not overwritten unless you add --overwrite. On a restricted archive, each extract or list with the extract password counts as one extraction; opening with the create password is never counted.
giz info contract.giz # visible details, no password needed
giz status contract.giz # days and extractions left
giz log contract.rcpt # who opened it, when and from where (create password)
giz test contract.giz # checks for damage, no password needed
giz test contract.giz --full # also decrypts and verifies every file
giz add reports.giz extra.xlsx
giz remove reports.giz old/
giz freshen reports.giz --from reports/
freshen replaces any file whose copy in the given folder is newer. Each of these needs the create password and produces a new archive with a new ID and a new extract password. The original keeps working for anyone who already holds it until its own limits run out. A restricted archive can only be changed while it is still live.
Extraction repairs damage automatically when it can. To write a repaired copy:
giz repair damaged.giz -o repaired.giz
Repair needs no password. If the damage is greater than the recovery records can cover, giz says so and the archive cannot be saved.
Each password can come from one of these sources:
| Source | Extract password | Create password |
|---|---|---|
| Typed on the command line | --extract-pass VALUE | --create-pass VALUE |
| An environment variable | --extract-pass-env NAME | --create-pass-env NAME |
| A file | --extract-pass-file PATH | --create-pass-file PATH |
| Standard input | --extract-pass-stdin | --create-pass-stdin |
| Generated by giz | --extract-pass-gen | --create-pass-gen |
| Prompt | when no source is given |
A password typed on the command line can be seen by other users of the same machine while giz runs, so prefer the other sources on shared systems.
The two passwords must differ, and a password you choose must pass the strength check described above. Passwords are used exactly as given. For a password that must survive any keyboard, system or language setting, or one that is binary, give it in hex with --hex:
giz extract archive.giz --hex --extract-pass 54657374
--hex applies to every password in that command. 54657374 is the same password as Test.
--json, --sh and --env give machine-readable output; --secrets-file PATH writes it to a new file readable only by you instead of the screen.
eval "$(giz create weekly.giz /data/reports/ --create-pass-env GIZ_OWNER_PASS \
--extract-pass-gen --days 30 --sh)"
echo "Send $GIZ_ARCHIVE, extract password $GIZ_EXTRACT_PASS"
| Variable | Meaning |
|---|---|
GIZ_ARCHIVE | Archive path |
GIZ_ID | Archive ID |
GIZ_TYPE | restricted or unrestricted |
GIZ_EXPIRES | Expiry, ISO 8601 UTC |
GIZ_EXTRACTIONS | Extraction limit |
GIZ_EXTRACT_PASS, GIZ_CREATE_PASS | Passwords, when generated or with --hex |
GIZ_STATE, GIZ_DAYS_LEFT, GIZ_EXTRACTIONS_LEFT | From status |
If you capture output in a temporary file, delete it once the passwords have been used.
| Option | Default | |
|---|---|---|
--days N, --extractions N | Makes the archive restricted | |
--suite cascade|xchacha20|aes256 | cascade | Cipher |
--compress zstd|xz|none, --level N | zstd, 19 | Compression |
--recovery PCT | 10 | Recovery records, 0 to 100% |
--pad padme|none | padme | Size padding |
--creator-name, --creator-email, --creator-im, --creator-url, --creator-phone | none | Your contact details, encrypted, readable with either password (for a restricted archive, only while it is live) |
--weak-pass-ok | off | Accept a chosen password below the strength minimum |
--receipt PATH | none | Write a receipt |
--follow-symlinks | off | Store what links point to, not the links |
Defaults can be set in ~/.config/giz/config on Linux, ~/Library/Application Support/giz/config on macOS, or %AppData%\giz\config on Windows, one option = value per line, for example creator-email = ops@example.com. Passwords cannot be set there.
| Code | Meaning |
|---|---|
| 0 | Success |
| 1 | General error |
| 2 | Usage error |
| 3 | Wrong password |
| 4 | Archive expired |
| 5 | Extractions used up |
| 6 | Damaged beyond repair |
| 7 | A newer giz is needed |
| 8 | Service unreachable |
| 9 | Licence missing, invalid or refused |
| 10 | Too many failed attempts, try later |