file permissions?

[sowosammerneger]

Hi,

I ran a standard file permission of 644 and directories with 755.
Does vaultwiki need some files with other permissions?

Another question is the permission of functions.php with 777 - I don't quite like that.
Is this only for the installation and we can change it afterwards or is there another way of achieving the same goals?

[pegasus]

Yes it needs to remain 777, because in the case where you upgrade vBulletin, you wouldn't be uninstalling and reinstalling VaultWiki again. Plus, I don't see how leaving that file 777 would be a security risk at all.

[sowosammerneger]

777 means nothing but anybody with access to that file can do with it whatever he likes.
So if we have user stuff which will be uploaded, I will accept that and make a rotating copy every hour, but when I see that my complete board becomes a non working wreck, when I update the vaultwiki, I start getting nervous with such file permissions for files that are for system functionality only.

Nevertheless, I like your wiki very much and I think it is a great step forward, so I hope you keep working on it for a very long time and someday I will install it at the production system.

[NickyPhils]

Well, we don't know what plans you have for your web site, so it's hard to say how big of a security risk it would be to you and your members. What do you mean by "user stuff"? We would need more information before we could help you deal with this perceived problem.

[sowosammerneger]

"user stuff"? Pictures for galleries as an example.

Don't take it to hard, I am somewhat paranoid regarding security, since we seem to have a lot of people who don't like us and try to get our servers down.

The only real problem I see, is that the update seems to have a chance to bring down the whole site by changing the paths for all vb related software.
Maybe you can find a way to use the defaults vb will deliver and you don't need to change anything like that any more.

Thanks for the help offered.

[pegasus]

The only real problem I see, is that the update seems to have a chance to bring down the whole site by changing the paths for all vb related software.
Maybe you can find a way to use the defaults vb will deliver and you don't need to change anything like that any more.

I'm not sure I see what you mean. Are you now referring to the "Simplify Wiki Links" option that was added in 2.0.0? In 2.0.0, yes this had a possibility of bringing a whole site down by changing the paths at the wrong times, but in 2.0.1 we added a check to ensure this path change only ever occurs when viewing wiki articles. Now if this option is not enabled, it should not ever be an issue.

[sowosammerneger]

I'm not sure I see what you mean. Are you now referring to the "Simplify Wiki Links" option that was added in 2.0.0?

If this was the reason for the 404s for showthread and other, yes.

In 2.0.0, yes this had a possibility of bringing a whole site down by changing the paths at the wrong times, but in 2.0.1 we added a check to ensure this path change only ever occurs when viewing wiki articles. Now if this option is not enabled, it should not ever be an issue.

Well, but if it is an option, I want it!
Who turns down santa claus?

No harm done, since I am still on the testing site.