{"version":"2.1.239","anchor":"powershell-profiles-and-hardware-ssh-keys-now-count-as-sensi","canonical_anchor":"powershell-profiles-and-hardware-ssh-keys-now-count-as-sensi","heading":"PowerShell profiles and hardware SSH keys now count as sensitive files","tier":"notice","area":"Credential Safety","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/powershell-profiles-and-hardware-ssh-keys-now-count-as-sensi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### PowerShell profiles and hardware SSH keys now count as sensitive files\n\nPowerShell profiles and hardware SSH keys are now treated as sensitive and won't be read or synced.\n\n**What**\n\nThe checks that stop credential files being read or synced now recognise three PowerShell profile locations (`documents\/powershell\/profile.ps1`, the WindowsPowerShell variant, and `.config\/powershell\/profile.ps1`) and hardware-backed SSH keys whose names end in `_ed25519_sk` or `_ed25519_sk_rk`.\n\n**Details**\n\n- A new counter, `skipped_content_filter`, was added to the breakdown of why files were skipped during sync, so content-filtered skips are distinguishable from other reasons.\n- Applies unconditionally.\n\n**Evidence**\n\n`skipped_content_filter`\n\n- Area: Credential Safety\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}