[Owasp-leaders] Customer Update: New Features With Your Managed PKI for SSL Account

Lucas Ferreira lucas at sapao.net
Sun Jun 6 21:10:03 EDT 2010


I agree. This "seal" business is quite controversial, and I would
rather stay away from it.

Regards,

Lucas

On Sat, Jun 5, 2010 at 01:07, Christian Heinrich
<christian.heinrich at owasp.org> wrote:
> James,
>
> I would prefer OWASP *not* to be associated with Verisign i.e.
> http://www.phreedom.org/blog/2009/verisign-and-responsible-disclosure/
>
> On Fri, Jun 4, 2010 at 11:38 PM, McGovern, James F. (P+C Technology)
> <James.McGovern at thehartford.com> wrote:
>> Is there merit in working with Verisign to further strengthen their offering
>> around the second bullet such that we can get consumer reports like ratings
>> and our name more visible? Maybe even create a spec such that other CAs that
>> follow in their path are consistent in approach?
>> ________________________________
>> From: VeriSign [mailto:updates at news.verisign.com]
>> Sent: Thursday, June 03, 2010 6:31 PM
>> To:  xxx
>> Subject: Customer Update: New Features With Your Managed PKI for SSL Account
>>
>> Dear  XXX ,
>>
>> VeriSign is pleased to announce that we have now taken your online security
>> and trust to a whole new level. Starting on July 15, 2010, we will be adding
>> new trust services with your existing certificates and to future purchases
>> at no additional cost.
>>
>> VeriSign® SSL Certificates will now come with:
>>
>> A new, enhanced VeriSign Trust™ Seal.*
>> VeriSign Seal-in-Search™: A feature that allows enabled browsers and
>> VeriSign partnered sites to recognize VeriSign trusted sites instantly and
>> display the VeriSign seal next to your web site link in search results. This
>> differentiates your link as a VeriSign trusted site and helps your web site
>> stand out in search results.*
>> Web site malware scanning: VeriSign performs a daily, non-invasive scan of
>> your externally-facing web pages for malicious code, so you can assure your
>> customers that your site is regularly monitored for their safety.*
>>
>> ************************************************************
>> This communication, including attachments, is for the exclusive use of
>> addressee and may contain proprietary, confidential and/or privileged
>> information.  If you are not the intended recipient, any use, copying,
>> disclosure, dissemination or distribution is strictly prohibited.  If you
>> are not the intended recipient, please notify the sender immediately by
>> return e-mail, delete this communication and destroy all copies.
>> ************************************************************
>>
>> _______________________________________________
>> OWASP-Leaders mailing list
>> OWASP-Leaders at lists.owasp.org
>> https://lists.owasp.org/mailman/listinfo/owasp-leaders
>>
>>
>
>
>
> --
> Regards,
> Christian Heinrich - http://www.owasp.org/index.php/user:cmlh
> OWASP "Google Hacking" Project Lead - http://sn.im/owasp_google_hacking
> _______________________________________________
> OWASP-Leaders mailing list
> OWASP-Leaders at lists.owasp.org
> https://lists.owasp.org/mailman/listinfo/owasp-leaders
>



-- 
Homo sapiens non urinat in ventum.


More information about the OWASP-Leaders mailing list