Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Windows clamscan Chinese catalog file path #1203

Open
cheng8482 opened this issue Mar 13, 2024 · 2 comments
Open

Windows clamscan Chinese catalog file path #1203

cheng8482 opened this issue Mar 13, 2024 · 2 comments

Comments

@cheng8482
Copy link

Tested with... Clamscan 64 bit v1.3.0

D:\资料备份\Clamav杀毒\clamav-1.2.1.win.x64>clamscan --move=D:\clamgeli D:\资料备份\Clamav杀毒\病毒样本\bd111.v
LibClamAV Warning: **************************************************
LibClamAV Warning: *** The virus database is older than 7 days! ***
LibClamAV Warning: *** Please update it as soon as possible. ***
LibClamAV Warning: **************************************************
Loading: 17s, ETA: 0s [========================>] 8.68M/8.68M sigs
Compiling: 4s, ETA: 0s [========================>] 41/41 tasks

D:\资料备份\Clamav杀毒\病毒样本\bd111.v: Win.Virus.Ramnit-9808983-0 FOUND
ERROR: Can't move file D:\资料备份\Clamav杀毒\病毒样本\bd111.v to D:\clamgeli\bd111.v
win32_openat: Failed to open file 'bd111.v'.
Error: 0xc0000043
ioStatusBlock: 0x0
traverse_to: Failed open bd111.v
traverse_unlink: Failed to open file descriptor for target directory!

----------- SCAN SUMMARY -----------
Known viruses: 8682155
Engine version: 1.2.1
Scanned directories: 0
Scanned files: 1
Infected files: 1
Not copied: 1
Data scanned: 0.13 MB
Data read: 0.13 MB (ratio 1.06:1)
Time: 23.822 sec (0 m 23 s)
Start Date: 2024:03:13 15:57:40
End Date: 2024:03:13 15:58:04

So scanning a Chinese catalog file path and using --copy or --move to quarantine
files will be an issue.

@ragusaa
Copy link
Contributor

ragusaa commented Mar 13, 2024

Hi,
Thank you for the bug report. I am able to reproduce the issue. I'll open a ticket internally, and update this issue when it is scheduled.

Thanks,
Andy

@cheng8482
Copy link
Author

thank you for your fast reply, expect

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

No branches or pull requests

2 participants