-
Notifications
You must be signed in to change notification settings - Fork 20
Description
Using the extension, it caused a form of a Denial of Service attack on my own system. The “The F5 Extension” currently creates a fresh UCS each time the user decides to “Explore Config” on an LTM, and I filled the drive of my LTM. This made me unable to interact with the box in several important ways.
The "The F5 Extension" adds an "Explore Config" option to VsCode. Performing that action creates a "/var/local/ucs/*.mini_ucs.tar.gz" file and never purges it. To correct I suggest we have a plan to purge those files routinely.
The “The F5 Extension” available for use in VsCode to conveniently manage LTMs through AS3 must give the user a convenient way to manage the UCS files it creates. I’m open to any of several possible solutions.
*) Every time the “Explore Config” option is executed, it could create and schedule a one-time bash job that would remove the new UCS after 4 hours.
*) Every time the “Explore Config” option is executed, it could notify the user of the space the UCS is likely to consume on the LTM and how much more space is available.
*) Every time the “Explore Config” option is executed, it could offer the user the option to delete previous UCSs over 4 hours old.
*) Every time the “Explore Config” option is executed, it could simply delete stale UCSs.
*) The f5-appsvcs iApp could simply handle keeping the /var/local/ucs folder clean, all by itself. The “Explore Config” action could create a “source identifier” file in the /var/local/ucs folder so f5-appsvcs could come along later and remove all UCS files sourced from the “Explore Config” option.