How to package with mkinstpkg under Linux because I find hard

RE: How to package with mkinstpkg under Linux because I find hard

QC — Fri, 15 Jan 2016 03:02:54 GMT

Hello AlexAbou Adam,

confirm
I'm not Sophos, what I say is only to the best of my knowledge. I'm pretty sure though that there isn't a way to include the source in the package (from chapter 3.3.1 of the SEC 5.3 startup guide for Linux : The necessary files are copied from the server and Sophos Anti-Virus is installed).

test the installation of SophosAV through a deb package
I fear I don't quite get what you are aiming at and why you want "everything" included? Normally you install only once on a machine, afterwards AutoUpdate takes care of both detection data and software updates (including itself). It doesn't make any difference whether the initial installation of SAV is done from an already populated folder or its contents are downloaded first (in fact, the latter ascertains that both the installation and updating work).

Christian

RE: How to package with mkinstpkg under Linux because I find hard

AlexAbou Adam — Thu, 14 Jan 2016 08:52:07 GMT

Ok so I did not understand the concept of mkinstpkg, it's not usefull for me as I have to create a deb package for ubuntu repositories (i386/x86_64). Do you confirm that one can't create a standalone deb package of sophosAV from the "sources" with mkinstmkg ?

Of couse we have got a RMS server but I didn't want to use it because my first wish was to package, install and test the installation of SophosAV through a deb package.

Otherwise, we solved our problem with the update.

RE: How to package with mkinstpkg under Linux because I find hard

QC — Wed, 13 Jan 2016 07:00:43 GMT

Hello AlexAbou Adam,

first of all, apparently the webserver returns 404 for files without an extension - your Microsoft Admin should be able to change this behaviour,

install in offline mode
mkinstpkg does not create a full package for offline install. The package "just" contains the AutoUpdate component with its configuration (including required credentials) as well as other configuration options so that no user input is necessary to perform the installation. AutoUpdate subsequently downloads the actual SAV from the source location and installs it. If no on-site source (HTTP or UNC path) is available you can use Sophos (--sophos must be given as argument when running mkinstpkg, --update-type, BTW, is used to select the supported or free version of savlinux) as source.
Eventually you'll need a valid --update-source-path anyway.

--enableRMS=false
you don't want to centrally manage Sophos on your Linux installations?

Christian

RE: How to package with mkinstpkg under Linux because I find hard

AlexAbou Adam — Wed, 13 Jan 2016 03:33:42 GMT

Tank you for you answer. Yes actually I know what means --update-source-path & --update-cache-path but the fact is I can't install SophosAV without been obliged to declare an antiviral base :(

To tell you all, in my company, we've got an update server :

For Windows Users : http://<sophos-server.mycomany.fr>/SophosUpdate/CIDs/S000/SAVSCFXP/
For Linux Users : http://<sophos-server.mycomany.fr>/SophosUpdate/CIDs/S000/savlinux/

When we try to access to the linux share folder, we have a "404 Error - File or directory not found" on some files but it's another problem :

9/16/2015 1:21 PM 7 savBuildID
9/16/2015 1:21 PM 8 savBuildRevision
9/16/2015 1:21 PM 7 savShortVersion
9/16/2015 1:21 PM 11 savVersion
10/6/2015 10:20 AM 16 suiteVersion
12/22/2015 10:17 AM 10 talpaVersion
9/14/2015 5:30 PM 15 version

The other ones are accessible (cac.dat, cidsync.upd, vdlmnfst.dat, enginemnfst.dat etc ...). The problem has been submited to our Microsoft Admin.

Example :

# /opt/sophos-av/bin/savconfig get PrimaryUpdateSourcePath
http://<sophos-server.mycomany.fr>/SophosUpdate/CIDs/S000/savlinux

# /opt/sophos-av/bin/savconfig get PrimaryUpdateCachePath
/opt/sophos-av/update/cache/Primary

# ./sophos-av/update/savupdate.sh Downloading http://<sophos-server.mycomany.fr>/SophosUpdate/CIDs/S000/savlinux/cidsync.upd
383723 bytes downloaded in 0.072467 secs (5.049851 MiB/s)
Downloading http://<sophos-server.mycomany.fr>/SophosUpdate/CIDs/S000/savlinux/savi/sav/vdlmnfst.dat
16591 bytes downloaded in 0.024006 secs (674.917181 KiB/s)
Downloading http://<sophos-server.mycomany.fr>/SophosUpdate/CIDs/S000/savlinux/savi/engine/32/enginemnfst.dat
3463 bytes downloaded in 0.021766 secs (155.372789 KiB/s)
Downloading http://<sophos-server.mycomany.fr>/SophosUpdate/CIDs/S000/savlinux/savi/engine/64/enginemnfst.dat
3463 bytes downloaded in 0.012246 secs (276.155440 KiB/s)
Downloading http://<sophos-server.mycomany.fr>/SophosUpdate/CIDs/S000/savlinux/sav.dat
65187 bytes downloaded in 0.020277 secs (3.065892 MiB/s)
Downloading http://<sophos-server.mycomany.fr>/SophosUpdate/CIDs/S000/savlinux/talpa.dat
443060 bytes downloaded in 0.354952 secs (1.190400 MiB/s)
Removing bad file version
Downloading http://<sophos-server.mycomany.fr>/SophosUpdate/CIDs/S000/savlinux/savi/sav/cidox-aq.ide
15310 bytes downloaded in 0.029154 secs (512.833228 KiB/s)
Downloading http://<sophos-server.mycomany.fr>/SophosUpdate/CIDs/S000/savlinux/savi/sav/xvdl87.vdb
560014 bytes downloaded in 0.072922 secs (7.323867 MiB/s)
Downloading http://<sophos-server.mycomany.fr>/SophosUpdate/CIDs/S000/savlinux/talpaVersion
Downloading http://<sophos-server.mycomany.fr>/SophosUpdate/CIDs/S000/savlinux/talpaVersion
Failed to download 'http://<sophos-server.mycomany.fr>/SophosUpdate/CIDs/S000/savlinux/talpaVersion': no such file. Please check PrimaryUpdateSourcePath.
Failed to replicate from all update sources

So as can see, I can't use our sophos update server, that's why I'm trying to install in offline mode. Could you give the command-line to do it or correct this one ? :

# cd /opt/sophos-av/update
# ./mkinstpkg -D -o /opt/savinstpkg.deb --update-type=n --extra-options="--instdir=/opt/sophos-av --enableSavProtectOnBoot=True --extrafiles-update-type=n --acceptlicence=True --enableRMS=false --automatic=True --enableOnAccess=false"

RE: How to package with mkinstpkg under Linux because I find hard

QC — Tue, 12 Jan 2016 09:06:45 GMT

Hello AlexAbou Adam,

the --update-source-path must point to a location from where the endpoint can update - either Sophos, a webserver, or a share. To quote:
When prompted for the location from which to update, type the address of the CID as it appears to the other computers. Enter the username and password that are required to access that address, if applicable.
And cache-path (where the updates are downloaded to) and source-path (where the updates are downloaded from) being the same ... well, doesn't make sense, does it?

Christian