show configuration on a Juniper device is a single flat dump of the entire box: interfaces, routing policy, firewall filters, and every credential the device holds, all in the same paste. Before that goes into a TAC case or an AI chat asking "why is this OSPF adjacency stuck," it's worth knowing exactly what's in there.
What a JunOS Config Actually Contains
root-authentication encrypted-password— a$9$-prefixed Juniper hash for the root accountsnmp communitystrings, often withauthorization read-write- BGP
authentication-keyand OSPF/IS-ISauthentication-key(MD5, sometimes cleartext in older configs) - IPsec
ike proposalpre-shared keys undersecurity ike policy ... pre-shared-key - RADIUS and TACACS+
secretvalues undersystem radius-server/system tacplus-server - Local user
authentication encrypted-passwordhashes for every configured account
Before and After
The same SNMP community or shared secret always maps to the same token across the whole sanitized output, so relationships between interfaces, policies, and neighbors stay intact — only the literal credential is replaced.
Steps
- Install ScrubForge from the Chrome Web Store (free)
- Run
show configuration | display setor the plain hierarchical form on your Juniper device - Paste the output into ScrubForge
- Review the sanitized result — hashes, keys, and community strings are tokenized, structure is untouched
- Copy and share, or continue in ScrubForge's built-in AI chat
Why Local Processing Matters
A $9$ root hash or a BGP MD5 key pasted into a TAC case or a shared chat log sits there indefinitely. ScrubForge sanitizes entirely inside the browser tab — nothing is uploaded before you decide to share it.