# Install dehydrated with Homebrew LetsEncrypt/acme client implemented as a shell-script. Version 0.7.2 via Homebrew; verified from local package data. ## Install ```sh sudo av install brew:dehydrated ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install dehydrated ``` Evidence: provider-native install command ## Package facts - **Package key:** brew:dehydrated - **Package manager:** Homebrew - **Version:** 0.7.2 - **Source summary:** LetsEncrypt/acme client implemented as a shell-script - **Homepage:** - **Repository:** - **Generated:** 2026-08-03T00:40:33+00:00 ## Executables - dehydrated (alias) ## Install behavior - Bottle: not available ## Freshness - Page generated: 2026-08-03 - Package-manager version: 0.7.2 ## Project history and usage dehydrated is a shell-script ACME client for obtaining and renewing TLS certificates from ACME certificate authorities such as Let's Encrypt and ZeroSSL. ### Project history The README describes dehydrated as a relatively simple bash-compatible client that uses OpenSSL for key and certificate handling and common Unix tools such as cURL, sed, grep, awk, and mktemp for the rest. It supports ACME v1 and ACME v2, including wildcard certificates. The release history starts with v0.1.0 in April 2016, reached v0.5.0 in January 2018, and continued through v0.7.2 in May 2025. The README notes that the repository is officially maintained by ZeroSSL. ### Adoption history dehydrated became a package-manager-friendly ACME client because it is a single script with familiar Unix dependencies. Homebrew packages it, and the upstream documentation is built around editable config files, domains.txt, hooks, cron-style renewal, and existing web-server integration. ### How it is used Administrators use dehydrated to register an ACME account, list certificate names in domains.txt, configure an HTTP, DNS, or TLS-ALPN challenge, and run `dehydrated -c` from cron or another scheduler. The man page emphasizes that certificates are normally stored under the configured certificate directory and renewed regularly. ### Why package nerds care dehydrated is significant because it shows the Unix-shell version of ACME automation: no daemon, no embedded web server, and no large runtime. For packagers and sysadmins, that makes it easy to audit, patch, hook into local deployment scripts, and run on minimal systems. ### Timeline - 2016: v0.1.0 is published. - 2018: v0.5.0 is published and the man page records 2015-2018 authorship. - 2020: v0.7.0 is published. - 2025: v0.7.2 is published. ### Related projects - dehydrated belongs to the ACME client ecosystem around Let's Encrypt, ZeroSSL, OpenSSL, and web-server or DNS-provider hook scripts. ### Sources - - - - - - - - - ## Security Notes broad file, network, media, or database tool signal. generalized runtime or code generation signal. - **Geiger risk:** yellow / medium - broad file, network, media, or database tool signal - generalized runtime or code generation signal ## Configuration and credential file locations These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval. ## Configuration files - Unix: /etc/dehydrated/config, /usr/local/etc/dehydrated/config, $PWD/config, $SCRIPTDIR/config ## Credential files - Unix: ${BASEDIR}/accounts ## Combined YAML source View the package source record on GitHub. [combined/dehydrated.yml](https://github.com/automic-vault/db/blob/main/combined/dehydrated.yml) ## Sources - Nucleus package database - Geiger risk classifier - curated configuration and credential file locations - curated package history - pkgdb category and tag curation