|
System |
|
Linux detected
permissions need to be set on this system |
|
Chmod settings |
|
No install directories detected
Selecting After-install Chmod settings for this process>
Error: No config.sys found |
|
Chmodmethod |
|
PHP CHMOD permitted by server
The normal CHMOD procedure will be used
(no need for an FTP connection) |
|
What is chmod?
|
CHMOD - What is it? |
Chmod stands for Change Mode. Basically it tells the server what the file or folder permissions are, ie. can the script read the info, or can it write information as well.
Some files or folders of integraMOD need to be given the right permissions to work properly. Giving permissions to files or folders in Unix world is called chmod. So chmod is a Unix command that lets you tell the system how much or little access it should be permitted to a file. |
|
CHMOD only works on LINUX systems! |
|
Both Linux and Windows come in desktop and server editions.
There is no such thing as CHMOD in WINDOWS.
CHMOD only works with Apache on a Unix, Linux system.
I can only recommend using a LINUX-server!
Why not on Windows-servers?
Windows can't distinguish between user/group/other the way it is done in UNIX-filesystems. Therefore, they always match the individual permissions.
And if you don't have admin rights, you will have to ask the server administrator to change permissions for you, there is no standard way for clients to change permissions remotely. Windows does not support FTP CHMOD and setuid solutions are much rarer there.
Unless the filesystem is NTFS then permissions aren't going to come into play at all. If you're using Fat32, then every file on the system is essentially chmod 777.
On Windows systems, most of the permissions shown are artificial, with no real meaning. The w bit is set according to the ReadOnly attribute, and the rx bits are always set on.
Why use Linux as server?
The UNIX/Linux commands that are offered are far more powerful than those offered by MS Windows.
There are more options in UNIX/Linux.
For example, switches are case sensitive, so you can have even more switches than in MS Windows, as MS Windows is not case sensitive.
This is just a minor comparison and contrast between UNIX/Linux and MS Windows.
Why recommend Linux as server?
There are several cases where a flaw in Apache poses little or no danger on Linux, but is a serious vulnerability on Windows. The reverse is rarely, if ever, the case.
Should the overall security ranking of Windows suffer because it is more adversely affected than Linux when using software that is most commonly associated with Linux?
But even the most critical differentiating factor between the two operating systems, is all about security.
Windows encourages you to use the familiar interface, which means administering Windows Server 2003 at the server itself.
Linux does not rely on or encourage local use of a graphical interface, in part because it is an unnecessary waste of resources to run a graphical desktop at the server, and in part because it increases security risks at the server.
For example, any server that encourages you to use the graphical interface at the server machine also invites you to perform similar operations, such as use the browser at the server. This exposes that server to any browser security holes. Any server that encourages you to administer it remotely removes this risk.
If you administer a Linux server remotely from a desktop user account, a browser flaw exposes only the remote desktop user account to security holes, not the server. This is why a browser security hole in Windows Server 2003 is potentially more serious than a browser security hole in Red Hat Enterprise Server AS.
Advantages of Linux.
Speed, efficiency and reliability are all increased by running a server instance of Linux without a GUI, something that server versions of Windows can not do.
|
|
What do the Chmod Settings Mean? |
Chmod tells the server the access privileges for a file. For example, common file settings are:
| 777: | all can read / write / execute the file. | | 755: | owner can do all, group / others can read / execute. | | 644: | owner can read / write, group / others can read only. |
chmod Tutorial
Using the numbering scheme, the chmod command has three number places,
for example 744, representing the three user types.
The first number on the left side is for 'user', the middle one is for 'group' and the right hand one for 'other'. Now, here's what each number does:
| 0 | --- | no access | | 1 | --x | execute | | 2 | -w- | write | | 3 | -wx | write and execute | | 4 | r-- | read | | 5 | r-x | read and execute | | 6 | rw- | read and write | | 7 | rwx | read write execute (full access) |
|
|
Chmod - How? |
An FTP client is often used for such task. Depending on the FTP client you are using, chmod is usually available through Menus or by simply clicking the right mouse button when hovering over a file/folder and choosing the (chmod/property) item. Then checking properties or entering the corresponding chmod numbers in that dialogue.
But when there are many files/directories to chmod, like with integraMOD, it can take some time to do it that way and mistakes can happen.
This chmoder-script will do it automatically for you.
2 PHP commands are used:
Chmod()
This will only work if you are authorized as the owner, but on some servers, only the host is the owner.
ftp_site(connection, CHMOD)
This will work for everybody, but as always with FTP, name and password are required.
For maximum comfort, the second method will only be used if the first one fails.
Username and password will only be asked for, when needed. |
|
