-
Notifications
You must be signed in to change notification settings - Fork 70
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
Unkown File Types #64
Comments
We can, but how do you validate them? Is there a parser to figure out sane/dangerous files? |
As far as my concern goes, the Quickbooks backup is safe because it's opened by the quickbooks program and read to a new file, it's not really opened directly. Obviously there's probably a way to use it to hide malware but for the most part in my experience when a virus gets ahold of it they either break the file by making it malicious (can't be restored from backup, but if you double click it, it runs a program) or it leaves them alone because it's an unkown file type. I'm trying to prevent clients bringing us unclean USBs that may have autorun malware, or images/executables that aren't intended for us but just on their USB (multipurpose USBs). I'm not suggesting this for every environment but I would like to just add the .QBB/.QBX file extension to automatically copy over. I'm going to talk to quickbooks about their linux applications and see if there's something that doesn't require licensing that can verify the backups. |
So your use case is to only allow .QBB/.QBX file extensions, and discard everything else? |
I suppose, we don't necessarily want to discard everything else though. Just to at least not mark .QBB/.QBX files DANGEROUS_MyKittyStore.QBX_DANGEROUS as that scares the bookkeepers. |
Makes sense. Do you have a sample file I could try to make sure it works properly? |
Sure thing. I downloaded a Quickbooks template online and made a backup of it: |
How do I go about adding a file type? I'm dealing with exchanging of Quickbooks Backups (*.QBB && *.QBX)
The text was updated successfully, but these errors were encountered: