The previous commands that use sudoedit are preferred because more secure: the command will copy the system file to a temporary file that can be edited with a normal editor. A way that would have worked, but which is less recommended for security, would be: sudo nano /etc/ImageMagick-6/policy.xml Thus, sudo attempts to run that file as an executable, but that fails because it is not an executable. However, instead of providing a command, you provided the file name. will run a command following it, which will elevate the following command to root permissions. sudo will then run that other command with elevated privileges (administrator or root privileges, required to change system files). This command should be followed by another command. The command you attempted yourself just specifies sudo. This opens the file in the standard terminal editor, nano on Ubuntu. If you can work with the standard terminal based editor nano, then the command simplifies to: sudoedit /etc/ImageMagick-6/policy.xml To make editing as easy as possible, you may want to open the system file in your graphical text editor, gedit in the standard Ubuntu desktop: env EDITOR=gedit sudoedit /etc/ImageMagick-6/policy.xml To edit the file, you need to open it in a text editor with root (administrator) privileges. Thus not preferred.Įditing the policy file to only enable PDF operations. Easy to do with a single rm (remove) command, but not secure at all. To overcome the restrictions, there are two possibilities: This answer gives you a detailed account of what you need to do.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |