I had to be very careful when selecting the long-awaited auto-update method for virus definitions. They had to be secure, and updated from a trusted source, while being latest definitions to maintain server security.
In 1.0.2 (to be released in the next week) I opted to download daily snapshots of the definitions from SourceForge. However under some circumstances this may not be acceptable.
Before it gets written in stone I'd appreciate any comments on methods, mechanisms, file formats, encryption/compression, and so forth for future releases.
I feel it's fundamental to project development and should be acceptable before development continues.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I had to be very careful when selecting the long-awaited auto-update method for virus definitions. They had to be secure, and updated from a trusted source, while being latest definitions to maintain server security.
In 1.0.2 (to be released in the next week) I opted to download daily snapshots of the definitions from SourceForge. However under some circumstances this may not be acceptable.
Before it gets written in stone I'd appreciate any comments on methods, mechanisms, file formats, encryption/compression, and so forth for future releases.
I feel it's fundamental to project development and should be acceptable before development continues.
How about base64_decode() and base64_encode()
If you don't want that I built a little function that encrypts the string and then decrypts it.
Add the regular expretions ability.