Currently seeing entries like the following in the SAV log on a Debian 64 bit system running Sophos Server Protection and the pCloud client
Directory path shown is the cloud-based one rather than a local synced directory.
Tue 06 Mar 2018 13:01:09 GMT: log.error Error occurred while scanning /home/adrian/pCloudDrive/Adrian/postgresql_backups/ahpc/.refreshc4bdda2b2296f79e662c0f18d19a31c2d2cfd2502f407d25ae50374b45d6bc08d7e7fef8: 0x3c: Unable to write to talpa socket (Close). (The operation was denied.)
Tue 06 Mar 2018 13:02:11 GMT: log.error Error occurred while scanning /home/adrian/pCloudDrive/Adrian/postgresql_backups/ahpc/.refreshc4bdda2b2296f79e662c0f18d19a31c21ae11b85a40f19bb3d6383997050f99e8846289c: 0x3c: Unable to write to talpa socket (Close). (The operation was denied.)
At the moment we have excluded the pCloudDrive directory path from on-demand scanning but this feels like opening a big hole in the network security as the linux workstations can access external files and they are only scanned if the user copies them to local storage, defeating one of the reasons for using pCloud.
Please place suggestions/advice in the box provided
Thanks in advance
Adrian
This thread was automatically locked due to age.
