eCart Security

I've used eCart before, but this is the first time I have used it with paypal pro. It seems to be connecting fine to the sandbox. However I have some security concerns.

1. I notice that some pages contain all the API user, password, signature in them - and these are in the public part of the site (eg checkout.php). Is this safe? Surely if someone downloads that page or uses a tool like 'Site Import', they'll have the api access details?

2. As my other eCart sites were just paypal std, I had no need for SSL. But I'll need to add SSL for the pro integration, which is fine. But as an SSL novice (my host will install for me) - do I need to place all the https required pages in a separate folder from the non ssl files. And do I need to put all ssl assets (images, css, javascript, webassist files etc etc) in the same folder as the SSL files. Or will I get a 'This page contains both secure and non secure......' warning if I don't.

1) Those details are in the php source code, the only way someone could download that information is by gaining FTP access to the server.

site import will only download the browser source, not the raw php code.

2) This depends on how your host configures the server. Some hosts set it up so that the SSL pages have their own directory, others dont.

the 'This page contains both secure and non secure......' error happens if you Fully Qualified links to assets that use http protocol, for example:
<img src="http://mydomain/images/image.jpg" />

if the link is relative link:
<img src="images/image.jpg" />

you wont get that error.

Thanks Jason,

Once the site is live all ftp & sftp/ssh will be disabled as they'll no longer be needed - so as long as the php code is safe (I did look at the live pages source code and it was fine, as you say).

The host will provide a full SSL using domain.com, not as a subdomain or specific folder.

And all the links are relative links.

So the only precaution would be to use .htaccess to prevent the secure pages from being viewed as non ssl. Or is that not necessary?

Many thanks for your response(s).

yes, you should make sure the checkout pages cannot be accessed by the non ssl address.