nessus-tool.patch 2.9 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657
  1. Index: nessus-core/doc/nessusd.8.in
  2. --- nessus-core/doc/nessusd.8.in.orig 2004-10-19 17:21:05 +0200
  3. +++ nessus-core/doc/nessusd.8.in 2005-03-23 11:59:54 +0100
  4. @@ -183,7 +183,7 @@
  5. .SH USERS MANAGEMENT
  6. The utility nessus-adduser(8) creates new nessusd users. Each nessusd user
  7. -is attributed a "home", in @NESSUS_STATEDIR@/users/<username>. This home contains the following directories :
  8. +is attributed a "home", in @NESSUSD_STATEDIR@/users/<username>. This home contains the following directories :
  9. .IP auth/
  10. This directory contains the authentification information for this user. It might contain the file 'dname' if the user is authenticating using a certificate, or 'hash' (or 'passwd') if the user is authenticating using a password. The file 'hash' contains a MD5 hash of the user password, as well as a random seed. The file 'password' should contain the password in clear text.
  11. @@ -206,7 +206,7 @@
  12. When a user attempts to log in, nessusd first checks that the directory
  13. -@NESSUS_STATEDIR@/users/<username> exists, then hashes the password sent by the user with the random salt found in <username>/auth/hash, and compares it with the password hash stored in the same file. If the users authenticates using a certificate, then nessusd checks that the certificate has been signed by a recognized authority, and makes sure that the dname of the certificate shown by the user is the same as the one in <username>/dname.
  14. +@NESSUSD_STATEDIR@/users/<username> exists, then hashes the password sent by the user with the random salt found in <username>/auth/hash, and compares it with the password hash stored in the same file. If the users authenticates using a certificate, then nessusd checks that the certificate has been signed by a recognized authority, and makes sure that the dname of the certificate shown by the user is the same as the one in <username>/dname.
  15. To remove a given user, use the command nessus-rmuser(8).
  16. Index: nessus-core/nessus-mkcert.in
  17. --- nessus-core/nessus-mkcert.in.orig 2004-12-10 20:40:22 +0100
  18. +++ nessus-core/nessus-mkcert.in 2005-03-23 12:00:24 +0100
  19. @@ -407,31 +407,12 @@
  20. chmod a+r $CACERT $SRVCERT #cln $CLNCERT
  21. -
  22. -CF=@sysconfdir@/nessus/nessusd.conf
  23. -egrep -v '^ *(pem_password|cert_file|key_file|ca_file|force_pubkey_auth) *=' "$CF" > "$CF.tmp"
  24. -echo "#
  25. -# Added by nessus-mkcert
  26. -#
  27. -cert_file=$SRVCERT
  28. -key_file=$SRVKEY
  29. -ca_file=$CACERT
  30. -# If you decide to protect your private key with a password,
  31. -# uncomment and change next line
  32. -# pem_password=password
  33. -# If you want to force the use of a client certificate, uncomment next line
  34. -# force_pubkey_auth = yes" >> "$CF.tmp"
  35. -
  36. -
  37. -
  38. -
  39. test -z "$QUIET" && header
  40. if [ -s "$CACERT" -a -s "$CAKEY" -a -s "$SRVCERT" -a -s "$SRVKEY" ];
  41. then
  42. test -z "$QUIET" && echo "Congratulations. Your server certificate was properly created."
  43. - mv -f "$CF.tmp" "$CF"
  44. test -z "$QUIET" && {
  45. echo
  46. echo "$CF updated