Thread Info
  • State Verified Answer
  • Replies 17 replies
  • Answers 1 answer
  • Subscribers 10 subscribers
  • Views 10607 views
  • Users 0 members are here
Options
Suggested

Installing Sophos Protection for Linux in a distribution without systemd

teoberi

Hello,

I've been using Sophos Anti-Virus for Linux in Slackware (a distribution without systemd) for a long time and I'm delighted with this product, which is the only antivirus I can install in this case with the exception of Clamav.

I read in the Sophos Central console that this product will no longer be supported after July 20, 2023, and the new Sophos Protection for Linux product requires systemd.

Can Sophos Protection for Linux be installed without systemd?

What happens to old users of Sophos products for Linux in this case, have we been totally abandoned?

I don't understand the reasons why compatibility was removed in the case of operating systems that do not use systemd for this new product that also works great and we would like to pay for it?



Added tags
[edited by: Gladys at 2:21 PM (GMT -7) on 5 Aug 2022]
Parents
  • 0

    Hello 

    Thank you for reaching community forum. Based on our initial checking, the current set-up for SPL really does require Systemd. Though we're currently confirming further if there will be an option in the future in our SLP to not use systemd. We'll keep you posted for more updates about this. 

    Glenn ArchieSeñas (GlennSen)
    Global Community Support Engineer

    The New Home of Sophos Support Videos!  - Visit Sophos Techvids
  • 0 in reply to GlennSen

    While waiting for an answer to my request, I have a few more questions:

    1. why are there two different locations for libsavi.so.3 and which should be used?

    /opt/sophos-spl/plugins/av/chroot/susi/update_source/libsavi/libsavi.so.3
/opt/sophos-spl/plugins/av/chroot/susi/distribution_version/<xxx>/libsavi.so.3

    2. why are there three different locations for virus definition files (.ide; .vdb) and which should be used?

    /opt/sophos-spl/plugins/av/chroot/susi/update_source/vdl/
/opt/sophos-spl/plugins/av/chroot/susi/distribution_version/<xxx>/vdb/
/opt/sophos-spl/base/update/cache/primary/ServerProtectionLinux-Plugin-AV/files/plugins/av/chroot/susi/update_source/vdl/

    I believe that location 3 in the list above is for configuring an update server, just like in the case of SAV for Linux (/opt/sophos-av/update/cache/).

    I would guess that the correct locations would be the ones with "/opt/sophos-spl/plugins/av/chroot/susi/distribution_version/<xxx>" but "xxx" differs from one installation to another, I don't know if they will also differ in the case of a version update.

    Can "xxx" be a customer id and that be the reason why it differs?

Reply
  • 0 in reply to GlennSen

    While waiting for an answer to my request, I have a few more questions:

    1. why are there two different locations for libsavi.so.3 and which should be used?

    /opt/sophos-spl/plugins/av/chroot/susi/update_source/libsavi/libsavi.so.3
/opt/sophos-spl/plugins/av/chroot/susi/distribution_version/<xxx>/libsavi.so.3

    2. why are there three different locations for virus definition files (.ide; .vdb) and which should be used?

    /opt/sophos-spl/plugins/av/chroot/susi/update_source/vdl/
/opt/sophos-spl/plugins/av/chroot/susi/distribution_version/<xxx>/vdb/
/opt/sophos-spl/base/update/cache/primary/ServerProtectionLinux-Plugin-AV/files/plugins/av/chroot/susi/update_source/vdl/

    I believe that location 3 in the list above is for configuring an update server, just like in the case of SAV for Linux (/opt/sophos-av/update/cache/).

    I would guess that the correct locations would be the ones with "/opt/sophos-spl/plugins/av/chroot/susi/distribution_version/<xxx>" but "xxx" differs from one installation to another, I don't know if they will also differ in the case of a version update.

    Can "xxx" be a customer id and that be the reason why it differs?

Children
No Data
Unfiltered HTML