At 4:04 PM -0800 11/22/01, William X Walsh wrote:
>Thursday, Thursday, November 22, 2001, 1:57:56 PM, [EMAIL PROTECTED] wrote:
>
>
>>  2. Entrust moves to Dun and Bradstreet verification
>>  -------------------
>>  Entrust, our Web Certificate supplier, apologizes for
>>  recent verification problems that have been reported. 
>>  Entrust has recently modified its verification practices
>>  by engaging Dun & Bradstreet for the purposes of
>>  verification of identity. Ultimately this will result in
>>  improved verification times and a more customer-friendly
>>  process. However, this switch-over has caused some
>>  near-term disruptions to the service levels that you had
>>  come to expect. Faced with an onslaught of discontent,
>>  Entrust has investigated the problem, have taken back much
>>  of the verification internally, will be attempting to
>>  manage the hand-off process in such a way that service
>>  levels will be maintained and ultimately improve, and
>>  apologize for the recent troubles. Please let your
>>  friendly Tucows sales or customer service rep know if you
>>  have any problems as we will be monitoring this situation
>>  closely. It should also be noted that beyond Entrust's
>>  internal changes Tucows is also working with Entrust
>>  specifically to make changes to the verification process for
>>  our certificates. This effort will also be geared toward
>>  efficient, hassle-free issuing of the SSL certificates.
>
>Does this mean that Entrust is now requiring that all certificate
>holders must be registered with D&B to get a certificate?
>
>(I'll hold off on commenting further awaiting that clarification)

And what does that mean for non-businesses who want certs?

D

-- 
+---------------------+-----------------------------------------+
| [EMAIL PROTECTED]  | "Thou art the ruins of the noblest man  |
|  Derek J. Balling   |  That ever lived in the tide of times.  |
|                     |  Woe to the hand that shed this costly  |
|                     |  blood" - Julius Caesar Act 3, Scene 1  |
+---------------------+-----------------------------------------+

Reply via email to