Applications that accept a keyset do not all look for it in the same place. This page explains why, and why a correctly formatted keyset can still be ignored — the situation that produces most “it says no keys” reports.
Where a keyset is expected
Three patterns are common. Some applications expect the keyset in a fixed subdirectory beside the executable. Some read a configuration value that names a path. Some accept it as a command-line argument and have no default location at all. Which pattern applies is a property of the application, not of the keyset.
Configuration
Check the application’s own documentation for the expected location before moving files around. A file placed in a plausible-looking directory is not the same as a file placed where the application looks, and trial and error tends to scatter copies of sensitive material across a filesystem.
Keyset recognition
Recognition is usually name-based first, structural second. That means an incorrectly named file fails before its contents are ever examined — which is why missing keyset and unrecognised keyset are separate topics.
Compatibility
The environment sits at one end of the compatibility chain: it expects a revision, and if the keyset carries a different one, the failure appears at the layer that could not be satisfied. See the compatibility hub and, for the specific case, unsupported revision.
Common errors
- No keyset found at all — a path or naming problem.
- Keyset found but rejected — a structural problem.
- Keyset loaded but content fails — a revision-relationship problem.