31.2 Guidelines and Technical Tips
| This section aims to unlock the dark secrets behind how SWAT may be made to work, may be made more secure, and how to solve Internationalization support problems. 31.2.1 Validate SWAT InstallationThe very first step that should be taken before attempting to configure a host system for SWAT operation is to check that it is installed. This may seem a trivial point to some, however several Linux distributions do not install SWAT by default, even though they do ship an installable binary support package containing SWAT on the distribution media. When you have configrmed that SWAT is installed it is necessary to validate that the installation includes the binary swat file as well as all the supporting text and Web files. A number of operating system distributions in the past have failed to include the necessary support files, evne though the swat binary executable file was installed. Finally, when you are sure that SWAT has been fully installed, please check the SWAT has been enebled in the control file for the internetworking super-daemon (inetd or xinetd) that is used on your operating system platform. 31.2.1.1 Locating the swat FileTo validate that SWAT is installed, first locate the swat binary file on the system. It may be found under the following directories:
The actual location is much dependant on the choice of the operating system vendor, or as determined by the administrator who compiled and installed Samba. There are a number methods that may be used to locate the swat binary file. The following methods may be helpful: If swat is in your current operating system search path it will be easy to find it. You can ask what are the command-line options for swat as shown here: frodo:~ # swat -? Usage: swat [OPTION...] -a, --disable-authentication Disable authentication (demo mode) Help options: -?, --help Show this help message --usage Display brief usage message Common samba options: -d, --debuglevel=DEBUGLEVEL Set debug level -s, --configfile=CONFIGFILE Use alternative configuration file -l, --log-basename=LOGFILEBASE Basename for log/debug files -V, --version Print version 31.2.1.2 Locating the SWAT Support FilesNow that you have found that swat is in the search path, it is easy to identify where the file is located. Here is another simple way this may be done: frodo:~ # whereis swat swat: /usr/sbin/swat /usr/share/man/man8/swat.8.gz If the above measures fail to locate the swat binary, another approach is needed. The following may be used: frodo:/ # find / - name swat -print /etc/xinetd.d/swat /usr/sbin/swat /usr/share/samba/swat frodo:/ # This list shows that there is a control file for xinetd , the internetwork super-daemon that is installed on this server. The location of the SWAT binary file is /usr/sbin/swat , and the support files for it are located under the directory /usr/share/samba/swat . We must now check where swat expects to find its support files. This can be done as follows : frodo:/ # strings /usr/sbin/swat grep "/swat" /swat/ ... /usr/share/samba/swat frodo:/ # The /usr/share/samba/swat/ entry shown in this listing is the location of the support files. You should verify that the support files exist under this directory. A sample list is as shown: jht@frodo:/> find /usr/share/samba/swat -print /usr/share/samba/swat /usr/share/samba/swat/help /usr/share/samba/swat/lang /usr/share/samba/swat/lang/ja /usr/share/samba/swat/lang/ja/help /usr/share/samba/swat/lang/ja/help/welcome.html /usr/share/samba/swat/lang/ja/images /usr/share/samba/swat/lang/ja/images/home.gif ... /usr/share/samba/swat/lang/ja/include /usr/share/samba/swat/lang/ja/include/header.nocss.html ... /usr/share/samba/swat/lang/tr /usr/share/samba/swat/lang/tr/help /usr/share/samba/swat/lang/tr/help/welcome.html /usr/share/samba/swat/lang/tr/images /usr/share/samba/swat/lang/tr/images/home.gif ... /usr/share/samba/swat/lang/tr/include /usr/share/samba/swat/lang/tr/include/header.html /usr/share/samba/swat/using_samba ... /usr/share/samba/swat/images /usr/share/samba/swat/images/home.gif ... /usr/share/samba/swat/include /usr/share/samba/swat/include/footer.html /usr/share/samba/swat/include/header.html jht@frodo:/> If the files needed are not available it will be necessary to obtain and install them before SWAT can be used. 31.2.2 Enabling SWAT for UseSWAT should be installed to run via the network super-daemon. Depending on which system your UNIX/Linux system has, you will have either an inetd - or xinetd -based system. The nature and location of the network super-daemon varies with the operating system implementation. The control file (or files) can be located in the file /etc/inetd.conf or in the directory /etc/[x]inet[d].d or similar. The control entry for the older style file might be: # swat is the Samba Web Administration Tool swat stream tcp nowait.400 root /usr/sbin/swat swat A control file for the newer style xinetd could be: # default: off # description: SWAT is the Samba Web Admin Tool. Use swat \ # to configure your Samba server. To use SWAT, \ # connect to port 901 with your favorite web browser. service swat { port = 901 socket_type = stream wait = no only_from = localhost user = root server = /usr/sbin/swat log_on_failure += USERID disable = yes } Both of the above examples assume that the swat binary has been located in the /usr/sbin directory. In addition to the above, SWAT will use a directory access point from which it will load its Help files as well as other control information. The default location for this on most Linux systems is in the directory /usr/share/samba/swat . The default location using Samba defaults will be /usr/local/samba/swat . Access to SWAT will prompt for a logon. If you log onto SWAT as any non-root user, the only permission allowed is to view certain aspects of configuration as well as access to the password change facility. The buttons that will be exposed to the non-root user are: HOME , STATUS , VIEW , PASSWORD . The only page that allows change capability in this case is PASSWORD . As long as you log onto SWAT as the user root , you should obtain full change and commit ability. The buttons that will be exposed include: HOME , GLOBALS , SHARES , PRINTERS , WIZARD , STATUS , VIEW , PASSWORD . 31.2.3 Securing SWAT through SSLMany people have asked about how to setup SWAT with SSL to allow for secure remote administration of Samba. Here is a method that works, courtesy of Markus Krieger. Modifications to the SWAT setup are as follows:
Afterward, simply connect to swat by using the URL https ://myhost:901 , accept the certificate and the SSL connection is up. 31.2.4 Enabling SWAT Internationalization SupportSWAT can be configured to display its messages to match the settings of the language configurations of your Web browser. It will be passed to SWAT in the Accept-Language header of the HTTP request. To enable this feature:
The name of msg file is same as the language ID sent by the browser. For example en means "English", ja means "Japanese", fr means "French. If you do not like some of messages, or there are no msg files for your locale, you can create them simply by copying the en.msg files to the dirertory for " your language ID.msg " and filling in proper strings to each " msgstr ". For example, in it.msg , the msg file for the Italian locale, just set: msgid "Set Default" msgstr "Imposta Default" and so on. If you find a mistake or create a new msg file, please email it to us so we will include this in the next release of Samba. Note that if you enable this feature and the display charset is not matched to your browser's setting, the SWAT display may be corrupted. In a future version of Samba, SWAT will always display messages with UTF-8 encoding. You will then not need to set this smb.conf file parameter. |
EAN: 2147483647
Pages: 297