AuthzSVNAccessFile /home/svnroot/repository/authz.conf //权限配置文件 AuthType Basic //连接类型设置 AuthName "Subversion.com" //连接框提示 ..
基于64个网页-相关网页
AuthzSVNAccessFile /home/svnroot/repository/authz.conf //权限配置文件 AuthType Basic //连接类型设置 AuthName "Subversion.com" //连接框提示 ..
基于60个网页-相关网页
AuthzSVNAccessFile /home/svnroot/repository/authz.conf //权限配置文件 AuthType Basic //连接类型设置 AuthName "Subversion.com" //连接框提示 ..
基于60个网页-相关网页
如果不谨慎地控制谁对文件系统有写访问权限,用户只需手工编辑配置文件,就可以破坏产品的安全性控制(比如审计)。
If you do not carefully control who has write access to the file system, a user can subvert the product security controls (such as auditing) by simply hand editing the configuration files.
要避免上述问题,有个出人意料的解决方法:不要让构建代理的网络账号对配置文件有写权限。
A surprisingly easy way to avoid the above problems is to simply not allow the build agent's network account to have write access to the configuration files.
在创建配置文件之前,帐户不具有权限。但使用第一个用例中的技巧需要为通道访问的每一个队列都创建一个配置文件。
The account has no access unless profiles are created for it, but using the techniques from the first case study would require a profile for every queue to which the channel needs access.
应用推荐