comment on

First notice that my solution need a higher development effort than some other listed here. I would recommend to create the web app on an other server for security reasons. You should have a look at the SSL modules on CPAN to pass the UNIX command to the target server.

I would authenticate the user to the web app with CGI::session and use an PK system to authenticate the web-app to the target server. Eventually jail the account you are using on the target server. Keep the validity time of the cookies of CGI::session short to avoid session theft as far as possible.

Once the user is authenticated I would prepare the UNIX command on the web-app server and pass it to the UNIX server with SSH. If you build a good system (i.e. PERL best practice!) you will be able to reuse the web-app for several UNIX servers.

PS: Never assume a user will log out. Keep the validity of the session short. I use for example 10 minutes for a login screen.

The best medicine against depression is a cold beer!

In reply to Re^3: Cross-platform GUI for UNIX based scripts by Zzenmonk
in thread Cross-platform GUI for UNIX based scripts by Anonymous Monk

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


"be consistent"
	PerlMonks