comment on

an executable that I can deliver to users who don't have perl installed on their machines. The exe has to connect to a database and must contain a password

That sounds dubious. Is the database on their network or yours ?

If it's on their network, put the user/pass in a plain textfile that gets read by the executable. You really shouldn't care if it readable by the customer.

If it's on your network, the executable should talk to the database via a carefully crafted set of RPC APIs (SOAP, XMLRPC, JSON, REST, whatever) that use password-auth/ACLs/IPs/certificates as appropriate to secure the service. Even then, you can feel free to store those credentials on the client's disk separately to the executable... just make sure users are aware of the security issues associated with losing/sharing their credentials (and you should have policies to deal with those aspects).

It's a really bad idea to expose an RDBMS over the internet.

-David

In reply to Re: PAR only filters one of two copies of the script to be placed in the executable by erroneousBollock
in thread PAR only filters one of two copies of the script to be placed in the executable by atopolc

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.


good chemistry is complicated, and a little bit messy -LW
	PerlMonks