Bastille v. Curses.pm

[steve saady]

I am having that problem "Could not load the 'Curses.pm' interface module." I am using HP's PERL 5.6.1. I even put Curses.pm in /opt/perl/lib/5.6.1. I am running this at the command line via ssh.
Is there a work around or a solution??

[Steven E. Protter]

Check the install state of perl with the swverify command.

It may need to be reinstalled.

SEP

[A. Clay Stephenson]

What are the permissions of the .pm file?

[Elena Leontieva]

I wonder if you already installed the module?
Elena.

[A. Clay Stephenson]

Also, the curses module requires compiler C; did you do all the install steps or simply copy in Curses.PM? If so, you haven't played by the rules.

[Elena Leontieva]

To install the module, you have to do the following:
cd /somedir
download the file to this dir
unzip/untar the file and a directory will be created that has the name of this module
cd to this module dir
perl MAkefile.PL
make
make test
make install

Elena.

[steve saady]

I have the file permissions below. SWverify said " 17 files had warnings during this operation".
I have GCC 3.2.3 installed.
I even downloaded it from CPAN and went through the compilation process.




-rwxr-xr-x 1 root sys 17013

[Tyler Easterling]

Hi

Bastille will first attempt to run it's Perl/Tk interface, if your DISPLAY is not set or you do not have Perl/TK installed the bastille script will attempt to use the Linux based Curses module. HP does not currently support this module so try the following:

# export DISPLAY=remoteipaddress:0.0
# bastille -x

If bastille reports that it could not find the Tk.pm then download the latest perl depot from software.hp.com and try again.

- Tyler

[steve saady]

Tyler -
Does that mean I need to run via x-windows and can nut run via command line?

# export DISPLAY=remoteipaddress:0.0
# bastille -x

I used those commands, and gut much further, but it crapped out saying:

couldn't connect to display "remoteipaddress:0.0"

at /opt/perl/lib/site_perl/5.6.1/PA-RISC1.1-thread-multi/Tk/MainWindow.pm line 55, line 3538.

MainWindow->new() at /opt/sec_mgmt/bastille/lib/Bastille_Tk.pm line 167

[Patrick Wallek]

Ahh...If you are trying to run via the command line then you are correct, this will most likely not work. As far as I know this does require X windows.

On your 'remoteipaddress' machine, you might try to make sure you do an 'xhost +' or whatever the equivalent is.

[Tyler Easterling]

Unfortunatly a full command line interface is not available now, it is on the futures list though. :) So yes the gui requires X to run.

A couple of thoughts:

The IP address of the machine that you would like to view the Bastille X based GUI on should have X running and should be accepting X based connections from the HP-UX machine that you are attempting to run Bastille from.

Try the following:

localhost> xhost +my_remote_ip_address


remotehost> export DISPLAY=localhost:0
remotehost> bastille -x

If that's all lined up with what you are doing then read on.

Are you "su"'ing from a regular user to root and then attempting to tunnel via ssh tunneling your X content? If the tunnel wasn't initiated by the sending uid then ssh will sometime refuse the x connection in weird ways.

Let me know how it goes.

- Tyler