Something I noticed whilst trying to get the HTTPS filtering to work.. I noticed that the CA root cert that the Astaro creates uses the cryptic DB reference as the "friendly name" when the cert is created... for example, mine is "REF_IfWHWrKeXd" ... this may cause confusion with users as IE7 makes it real easy to check which cert is being used, and it reports this goofy name... please look into using the "real" friendly name when generating the certificate. Other examples of cases where these cryptic DB references are used are in the ASC config files generated by the ASG.. the IPSEC policies all use these cryptic names, as does the name of the connection itself that is saved in the ASC config .ini file. It looks really unpolished in a security product.
