| Mechanism | Description | Exclusivity Level | |-----------|-------------|-------------------| | | conan remote remove all but one remote | Strictest | | Explicit recipe revision pinning | requires = "pkg/1.0@user/channel#recipe_revision" – ties to a specific remote’s revision | Recipe-level | | Binary hash pinning | lockfiles (conan.lock) pin binary package IDs, preventing remote switching | Binary-level | | Private repository with same name masking | Conan resolves by remote order; place internal remote first, never fallback | Priority-based | | allowed_packages (Conan 2.x) | In conan.conf or profiles: restrict which remotes can serve specific packages | Package-level |
conan lock create . conan lock modify --add-remote my-private --exclusive-packages=* conan repository exclusive
If you'd like to dive deeper into specific implementations, let me know: | Mechanism | Description | Exclusivity Level |
Remember: A package without an exclusive home is a package waiting to betray you. Lock it down, own your dependencies, and build with confidence. By enforcing an exclusive internal repository route for
By enforcing an exclusive internal repository route for company-scoped packages, public remotes are never queried for internal dependencies, entirely neutralizing this attack vector. 2. Ensuring Strict Build Determinism
:Point the client to your internal server: conan remote add my-private-repo
That night, Mara did something rarer than a theft and more remarkable than many courage acts: she read. She read protocol after protocol, not as a thief searching for profit but as someone testing a perimeter. She learned that the repository required specificity. It did not grant power to just anyone; it granted it to categories: judges, mediators, archivists, and claimants who could prove, with ritual words and witnesses, their right to rebind a treaty. The exclusive protocols were keyed not to wealth but to legitimacy. That meant someone—Madam Kest included—was already entitled, in some sense Mara could not see.