1.
ftp://ftp.cerias.purdue.edu/pub/tools/unix/scanners/cops/



2. 기본사용법

# Usage: cops [-vx] [-c config file] [-s secure_dir] [architecture]



3. Cops 자세한 설치및 사용법



3-1. 소스구하기

3-2. 압축풀기

3-3. README.FIRST파일을 먼저 읽어본다.

3-4. makefile 알맞게 수정하기

3-4-1. chmod, test, mkdir, cp, cc, rm 실행파일들 위치를 which로 조회하여 맞추어 줄것..

3-4-2. pass.c 와 관련된 에러는 주석문을 읽어보고 처리할 것

(첫째행을 주석처리하고, 둘째와셋째를 풀어준다.)

vi makefile에서 다음의 행을...

# If fast crypt will work, comment the first CC line, uncomment

# the next two:

pass.chk: src/pass.c

#$(CC) $(CFLAGS) -o pass.chk src/pass.c $(BRAINDEADFLAGS)

$(CC) $(CFLAGS) -Dcrypt=fcrypt -DFCRYPT -o pass.chk src/pass.c \

src/crack-fcrypt.c src/crack-lib.c $(BRAINDEADFLAGS)

3-4-3. root.chk와 관련된 에러는 적당히 처리한다.

3-5. make 또는 make all

3-6. make install

make install실행시에 발생하는 에러중 pass.chk가 없어 make install이 되지않을 경우는

다음과 같이 해준다.

[root@www cops_104]# cd docs

[root@www docs]# cp pass.chk ../

[root@www docs]#

[root@www docs]#

[root@www docs]#

[root@www docs]# cd ..

[root@www cops_104]#

[root@www cops_104]#

[root@www cops_104]# make install

if /usr/bin/test ! -d sun ; then mkdir sun ; fi

/bin/cp home.chk user.chk pass.chk is_writable crc crc_check addto clearfiles filewriters members tilde is_able

chk_strings root.chk dev.chk cron.chk is_able.chk cops group.chk rc.chk passwd.chk ftp.chk crc.chk misc.chk suid.chk

kuang init_kuang reconfig res_diff yp_pass.chk bug.chk bug.chk.aix bug.chk.apollo bug.chk.dec bug.chk.next bug.chk.sgi

bug.chk.sun bug.chk.svr4 bug_cmp is_able.lst suid.stop crc_list sun



3-7. cops 실행파일을 열어서 적당히 다음과 같은 것을 설정해 준다.

3-7-1. echo, test, rm, cat, mail, date, chmod, awk, sed, mv, mkdir실행파일들의

위치를 which로 조회하여 맞추어준다.

3-7-2. SECURE와 SECURE_USERS의 위치를 맞추어준다.

######################

# Change these lines!

######################

SECURE=/home/manager/cops/cops_104

#SECURE=/usr/foo/bar

#SECURE=/home/manager/.secure

SECURE_USERS="manager@owner.co.kr"

######################



-- Change lines 93 and 94 in the "cops" shell file. They are originally:



SECURE=/usr/foo/bar

SECURE_USERS="foo@bar.edu"



SECURE should be the same directory as the directory that contains

the COPS programs, and SECURE_USERS should be your own login id,

or whomever you designate as the recipient of the output.



3-8. 자세한 실행방법 및 설치의 다양한 예

3-8-1. ./cops -v -s . -b cops_errs

3-8-2. ./cops -m user

3-8-3. ./cops -v output-file

3-8-4. 실행방법들

# Usage cops [-a architecture] [-b bit_bucket] [-s secure_dir] \

# [-m user] [-f filter_file] [-dxvV]

#

# -a specifies the architecure subdirectory you want to run in; you

# must run "make install" to install the appropriate binaries there

#

# -b specifies the "bit bucket", where all the error messages go to.

#

# -d will mail a report only if there have been changes since the

# last one. Only makes sense with the -m flag or by setting the

# MMAIL var below.

#

# -f specifies the cops filter file, which is used for filtering out

# extraneous warning message.

#

# -m tells cops to mail the output to the user specified

#

# -s tells cops where the secure directory is; mostly this is used by

# cops itself, when it is run with the -a flag; it will rerun itself

# with the -a flag's argument as an argument to this.

#

# -x prints out the version number (running out of letters! :-))

#

가장좋은방법--> # -[vV] are the verbose flags. Small "v" says print whatever program

# is running, when it is executed, in the output file; capital

# "V" says print everything to the screen.



가장좋은 방법은 "#./cops -V"로 모니터에서 결과를 바로 확인하는 방법...

[root@www cops_104]# ./cops -V

**** root.chk ****

**** dev.chk ****

**** is_able.chk ****

Warning! /etc/security is _World_ readable!

**** rc.chk ****

**** cron.chk ****

**** group.chk ****

**** home.chk ****

**** passwd.chk ****

**** user.chk ****

**** misc.chk ****