htpasswd (Mixed Algorithms) — SAMPLE
Multi-user SAMPLE htpasswd mixing bcrypt, APR1, and {SHA} lines for algorithm-detection tests.
novus:$2y$10$N9qo8uLOickgx2ZMRZoMyeIjZAgcfl7p92ldGxad68LJZdL17lhWy
alice:$apr1$r31.....$HqJZimcKQFAMIsodAhFCN0
bob:{SHA}5en6G6MezRroT3XKqkdPOmY/BfQ=
Specifications
- Algorithms
- bcrypt,apr1,sha
- Users
- 3
- Sample Only
- true
Testing contract
Expected to pass- Scenario
- Exercise htpasswd (Mixed Algorithms) — SAMPLE in its htpasswd workflow. Multi-user SAMPLE htpasswd mixing bcrypt, APR1, and {SHA} lines for algorithm-detection tests.
- Expected result
- 3 text lines, decoded as UTF-8; first nonempty line is 'novus:$2y$10$N9qo8uLOickgx2ZMRZoMyeIjZAgcfl7p92ldGxad68LJZdL17lhWy'. Declared feature checks: algorithms=bcrypt,apr1,sha; users=3.
What is a .htpasswd file?
An .htpasswd file stores usernames and hashed passwords for HTTP Basic Authentication, one user per line as user:hash. The hash is typically bcrypt, Apache MD5 (apr1), or SHA, never plaintext. Apache and nginx read it to guard a directory or route.
How to use this file
Use an example .htpasswd to test Basic-Auth credential parsers, password-hash identification, and web-server auth configuration. The sample credentials are documented and for testing only.
How to use this file for testing
“htpasswd (Mixed Algorithms) — SAMPLE” is a deterministic Novus Examples fixture for Certificate & key testing. Self-signed X.509 certificates (PEM, CRT, DER), a CSR, RSA and Ed25519 keys, an SSH public key, a PKCS#12 bundle, and an htpasswd file, all published sample-only material, for testing certificate parsers, TLS tooling, keystore importers, and PEM/DER decoders.
Documented properties for this file: HTPASSWD · 152 bytes. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.
Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such, expect parsers to fail loudly rather than silently accept them.
This is published, SAMPLE-only security material, never a real secret. Point certificate, key, or token parsers at it, test PEM/DER decoding and PKCS handling, and confirm your tooling reads the documented fields; any sample password is printed on this page.
This is a published, sample-only certificate/key. Parse it, verify the chain or signature, and test PEM↔DER conversion, never deploy it anywhere real.
Related files
- htpasswdhtpasswd (APR1 MD5) — SAMPLESAMPLE htpasswd using Apache APR1 MD5-style hash for legacy Basic-auth tests.
- htpasswdhtpasswd (bcrypt) — SAMPLESAMPLE htpasswd with a bcrypt hash line for Basic-auth file parsers.
- jsonCRL Metadata JSON — SAMPLESAMPLE CRL metadata JSON (no binary CRL) for revocation-list UI and loader tests.
- keyEd25519 Private Key (PEM) — SAMPLEDeterministic SAMPLE Ed25519 private key for SSH/TLS tooling tests.
- keyEncrypted PKCS#8 RSA Key — SAMPLEPassword-encrypted SAMPLE PKCS#8 private key (password printed in specs) for decrypt-import tests.
- txtOpenPGP Public Key (ASCII Armor) — SAMPLE ShapeASCII-armored SAMPLE-shaped PGP public key placeholder for armor detectors (not a cryptographically valid key).
Generated by generation/security_wave_g.py. Free for any use, no attribution required, license.