search

immauss / openvas

Containers for running the Greenbone Vulnerability Manager. Run as a single container with all services or separate single applications containers via docker-compose.
GNU Affero General Public License v3.0
360 stars 102 forks source link

email alert is not attaching report PDF #27

Closed heinrichat closed 3 years ago

heinrichat commented 3 years ago

When mailing the reports in PDF form I get the following error in the report email:

"This report exceeds the maximum length of 1048576 characters and thus was truncated." The email has no attachments. This error occurs when scanning /26 IP range. /27 IP ranges work fine.

I've modified your your start start.sh script in line :253 from

su -c "gvmd --osp-vt-update=/tmp/ospd.sock" gvm

to

su -c "gvmd --osp-vt-update=/tmp/ospd.sock --max-email-attachment-size=64000000 --max-email-include-size=64000000 --max-email-message-size=64000000" gvm

and deleted the old container plus volume and build a new container with $ docker-compose up -d

...but it seems that this doesn't work. When scanning the /26 range again the error persists.

immauss commented 3 years ago

Try this again … but don’t delete the container. Just make the change, and then run:

Docker restart

When you delete the container, you deleted your changes.

A docker restart will keep the changes you made and restart all the container processes.

Let me know if that worked out. I’ve not done any testing with large attachments before. If that works, I can add it into the base build so it will be there the next time for you.

-Scott

immauss commented 3 years ago

OR ... you could try out this image tag. immauss/openvas:heinrichat

I'm pushing it now.

You'll need to use that tag in your docker-compose.yaml

immauss commented 3 years ago

Were you able to test this? I may have time this weekend to test this if not. please let me know.

heinrichat commented 3 years ago

Were you able to test this? I may have time this weekend to test this if not. please let me know.

I will try it Monday (UTC+1)

heinrichat commented 3 years ago

Nope. Same Error. I'm positive, that this is not an error with your docker container. It is a greenbone issue, but an unresolved one. I think I should post it in the Greenbone Forum or their repo hoster.

immauss commented 3 years ago

OK ... since I'm inclined to agree with you on this, I'm going to close this issue. Please let me know though if you come across a solution I can add to the image.