Issue 124420 - Legacy registry keys
Summary: Legacy registry keys
Status: CONFIRMED
Alias: None
Product: Installation
Classification: Application
Component: ui (show other issues)
Version: 3.3.0 or older (OOo)
Hardware: All Windows, all
: P3 Normal (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-03-13 20:16 UTC by halsteaw
Modified: 2014-03-18 09:58 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments
Registry export (704 bytes, text/plain)
2014-03-13 20:16 UTC, halsteaw
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description halsteaw 2014-03-13 20:16:25 UTC
Created attachment 82855 [details]
Registry export

See attachment.

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Sun Microsystems\StarOffice\XMergeSync\Messages\Error

Upon install of OO 4.0.1, the above key is created. The only data inside of it is in the Error key.

I cannot find where this key is being created in the source or what its utility is.

I do know that because of the StarOffice portion of the string, it is causing a false positive in some security software because it thinks StarOffice or an old version of OO is installed.

Is this legacy and can be removed or is there some ulilty I can pass to the security software developers to tell them to base their checks on some other file?

V/R,

~Warren
Comment 1 Andre 2014-03-14 07:42:52 UTC
The key is defined in 
    scp2/source/javafilter/registryitem_javafilter.scp
and is accessed in
    xmerge/source/activesync/XMergeFilter.cpp

Maybe it is possible to rename it.  Would that solve the problem?
Comment 2 Oliver-Rainer Wittmann 2014-03-14 08:44:06 UTC
I think this issue is only related to Windows --> changing corresponding field
Comment 3 Oliver-Rainer Wittmann 2014-03-14 09:40:42 UTC
I find the mentioned registry key on my Windows 7 on which certain OpenOffice versions had been installed in the past - from OOo 3.3.0 to recent AOO 4.0.1

On a Windows 7 Home Premium VM with corresponding snapshots I did not find the registry key on snapshots having OOo 3.3.0, AOO 3.4.0, AOO 3.4.1, AOO 4.0.0 and AOO 4.0.1 installed. Thus, currently I am not able to reproduce the described creation of the registry key upon installation of AOO 4.0.1
Comment 4 Oliver-Rainer Wittmann 2014-03-14 09:48:50 UTC
On another native Windows 7 machine on which AOO 3.4.0, AOO 3.4.1 and AOO 4.0.0 have been installed I did not found the mentioned registry key.
I will now install AOO 4.0.1 on this system to see, if the registry key is created.
Comment 5 Andre 2014-03-14 10:48:18 UTC
I used Orca to look into the openoffice410.msi file of my developer build.  I see 8 entries with key
  Software\Sun Microsystems\StarOffice\XMergeSync\Messages\Error
and 2 with key
  Software\Sun Microsystems\StarOffice\XMergeSync\Messages
Comment 6 halsteaw 2014-03-14 13:08:49 UTC
@Oliver Just to confim the bases were covered, did you look for both

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Sun Microsystems\StarOffice\XMergeSync\Messages\Error]

and

[HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\StarOffice\XMergeSync\Messages\Error]

I don't know if your VM is 64-bit or not and you didn't say.....

I would like to state for the bug record, that before installation I sight verified the keys did not exist in the registry before installation.
Comment 7 Oliver-Rainer Wittmann 2014-03-14 13:38:37 UTC
(In reply to halsteaw from comment #6)
> @Oliver Just to confim the bases were covered, did you look for both
> 
> [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Sun
> Microsystems\StarOffice\XMergeSync\Messages\Error]
> 
> and
> 
> [HKEY_LOCAL_MACHINE\SOFTWARE\Sun
> Microsystems\StarOffice\XMergeSync\Messages\Error]
> 

I just searched the whole registry for 'XMergeSync' and did not found it.

> I don't know if your VM is 64-bit or not and you didn't say.....

The Windows 7 Home Premium in the VM is a 64bit Windows 7

> 
> I would like to state for the bug record, that before installation I sight
> verified the keys did not exist in the registry before installation.

Ok.
It is not my intention to express any doubts on your observations by presenting my observations.
It just seems that some part on my systems is missing to reproduce it.
On my working system the registry key exists, but I can not reproduce that it is coming from the AOO 4.0.1 installation.

On my other native Windows 7 system on which only AOO 3.4.1 and AOO 4.0.0 had been installed the installation of AOO 4.0.1 does not create the mentioned registry key. Just my observation.
Comment 8 halsteaw 2014-03-14 14:25:49 UTC
@Oliver  Just did some tests and I think I found why you don't see it.

Don't do a typical install. Select custom and install ALL the optional components. Do a FULL install.
Comment 9 halsteaw 2014-03-14 14:59:34 UTC
@Oliver To be more specific install (under Optional Components) Mobile Device Filters->Pocket PC->Pocket Word or Pocket Excel
Comment 10 Oliver-Rainer Wittmann 2014-03-18 09:58:01 UTC
(In reply to halsteaw from comment #9)
> @Oliver To be more specific install (under Optional Components) Mobile
> Device Filters->Pocket PC->Pocket Word or Pocket Excel

This is the missing piece.
I did a 'modify' setup of AOO 4.0.1 on my other native Windows 7 machine. I installed optional component Mobile Device Filters->Pocket PC->Pocket Word.
--> The above mentioned registry key is created.

I did a 'modify' setup of OOo 3.3.0 on the corresponding snapshot on my Windows 7 Home Premium VM and installed the corresponding optional component.
--> The above mentioned registry key is created.