Skip to content

Windows: code quality improvement for --move and --remove options - #1470

Merged
val-ms merged 1 commit into
Cisco-Talos:mainfrom
val-ms:CLAM-2736-windows-traverse-reparse-point
Mar 22, 2025
Merged

Windows: code quality improvement for --move and --remove options#1470
val-ms merged 1 commit into
Cisco-Talos:mainfrom
val-ms:CLAM-2736-windows-traverse-reparse-point

Conversation

@val-ms

@val-ms val-ms commented Mar 19, 2025

Copy link
Copy Markdown
Contributor

When the --move or --remove options are used, ClamAV carefully traverses the file path one layer at a time so as to avoid following a directory that is a symlink or reparse point.
We do this for directories, but could also do it for files. Only an admin should be able to create a reparse point for a file, but it is better to be consistent.

Thank you to Maxim Suhanov for reporting this issue.

When the --move or --remove options are used, ClamAV carefully traverses
the file path one layer at a time so as to avoid following a directory
that is a symlink or reparse point.
We do this for directories, but could also do it for files.
Only an admin should be able to create a reparse point for a file,
but it is better to be consistent.

Thank you to Maxim Suhanov for reporting this issue.

@TheRaynMan TheRaynMan left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Known option change, looks good to me.

@val-ms

val-ms commented Mar 20, 2025

Copy link
Copy Markdown
Contributor Author

Waiting on internal test pipelines. Seems like a firewall issue or something to our win 11 arm64 test node. The move/remove/copy action tests worked fine though for win 10 x64, win 10 x86, and win 8 x64.

@val-ms

val-ms commented Mar 22, 2025

Copy link
Copy Markdown
Contributor Author

Test pipelines looking okay now.

@val-ms
val-ms merged commit 640413d into Cisco-Talos:main Mar 22, 2025
@val-ms
val-ms deleted the CLAM-2736-windows-traverse-reparse-point branch March 22, 2025 19:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants