New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with plugin upload functionality #762
Comments
Hi, I too am having the EXACT same issue, as I was trying to upload the plugin file manually provided by Tenable and unfortunately all the Tenable.SC plugins have exceed 2GB now. Last month it was just under the 2GB limit. I've sent a ticket to Tenable support and see if they have a hotfix or something to apply to Tenable.SC to fix this issue. I will try to update this github ticket accordingly. For the methods to update the plugins I did exactly what you did which was via webgui and pyTenable script, both failed. |
The Security Center team is aware and is working on this issue, and they're planning to fix it in SC v6.4.0, which is expected to come out in the first half of this year. |
That is great to hear so the bigger question is this affecting all versions of tenable.sc or just 6.3.0? |
@kintaroju this seems to affect all SC versions. In the mean time, the SC team has put out a workaround for this issue. You may have to reach out to Customer Support for the same. |
Good to know thanks for the info. I will remind the tech about not requiring the legendary diagnostics file to deal with this issue lol |
@aseemsavio I finally got a response from Tenable and they provided me a workaround (can't post the workaround as they indicated they will post a KB on this), except it only worked for the WebGUI and not via pyTenable. So the question is for a pyTenable perspective how can I upload the plugins, or do we have to wait till there is an official patch before pyTenable can be fixed as well? |
@kintaroju they gave me 2 KBs, neither worked, they seem to have managed to minimize the plugin-set size, though this doesn't work with pyTenable. |
Hey,
|
We're being hit by the 32-bit limit again for this. OverflowError: string longer than 2147483647 bytes |
looks like the error is related to how requests is handling files differently than raw encoded data. Took aq little digging but this seems to be related: https://stackoverflow.com/questions/22915295/python-requests-post-and-big-content/22915488#22915488 |
After some testing the memory usage using the file upload went from 2G to to under 50M. I think this should long-term solve this issue on the library-front. |
Thanks for resolving this @SteveMcGrath - do we have an estimated release date? I notice the last release is >1mo ago so presumably its soon-ish? |
yeah, just trying to work through the backlog of PRs before releasing. If you're in a rush, you can always test with a pip install from git:
|
All good, we're in an airgapped network so happy to wait. Soon-ish is good enough for me! |
Describe the bug
Currently, the offline pluginset uploaded by tenable to https://plugins.nessus.org/get.php?f=sc-plugins-diff.tar.gz (passing username/password strings) is too large for ssl.py to handle (larger than 32-bit limit). This causes issues when using the following code to upload plugins:
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Plugin to upload and process without failing out.
Screenshots
edit: This seems to cause an error when uploading through the UI too, I've raised as a case with Tenable directly.
System Information (please complete the following information):
The text was updated successfully, but these errors were encountered: