Under Review

Sophos XGS import doesn't recognize generated tarball

I want to create a WebFilterException template for use on several XGS firewals.  I extracted edited the Entites.xml file to strip out the built-in entries.  Then in terminal "tar cvf O365_Exceptions.tar Entities.xml". The resulting file will not import into another firewall, saying it's not a tar file.  What is the correct process for doing this?

Parents
  • And I resolved it.

    Opened tarball in 7Zip.

    Open Entities.xml

    Edit to add and remove what I wanted.

    Missed a line - I had accidentally removed the highlighted line below. I found it by clicking on the first statement for each section, and Notepad++ highlights both the opening and closing statement. This entry didn't have the opening statement.  I copied from the original file.

    Added that line back in, and saved the file locally.

    Dragged that back into 7zip and it replaced the existing Entities.xml.  I was then able to successfully import.

    I added a different documentation update idea here >  https://community.sophos.com/product-documentation/i/feedback/please-describe-how-to-create-a-compatible-tar-ball

    In that, I demonstrated how I used VS Code to help validate the xml prior to replacing in the tarball. There may be better ways.

Comment
  • And I resolved it.

    Opened tarball in 7Zip.

    Open Entities.xml

    Edit to add and remove what I wanted.

    Missed a line - I had accidentally removed the highlighted line below. I found it by clicking on the first statement for each section, and Notepad++ highlights both the opening and closing statement. This entry didn't have the opening statement.  I copied from the original file.

    Added that line back in, and saved the file locally.

    Dragged that back into 7zip and it replaced the existing Entities.xml.  I was then able to successfully import.

    I added a different documentation update idea here >  https://community.sophos.com/product-documentation/i/feedback/please-describe-how-to-create-a-compatible-tar-ball

    In that, I demonstrated how I used VS Code to help validate the xml prior to replacing in the tarball. There may be better ways.

Children
No Data