Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 3 subscribers
  • Views 655 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

The SSL v3.0 CBC (Poodle) vulnerability - webadmin can't restarted

thastu
Hi,
after change the httpd.conf file with "SSLProtocol all -SSLv2 -SSLv3"  cant able to restart the webadmin by using "/etc/init.d/httpd restart" as per the KB 121509.

If any one having solution for this issue kindly let me know.[:)]


This thread was automatically locked due to age.
  • 0
    UTM "firmware" version?

    Paste of the error message?
  • 0
    Tested is under 9.113, might work in other versions.  

    If the error appears like this:
    UTM9.113:/root # /etc/init.d/httpd restart                                                                               :: Stopping WebAdmin                                                                                      done
    :: Starting WebAdmintr: misaligned [:upper:] and/or [:lower:] construct
    /etc/init.d/httpd: line 40: [: =: unary operator expected
    /etc/init.d/httpd: line 56: [: =: unary operator expected
                                                                                                              done
    :: Restarting WebAdmin


    Then the following, when run as root, will create a new /etc/init.d/httpd.teched that should work:
    cp /etc/init.d/httpd /etc/init.d/httpd.teched && sed -i -e 's/[:upper:]/A-Z/; s/[:lower:]/a-z/' /etc/init.d/httpd.teched && diff /etc/init.d/httpd /etc/init.d/httpd.teched


    Expected output:
    39c39
         PRODUCT=$(awk -F\'  "\$2 ~ /ID/ {  print(\$4); };" /etc/product | tr A-Z a-z)


    Now running "/etc/init.d/httpd.teched restart" should successfully restart WebAdmin:
    UTM9.113:/root # /etc/init.d/httpd.teched restart
    :: Stopping WebAdmin                                                                                      done
    :: Starting WebAdmin                                                                                      done
    :: Restarting WebAdmin


    (The file dates from my local files indicate I last worked with this problem in May 2014, I was running 9.111 at the time.)

    Otherwise the version and error messages (and maybe logs) are needed. Don't overlook the possibility configuration errors (typos?) were introduced in the httpd.conf.