Client-serveur flow secure (http, smtp, pop, etc.)
Securing web pages (aka using SSL mode), allows webusers to:- know who's the owner of the visited website
- know that this owner really existed when the certificate was issued
- be sure the information transiting on this website is encrypted
- Do you have an authenticity logo for my website?
- Use SSL linux / openssl client
- Configure Apache to run under 128-bit encryption only
- Configure Apache for a 128-bit-guaranteed server certificate
- Use a SSL java client
- Configure IIS for a Wildcard or Multiple-Site certificate
- Configure a IIS6 website to make it accessible in HTTPS only
- Which version of OpenSSL to use?
- How to debug a SSL connection with OpenSSL?
- Activate SMTP TLS on Microsoft Exchange
- Activate POP3 or IMAP4 TLS on Microsoft Exchange
- Use Exchange with RPC over HTTPS
- Microsoft Office Communicator Web Access (CWA)
- I renewed / reissued my Thawte certificate and the trust logo is not displayed anymore?!
- Use Exchange for OWA
- Certificates compatible with SafeMashups
- Pfsense and chained certificates
- Windows Communication Foundation (WCF)
- Disable SSL renegociation on Apache
Last edited on 07/15/2011 13:25:04 --- [search]
