openclaw-credential-encryption

Encrypt OpenClaw credentials using macOS Keychain, FileVault, and file permissions.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/hummbl-dev/hummbl-agent --skill openclaw-credential-encryption
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openclaw-credential-encryption
Source: https://github.com/hummbl-dev/hummbl-agent/tree/main/skills/openclaw-credential-encryption
Command: npx skills add https://github.com/hummbl-dev/hummbl-agent --skill openclaw-credential-encryption

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill addresses the critical security vulnerability of storing sensitive OpenClaw runtime credentials in plaintext, ensuring robust protection through macOS-native security features and encryption.

Core Features & Use Cases

  • macOS Keychain Integration: Securely stores and retrieves sensitive tokens and API keys.
  • File System Hardening: Enforces strict permissions on credential and session files within ~/.clawdbot/.
  • FileVault Enforcement: Ensures full-disk encryption is active for comprehensive data protection.
  • OAuth Material Encryption: Protects OAuth tokens via OpenSSL encryption or Keychain storage.
  • Use Case: After installing OpenClaw, use this skill to migrate all plaintext API keys and tokens from configuration files into the macOS Keychain and encrypt any OAuth JSON files.

Quick Start

Use the openclaw-credential-encryption skill to migrate existing OpenClaw credentials to the macOS Keychain.

Frequently Asked Questions about openclaw-credential-encryption

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I encrypt plaintext OpenClaw credentials in macOS?

Encrypt plaintext OpenClaw credentials on macOS by migrating API keys and OAuth tokens into the macOS Keychain using OpenSSL, while enforcing strict file system permissions on the ~/.clawdbot/ directory.

Does openclaw-credential-encryption require FileVault to be enabled?

Yes, the skill enforces FileVault full-disk encryption using the fdesetup command-line tool to guarantee comprehensive data protection for runtime credentials stored on macOS systems.

What command-line tools do I need to secure OpenClaw OAuth materials?

Securing OpenClaw OAuth materials requires the security command-line tool for Keychain access, openssl for encrypting JSON files, and fdesetup for verifying FileVault full-disk encryption status.

How do I migrate API keys to the macOS Keychain from configuration files?

Migrate API keys to the macOS Keychain by extracting plaintext tokens from configuration files in ~/.clawdbot/ and storing them securely using the macOS security command-line tool, then hardening the original file permissions.

What are the limitations of using macOS Keychain for OpenClaw credential storage?

Using macOS Keychain for OpenClaw credential storage limits you to macOS environments, as it depends strictly on native tools like security and fdesetup, preventing cross-platform portability of your encrypted configuration.

Why are my OpenClaw OAuth tokens exposed in plaintext?

OpenClaw OAuth tokens are exposed in plaintext because default configuration stores them unencrypted in ~/.clawdbot/ files, requiring OpenSSL encryption or Keychain migration to mitigate the credential exposure vulnerability.