As promised, here's the announcement that went out:

<snip>
Subject: OpenSRS Live Reseller Update [certs] - 03/14/02

Greetings -

Please find following an update on OpenSRS.

We have made a number of modifications to the Web Certificate
registration process in the last while which should streamline
identity verification and certificate issuance (this is not the
end of our efforts so keep the feedback coming).

Renewals:
Renewals are now facilitated on the certificateregistration.com
website. The buy process is the same, the codes used are the
same, the process is the same except you now have the option to
select 'Renew your Web Certificate' after the code is entered.
If you recall the password that you created the previous year all
the data will be pre-populated. Assuming no changes to the
contact information all you will have to do is enter generate and
submit a new CSR (Certificate Signing Request). The company for
which the certificate is requested will still get a confirmation
call but there should be no new document faxing required.

Reminder Emails:
Both the Tech contact and the Authorization Contact for the
certificate are issued renewal reminder e-mails. These e-mails
direct the recipient to it's Tucows OpenSRS reseller to purchase
a renewal certificate.

Identity Verification:
Dunn & Bradstreet is now (and has been for the last couple
months) performing verification for the certificates. This
simplifies verification because in almost all cases there will be
no faxing of documentation required. If a company does not have a
D&B number it will be issued one as part of the verification
process (there is no cost for this, it is just a side-effect of
successful verification). There is a brief summary of the
verification process on the certs.tucows.com web-site at
https://certs.tucows.com/pdf/verification.pdf.

Same Tech and Auth Contact:
In the past there was much distress over the verification
required if the Technical and Authorization contact were the same
(namely third party verification). The third party verification
is no longer required. If your Tech and Auth contact are the same
and your organization employs less than 5 people the cert will be
issued without any additional verification. If your organization
employs more than 5 people, make sure you provide different names
as authorization and technical contact. (A technical or
authorization contact must be the name of a physical person and
not a department name).

Note:
Entrust has informed that there have been a recurring difficulty
encountered in the process. Namely make sure that the name of the
company for which the certificate is being requested is also the
name of the company that owns the domain name (Admin Contact in
OpenSRS whois). Please remember and/or remind your customers that
the organization attribute in this csr matches the organization
for which you are requesting a certificate (authorizing
organization) and is the organization that owns the domain name
for which you are requesting this certificate.

As always - thanks for your continued support of OpenSRS!

Thanks -

Darryl Green
Tucows/OpenSRS Certs Manager
</snip>

Charles Daminato
OpenSRS Product Manager
Tucows Inc. - [EMAIL PROTECTED]

> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Charles Daminato
> Sent: March 18, 2002 7:17 PM
> To: Mike Allen
> Cc: Kirk Fletcher; [EMAIL PROTECTED]
> Subject: Re: Entrust cert renewals
>
>
> I'm actually going to let Darryl take this (Mr. Cert), but you are
> "renewing" in a sense, but you have to replace the cert since the
> technology has the expiry built into the cert itself (so your customer's
> browsers will give an ugly "THIS CERT HAS EXPIRED" message which makes you
> look bad)
>
> afaik if you already own the cert, you've gone through the verification
> process, so it's simpler.  There was an announcement sent to all "cert"
> enabled resellers; I'll dig it up and repost tomorrow.
>
> Charles Daminato
> TUCOWS Product Manager
> [EMAIL PROTECTED]
>
> On Mon, 18 Mar 2002, Mike Allen wrote:
>
> > I had seen a post on this list just a few days ago stating that
> their was no
> > such thing as a "Renewal" for certificates and that you had to buy a new
> > certificate. Same, process as buying a new one.... I am sure
> Charles will
> > reply shortly... ;)
> >
> > Mike Allen, 4CheapDomains.Net
> > [EMAIL PROTECTED]
> > http://www.4CheapDomains.Net
> > (812) 275-8425 - Office
> > (815) 364-1278 - Fax
> >
> > *** DeerSearch.Com   -   Get Targeted Traffic to your site for
> as little as
> > 1 penny per visit!
> > http://www.DeerSearch.Com          Is currently paying $6.00
> per sale to all
> > affiliates!
> >
> > *** PWDOnLine.Com - Looking for someone to design your web-site? Here we
> > are!
> > http://www.PwdOnline.Com
> >
> > *** ProNetworks.Biz - Get a DSL, SDSL or T-Span network for well below
> > others prices!
> > http://www.ProNetworks.Biz
> > ----- Original Message -----
> > From: "Kirk Fletcher" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Monday, March 18, 2002 3:22 PM
> > Subject: Entrust cert renewals
> >
> >
> > > Hey all,
> > >
> > > When we started selling certs, we were advised that a
> > > renewal process would be in place before the time came
> > > - so that we could handle renewals (and the customer
> > > would remain ours).  There was also an indication that
> > > the wholesale pricing for renewals was to be competitive.
> > >
> > > Well... the time is getting closer.  How do we handle
> > > renewals?  What's the charge going to be?  Is there any
> > > further checking to be done for renewals (eg, checking
> > > that the company still exists), or are renewals straight
> > > forward since all the checking was done when the cert
> > > was purchased?  If its a simple process, then are the
> > > renewals cheaper than new certs?
> > >
> > > Cheers,
> > > Kirk Fletcher
> > >
> > >
> > >
> >
> >
>

Reply via email to