投稿日:2002年11月08日 作成鷹の巣

No.6283 このアクセスは放置しておいていいのでしょうか?



このアクセスは放置しておいていいのでしょうか?

No.6283 投稿時間:2002年11月08日(Fri) 09:10 投稿者名:リカ URL:

お世話になってます。m(_ _)m 。新米ルートのリカです。
自分の担当してるサーバーに最近こんなアクセスがやたらあるのですが
放置しておいてよろしいのでしょうか?
少し調べたのですが、バックドアから侵入しようとしてるとありましたが、
対処がよくわかりません。
OSはRedHat7.3でカーネルは最新のものにバージョンupしてあります。
また、いい参考サイトとかご存知でしたら教えてください。
よろしくお願いします。

"GET /MSADC/root.exe?/c+dir HTTP/1.0" 404 278
"GET /c/winnt/system32/cmd.exe?/c+dir HTTP/1.0" 404 288
"GET /d/winnt/system32/cmd.exe?/c+dir HTTP/1.0" 404 288
"GET /scripts/..%255c../winnt/system32/cmd.exe?/c+dir HTTP/1.0" 404 302
"GET /_vti_bin/..%255c../..%255c../..%255c../winnt/system32/cmd.exe?/c+dir HTTP/1.0" 404 319
"GET /_mem_bin/..%255c../..%255c../..%255c../winnt/system32/cmd.exe?/c+dir HTTP/1.0" 404 319
"GET /msadc/..%255c../..%255c../..%255c/..%c1%1c../..%c1%1c../..%c1%1c../winnt/system32/cmd.exe?/c+dir HTTP/1.0" 404 335
"GET /scripts/..%c1%1c../winnt/system32/cmd.exe?/c+dir HTTP/1.0" 404 301
"GET /scripts/root.exe?/c+dir HTTP/1.0" 404 280
"GET /scripts/..%c0%2f../winnt/system32/cmd.exe?/c+dir HTTP/1.0" 404 301
"GET /scripts/..%c0%af../winnt/system32/cmd.exe?/c+dir HTTP/1.0" 404 301
"GET /scripts/..%c1%9c../winnt/system32/cmd.exe?/c+dir HTTP/1.0" 404 301
"GET /scripts/..%%35%63../winnt/system32/cmd.exe?/c+dir HTTP/1.0" 400 285
"GET /scripts/..%%35c../winnt/system32/cmd.exe?/c+dir HTTP/1.0" 400 285
"GET /scripts/..%25%35%63../winnt/system32/cmd.exe?/c+dir HTTP/1.0" 404 302
"GET /scripts/..%252f../winnt/system32/cmd.exe?/c+dir HTTP/1.0" 404 302


WindowsのIISサーバーに対する攻撃です

No.6290 投稿時間:2002年11月08日(Fri) 18:55 投稿者名:ryujin URL:http://www.ryujin.info/

IISを未使用ですし、全て404ですから無視しましょう。
これからもチョクチョク見かける残骸ログになるでしょうね。

ワームによる IIS への攻撃
http://www.jpcert.or.jp/at/2001/at010009.txt

> "GET /MSADC/root.exe?/c+dir HTTP/1.0" 404 278
> "GET /c/winnt/system32/cmd.exe?/c+dir HTTP/1.0" 404 288
> "GET /d/winnt/system32/cmd.exe?/c+dir HTTP/1.0" 404 288
> "GET /scripts/..%255c../winnt/system32/cmd.exe?/c+dir HTTP/1.0" 404 302
> "GET /_vti_bin/..%255c../..%255c../..%255c../winnt/system32/cmd.exe?/c+dir HTTP/1.0" 404 319
> "GET /_mem_bin/..%255c../..%255c../..%255c../winnt/system32/cmd.exe?/c+dir HTTP/1.0" 404 319

http://www.ipa.go.jp/security/index.html
http://www.jpcert.or.jp/at/
https://www.netsecurity.ne.jp/
などの情報を時たま参照してLinuxの脆弱性報告を点検しましょう。

参考)
Code Red ワームが侵入を試みたホスト上で稼動している
Web サーバプログラムのログには以下のような記録が残ることがあります
http://www.jpcert.or.jp/at/2001/at010014.txt


ryujinさん、ありがとうございました。

No.6298 投稿時間:2002年11月09日(Sat) 01:12 投稿者名:リカ URL:

ryujinさん、またまたありがとうございます。
jcode.plの件ではお騒がせしました。m(_ _)m
サーバーがおちるぐらいならまだしも、ルートをとられるのだけは
絶対にさけたいので,案内いただいたサイトを参考にして、
メンテしていきます。


Re: access_log で目障りなら分離してみるとか

No.6300 投稿時間:2002年11月09日(Sat) 01:19 投稿者名:yk URL:

> これからもチョクチョク見かける残骸ログになるでしょうね。

無視していいんですが access_log で目障りなら、分離して
IPアドレスやホスト名を公開してあげる
という手もあります。(自分は、ほとんど気づいてないし)

この場合の設定
/etc/httpd/conf/httpd.conf
の Log設定で

####################### Log

HostnameLookups Off

### Only Lookup Host Neme ( Atack request) .exe についてだけホストネームを探る
<Files ~ "\.(exe)$>
HostnameLookups on
</Files>

# ErrorLog: The location of the error log file.
ErrorLog /var/log/httpd/error_log
LogLevel warn

# Atack Log Set 攻撃文字列の指定 .exe(増えたら適宜追加)
<IfModule mod_setenvif.c>
SetEnvIf Request_URI "\.exe" atack
</IfModule>

LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined

#access_log から atackを除外
CustomLog /var/log/httpd/access_log combined env=!atack

#ドキュメントルートが /home/wwwの場合 atack_log.txtを公開するためここに作成
CustomLog /home/www/usage/atack_log.txt combined env=atack


これは400番台のエラーメッセージに自分のIPが表示されるってことでしょうか?

No.6330 投稿時間:2002年11月10日(Sun) 02:43 投稿者名:リカ URL:

ykさん、回答ありがとうございます。
なにぶん設定ファイルを直接編集したことがほとんどないのでおっしゃる意味がよくわかっていません。
apacheはOS付属の設定ツールとファイル編集を併用してはいけないと本にあったのですが、本当なのでしょうか?
加えて.htaccessを置いてでアクセス制限したいのですが、私の調べ方がまずいのか、
(1)どの設定ファイルの(2)どこを(3)どのように書き換えればいいのかわかりませんでした。
またバーチャルホストの設定もうまくいかず、新しくホストをつくるとデフォルトのホストが表示されなくなってしまいます(涙)
どうやって解決すればいいでしょうか?アドバイスよろしくお願いしますm(_ _)m


アパッチ設定

No.6333 投稿時間:2002年11月10日(Sun) 07:57 投稿者名:OAK URL:

> 加えて.htaccessを置いてでアクセス制限したいのですが、私の調べ方がまずいのか、
> (1)どの設定ファイルの(2)どこを(3)どのように書き換えればいいのかわかりませんでした。
> またバーチャルホストの設定もうまくいかず、新しくホストをつくるとデフォルトのホストが表示されなくなってしまいます(涙)
> どうやって解決すればいいでしょうか?アドバイスよろしくお願いしますm(_ _)m


.htaccess の設定。http://www.apache.jp/docs/configuring.html
バーチャルホストの設定 http://www.apache.jp/docs/vhosts/name-based.html

うまく行かない場合は、confファイルをこう直したけどここがだめとか書いてください。


httpd.conf公開 第一弾

No.6342 投稿時間:2002年11月10日(Sun) 14:57 投稿者名:リカ URL:

OAKさん、回答ありがとうございます。忘れもしません、以前Apacheの件でお世話になりました。m(_ _)m
私のやりたいことは
(1)新たにインストールしたApacheのドキュメントルートを/var/www/html(http://abc.com,master@abc.com),
CGIの置き場所を/var/www/cgi-bin/に変更して、これ以外の場所でCGIは使用不可にする。
(2).htaccessを/var/www/html以下限定で利用可にする。
(3)バーチャルホスト(http://xyz.com,master@xyz.com)を/home/user/public_htmlで公開する。以上3点です。

それを以下に記した(section2)httpd.confで指定したつもりですが、
次の不具合がでます。
(a)http://abc.comhttp://xyz.com共に/home/user/public_htmlが表示される。
(b).htaccessで試験的に192.168.0.*からだけのアクセス許可にしたつもりが、外部からも見えてしまう。
.htaccessの中身は

order allow,deny
deny from all
allow from 192.168.0
<Files ".*">
deny from all
</Files>

修正、疑問のあるところは、<----------------がついてます。
どこに不備があるのか、ご指摘お願いします。m(_ _)m
なおApacheのバージョンは1.3.27です。

# Section 2: 'Main' server configuration
#
# The directives in this section set up the values used by the 'main'
# server, which responds to any requests that aren't handled by a
# <VirtualHost> definition. These values also provide defaults for
# any <VirtualHost> containers you may define later in the file.
#
# All of these directives may appear inside <VirtualHost> containers,
# in which case these default settings will be overridden for the
# virtual host being defined.
#

<IfModule !mpm_winnt.c>
<IfModule !mpm_netware.c>
#
# If you wish httpd to run as a different user or group, you must run
# httpd as root initially and it will switch.
#
# User/Group: The name (or #number) of the user/group to run httpd as.
# . On SCO (ODT 3) use "User nouser" and "Group nogroup".
# . On HPUX you may not be able to use shared memory as nobody, and the
# suggested workaround is to create a user www and use that user.
# NOTE that some kernels refuse to setgid(Group) or semctl(IPC_SET)
# when the value of (unsigned)Group is above 60000;
# don't use Group #-1 on these systems!
#
User nobody
Group #-1
</IfModule>
</IfModule>

#
# ServerAdmin: Your address, where problems with the server should be
# e-mailed. This address appears on some server-generated pages, such
# as error documents. e.g. admin@your-domain.com
#
ServerAdmin master@abc.com <-----------------------------------------ok!

#
# ServerName gives the name and port that the server uses to identify itself.
# This can often be determined automatically, but we recommend you specify
# it explicitly to prevent problems during startup.
#
# If this is not set to valid DNS name for your host, server-generated
# redirections will not work. See also the UseCanonicalName directive.
#
# If your host doesn't have a registered DNS name, enter its IP address here.
# You will have to access it by its address anyway, and this will make
# redirections work in a sensible way.
#
ServerName abc.com <--------------------------------------------------------ok!

#
# UseCanonicalName: Determines how Apache constructs self-referencing
# URLs and the SERVER_NAME and SERVER_PORT variables.
# When set "Off", Apache will use the Hostname and Port supplied
# by the client. When set "On", Apache will use the value of the
# ServerName directive.
#
UseCanonicalName Off

#
# DocumentRoot: The directory out of which you will serve your
# documents. By default, all requests are taken from this directory, but
# symbolic links and aliases may be used to point to other locations.
#
DocumentRoot "/var/www/html" <-------------------------------ok!
#
# Each directory to which Apache has access can be configured with respect
# to which services and features are allowed and/or disabled in that
# directory (and its subdirectories).
#
# First, we configure the "default" to be a very restrictive set of
# features.
#
<Directory />
Options FollowSymLinks
AllowOverride all <--------------------?これで.htaccessを許可できたとおもうのですが・・

</Directory>

#
# Note that from this point forward you must specifically allow
# particular features to be enabled - so if something's not working as
# you might expect, make sure that you have specifically enabled it
# below.
#

#
# This should be changed to whatever you set DocumentRoot to.
#
<Directory "/var/www/html"> <--------------------ok!

#
# Possible values for the Options directive are "None", "All",
# or any combination of:
# Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI Multiviews
#
# Note that "MultiViews" must be named *explicitly* --- "Options All"
# doesn't give it to you.
#
# The Options directive is both complicated and important. Please see
# http://httpd.apache.org/docs-2.0/mod/core.html#options
# for more information.
#
Options Indexes FollowSymLinks

#
# AllowOverride controls what directives may be placed in .htaccess files.
# It can be "All", "None", or any combination of the keywords:
# Options FileInfo AuthConfig Limit
#
AllowOverride all <---------------------------------?

#
# Controls who can get stuff from this server.
#
Order allow,deny
Allow from all

</Directory>

#
# UserDir: The name of the directory that is appended onto a user's home
# directory if a ~user request is received.
#
UserDir public_html <-------------------------------ok!

#
# Control access to UserDir directories. The following is an example
# for a site where these directories are restricted to read-only.
#
<Directory /home/*/public_html> <----------------------?
AllowOverride FileInfo AuthConfig Limit Indexes
Options MultiViews Indexes SymLinksIfOwnerMatch IncludesNoExec
<Limit GET POST OPTIONS PROPFIND>
Order allow,deny
Allow from all
</Limit>
<LimitExcept GET POST OPTIONS PROPFIND>
Order deny,allow
Deny from all
</LimitExcept>
</Directory>

#
# DirectoryIndex: sets the file that Apache will serve if a directory
# is requested.
#
# The index.html.var file (a type-map) is used to deliver content-
# negotiated documents. The MultiViews Option can be used for the
# same purpose, but it is much slower.
#
DirectoryIndex index.html index.html.var

#
# AccessFileName: The name of the file to look for in each directory
# for additional configuration directives. See also the AllowOverride
# directive.
#
AccessFileName .htaccess <-----------------------ok!

#
# The following lines prevent .htaccess and .htpasswd files from being
# viewed by Web clients.
#
<Files ~ "^\.ht"> <-----------ok! .htaccessが格納されたディレクトリはアクセスを拒否
Order allow,deny
Deny from all
</Files>

#
# TypesConfig describes where the mime.types file (or equivalent) is
# to be found.
#
TypesConfig conf/mime.types

#
# DefaultType is the default MIME type the server will use for a document
# if it cannot otherwise determine one, such as from filename extensions.
# If your server contains mostly text or HTML documents, "text/plain" is
# a good value. If most of your content is binary, such as applications
# or images, you may want to use "application/octet-stream" instead to
# keep browsers from trying to display binary files as though they are
# text.
#
DefaultType text/plain

#
# The mod_mime_magic module allows the server to use various hints from the
# contents of the file itself to determine its type. The MIMEMagicFile
# directive tells the module where the hint definitions are located.
#
<IfModule mod_mime_magic.c>
MIMEMagicFile conf/magic
</IfModule>

#
# HostnameLookups: Log the names of clients or just their IP addresses
# e.g., www.apache.org (on) or 204.62.129.132 (off).
# The default is off because it'd be overall better for the net if people
# had to knowingly turn this feature on, since enabling it means that
# each client request will result in AT LEAST one lookup request to the
# nameserver.
#
HostnameLookups Off

#
# EnableMMAP: Control whether memory-mapping is used to deliver
# files (assuming that the underlying OS supports it).
# The default is on; turn this off if you serve from NFS-mounted
# filesystems. On some systems, turning it off (regardless of
# filesystem) can improve performance; for details, please see
# http://httpd.apache.org/docs-2.0/mod/core.html#enablemmap
#
#EnableMMAP off

#
# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here. If you *do* define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
#
ErrorLog logs/error_log

#
# LogLevel: Control the number of messages logged to the error_log.
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
#
LogLevel warn

#
# The following directives define some format nicknames for use with
# a CustomLog directive (see below).
#
LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
LogFormat "%h %l %u %t \"%r\" %>s %b" common
LogFormat "%{Referer}i -> %U" referer
LogFormat "%{User-agent}i" agent

#
# The location and format of the access logfile (Common Logfile Format).
# If you do not define any access logfiles within a <VirtualHost>
# container, they will be logged here. Contrariwise, if you *do*
# define per-<VirtualHost> access logfiles, transactions will be
# logged therein and *not* in this file.
#
CustomLog logs/access_log common

#
# If you would like to have agent and referer logfiles, uncomment the
# following directives.
#
#CustomLog logs/referer_log referer
#CustomLog logs/agent_log agent

#
# If you prefer a single logfile with access, agent, and referer information
# (Combined Logfile Format) you can use the following directive.
#
#CustomLog logs/access_log combined

#
# ServerTokens
# This directive configures what you return as the Server HTTP response
# Header. The default is 'Full' which sends information about the OS-Type
# and compiled in modules.
# Set to one of: Full | OS | Minor | Minimal | Major | Prod
# where Full conveys the most information, and Prod the least.
#
ServerTokens Full

#
# Optionally add a line containing the server version and virtual host
# name to server-generated pages (internal error documents, FTP directory
# listings, mod_status and mod_info output etc., but not CGI generated
# documents or custom error documents).
# Set to "EMail" to also include a mailto: link to the ServerAdmin.
# Set to one of: On | Off | EMail
#
ServerSignature On

#
# Aliases: Add here as many aliases as you need (with no limit). The format is
# Alias fakename realname
#
# Note that if you include a trailing / on fakename then the server will
# require it to be present in the URL. So "/icons" isn't aliased in this
# example, only "/icons/". If the fakename is slash-terminated, then the
# realname must also be slash terminated, and if the fakename omits the
# trailing slash, the realname must also omit it.
#
# We include the /icons/ alias for FancyIndexed directory listings. If you
# do not use FancyIndexing, you may comment this out.
#
Alias /icons/ "/usr/local/apache2/icons/"

<Directory "/usr/local/apache2/icons">
Options Indexes MultiViews
AllowOverride None
Order allow,deny
Allow from all
</Directory>

#
# This should be changed to the ServerRoot/manual/. The alias provides
# the manual, even if you choose to move your DocumentRoot. You may comment
# this out if you do not care for the documentation.
#
Alias /manual "/usr/local/apache2/manual"

<Directory "/usr/local/apache2/manual">
Options Indexes FollowSymLinks MultiViews IncludesNoExec
AddOutputFilter Includes html
AllowOverride None
Order allow,deny
Allow from all
</Directory>

#
# ScriptAlias: This controls which directories contain server scripts.
# ScriptAliases are essentially the same as Aliases, except that
# documents in the realname directory are treated as applications and
# run by the server when requested rather than as documents sent to the client.
# The same rules about trailing "/" apply to ScriptAlias directives as to
# Alias.
#
ScriptAlias /cgi-bin/ "/var/www/cgi-bin/" <---------------ok!

<IfModule mod_cgid.c>
#
# Additional to mod_cgid.c settings, mod_cgid has Scriptsock <path>
# for setting UNIX socket for communicating with cgid.
#
#Scriptsock logs/cgisock
</IfModule>


httpd.conf公開第二弾

No.6343 投稿時間:2002年11月10日(Sun) 15:01 投稿者名:リカ URL:

#
# "/usr/local/apache2/cgi-bin" should be changed to whatever your ScriptAliased
# CGI directory exists, if you have that configured.
#
<Directory "/var/www/cgi-bin"> <-------------------ok!
AllowOverride None
Options None
Order allow,deny
Allow from all <---------?cgi-binディレクトリのアクセス権allでいいのでしょうか?
</Directory>

#
# Redirect allows you to tell clients about documents which used to exist in
# your server's namespace, but do not anymore. This allows you to tell the
# clients where to look for the relocated document.
# Example:
# Redirect permanent /foo http://www.example.com/bar

#
# Directives controlling the display of server-generated directory listings.
#

#
# IndexOptions: Controls the appearance of server-generated directory
# listings.
#
IndexOptions FancyIndexing VersionSort

#
# AddIcon* directives tell the server which icon to show for different
# files or filename extensions. These are only displayed for
# FancyIndexed directories.
#
AddIconByEncoding (CMP,/icons/compressed.gif) x-compress x-gzip

AddIconByType (TXT,/icons/text.gif) text/*
AddIconByType (IMG,/icons/image2.gif) image/*
AddIconByType (SND,/icons/sound2.gif) audio/*
AddIconByType (VID,/icons/movie.gif) video/*

AddIcon /icons/binary.gif .bin .exe
AddIcon /icons/binhex.gif .hqx
AddIcon /icons/tar.gif .tar
AddIcon /icons/world2.gif .wrl .wrl.gz .vrml .vrm .iv
AddIcon /icons/compressed.gif .Z .z .tgz .gz .zip
AddIcon /icons/a.gif .ps .ai .eps
AddIcon /icons/layout.gif .html .shtml .htm .pdf
AddIcon /icons/text.gif .txt
AddIcon /icons/c.gif .c
AddIcon /icons/p.gif .pl .py
AddIcon /icons/f.gif .for
AddIcon /icons/dvi.gif .dvi
AddIcon /icons/uuencoded.gif .uu
AddIcon /icons/script.gif .conf .sh .shar .csh .ksh .tcl
AddIcon /icons/tex.gif .tex
AddIcon /icons/bomb.gif core

AddIcon /icons/back.gif ..
AddIcon /icons/hand.right.gif README
AddIcon /icons/folder.gif ^^DIRECTORY^^
AddIcon /icons/blank.gif ^^BLANKICON^^

#
# DefaultIcon is which icon to show for files which do not have an icon
# explicitly set.
#
DefaultIcon /icons/unknown.gif

#
# AddDescription allows you to place a short description after a file in
# server-generated indexes. These are only displayed for FancyIndexed
# directories.
# Format: AddDescription "description" filename
#
#AddDescription "GZIP compressed document" .gz
#AddDescription "tar archive" .tar
#AddDescription "GZIP compressed tar archive" .tgz

#
# ReadmeName is the name of the README file the server will look for by
# default, and append to directory listings.
#
# HeaderName is the name of a file which should be prepended to
# directory indexes.
ReadmeName README.html
HeaderName HEADER.html

#
# IndexIgnore is a set of filenames which directory indexing should ignore
# and not include in the listing. Shell-style wildcarding is permitted.
#
IndexIgnore .??* *~ *# HEADER* README* RCS CVS *,v *,t

#
# AddEncoding allows you to have certain browsers (Mosaic/X 2.1+) uncompress
# information on the fly. Note: Not all browsers support this.
# Despite the name similarity, the following Add* directives have nothing
# to do with the FancyIndexing customization directives above.
#
AddEncoding x-compress Z
AddEncoding x-gzip gz tgz

#
# DefaultLanguage and AddLanguage allows you to specify the language of
# a document. You can then use content negotiation to give a browser a
# file in a language the user can understand.
#
# Specify a default language. This means that all data
# going out without a specific language tag (see below) will
# be marked with this one. You probably do NOT want to set
# this unless you are sure it is correct for all cases.
#
# * It is generally better to not mark a page as
# * being a certain language than marking it with the wrong
# * language!
#
# DefaultLanguage nl
#
# Note 1: The suffix does not have to be the same as the language
# keyword --- those with documents in Polish (whose net-standard
# language code is pl) may wish to use "AddLanguage pl .po" to
# avoid the ambiguity with the common suffix for perl scripts.
#
# Note 2: The example entries below illustrate that in some cases
# the two character 'Language' abbreviation is not identical to
# the two character 'Country' code for its country,
# E.g. 'Danmark/dk' versus 'Danish/da'.
#
# Note 3: In the case of 'ltz' we violate the RFC by using a three char
# specifier. There is 'work in progress' to fix this and get
# the reference data for rfc1766 cleaned up.
#
# Danish (da) - Dutch (nl) - English (en) - Estonian (et)
# French (fr) - German (de) - Greek-Modern (el)
# Italian (it) - Norwegian (no) - Norwegian Nynorsk (nn) - Korean (ko)
# Portugese (pt) - Luxembourgeois* (ltz)
# Spanish (es) - Swedish (sv) - Catalan (ca) - Czech(cz)
# Polish (pl) - Brazilian Portuguese (pt-br) - Japanese (ja)
# Russian (ru) - Croatian (hr)
#
AddLanguage da .dk
AddLanguage nl .nl
AddLanguage en .en
AddLanguage et .et
AddLanguage fr .fr
AddLanguage de .de
AddLanguage he .he
AddLanguage el .el
AddLanguage it .it
AddLanguage ja .ja
AddLanguage pl .po
AddLanguage ko .ko
AddLanguage pt .pt
AddLanguage nn .nn
AddLanguage no .no
AddLanguage pt-br .pt-br
AddLanguage ltz .ltz
AddLanguage ca .ca
AddLanguage es .es
AddLanguage sv .se
AddLanguage cz .cz
AddLanguage ru .ru
AddLanguage tw .tw
AddLanguage zh-tw .tw
AddLanguage hr .hr

#
# LanguagePriority allows you to give precedence to some languages
# in case of a tie during content negotiation.
#
# Just list the languages in decreasing order of preference. We have
# more or less alphabetized them here. You probably want to change this.
#
LanguagePriority en da nl et fr de el it ja ko no pl pt pt-br ltz ca es sv tw

#
# ForceLanguagePriority allows you to serve a result page rather than
# MULTIPLE CHOICES (Prefer) [in case of a tie] or NOT ACCEPTABLE (Fallback)
# [in case no accepted languages matched the available variants]
#
ForceLanguagePriority Prefer Fallback

#
# Specify a default charset for all pages sent out. This is
# always a good idea and opens the door for future internationalisation
# of your web site, should you ever want it. Specifying it as
# a default does little harm; as the standard dictates that a page
# is in iso-8859-1 (latin1) unless specified otherwise i.e. you
# are merely stating the obvious. There are also some security
# reasons in browsers, related to javascript and URL parsing
# which encourage you to always set a default char set.
#
AddDefaultCharset ISO-8859-1

#
# Commonly used filename extensions to character sets. You probably
# want to avoid clashes with the language extensions, unless you
# are good at carefully testing your setup after each change.
# See ftp://ftp.isi.edu/in-notes/iana/assignments/character-sets for
# the official list of charset names and their respective RFCs
#
AddCharset ISO-8859-1 .iso8859-1 .latin1
AddCharset ISO-8859-2 .iso8859-2 .latin2 .cen
AddCharset ISO-8859-3 .iso8859-3 .latin3
AddCharset ISO-8859-4 .iso8859-4 .latin4
AddCharset ISO-8859-5 .iso8859-5 .latin5 .cyr .iso-ru
AddCharset ISO-8859-6 .iso8859-6 .latin6 .arb
AddCharset ISO-8859-7 .iso8859-7 .latin7 .grk
AddCharset ISO-8859-8 .iso8859-8 .latin8 .heb
AddCharset ISO-8859-9 .iso8859-9 .latin9 .trk
AddCharset ISO-2022-JP .iso2022-jp .jis
AddCharset ISO-2022-KR .iso2022-kr .kis
AddCharset ISO-2022-CN .iso2022-cn .cis
AddCharset Big5 .Big5 .big5
# For russian, more than one charset is used (depends on client, mostly):
AddCharset WINDOWS-1251 .cp-1251 .win-1251
AddCharset CP866 .cp866
AddCharset KOI8-r .koi8-r .koi8-ru
AddCharset KOI8-ru .koi8-uk .ua
AddCharset ISO-10646-UCS-2 .ucs2
AddCharset ISO-10646-UCS-4 .ucs4
AddCharset UTF-8 .utf8

# The set below does not map to a specific (iso) standard
# but works on a fairly wide range of browsers. Note that
# capitalization actually matters (it should not, but it
# does for some browsers).
#
# See ftp://ftp.isi.edu/in-notes/iana/assignments/character-sets
# for a list of sorts. But browsers support few.
#
AddCharset GB2312 .gb2312 .gb
AddCharset utf-7 .utf7
AddCharset utf-8 .utf8
AddCharset big5 .big5 .b5
AddCharset EUC-TW .euc-tw
AddCharset EUC-JP .euc-jp
AddCharset EUC-KR .euc-kr
AddCharset shift_jis .sjis

#
# AddType allows you to add to or override the MIME configuration
# file mime.types for specific file types.
#
AddType application/x-tar .tgz
AddType image/x-icon .ico

#
# AddHandler allows you to map certain file extensions to "handlers":
# actions unrelated to filetype. These can be either built into the server
# or added with the Action directive (see below)
#
# To use CGI scripts outside of ScriptAliased directories:
# (You will also need to add "ExecCGI" to the "Options" directive.)
#
#AddHandler cgi-script .cgi

#
# For files that include their own HTTP headers:
#
#AddHandler send-as-is asis

#
# For server-parsed imagemap files:
#
#AddHandler imap-file map

#
# For type maps (negotiated resources):
# (This is enabled by default to allow the Apache "It Worked" page
# to be distributed in multiple languages.)
#
AddHandler type-map var

#
# Filters allow you to process content before it is sent to the client.
#
# To parse .shtml files for server-side includes (SSI):
# (You will also need to add "Includes" to the "Options" directive.)
#
#AddType text/html .shtml
#AddOutputFilter INCLUDES .shtml

#
# Action lets you define media types that will execute a script whenever
# a matching file is called. This eliminates the need for repeated URL
# pathnames for oft-used CGI file processors.
# Format: Action media/type /cgi-script/location
# Format: Action handler-name /cgi-script/location
#

#
# Customizable error responses come in three flavors:
# 1) plain text 2) local redirects 3) external redirects
#
# Some examples:
#ErrorDocument 500 "The server made a boo boo."
#ErrorDocument 404 /missing.html
#ErrorDocument 404 "/cgi-bin/missing_handler.pl"
#ErrorDocument 402 http://www.example.com/subscription_info.html
#

#
# Putting this all together, we can internationalize error responses.
#
# We use Alias to redirect any /error/HTTP_<error>.html.var response to
# our collection of by-error message multi-language collections. We use
# includes to substitute the appropriate text.
#
# You can modify the messages' appearance without changing any of the
# default HTTP_<error>.html.var files by adding the line:
#
# Alias /error/include/ "/your/include/path/"
#
# which allows you to create your own set of files by starting with the
# /usr/local/apache2/error/include/ files and copying them to /your/include/path/,
# even on a per-VirtualHost basis. The default include files will display
# your Apache version number and your ServerAdmin email address regardless
# of the setting of ServerSignature.
#
# The internationalized error documents require mod_alias, mod_include
# and mod_negotiation. To activate them, uncomment the following 30 lines.

# Alias /error/ "/usr/local/apache2/error/"
#
# <Directory "/usr/local/apache2/error">
# AllowOverride None
# Options IncludesNoExec
# AddOutputFilter Includes html
# AddHandler type-map var
# Order allow,deny
# Allow from all
# LanguagePriority en de es fr it nl sv
# ForceLanguagePriority Prefer Fallback
# </Directory>
#
# ErrorDocument 400 /error/HTTP_BAD_REQUEST.html.var
# ErrorDocument 401 /error/HTTP_UNAUTHORIZED.html.var
# ErrorDocument 403 /error/HTTP_FORBIDDEN.html.var
# ErrorDocument 404 /error/HTTP_NOT_FOUND.html.var
# ErrorDocument 405 /error/HTTP_METHOD_NOT_ALLOWED.html.var
# ErrorDocument 408 /error/HTTP_REQUEST_TIME_OUT.html.var
# ErrorDocument 410 /error/HTTP_GONE.html.var
# ErrorDocument 411 /error/HTTP_LENGTH_REQUIRED.html.var
# ErrorDocument 412 /error/HTTP_PRECONDITION_FAILED.html.var
# ErrorDocument 413 /error/HTTP_REQUEST_ENTITY_TOO_LARGE.html.var
# ErrorDocument 414 /error/HTTP_REQUEST_URI_TOO_LARGE.html.var
# ErrorDocument 415 /error/HTTP_SERVICE_UNAVAILABLE.html.var
# ErrorDocument 500 /error/HTTP_INTERNAL_SERVER_ERROR.html.var
# ErrorDocument 501 /error/HTTP_NOT_IMPLEMENTED.html.var
# ErrorDocument 502 /error/HTTP_BAD_GATEWAY.html.var
# ErrorDocument 503 /error/HTTP_SERVICE_UNAVAILABLE.html.var
# ErrorDocument 506 /error/HTTP_VARIANT_ALSO_VARIES.html.var


#
# The following directives modify normal HTTP response behavior to
# handle known problems with browser implementations.
#
BrowserMatch "Mozilla/2" nokeepalive
BrowserMatch "MSIE 4\.0b2;" nokeepalive downgrade-1.0 force-response-1.0
BrowserMatch "RealPlayer 4\.0" force-response-1.0
BrowserMatch "Java/1\.0" force-response-1.0
BrowserMatch "JDK/1\.0" force-response-1.0

#
# The following directive disables redirects on non-GET requests for
# a directory that does not include the trailing slash. This fixes a
# problem with Microsoft WebFolders which does not appropriately handle
# redirects for folders with DAV methods.
# Same deal with Apple's DAV filesystem.
#
BrowserMatch "Microsoft Data Access Internet Publishing Provider" redirect-carefully
BrowserMatch "^WebDrive" redirect-carefully
BrowserMatch "^WebDAVFS/1.[012]" redirect-carefully

#
# Allow server status reports generated by mod_status,
# with the URL of http://servername/server-status
# Change the ".example.com" to match your domain to enable.
#
#<Location /server-status>
# SetHandler server-status
# Order deny,allow
# Deny from all
# Allow from .example.com
#</Location>

#
# Allow remote server configuration reports, with the URL of
# http://servername/server-info (requires that mod_info.c be loaded).
# Change the ".example.com" to match your domain to enable.
#
#<Location /server-info>
# SetHandler server-info
# Order deny,allow
# Deny from all
# Allow from .example.com
#</Location>

#
# Proxy Server directives. Uncomment the following lines to
# enable the proxy server:
#
#<IfModule mod_proxy.c>
#ProxyRequests On
#
#<Proxy *>
# Order deny,allow
# Deny from all
# Allow from .example.com
#</Proxy>

#
# Enable/disable the handling of HTTP/1.1 "Via:" headers.
# ("Full" adds the server version; "Block" removes all outgoing Via: headers)
# Set to one of: Off | On | Full | Block
#
#ProxyVia On

#
# To enable the cache as well, edit and uncomment the following lines:
# (no cacheing without CacheRoot)
#
#CacheRoot "/usr/local/apache2/proxy"
#CacheSize 5
#CacheGcInterval 4
#CacheMaxExpire 24
#CacheLastModifiedFactor 0.1
#CacheDefaultExpire 1
#NoCache a-domain.com another-domain.edu joes.garage-sale.com

#</IfModule>
# End of proxy directives.

#
# Bring in additional module-specific configurations
#
<IfModule mod_ssl.c>
Include conf/ssl.conf
</IfModule>


### Section 3: Virtual Hosts
#
# VirtualHost: If you want to maintain multiple domains/hostnames on your
# machine you can setup VirtualHost containers for them. Most configurations
# use only name-based virtual hosts so the server doesn't need to worry about
# IP addresses. This is indicated by the asterisks in the directives below.
#
# Please see the documentation at
# <URL:http://httpd.apache.org/docs-2.0/vhosts/>
# for further details before you try to setup virtual hosts.
#
# You may use the command line option '-S' to verify your virtual host
# configuration.

#
# Use name-based virtual hosting.
#
NameVirtualHost * <------------------------ok!#を消しました

#
# VirtualHost example:
# Almost any Apache directive may go into a VirtualHost container.
# The first VirtualHost section is used for requests without a known
# server name.
#
<VirtualHost *> <---------?これでいいとおもうんですが・・
ServerAdmin master@xyz.com
DocumentRoot /home/user/public_html
ServerName xyz.com
ErrorLog logs/xyz.com-error_log
CustomLog logs/xyz.com-access_log common
</VirtualHost>


バーチャルホスト

No.6344 投稿時間:2002年11月10日(Sun) 15:28 投稿者名:OAK URL:

いくらなんでも自分で変更したあたりだけにしてくれませんか

> NameVirtualHost * <------------------------ok!#を消しました
> <VirtualHost *> <---------?これでいいとおもうんですが・・
> ServerAdmin master@xyz.com
> DocumentRoot /home/user/public_html
> ServerName xyz.com
> ErrorLog logs/xyz.com-error_log
> CustomLog logs/xyz.com-access_log common
> </VirtualHost>

バーチャルホストの話を先に。
<VirtualHost>で abc.com も作る必要があります。
したがって
<VirtualHost *>
ServerAdmin master@xyz.com
DocumentRoot /var/www/html
ServerName abc.com
ErrorLog logs/abc.com-error_log
CustomLog logs/abc.com-access_log common
</VirtualHost>

見たいな物を追加する。<VirtualHost> ~ </VirtualHost>が2組必要です。
今のアパッチは*でよいはずですが私のマニュアルだと、*でなく
サーバーのLANアドレスを書く事になっています。だめなら変更してください。
NameVirtualHost 192.168.0.100 <VirtualHost 192.168.0.100>という風に。


アクセス制限

No.6345 投稿時間:2002年11月10日(Sun) 16:48 投稿者名:OAK URL:

アクセス制限

> order allow,deny
> deny from all
> allow from 192.168.0
> <Files ".*">
> deny from all
> </Files>

192.168からの要求のみ許可、残りはだめの設定は order deny,allow
です(順序が逆)
Files ".*" こんな設定できましたっけ?

order deny,allow
deny from all
allow from 192.168.0
<Files ~"^\.">
Order allow,deny
Deny from all
Satisfy All
</Files>
こんな感じではなっかたですかね。忘れました。自分で調べて。
http://www.mikeneko.ne.jp/~lab/web/htaccess/ が詳しい。


解決しました!感激、ありがとうございました

No.6353 投稿時間:2002年11月11日(Mon) 04:57 投稿者名:リカ URL:

OAKさん、すみませんでした。
Apache設定ファイルを直接編集するのは初めてだったので、必要、不必要の判断ができなく、
とりあえず全部のせちゃいました。バーチャルホスト、アクセス制限ともできるようになりました。
ありがとうございました。


ApacheのversionUp時の設定保存

No.6331 投稿時間:2002年11月10日(Sun) 05:08 投稿者名:リカ URL:

ryujinさんのご指摘でhttp://www.ipa.go.jp/security/index.htmlを調べたらapache1.3.24では不正侵入されるとあったので、
心配性なリカはさっそく1.3.27の最新版をいれました。旧バージョンの設定保存&書きという気のきいた事を期待していたのですが、
やはり・・そこはLinuxでした。新しく表示されるindex.htmlがどこにあるのかわからないありさまです(再び涙)。
新しくいれたapacheに以前の設定を移行させるのってどうやるんでしょうか?
同じような経験があるwebmaster様がいらっしゃいましたら教えてください。よろしくお願いします。


これでいいのかな?

No.6334 投稿時間:2002年11月10日(Sun) 08:13 投稿者名:リカ URL:

ツールではらちがあかないので、意を決して設定ファイルを
直接編集する事にしました。/usr/local/apache/conf/httpd.confのDocumentRoot"/usr/local/apache/htdocs"→"/var/www/html"
ScriptAliaas /cgi-bin/"/usr/local/apache/cgi-bin"
→"/var/www/cgi-bin/"
とりあえずこの2箇所を書き換えたら元のHPがみえるようになったけど、これだけでいいのかな?
Apache設定のわかりやすいHPありましたら教えてください。


httpd.confは退避しておこう

No.6335 投稿時間:2002年11月10日(Sun) 09:58 投稿者名:ryujin URL:http://www.ryujin.info/

> ツールではらちがあかないので、意を決して設定ファイルを
> 直接編集する事にしました。/usr/local/apache/conf/httpd.confのDocumentRoot"/usr/local/apache/htdocs"→"/var/www/html"
> ScriptAliaas /cgi-bin/"/usr/local/apache/cgi-bin"
> →"/var/www/cgi-bin/"
> とりあえずこの2箇所を書き換えたら元のHPがみえるようになったけど、これだけでいいのかな?
いいと思いますよ。後はそちらの環境により変更するところがあるでしょう・・・

> Apache設定のわかりやすいHPありましたら教えてください。
httpd.confとredhatで検索しますと色々出てきますよ!
質問も出来るサイトとして
http://www.ayamizu.com/のサーバー構築日記
http://www.kozupon.com/apache/apache1.html


説明が具体的でわかりやすいです。

No.6354 投稿時間:2002年11月11日(Mon) 05:21 投稿者名:リカ URL:

ryujinさん、サイト紹介ありがとうございました。
特にkozuponの説明が具体的でわかりやすかったです。
やっぱり一般化ってのは説明される側の頭の中ですることで、
説明する側ですることじゃないですよね。


私も同じ攻撃を受けて困っています。

No.6356 投稿時間:2002年11月11日(Mon) 14:35 投稿者名:koko URL:

済みませんm(_ _)m便乗です。
私もこの攻撃で大変困った事が先日起こりました。
夜、8時くらいに連続で(7.8回)攻撃されていることが
ログを見てわかりました。その日は全然気がつかなかったのですが
良く見るとDICEが止まっていて全然アクセスが出来ない状態が丸1日ありました。
気がついたのは翌日でした。この攻撃は以前からありましたが、今回みたいに
連続でやられるとなぜかDICEが停止するみたいです。
ログを見てわかったのですが、だいたい夜中にやられています。
なんとかならないでしょうか?
宜しく、お願い致します。
私は、HTTPD 1.39fを使っております。


どちらかと言えばシステムかHTTPDが要因では?

No.6357 投稿時間:2002年11月11日(Mon) 14:54 投稿者名:APACHE URL:

> 済みませんm(_ _)m便乗です。
> 私もこの攻撃で大変困った事が先日起こりました。
> 夜、8時くらいに連続で(7.8回)攻撃されていることが
> ログを見てわかりました。その日は全然気がつかなかったのですが
> 良く見るとDICEが止まっていて全然アクセスが出来ない状態が丸1日ありました。
> 気がついたのは翌日でした。この攻撃は以前からありましたが、今回みたいに
> 連続でやられるとなぜかDICEが停止するみたいです。
> ログを見てわかったのですが、だいたい夜中にやられています。
> なんとかならないでしょうか?
> 宜しく、お願い致します。
> 私は、HTTPD 1.39fを使っております。
NimdaやCODEREDの攻撃とかはDICEには関係なくないか?
どちらかと言えばシステムかHTTPDが要因では?
ちなみにうちはOSwin2kでサービス登録にしてるけど問題ないよ
それ以前win98でやってたときも同じくDICEは止まらなかった...
ちなみにHTTPDはApache 1.3.27と2.0.43


|目次|掲示板|過去ログ目次|▲頁先頭|