Vault changes file permissions?

[lvarney]

Hi,

Recently we installed the newest version of Vault (standard) onto our Windows 2008 R2 server. A few days later we noticed one of our web applications was erroring with "Unable to obtain public key for StrongNameKeyPair". This error is thrown by NHibernate and CastleWindsor.

After days of frustration we found the cause to be the permissions on the following folder:
....\Microsoft\Crypto\RSA\MachineKeys

The permissions had been changed which included the addition of a user called VaultAppPool. For some reason it would appear that Vault had found it necessary to alter permissions on this folder and files.

I would like to know why it does this? Surely Vault should not be changing existing permissions on any existing folder? Can anyone shed any light on this please?

Thanks,
Laura

[Beth]

Vault only adds permissions to that folder so that it has access to it. It doesn't take away from it.

Besides the addition of the VaultAppPool, were there any changes that removed permissions? If so, which ones?

[lvarney]

Hi Beth,

We found a solution from this blog:
http://ayende.com/Blog/archive/2006/06/ ... yPair.aspx

The permissions we had to set for Everyone are these:
READ_CONTROL
SYNCHRONIZE
FILE_GENERIC_READ
FILE_GENERIC_WRITE
FILE_READ_DATA
FILE_WRITE_DATA
FILE_APPEND_DATA
FILE_READ_EA
FILE_WRITE_EA
FILE_READ_ATTRIBUTES
FILE_WRITE_ATTRIBUTES

After installing Vault we had to force correct permissions down to the lowest folder level and this seemed to fix the problem. There were no server updates made or any other installations before this problem occurred. the only thing that chaned on the server was the installation of Vault.

I could be wrong in my assumption that it was Vault but we're at a loss as to what else it could be.

Thanks for replying,
Laura

[Beth]

I have a bug logged to check into file permission changes. There was another thread that was similar posted here: http://support.sourcegear.com/viewtopic ... 5&start=15. Vault should add a few permissions, but shouldn't take away permissions. Your work-around was the correct thing to do.

I haven't been able to reproduce this on any machine yet, and the bulk of our customers don't run into this.

F: 15752

[aamoros]

I've just installed Vault Standard and had the same issue where the permissions for the Crypto folder was changed. This is definately a bug.

Thanks,
Alberto

[lbauer]

We'll take another look.

What version of Vault Standard did you install, and on what operating system?

How did it change the permissions?