Re: March towards 1.2.0

AJ,

Thanks for you vote on CAcert. Someone in IRC also mentioned CAcert. So i
will go that route. I will request the cert this weekend, and install it
when i get it back. I will also configure Apache to use ajp for the jboss
hudson server. I am going to request a wild-card cert. That way we can use
it for multiple services. Unless there is a reason not to do this i will
just request one for hudson.phpeclise.??? That brings up the question. Now
that we have the .com domain, which one do we want to use? .net/.de/.com?

I guess i will need to know that as well.

Many people know the site as either .net or .de. But this is a new service,
so the links can point to .com. Just throwing this out there for comment.
And again if i don't hear anything back i will just use .com.

Thanks again.

> Hi Ed,
>
> There's also CAcert - http://www.cacert.org/. It's a free cert provider
>
> Cheers,
> AJ
>
> On Sep 15, 2007, at 1:40 PM, Edward Mann wrote:
>
>> Team,
>>
>> As we march towards our 1.2.0 release, there are new services that are
>> now available to our community. However there are some things that
>> need
>> input from those that are involved in the project. Below are a few
>> things that i have in my que to work on, and i would like peoples
>> input.
>>
>> Site Certificate:
>>
>> The new build system is online and uses SSL for administrative work. I
>> have put a temp cert on the machine, but was looking at putting a cert
>> that is signed by an authority that is in a majority of the
>> browsers. I
>> have some options.
>> 	a. Godaddy.com will give an open source project a 1 year certificate
>> for free. They say no strings attached, so that sounds promising. The
>> only problem that i see is we would need to renew the cert every year.
>> But not bad for free.
>> 	b. Sign the cert ourselves and use that. The issue with this is
>> that it
>> will be an annoyance to users with a prompt about the authenticity of
>> the cert. But we can make it last allot longer.
>> 	c. Purchase a cert. The disadvantage of this should be obvious. But
>> this is an option.
>>
>> We are also planing to migrate to Trac, and there may be parts of that
>> service that we would want to put behind ssl. So doing a wildcard Cert
>> may be something that we would want to do.
>>
>> That is all i have discovered for Certificate signing and usage. If
>> anyone has anything more to add or other services that are available
>> please let me know.
>>
>> If i don't hear back from anyone i will just decide on something
>> myself.
>>
>> Thanks
>>
>>
>> ----------------------------------------------------------------------
>> ---
>> This SF.net email is sponsored by: Microsoft
>> Defy all challenges. Microsoft(R) Visual Studio 2005.
>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>> _______________________________________________
>> Phpeclipse-devel mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/phpeclipse-devel
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Phpeclipse-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/phpeclipse-devel
>



-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/