Tag Info

New answers tagged

1

The problem not lies precisely in the authorization/authentication but in the modules that now manages the IIS. Inside system.webServer you should have runAllManagedModulesForAllRequests set to false so you can display all images/css without problems with authentication. In ASP.NET websites, the value of runAllManagedModulesForAllRequests previously had to ...


1

There's no difference. The first creates a new share (you can edit one) and automatically configures the share permissions to System and your current user. The second allows you to manage the share (permissions, remove, offline files, etc.).


0

In my case I had no more free space on the server with svn. Check whether you have free space in temp partition and in partition where you have svn on the server.


0

It is possible to set up multiple logins to act as the database owner: Create a "nologin" role to act as the owner: create role dbowner nologin Change the owner of your database to this: alter database mydb owner dbowner Grant all your logins to this new role: grant dbowner to user1, user2 Now, if either user1 or user2 login, they have all permissions on ...


1

On VirtualBox, at least, it seems you can't change the ownership of a share. Since boot2docker uses VirtualBox for most of the developers I'm trying to support, I can't expect to solve my problem with chown. My problem wouldn't be difficult if I could use Docker Volume Containers, but that hampers developer use. So I've come up with another solution: I wrote ...


1

I finally fixed my administrative share access issue. In my case it turned out to be a corrupted relationship between the domain and the PC. To fix it follow these simple steps: - leave the domain and join a workgroup (I used TEMP), you will be required to restart - rejoin the domain, restart required that's it, the trust was re-established and I can now ...


2

Based on comments so far: your mount works with NFSv3, it doesn't with NFSv3. you're using local accounts. This means that the problem is most likely down to NFSv4 account handling and idmapd. What happens in NFSv3 is that your client tells the server what UID and GID you're using. What happens in NFSv4 is that they use usernames and use idmapd to map ...


1

Just check nginx & php-fpm running user. ps aux | grep nginx ps aux | grep php-fpm they should work with the same user (probably nginx as i see in your config) then check that user if it can read the file. su - nginx -c "cat /usr/share/nginx/html/phpinfo.php"


2

The first things I would try in this case is to double-check the permissions on the files you are trying to read, just in case a startup script caused them to be changed. "ls -l /var/www/" would let you see this, where /var/www/ is your web root. Then, try turning on error reporting in the php configuration to see if PHP reports any additional errors when ...


0

Oh God, I feel so ashamed right now. Everything is fine. You need to RESTART nagios-nrpe-server after changing sudoers, reload is not enough. Reload is fine if you only change nrpe.cfg or other config file. @MadHatter, @Keith - thank you guys for your help!


2

S3 Signed URLs are the preferred way to do this. To use signed URLs, your ruby backend will need to use the S3 API to generate a time-limited signed URL, which is then passed to your mobile app. Doing things this way does not require you to deploy access keys to your mobile app, which is a much safer solution security-wise, and is also much easier to ...


2

This problem also occurs when you must let dovecot-lda talk with postfix. On this documentation, the author suggest two solutions Make dovecot-lda setuid-root Use sudo to wrap the invocation of dovecot-lda. Option one was well explained by coincoin. The second one will be explained below. For do that, you should have dedicated user to do sudo. Let ...


0

Try clicking the "Locations..." button and selecting "Entire Directory". If it starts working, then you have an LDAP issue. Selecting "Entire Directory" forces the Select dialog to use a GC port to execute the query. Selecting a specific domain will cause it to use an LDAP port.


0

There is no requirement that the permissions have to be 700, they just must not be writable by anybody except from the owner. And it has to be owned by yourself or root. It will only be secure if the above holds for the entire path from the root of the file system to the authorized_keys file. Some distributions by default create files and directories as ...


1

Voretaq7 has provided a good answer to your specific question (AD does not distinguish), but I do want to add that what you want is possible, depending on how much extra work you want to put in. The methods to do this involve giving your help desk users specific, delegated permissions to perform functions with a service account that is higher-privileged ...


5

To protect your, because otherwise another user on the system could add his own key to your authorized_keys file and impersonate you easily.


1

An error message like "could not open session" is often the result from error in the authentication proces. In Linux is that the PAM stack, pluggable authentication Modules. By default most distro's log authentication error messages in /var/log/secure. Start by checking there. As discussed in chat: in this case the error originated from the pam_mkhomedir ...


11

Logically a "move" is a copy (or in filesystem parlance a hard link) followed by a delete: you can't move something if you can't remove it from its original location. So no, Microsoft doesn't distinguish between "move" and "delete" because in order to do the former you must, by necessity, do the latter. If you want to prevent accidental deletion of user ...


0

After applying what SteffenNielsen said, the entire server started giving internal 500 errors. Checking the logs eventually made me realize that all the permissions got messed up because of this setting. I've managed to fix them and found the reason why I was unable to create a directory as well. It turned out I was trying to create a directory inside a ...


1

This is a setting under ISPconfig changing the immutable flag of files/folders under your web domains also preventing root from editing them. You can change it manually by entering the directory in question and execute chattr -Ri But preferably you would like to turn off the setting within ISPconfig, as it will change the above flag from time to time. Go ...


1

I tried to replicate your problem on a Debian Squeeze (6.0.10) box, but I had no trouble. If you set things up exactly like this (with the correct sudo setup, as MadHatter points out), including permissions and modes being correct, it will behave as you expect. # ls -l /etc/sudoers.d/nagios-test -r--r----- 1 root root 44 Dec 1 11:36 ...


1

Your sudoers entry specifies privileges to run /usr/local/bin/debug_now, but your script says sudo -u userA whoami. This will not work; whatever command you want to run with sudo privileges, that is what must appear in the sudoers file.


0

I suspect that mod_sql might be filtering the UID/GID values that you have assigned to your users in your SQL database. By default, mod_sql (for historical reasons) imposes a minimum value for the numeric IDs; any values below this minimum are mapped to a default value. See: http://www.proftpd.org/docs/contrib/mod_sql.html#SQLMinID and that value of ...


1

This is not possible. The permissions in TFS are created at the time the team project is created and there is no way to get back to the original set automatically. You can create a new Team Project and painstakingly go through all of the permissions and manually set them.


2

The permission for your crontab is wrong, it is owned by an (nonexistant?) user with the uid 1001, not the user gauthier (or you have some further issues with your system if your uid is 1001). Try sudo chown gauthier /var/spool/cron/crontabs/gauthier and see if this fixes this.


-1

have you check cron.allow/cron.deny ? as per man crontab says: you must be listed in cron.allow if it exist. you must not be listed in cron.deny if it exists. one of these file must exists.


0

You can edit your user crontab if you have superuser access, without modifying permissions: $ sudo crontab -u username -e I thought you could edit your user crontab without sudo, but I get the same permission issues as you, even after adding myself to the crontab group. The permissions in my user's crontab (/var/spool/cron/crontabs) are -rw-------, group ...


0

I have an alternative: What I usually do when having to move large amounts of changing data is to make a repeated run of rsync: Copy everything while the system is running, then stop it and repeat the rsync. This allows for a very short interruption. If the initial run takes very long and the data changes a lot, I sometimes insert a second run on the ...


0

You are looking for configuration management. A good step in the right direction would be to create a domain controller and add these computers to a domain. Then, you could use GPOs for the majority of configuration management tasks, often including installing software. That is a broad area and there is a learning curve associated with it. For other ...


5

You do not need root permissions - you need group permissions. For example if the group is www-data, do something along the lines of usermod -a -G www-data misterX and make sure the files are group-writable.


0

I think I missed an important point, the server is a proxy server, and the upstream server has a lot rewrite rules, so what should be matched here is not the file itself, but the url. so the solution is like this: find the rewrite rule in the upstream server, locate the key word you want to match, add location ^~ /keyword { return 404; }


0

Use location /path/to/xxx.php instead of location xxx.php.



Top 50 recent answers are included