Lmcq Runtime Lora Encryption

The LoRA version of the pack's local-only protection system: encrypt a LoRA with a key and, optionally, a list of authorized machine codes, and it can only be loaded again by LmcqRuntimeLoraDecryption running on one of those specific machines. Everything happens locally - no LMCQ account, no cloud auth server, nothing that needs a network connection at any point, which is the whole reason this "Runtime" family exists alongside the pack's cloud-backed LmcqAuthLoraEncryption.

Why pick this over the Auth version. Both encrypt a LoRA behind a password; the difference is what happens after you hand the file over. LmcqAuthLoraEncryption ties decryption to LMCQ's own hosted platform - real-time validation, usage limits, the ability to revoke access remotely - but that means your buyer's decryption can depend on LMCQ's servers being reachable. This node skips all of that: per the README, the encrypted LoRA is only ever decrypted in memory during a run and never written back to disk unencrypted, so once it's out there, it works or doesn't purely based on the key and machine list you baked in - no ongoing dependency on a third party, but also no way to revoke or extend access after the fact without re-encrypting and redistributing.

The fields. lora_name is a dropdown of the LoRA files in your local loras folder. key is the encryption password. save_name (default encrypted_lora) names the output file. machine_codes is a multiline field - leave it blank if you only want password protection, or paste in one hardware ID per line to also lock the file to specific machines. Gather those codes ahead of time: have each person you're authorizing run LmcqGetMachineCode on their own install and send you the result, and add all of them before you encrypt - since there's no server to add one to later, a missed code means starting over. This is a terminal, output-only node; no wired outputs, it just writes the file.

Installing it. Through ComfyUI Manager (search "ComfyUI-LMCQ") or manually:

cd ComfyUI/custom_nodes
git clone https://github.com/sebord/ComfyUI-LMCQ

Restart ComfyUI afterward.

The trust question, briefly. Like the rest of this pack's protection nodes, the actual encryption logic ships as compiled, obfuscated code rather than readable Python - deliberate, per the README, specifically so it resists reverse-engineering. That's reasonable given the node's purpose, but it means the implementation isn't something you or a buyer can independently verify; you're trusting the team's claims about how it behaves, same as with any closed-source protection tool. Custom nodes in ComfyUI also run with full, unsandboxed system access regardless of what they do, which is worth keeping in mind generally, not specifically because of anything reported about this pack.

Troubleshooting. The pack's most common failure mode has nothing to do with LoRAs specifically: a compiled runtime module the protection nodes depend on has gone missing on some installs, throwing a ModuleNotFoundError referencing runtime.model_protection at ComfyUI startup, and because that import lives in the pack's shared __init__.py, it crashes registration for the entire pack - this node included, even though the bug traces back to the model-protection module rather than anything LoRA-specific. If none of the Lmcq nodes are showing up in your search, check your console log for that error first. The fix, documented in the pack's January 2026 changelog: copy the runtime files matching your Python version into the runtime folder, delete the mismatched ones, restart ComfyUI.