Setup: when choosing sensor-only and entering server name, do not allow the hostname or IP address of the sensor itself #527

Closed
GoogleCodeExporter opened this Issue Mar 24, 2015 · 3 comments

Comments

Projects
None yet
1 participant
@GoogleCodeExporter
Setup: when choosing sensor-only and entering server name, do not allow the 
hostname or IP address of the sensor itself

Original issue reported on code.google.com by doug.bu...@gmail.com on 22 Apr 2014 at 10:23

@GoogleCodeExporter

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter Mar 24, 2015

                        # Did the user enter the hostname or IP address of the local box?
                        if [ "$SERVERNAME" = "$HOSTNAME" ]; then
                                zenity --error --text="That is the hostname of this box\!\r \
\r \
Since you chose a sensor-only installation, the Sguil server should be a 
separate box."
                        elif [ "$SERVERNAME" = "$IP" ]; then
                                zenity --error --text="That is the IP address of this box\!\r \
\r \
Since you chose a sensor-only installation, the Sguil server should be a 
separate box."
                        else

Original comment by doug.bu...@gmail.com on 16 Jul 2014 at 8:40

  • Added labels: ****
  • Removed labels: ****
                        # Did the user enter the hostname or IP address of the local box?
                        if [ "$SERVERNAME" = "$HOSTNAME" ]; then
                                zenity --error --text="That is the hostname of this box\!\r \
\r \
Since you chose a sensor-only installation, the Sguil server should be a 
separate box."
                        elif [ "$SERVERNAME" = "$IP" ]; then
                                zenity --error --text="That is the IP address of this box\!\r \
\r \
Since you chose a sensor-only installation, the Sguil server should be a 
separate box."
                        else

Original comment by doug.bu...@gmail.com on 16 Jul 2014 at 8:40

  • Added labels: ****
  • Removed labels: ****
@GoogleCodeExporter

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter Mar 24, 2015

Submitted for testing:
https://groups.google.com/d/topic/security-onion-testing/my5dRuEsvBQ/discussion

Original comment by doug.bu...@gmail.com on 16 Jul 2014 at 9:03

  • Added labels: ****
  • Removed labels: ****
Submitted for testing:
https://groups.google.com/d/topic/security-onion-testing/my5dRuEsvBQ/discussion

Original comment by doug.bu...@gmail.com on 16 Jul 2014 at 9:03

  • Added labels: ****
  • Removed labels: ****
@GoogleCodeExporter

This comment has been minimized.

Show comment
Hide comment
@GoogleCodeExporter

GoogleCodeExporter Mar 24, 2015

Published:
http://blog.securityonion.net/2014/07/new-securityonion-setup-package.html

Original comment by doug.bu...@gmail.com on 22 Jul 2014 at 2:34

  • Changed state: Verified
  • Added labels: ****
  • Removed labels: ****
Published:
http://blog.securityonion.net/2014/07/new-securityonion-setup-package.html

Original comment by doug.bu...@gmail.com on 22 Jul 2014 at 2:34

  • Changed state: Verified
  • Added labels: ****
  • Removed labels: ****
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment