I think it would be good that we get a signed certificate, not doing so makes
Open64 look like a Podunk project, which it is not.
It only costs several hundred dollars a year and I would be happy to contribute
$50 a year to help make this happen.
Note that Open64 appears to be a SPI member project:
http://www.spi-inc.org/projects/open64/
and
http://www.spi-inc.org/donations
discusses how donations to SPI can be steered to member projects. Also I’ll
lobby my company to do so.
Doug
From: Aida Rivas [mailto:open64ri...@yahoo.com]
Sent: Thursday, June 23, 2011 2:12 PM
To: Aida Rivas; Open64-devel@lists.sourceforge.net
Subject: [Open64-devel] SSL Certificate: Open64.net
Hello Everyone
A couple of developers have sent email wanting to understand why the following
warning,
• SSL certificate can’t be verified when accessing https://bugs.open64.net/
is generated when you're going to this website, https://bugs.open64.net/
So here’s the root cause
• Root cause: The open64.net<http://open64.net/> website has been
using a self-signed certificate since the beginning
OSG would like to let you know that Open64 certificate is self-signed, and it's
safe to ignore the warning.
Kind regards
OSG
------------------------------------------------------------------------------
Simplify data backup and recovery for your virtual environment with vRanger.
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Data protection magic?
Nope - It's vRanger. Get your free trial download today.
http://p.sf.net/sfu/quest-sfdev2dev
_______________________________________________
Open64-devel mailing list
Open64-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/open64-devel
