Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
![]() ![]() ![]() ![]() ![]() ![]() ![]() |
62 posts
|
My deployed application creates registry keys under hkey current user. Why?
HKCU\Software\ Object Arts\ HKCU\Software\Object Arts\ DolphinSure\ HKCU\Software\Object Arts\DolphinSure\ Certificates\ HKCU\Software\Object Arts\DolphinSure\Certificates\ TemporaryTrust\ Regards Carsten Härle |
Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
![]() ![]() ![]() ![]() ![]() ![]() ![]() |
1420 posts
|
"Carsten Haerle" <[hidden email]> wrote in message
news:40e02394$0$12494$[hidden email]... > My deployed application creates registry keys under hkey current user. > Why? > ... > HKCU\Software\Object Arts\DolphinSure\Certificates\ > TemporaryTrust\ > In short, because you have DolphinSure in it. During session initialisation the DolphinSureCertificateStore class discards any old temporary trust entries, and in so doing creates the above registry key. I found this out by browsing the image for methods containing the text 'TemporaryTrust' and then browsing from there, so you can do the same. Frankly it doesn't need to create the entries if they are not there, but assuming that you are using DolphinSure in your application then it would need to be able to write to the registry anyway (under HKCU, which should not be an issue) at some later point, so I don't see why this would be anything to worry about. If you aren't expecting DolphinSure to be in there, they you will need to track down the dependency and break it. This might help: t := VirtualTreeModel new. t getChildrenBlock: [:each | each dependentPackages]. t addRoot: (Package manager packageNamed: 'DolphinSure'). TreePresenter showOn: t Or you can use the PackageBrowser's prereqs tree, and expand it until you find the path to DolphinSure. Regards Blair |
Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
![]() ![]() ![]() ![]() ![]() ![]() ![]() |
62 posts
|
I am just using the class SecureHashAlgorithm, which is in the DolphinSure
package. I don't use any of the Certificate things. Regards Carsten "Blair McGlashan" <[hidden email]> schrieb im Newsbeitrag news:[hidden email]... > "Carsten Haerle" <[hidden email]> wrote in message > news:40e02394$0$12494$[hidden email]... > > My deployed application creates registry keys under hkey current user. > > Why? > > ... > > HKCU\Software\Object Arts\DolphinSure\Certificates\ > > TemporaryTrust\ > > > > In short, because you have DolphinSure in it. During session > the DolphinSureCertificateStore class discards any old temporary trust > entries, and in so doing creates the above registry key. I found this out > by browsing the image for methods containing the text 'TemporaryTrust' and > then browsing from there, so you can do the same. Frankly it doesn't need to > create the entries if they are not there, but assuming that you are using > DolphinSure in your application then it would need to be able to write to > the registry anyway (under HKCU, which should not be an issue) at some later > point, so I don't see why this would be anything to worry about. > > If you aren't expecting DolphinSure to be in there, they you will need to > track down the dependency and break it. This might help: > > t := VirtualTreeModel new. > t getChildrenBlock: [:each | each dependentPackages]. > t addRoot: (Package manager packageNamed: 'DolphinSure'). > TreePresenter showOn: t > > Or you can use the PackageBrowser's prereqs tree, and expand it until you > find the path to DolphinSure. > > Regards > > Blair > > ... [show rest of quote] |
Free forum by Nabble | Edit this page |