Luhn Validator
Check any number against the Luhn checksum and see the working.
Generate .htpasswd lines with bcrypt, APR1-MD5 or SHA-1.
Put it outside the document root. A .htpasswd file inside the served directory can be downloaded.
The Htpasswd Generator builds .htpasswd lines with bcrypt, Apache’s APR1-MD5 or SHA-1, accumulates several users into one file, and generates the Apache and nginx configuration that goes with it.
A .htpasswd file is one line per user: the username, a colon, and a hashed password. This generates those lines with any of the three hashes that matter, and builds up a multi-user file as you add entries.
bcrypt is the right choice and what Apache 2.4 and nginx both accept. APR1-MD5 — the $apr1$ format — is Apache's own and still required by some older configurations, so it is here, correctly implemented rather than approximated. SHA-1 is included because it appears in old files, with a clear warning that it is unsalted and should be replaced. The matching Apache and nginx configuration blocks are generated alongside, since the file alone does nothing.
Apache’s $apr1$ hash is implemented properly — a thousand rounds of MD5 with its own peculiar schedule — not approximated.
The right choice for any current Apache or nginx, with the older formats available only when something forces them.
Add as many users as you need and the whole file is built up, one line each.
The Apache directory block and the nginx location block are generated too, since the file alone does nothing.
The page is clear that the file belongs outside the document root, which is the mistake that makes it pointless.
Add as many users as you need; each becomes a line.
bcrypt unless something forces otherwise. APR1 for older Apache, SHA-1 only for legacy files.
The complete .htpasswd contents, one user per line.
Apache and nginx blocks are generated to go with it.
bcrypt. Apache has supported it since 2.4 and nginx accepts it too. APR1-MD5 only if you are on something old enough to require it, and SHA-1 only when editing a file that already uses it.
Anywhere the web server can read and the public cannot — outside the document root. Putting it inside the served directory is a common and serious mistake.
Yes, through auth_basic_user_file. It accepts bcrypt and APR1 formats, so a file generated here works for both servers without modification.
No. Hashing happens in your browser, including bcrypt. Nothing is transmitted, though a password typed into any web page is worth treating as exposed.
What people who use the Htpasswd Generator think of it. Reviews come from visitors and are posted as written.
No ratings yet
Yours would be the first.
0 reviews
Newest first
No reviews yet
Be the first to rate the Htpasswd Generator. It takes half a minute and no account.
Write the first reviewCheck any number against the Luhn checksum and see the working.
Encode and decode Base58 in the Bitcoin, Ripple or Flickr alphabets.
Serialise a JSON object into a percent-encoded URL query string.
Work out a subnet: network, broadcast, host range and usable count.
Re-indent JavaScript, with strings and regular expressions left alone.
Convert JSON into XML, with control over attributes, arrays and the root element.
Build CSS keyframe animations and watch them run as you edit.
Generate deterministic UUIDs from a namespace and a name.