I'm new to scripting, forgive me if I'm posting in the wrong section.
While first attempts resulted in an error saying it couldn't access the /var/folders location
I'm not sure whats different now, because I've been able to run $ brew pkg --with-deps --without-kegs --identifier-prefix org.TESTING clamav
and it builds the clam-0.99.2_1pkg installer
Inspecting the pkg file I can't see the conf file /usr/local/etc/clamav/freshclam.conf is included
Making me think this is perhaps not the way.
Any suggestions or guidance to kb articles you're aware of would be amazing
End game: Ultimately, deploying clamav via addigy as we've moved away from Gruntwork. Then run scans on a schedule - not much cashflow for paid software on all the clients.
clamav appears to be running fine in the test client VM.
It will discover EICAR files I've littered around and scan will run, I'm still not sure how to quarantine infected files(but thats a different conversation)
Anyway, Thanks for the info I keep seeing you posting on various sites.
Top work.
Hi Tim,
I'm hoping to use your brew-pkg tool to make a clamav install package with no dependancy of brew being installed on the client endpoints.
I've stumbled across this project via: https://www.jamf.com/jamf-nation/discussions/6999/deploying-homebrew-through-casper while looking for a way to install brew silently, and you raise a valid point about not going wild and installing brew everywhere.
I'm new to scripting, forgive me if I'm posting in the wrong section.
While first attempts resulted in an error saying it couldn't access the /var/folders location I'm not sure whats different now, because I've been able to run $ brew pkg --with-deps --without-kegs --identifier-prefix org.TESTING clamav
and it builds the clam-0.99.2_1pkg installer
Inspecting the pkg file I can't see the conf file /usr/local/etc/clamav/freshclam.conf is included
Making me think this is perhaps not the way.
Any suggestions or guidance to kb articles you're aware of would be amazing
End game: Ultimately, deploying clamav via addigy as we've moved away from Gruntwork. Then run scans on a schedule - not much cashflow for paid software on all the clients.
Anyway, Thanks for the info I keep seeing you posting on various sites. Top work.
Regards, Miro