What's wrong with this entry?
What: Enhanced security check that detects suspicious Windows-specific path patterns and requires manual approval before allowing file access.
How to use: Automatic protection when Claude attempts to access files with suspicious paths. You'll receive a prompt like: > "Claude requested permissions to read/write to {path}, which contains a suspicious Windows path pattern that requires manual approval."
Details:
- Detects alternate data streams (
:in paths beyond drive letter) - Detects short/8.3 format names (
~1,~2patterns used to bypass filters) - Detects long path prefixes (
\\?\,\\.\) that can bypass security checks - Detects trailing dots or spaces that Windows ignores
- Detects reserved device names (CON, PRN, AUX, NUL, COM1-9, LPT1-9)
- Applies to both read and write permission checks
- Evidence:
ZMQ() at line 454449, integrated intob41() at line 454621andop() at line 454708(function and security checks completely absent from v2.0.15)
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.