07-04-2025 08:24 AM - edited 07-04-2025 08:26 AM
Let me summarize your options here:
- You can complain that this bug exists and demand that it is getting fixed for the version you have decided to use which happens to be almost 2 years old
But NI has a policy to only make bug fixes for the latest current version unless it is a security bug (with according CVE report).
So there is another option: Invest time and effort into proofing that it is a security risk and get an according CVE assigned.
- Or you can take action yourself and work around it
Which do you think will cost you less effort?
07-04-2025 08:37 AM
@rolfk ha scritto:
Let me summarize your options here:
- You can complain that this bug exists and demand that it is getting fixed for the version you have decided to use which happens to be almost 2 years old
But NI has a policy to only make bug fixes for the latest current version unless it is a security bug (with according CVE report).
So there is another option: Invest time and effort into proofing that it is a security risk and get an according CVE assigned.
- Or you can take action yourself and work around it
Which do you think will cost you less effort?
Again, I simply find the solutions you propose, funny.
I find it funny that the uncritical Labview developers didn't realize that they broke a feature like copy and paste.
And I find it funny that support for a product that you definitely pay no small amount of money for, almost doesn't exist and always seems to be a detached entity.
Maybe we need to get back a little more in touch with reality.
I find it all amusing, but I am actually very saddened.