httpd vs httpds

A potential client wishes to have a site made secure, but I have no knowledge of what is involved from a developers standpoint (I know how to use passwords and htaccess - he wants that, but also secure data transmission).

I think we are looking at using httpds -- can anyone supply some basic info on httpds, and/or how much is involved with setting it up?

Thanks!

>> can anyone supply some basic info on httpds

Start here -> http://www.modssl.org/

>> how much is involved with setting it up?

That depends. Your current setup might vary. One thing you need to aware is, if this client's site is configured as a vhost (name-based), and your default site currently doesn't have SSL enabled, you then need to make decision whether to implement SSL for your default site. If so, this client is better off to access his secure site via https://www.yourdefaultdomain.com/client/
If he wants https://www.client.com/, you must configure his vhost to use IP-based.

The cn (common name) for the cert MUST match the FQDN. You need to generate a cert for www.client.com. Also be aware that ONE cert for ONE FQDN per IP. That's why you need to use IP-based vhost configuration for multiple certs.