[Solved] Xinorbis - Alter Product Name

[OLLI_S]

Xinorbis is detected correctly on my system, but the displayed product name should be altered.
In the application the displayed product name is Xinorbis Pro.
In VulnDetect the displayed product name is Xinorbis.
So you should show the same product name that is shown in the app.

Tell me if you need a screen shot of the Help -> About window.

---

Here the information extracted from the EXE file:

File name and path:     D:\PortableApps\PortableApps\_XinorbisPortable\Xinorbis_8.1.10_Pro_x64\x8.64.exe
Product Name:           Xinorbis
Internal Name:          
Original Filename:      

File Description:       64 bit Pro
Company:                www.MaximumOctopus.com
Legal Copyright:        (c) Paul Alan Freshney 2017
Legal Trademarks:       Maximum Octopus Limited
Comments:               

File Version String:    8.0.15.44
File Version:           8.0.15.44
Product Version String: 8.0.0.0
Product Version:        8.0.0.0

[Tom]

I can see, however, "pro" does not seem to be used in any way on the website and if you search for "xinorbis pro", only unofficial sites and threads here on vulndetect.org come up:
https://duckduckgo.com/?q="xinorbis+pro"
https://www.google.com/search?source=hp&q="xinorbis+pro"

It is far more important, that people can Duck or Google for the names and versions used by VulnDetect and be reasonable certain to find the official vendor pages, security bulletins and identify the correct download or support article, rather than matching whatever is shown in the GUI of the product.

It would be nice if we could fix this, but there is no good or easy solution when vendors are inconsistent in naming and versioning.

[OLLI_S]

The current version has the text Pro in the application title bar:

---

An older version has the text Free in the application title bar:

---

So, @Tom, what do you suggest?

[Tom]

@OLLI_S I suggest that we just leave it as is, since this is most consistent with the current information on the site.

[OLLI_S]

OK, master, I agree!
OK, I mark the topic as Solved and move it to the category Solved Detection Issues.